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 with clear trigger terms, explicit 'when to use' guidance, and strong distinctiveness through its specificity to the claude-code-plugins two-catalog system. The main weakness is that the capability descriptions could be more concrete — 'manages updates' and 'handles distribution' are somewhat vague about the actual operations performed.
Suggestions
Replace vague verbs like 'manages' and 'handles' with specific actions, e.g., 'adds new plugin entries to marketplace.json, updates version numbers, generates distribution metadata'.
| 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). Has explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'marketplace update', 'sync catalog', 'add to marketplace', plus domain-specific terms like 'marketplace.json' and 'plugin distribution'. Good coverage of likely user phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specific to 'claude-code-plugins two-catalog system' with unique triggers like 'marketplace.json' and 'sync catalog'. 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 thorough, actionable guidance for managing a two-catalog marketplace system with good workflow sequencing and validation checkpoints. However, it is significantly bloated with redundant sections (trigger keywords, automation capabilities list, output format template, narrative examples) that don't add actionable value. Trimming the padding and deduplicating repeated sync/validation instructions would substantially improve token efficiency.
Suggestions
Remove the 'Trigger Keywords', 'Automation', and 'Output Format' sections — these describe Claude's behavior rather than providing actionable instructions, and Claude can infer appropriate triggers and output formatting.
Consolidate the duplicate sync validation steps (sections 2-3 and the full 'Sync Process' section) into a single authoritative workflow.
Replace the narrative 'Examples' section with a single concise example showing input→action→validation rather than three examples that all say 'I automatically' do steps already documented above.
Consider extracting the schema definitions and troubleshooting into referenced files to improve progressive disclosure for this length of content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Significant verbosity throughout. The 'Trigger Keywords' section, 'Automation' section listing what 'I can do', the 'Output Format' section with a mock report, and the 'Examples' section describing what 'I automatically' do are all padding. The 'Repository-Specific Features' section restates what's already clear. Many sections repeat information (e.g., sync validation appears in both section 3 and the Sync Process section). The skill could be cut by 50%+ without losing actionable content. | 1 / 3 |
Actionability | Provides concrete, executable bash commands and JSON schemas throughout. The sync process, validation commands (jq), git operations, and JSON entry formats are all copy-paste ready. Schema definitions with required/optional fields are specific and complete. | 3 / 3 |
Workflow Clarity | The sync process is clearly sequenced with explicit validation checkpoints: backup → run sync → validate JSON → check diff → commit. The version update workflow includes validation steps. Error recovery is addressed in the 'Common Issues & Fixes' section with specific diagnostic commands. | 3 / 3 |
Progressive Disclosure | Content is organized into logical sections with headers, but it's monolithic — everything is inline in one file with no references to external documentation. The schema details, troubleshooting, and examples could be split out. For a skill of this length (~200 lines), some content separation would improve navigability. | 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
13d35b8
- 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.