engineer-plugin-marketplace

Design AI-IDE plugin marketplaces - requirements, host-specific payloads, local dogfood, release sync, and validation. Use when the user wants to create or publish a plugin marketplace.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%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.

A tight, well-structured instruction skill with an excellent evidence-first and validation-gated workflow. It could improve actionability with concrete build/validate commands and split more detail into reference files.

Suggestions

Add a small "Quick start" block with concrete build/validate commands (e.g. a script invocation or CLI snippet) so the most common operations are copy-paste ready rather than described.

Move the detailed marketplace-contract field lists and packaging-transform spec into a references file (e.g. references/marketplace-contract.md) and link to it, keeping SKILL.md as a concise overview.

Include a single concrete example manifest snippet (e.g. a minimal marketplace.json or plugin manifest) inline to ground the contract description.

Dimension	Reasoning	Score
Conciseness	Lean, dense instruction prose that assumes Claude's competence—no padding, no explaining what a plugin is—every section earns its tokens.	5 / 5
Actionability	Gives concrete, enumerated steps with specifics (e.g. "MCP handshake smoke: initialize and tools/list", "<name>-local", "isolated host homes"), but offers no executable commands or scripts for build/sync/validate, leaving some steps as guidance rather than copy-paste actions.	4 / 5
Workflow Clarity	The Workflow is a clearly numbered 6-step sequence with explicit validation gates (step 6 enumerates schema/path validation, stale-rebuild failure, byte-determinism, install smoke, MCP/hook smoke, cache refresh), satisfying the destructive/batch feedback-loop requirement.	5 / 5
Progressive Disclosure	Well-organized overview sections with a clearly signaled one-level reference to references/related-skills.md, but most detail (catalog contract, transforms, validation) is inlined in SKILL.md rather than split into separate reference files.	4 / 5
	Total	18 / 20 Passed

Description

92%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.

A strong, concrete description that names the domain plus several specific capabilities and includes an explicit "Use when" trigger. Minor room for more trigger-term synonyms, but it is clearly distinct from sibling skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete marketplace actions—"requirements, host-specific payloads, local dogfood, release sync, and validation"—covering the domain comprehensively rather than with a single generic verb.	5 / 5
Completeness	Clearly answers both what (designing marketplace requirements, payloads, sync, dogfood, validation) and when ("Use when the user wants to create or publish a plugin marketplace") with an explicit trigger clause.	5 / 5
Trigger Term Quality	Natural terms like "create or publish a plugin marketplace" map to likely user phrasings, but it lacks synonyms/variants (e.g. "catalog", "distribute", "host payload") users might also say.	4 / 5
Distinctiveness Conflict Risk	Scoped to marketplace-level distribution and explicitly routed away from the single-plugin skill, giving it a distinct niche with minimal overlap risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: korchasa/flowai-plugins
Path: plugins/flowai-engineering/skills/engineer-plugin-marketplace/SKILL.md
Commit: ad81ae6

Reviewed: 8 hours 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.