forge-help
Show all available Product Forge agents, skills, and commands
77
66%
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/product-design/skills/forge-help/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description provides a basic understanding of what the skill does but lacks explicit trigger guidance, limiting Claude's ability to know when to select it. The Product Forge branding adds some distinctiveness, but the description would benefit from more specific actions and a clear 'Use when...' clause.
Suggestions
Add a 'Use when...' clause with trigger terms like 'list available tools', 'what can Product Forge do', 'show help', 'available capabilities'
Include more specific actions such as 'browse agent catalog', 'search commands by name', 'view skill documentation'
Add natural language variations users might say: 'help', 'what's available', 'show me tools', 'list features'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Product Forge) and a general action (show available agents, skills, commands), but doesn't list specific concrete actions like 'list agents with descriptions', 'filter by category', or 'search commands'. | 2 / 3 |
Completeness | Only describes what the skill does ('show available...') but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords ('agents', 'skills', 'commands', 'Product Forge') but misses common variations users might say like 'list', 'what can you do', 'help', 'available tools', or 'capabilities'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Product Forge' provides some specificity, but 'agents, skills, and commands' is generic enough to potentially conflict with other help/listing skills. The scope is somewhat defined but not sharply distinct. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary simple skill that demonstrates excellent token efficiency and actionability. It provides everything needed to use the command (usage examples, execution logic, regeneration) without any unnecessary explanation or verbosity. The structure is clean and appropriate for the skill's scope.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations - assumes Claude knows how to read files, filter content, and run scripts. Every line serves a purpose. | 3 / 3 |
Actionability | Provides concrete, executable commands for all use cases: usage examples with actual command syntax, and a complete bash command for regenerating the index. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose skill (display/filter an index file). The single action is unambiguous and the regeneration workflow is clear with explicit command. | 3 / 3 |
Progressive Disclosure | Appropriately structured for a simple skill under 50 lines. References the external forge-index.md file without unnecessary nesting. Clear sections for usage, execution, and maintenance. | 3 / 3 |
Total | 12 / 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.