propose-forge-improvement
Propose improvements or new components for Product Forge
59
42%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/claude-code-dev/skills/propose-forge-improvement/SKILL.mdQuality
Discovery
7%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 description is severely underdeveloped and would be nearly impossible for Claude to correctly select from a pool of skills. It lacks specific actions, natural trigger terms, and any guidance on when to use it. The only distinguishing element is the product name 'Product Forge'.
Suggestions
Add specific concrete actions like 'Analyzes existing Product Forge architecture, suggests feature enhancements, designs new UI components, proposes API improvements'
Include a 'Use when...' clause with trigger terms such as 'Use when the user asks about Product Forge enhancements, feature ideas, component design, or roadmap suggestions'
Add natural keywords users might say: 'Product Forge features', 'improve Product Forge', 'new functionality', 'enhancement ideas', 'component suggestions'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('propose improvements or new components') without listing any concrete actions. It doesn't specify what kinds of improvements, what components, or what actions Claude would take. | 1 / 3 |
Completeness | The description weakly addresses 'what' (propose improvements) but completely lacks any 'when' guidance. There is no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only potential trigger term is 'Product Forge' which is a proper noun/product name. There are no natural keywords users would say like 'enhance', 'feature request', 'roadmap', or specific component types. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Product Forge' as a specific product name provides some distinctiveness, but 'propose improvements or new components' is generic enough to potentially conflict with other product development or ideation skills. | 2 / 3 |
Total | 5 / 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 is a well-structured command skill with strong actionability and clear workflow sequencing. The execution instructions are concrete and the decision flow is explicit. The main weakness is moderate verbosity in the proposal templates which could be more concise, and the inline templates make the document longer than necessary.
Suggestions
Consider moving the detailed proposal templates to a separate TEMPLATES.md file and referencing them, reducing the main skill length
Condense the proposal template examples - show one complete example and note variations rather than two full templates
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some verbose sections like the full markdown proposal templates that could be condensed. The decision flow diagram and tables add structure but some explanatory text is redundant. | 2 / 3 |
Actionability | Provides concrete, executable guidance with specific bash commands, clear markdown templates for proposals, and explicit file paths. The step-by-step execution instructions are copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 6-step sequence with explicit decision points, a visual decision flow diagram, and numbered next steps. The workflow handles both improvement and new component paths with clear branching logic. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is somewhat monolithic with lengthy proposal templates inline. The templates could potentially be referenced from separate files, though the skill remains navigable. | 2 / 3 |
Total | 10 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- jpoutrin/product-forge
- Commit
0ebe7ae
- 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.