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'.
84
79%
Does it follow best practices?
Impact
89%
1.48xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./dist/plugins/game-changing-features/skills/game-changing-features/SKILL.mdQuality
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 an explicit 'Use when...' clause containing natural user phrases. However, it lacks specificity in describing concrete actions the skill performs, and the domain could overlap with other product-focused skills. The description would benefit from more specific capability statements.
Suggestions
Add specific concrete actions like 'analyzes user feedback', 'identifies leverage points', 'prioritizes opportunities by impact/effort', or 'generates strategic recommendations'
Differentiate from general product management skills by specifying the unique methodology or framework used (e.g., '10x thinking framework', 'leverage analysis')
| 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'. The phrase 'Find 10x product opportunities' is somewhat abstract. | 2 / 3 |
Completeness | Clearly answers both what ('Find 10x product opportunities and high-leverage improvements') and when with explicit 'Use when...' clause listing multiple trigger scenarios. The structure follows the recommended pattern. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: '10x', 'what would make this 10x better', 'product strategy', 'what should we build next', 'high-impact features'. These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The '10x' and 'product strategy' terms create some distinctiveness, but 'high-leverage improvements' and 'what should we build next' could overlap with general product management, roadmapping, or feature prioritization 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 strong actionability and clear workflow. The evaluation frameworks, scoring systems, and output templates provide concrete guidance. Main weakness is length—some sections could be more concise or split into reference files, and a few explanatory passages assume less of Claude's intelligence than necessary.
Suggestions
Trim 'The Point' section—Claude understands the difference between incremental and transformative thinking without the preamble
Consider moving the detailed 'Idea Categories to Explore' table and 'Output Format' template to separate reference files to reduce main skill length
Condense the 'Prompts to Unstick Thinking' section into a more compact bullet list without the conversational framing
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some verbose sections that could be tightened. Phrases like 'Most product work is incremental: fix bugs, add requested features, polish edges. That's necessary but not sufficient.' explain concepts Claude understands. The 'Prompts to Unstick Thinking' section adds value but could be more compact. | 2 / 3 |
Actionability | Highly actionable with specific frameworks, concrete questions to ask, clear evaluation criteria with scoring system (🔥/👍/🤔/❌), detailed output templates, and specific category tables. The guidance is specific enough to execute immediately. | 3 / 3 |
Workflow Clarity | Clear 5-step workflow with explicit sequencing: Understand → Find Opportunities → Evaluate → Identify Leverage → Prioritize. Each step has concrete sub-tasks and the output format provides a clear checkpoint structure. For a strategy skill (no destructive operations), validation is appropriately scoped. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but it's a monolithic document (~200 lines) that could benefit from splitting detailed frameworks (evaluation criteria, idea categories, output template) into separate reference files. The output path convention is good but inline content is heavy. | 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.
3027f20
Table of Contents
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.