marketplace-manager
Automatically manages marketplace catalog updates, syncs marketplace.json, and handles plugin distribution when user mentions marketplace update, sync catalog, or add to marketplace. Specific to claude-code-plugins two-catalog system.
91
76%
Does it follow best practices?
Impact
93%
1.60xAverage score across 12 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/examples/skills-powerkit/skills/marketplace-manager/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its niche domain, provides explicit trigger terms, and answers both what and when. The main weakness is that the specific actions could be more concrete—terms like 'manages' and 'handles' are somewhat vague compared to listing exact operations. The scoping to the 'claude-code-plugins two-catalog system' is excellent for distinctiveness.
Suggestions
Replace vague verbs like 'manages' and 'handles' with more specific actions, e.g., 'adds new plugins to marketplace.json, updates version entries, generates distribution manifests, and syncs the two-catalog system'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (marketplace catalog) and some actions (manages updates, syncs marketplace.json, handles plugin distribution), but the actions are somewhat vague—'manages updates' and 'handles distribution' lack concrete detail about what specific operations are performed. | 2 / 3 |
Completeness | Clearly answers both 'what' (manages marketplace catalog updates, syncs marketplace.json, handles plugin distribution) and 'when' (when user mentions marketplace update, sync catalog, or add to marketplace), with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'marketplace update', 'sync catalog', 'add to marketplace', 'marketplace.json', and 'plugin distribution'. These cover the likely phrases a user would use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive—references a specific system ('claude-code-plugins two-catalog system'), specific file (marketplace.json), and a narrow domain (marketplace catalog management). Very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, concrete guidance with good workflow sequencing and validation checkpoints for marketplace management. However, it is significantly bloated with redundant content—sync validation appears in at least three places, the examples section restates earlier content, and sections like 'Automation' and 'Output Format' add little value. The document would benefit from aggressive deduplication and splitting reference material into separate files.
Suggestions
Eliminate redundancy by consolidating sync validation into a single section and referencing it from other workflows instead of repeating the same jq/git commands.
Remove the 'Automation' section (just a summary of what's already covered) and the 'Trigger Keywords' section (not actionable for Claude).
Move the marketplace schema, valid categories list, and common issues into separate reference files (e.g., SCHEMA.md, TROUBLESHOOTING.md) and link to them from the main skill.
Remove the 'Output Format' template—it's prescriptive formatting that doesn't add actionable guidance for the actual marketplace management tasks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Significantly verbose with substantial redundancy. The sync validation steps are repeated across sections 2, 3, and the 'Sync Process' section. The 'Trigger Keywords' section, 'Automation' summary, and 'Output Format' template add tokens without actionable value. The 'Examples' section at the end just restates what was already covered. The ASCII diagram for the two-catalog system, while helpful, is followed by redundant explanations of the same concept. | 1 / 3 |
Actionability | Provides fully executable bash commands and complete JSON examples throughout. The sync commands, validation steps, jq queries, and git operations are all copy-paste ready. The marketplace schema with required/optional fields is concrete and specific. | 3 / 3 |
Workflow Clarity | The Sync Process section has a clear 5-step sequence with explicit validation (jq empty, plugin count check, git diff) and a backup step before destructive operations. The 'Update Plugin Version' workflow includes validation via git diff. Common Issues section provides error recovery paths. | 3 / 3 |
Progressive Disclosure | Content is organized into clear sections with headers, but it's a monolithic document that could benefit from splitting the schema reference, common issues, and valid categories into separate files. At ~200 lines, the inline content is heavy for a SKILL.md overview. No references to external files for detailed content. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Commit
805deb2
- Reviewed
Table of Contents
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.