CtrlK
BlogDocsLog inGet started
Tessl Logo

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'.

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/game-changing-features/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers a well-sequenced, genuinely actionable strategy workflow with concrete evaluation criteria and a complete output template — exactly what an instruction-only skill needs. Its weaknesses are token efficiency (motivational sections like 'The Point' and 'Prompts to Unstick Thinking' restate what a capable model already knows) and the absence of a worked example showing a scored, prioritized result.

Suggestions

Trim or cut 'The Point' and 'Prompts to Unstick Thinking' — both restate generic brainstorming framing Claude already applies; keep the distinct rules (e.g., 'SMALL CAN BE HUGE', 'NO SAFE IDEAS') and the category table, which act as forcing functions.

Add one compact worked example: a sample product with two ideas scored against the Impact/Reach/Frequency table and slotted into the Do Now / Explore priority tiers, so the output format is demonstrated rather than only templated.

Consider moving the full output-format template into a reference file (e.g., references/output-template.md) linked from a short 'Output Format' section, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The tables, workflow, and output template earn their tokens, but sections like "The Point" ("Not 10% better. Not 'nice to have.' Game-changing.") and "Prompts to Unstick Thinking" are motivational padding a competent model could generate on its own. Mostly efficient with several passages that could be tightened, matching anchor 3 rather than the minor-trims-only anchor 4.

3 / 5

Actionability

Concrete, executable guidance throughout: a six-criteria evaluation table (Impact/Reach/Frequency/Differentiation/Defensibility/Feasibility), an explicit scoring scale (🔥/👍/🤔/❌), a stack-rank priority template, and a fully specified copy-paste output format. Falls short of anchor 5 only because there is no worked example of an evaluated idea.

4 / 5

Workflow Clarity

A clear five-step sequence (Understand Current Value → Find Opportunities → Evaluate Ruthlessly → Identify Highest-Leverage Moves → Prioritize) where Step 3 acts as an explicit filter checkpoint, plus a Questions/Blockers section in the output for handling missing input. No error-recovery feedback loop is present, and none is strictly required for a non-destructive strategy task, so this sits at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

No bundle files exist, and the body is well-organized into clearly headed sections with no nested or buried references. However, everything — the ten-category idea table, the full output template, the unstick prompts — is inlined in a single ~280-line file; some of this could be split into one-level-deep references, keeping it at anchor 4 rather than 5.

4 / 5

Total

15

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it clearly states what the skill does and provides an explicit, multi-trigger 'Use when' clause with natural user phrasing centered on the distinctive '10x' framing. The main gap is specificity — the capability statement stays at the level of "find opportunities and improvements" rather than naming the concrete activities (opportunity sizing, stack-ranked prioritization, category sweep) the skill actually performs.

DimensionReasoningScore

Specificity

"Find 10x product opportunities and high-leverage improvements" names the domain and 1-2 actions, but does not enumerate several specific concrete capabilities. It is above score 2 (domain plus minimal generic action) yet lacks the multiple specific actions of score 4.

3 / 5

Completeness

Explicitly answers both parts: the 'what' ("Find 10x product opportunities and high-leverage improvements") and a multi-trigger 'when' clause ("Use when user wants strategic product thinking, mentions '10x', ... or says 'what should we build next'"). This matches the anchor for explicit what-and-when with concrete trigger phrases; score 4 would require the 'when' to be less explicit than it is.

5 / 5

Trigger Term Quality

Includes natural phrases users would actually say: "mentions '10x'", "'what would make this 10x better'", "'product strategy'", "'what should we build next'". A few natural variations (e.g., "brainstorm features", "roadmap", "prioritize features") are missing, keeping it below comprehensive coverage at 5.

4 / 5

Distinctiveness Conflict Risk

The '10x' framing carves a fairly distinct niche with dedicated triggers, but phrases like "'product strategy'" and "'what should we build next'" could overlap with general brainstorming, roadmap, or prioritization skills. Mostly distinct with minor overlap risk, matching anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

16

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openstatusHQ/data-table-filters
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.