tessl install https://github.com/softaworks/agent-toolkit --skill plugin-forgegithub.com/softaworks/agent-toolkit
Create and manage Claude Code plugins with proper structure, manifests, and marketplace integration. Use when creating plugins for a marketplace, adding plugin components (commands, agents, hooks), bumping plugin versions, or working with plugin.json/marketplace.json manifests.
Average Score
93%
Content
88%
Description
100%
Generated
Validations
Total score
14/16| Criteria | Score |
|---|---|
skill_md_line_count SKILL.md line count is 225 (<= 500) | |
frontmatter_valid YAML frontmatter is valid | |
name_field 'name' field is valid: 'plugin-forge' | |
description_field 'description' field is valid (278 chars) | |
description_voice 'description' uses third person voice | |
description_trigger_hint Description includes an explicit trigger hint | |
compatibility_field 'compatibility' field not present (optional) | |
allowed_tools_field 'allowed-tools' field not present (optional) | |
metadata_version 'metadata' field is not a dictionary | |
metadata_field 'metadata' field not present (optional) | |
license_field 'license' field is missing | |
frontmatter_unknown_keys No unknown frontmatter keys found | |
body_present SKILL.md body is present | |
body_examples Examples detected (code fence or 'Example' wording) | |
body_output_format Output/return/format terms detected | |
body_steps Step-by-step structure detected (ordered list) |
Content
Suggestions 2
Total score
11/12| Dimension | Score |
|---|---|
conciseness Content is lean and efficient, using tables and code blocks without unnecessary explanation. Assumes Claude understands plugin concepts, versioning, and directory structures without over-explaining. | 3/3 |
actionability Provides fully executable bash commands, complete JSON examples, and specific file paths. The create_plugin.py and bump_version.py commands are copy-paste ready with all required flags documented. | 3/3 |
workflow_clarity Development workflow has clear numbered steps, but lacks validation checkpoints. No verification step after creating structure, no validation after updating manifests, and the testing workflow doesn't include a 'verify installation succeeded' step. | 2/3 |
progressive_disclosure Excellent structure with quick start at top, detailed workflows in middle, and clear references table at bottom pointing to one-level-deep documentation files. Navigation is well-signaled with tables for components, references, and scripts. | 3/3 |
Suggestions
Add validation checkpoint after step 3 (Register in Marketplace): e.g., 'Validate JSON: python -m json.tool marketplace.json'
Include verification step in local testing workflow: 'Verify installation: /plugin list should show plugin-name@marketplace-name'
Overall Assessment
This is a well-structured, actionable skill that efficiently covers plugin creation and management. The content is appropriately concise with executable examples and good progressive disclosure through reference tables. The main weakness is the lack of explicit validation steps in workflows, particularly for manifest updates and plugin installation verification.
Description
Total score
12/12| Dimension | Score |
|---|---|
specificity Lists multiple specific concrete actions: 'Create and manage Claude Code plugins', 'adding plugin components (commands, agents, hooks)', 'bumping plugin versions', 'working with plugin.json/marketplace.json manifests'. | 3/3 |
completeness Clearly answers both what ('Create and manage Claude Code plugins with proper structure, manifests, and marketplace integration') and when ('Use when creating plugins for a marketplace, adding plugin components...'). | 3/3 |
trigger_term_quality Includes natural keywords users would say: 'plugins', 'marketplace', 'commands', 'agents', 'hooks', 'plugin versions', 'plugin.json', 'marketplace.json', 'manifests'. Good coverage of domain-specific terms. | 3/3 |
distinctiveness_conflict_risk Very specific niche targeting Claude Code plugins with distinct triggers like 'plugin.json', 'marketplace.json', 'plugin components'. Unlikely to conflict with general coding or documentation skills. | 3/3 |
Overall Assessment
This is a well-crafted skill description that excels across all dimensions. It provides specific actions, includes natural trigger terms users would actually use, explicitly states both what the skill does and when to use it, and occupies a clear niche that won't conflict with other skills.