Name: marqeta
Rating: 62.4 (1 reviews)
Author: membranedev

marqeta

Marqeta integration. Manage data, records, and automate workflows. Use when the user wants to interact with Marqeta data.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/marqeta/SKILL.md

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a tightly actionable Membrane/CLI integration guide with executable commands and a real state-machine feedback loop for connection setup. Its main weaknesses are a padded marketing intro and a slightly broken step labeling ("Step 2" with no Step 1/2 labels) that keeps workflow clarity just short of excellent.

Suggestions

Trim the opening marketing paragraph to one factual line about what Marqeta is, removing "modern", "innovative", and "real-time insights" filler.

Fix the step references: either relabel the connect/search/run sections as an explicit numbered Step 1→2→3 sequence or remove the dangling "Step 2" mentions so the workflow is self-consistent.

Consider moving the detailed connection state-machine and the Marqeta object catalog into a references file, leaving SKILL.md as a concise overview pointing to it.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean CLI commands and a flag table, but the opening marketing paragraph ("modern card issuing platform... innovative payment solutions... real-time insights") and a few phrasings ("so you can focus on the integration logic rather than auth plumbing") are mild over-explanation that could be trimmed, fitting the efficient-with-minor-padded-instances anchor.	4 / 5
Actionability	It provides copy-paste-ready, fully executable commands across the common cases (install, login, connection ensure/get, action list/run, proxy) plus a complete proxy flag table, matching the fully-executable anchor with common cases covered.	5 / 5
Workflow Clarity	The connection flow has an explicit state-machine feedback loop (poll, branch on READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, act, re-poll), but the "Step 2" references have no matching labeled steps and the overall connect→search→run sequence is not packaged as one numbered checklist, leaving minor gaps.	4 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-organized into clear sections with no nested references (a plus), but the detailed connection state-machine and the object catalog are fully inline with no offloading to reference files, which is a minor organization gap.	4 / 5
	Total	17 / 20 Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description names a distinct brand with an explicit "Use when" clause, giving good completeness and low conflict risk, but its actions are generic and its trigger terms lack synonyms or concrete Marqeta object names. Tightening the what into concrete capabilities (card issuing, funding sources, transactions) would raise specificity and trigger coverage.

Suggestions

Replace the generic "Manage data, records, and automate workflows" with concrete Marqeta capabilities such as issuing cards, managing funding sources and transactions, and handling webhooks.

Add natural trigger terms beyond the brand name, e.g. "Use when the user wants to issue cards, manage funding sources, view transactions, or configure Marqeta card programs."

Keep the explicit "Use when..." clause but make the trigger scenarios more specific to Marqeta objects to improve completeness toward a 5.

Dimension	Reasoning	Score
Specificity	Names the Marqeta domain and lists a few actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete Marqeta-specific operations (cards, funding sources, transactions), matching the 1-2 concrete-but-not-comprehensive anchor.	3 / 5
Completeness	It provides a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Marqeta data"), but the when is generic and the what not fully specific, so it has both but the when could be more concrete rather than answering both explicitly with concrete triggers.	4 / 5
Trigger Term Quality	The trigger relies on the brand name "Marqeta" plus "interact with Marqeta data", giving a relevant keyword but missing common variations, synonyms, or concrete object terms users would say, fitting the some-relevant-keywords anchor rather than comprehensive coverage.	3 / 5
Distinctiveness Conflict Risk	Naming the specific brand "Marqeta" creates a clear niche with distinct, brand-specific triggers unlikely to fire for unrelated skills, matching the clear-niche anchor.	5 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/marqeta/SKILL.md
Commit: f484c82

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.