game-changing-features
Find 10x product opportunities and high-leverage improvements. Use when user wants strategic product thinking, mentions '10x', wants to find high-impact features, or says 'what would make this 10x better', 'product strategy', or 'what should we build next'.
Install with Tessl CLI
npx tessl i github:softaworks/agent-toolkit --skill game-changing-features83
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/skillAgent success when using this skill
Validation for skill structure
Discovery
82%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 has strong trigger term coverage and completeness with explicit 'Use when' guidance. However, it lacks specificity about concrete actions the skill performs (e.g., what methods or outputs it produces) and could potentially conflict with other product-related skills due to somewhat generic strategic language.
Suggestions
Add specific concrete actions like 'analyzes user pain points', 'identifies leverage points', 'generates prioritized feature recommendations' to improve specificity
Consider adding distinguishing output types or methodologies to reduce potential overlap with other product strategy skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (product opportunities, improvements) and mentions 'strategic product thinking' and 'high-impact features', but lacks concrete actions like 'analyze user feedback', 'prioritize features', or 'create roadmaps'. | 2 / 3 |
Completeness | Clearly answers both what ('Find 10x product opportunities and high-leverage improvements') and when ('Use when user wants strategic product thinking, mentions 10x...') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: '10x', 'product strategy', 'what would make this 10x better', 'what should we build next', 'high-impact features'. These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The '10x' and specific phrases provide some distinctiveness, but 'product strategy' and 'what should we build next' could overlap with general product management or roadmapping skills. | 2 / 3 |
Total | 10 / 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 strategic thinking skill with excellent actionability and workflow clarity. The evaluation framework, output template, and unsticking prompts are particularly strong. However, it's somewhat verbose with philosophical framing Claude doesn't need, and the length could be reduced by extracting reference tables to separate files.
Suggestions
Remove the philosophical framing in 'The Point' section - Claude understands the concept of 10x thinking without explanation
Consider extracting the 'Idea Categories to Explore' table to a separate reference file to reduce main skill length
Tighten the evaluation criteria section - the table format is good but some explanatory text around it is redundant
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some verbose explanations that Claude doesn't need (e.g., explaining what 10x thinking means, the philosophical framing about 'most product work is incremental'). The tables and category lists are useful but could be tightened. | 2 / 3 |
Actionability | Provides highly concrete guidance with specific questions to ask, evaluation criteria with clear scoring system (🔥/👍/🤔/❌), detailed output format template, and specific prompts to unstick thinking. The workflow steps are clear and executable. | 3 / 3 |
Workflow Clarity | Clear 5-step sequential workflow with explicit phases (Understand → Find → Evaluate → Identify → Prioritize). Each step has concrete sub-tasks and the output format provides a clear checklist structure. Appropriate for a strategy skill that doesn't involve destructive operations. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but it's a long monolithic document (~200 lines) that could benefit from splitting detailed category tables or evaluation criteria into separate reference files. The output path structure is good but the skill itself doesn't reference external files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.