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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill marketplace-manager84
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 well-crafted description that excels at completeness and distinctiveness by clearly specifying both the actions and when to use the skill, while anchoring to a specific system (claude-code-plugins). The main weakness is that the capability descriptions could be more concrete about what specific operations are performed during catalog management.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (marketplace catalog) and some actions (manages updates, syncs, handles distribution), but lacks comprehensive detail about what specific operations are performed beyond general verbs. | 2 / 3 |
Completeness | Clearly answers both what (manages 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', plus technical terms like 'marketplace.json' and 'plugin distribution' that are contextually appropriate. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific scope: 'claude-code-plugins two-catalog system', 'marketplace.json', and marketplace-specific triggers make it unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable guidance for marketplace management with executable commands and clear workflows. However, it's overly verbose with redundant sections (Automation, Examples at the end repeat earlier content) and could benefit from splitting detailed reference material into separate files. The core workflow documentation is strong with proper validation steps.
Suggestions
Remove the 'Automation' section - it restates capabilities already demonstrated in the workflows
Move the detailed schema definitions and 'Common Issues & Fixes' to separate reference files (e.g., SCHEMA.md, TROUBLESHOOTING.md)
Consolidate the 'Examples' section into the main task sections rather than repeating at the end
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains useful information but is verbose in places. The ASCII diagram for the two-catalog system is helpful, but sections like 'Automation' and 'I can automatically' list capabilities Claude already understands from context. The output format template adds bulk without being essential. | 2 / 3 |
Actionability | Provides fully executable commands and JSON examples throughout. The sync process, validation commands, and schema definitions are copy-paste ready with specific jq queries and npm commands. | 3 / 3 |
Workflow Clarity | The sync process section provides clear numbered steps with explicit validation checkpoints (backup, run sync, validate output, check diff, commit). The 'Common Issues & Fixes' section provides error recovery guidance. | 3 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is in one monolithic file. The schema definitions, common issues, and examples could be split into separate reference files. No external file references are provided. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
- 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.