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

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%

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

A well-structured, actionable strategy framework with a clear sequenced workflow and concrete templates; its main weaknesses are some unnecessary explanatory prose and a monolithic single-file structure with no progressive disclosure.

Suggestions

Trim conceptual prose like 'The Point' section that restates what Claude already knows about incremental product work, keeping only the directive framing.

Move the long Idea Categories table and/or the 'Prompts to Unstick Thinking' list into a reference file (e.g. references/idea-categories.md) referenced one level deep, so SKILL.md stays a lean overview and progressive disclosure improves.

Consider extracting the full Output Format template into a separate reference so the main body focuses on process rather than boilerplate.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient scaffolding (tables, scoring systems, templates) but includes explanatory prose Claude does not need, e.g. 'Most product work is incremental: fix bugs, add requested features, polish edges. That's necessary but not sufficient.' — efficient but could be tightened, so it sits at 2 rather than the lean level-3 anchor.	2 / 3
Actionability	For an instruction-only strategy skill it gives concrete, specific guidance: a copy-paste output format template, a criteria scoring table, a 🔥/👍/🤔/❌ scoring scheme, a priority template, and explicit 'be specific' rules with examples ('One-click rescheduling from notification'), matching the level-3 actionable anchor.	3 / 3
Workflow Clarity	A clearly sequenced five-step process (Understand → Find → Evaluate → Identify → Prioritize) with a defined output artifact; this is a non-destructive strategy task so the absence of validation checkpoints does not cap the score at 2 per the rubric's destructive/batch-operations note.	3 / 3
Progressive Disclosure	No bundle files exist and the ~280-line body is a single monolithic SKILL.md with no external references; sections are well-organized (not a wall of text) but content that could be split (Idea Categories table, unsticking prompts, full output template) is inline, matching the level-2 anchor rather than the one-level-deep reference structure of a 3.	2 / 3
	Total	10 / 12 Passed

Description

90%

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 with an explicit 'Use when' clause and natural, well-covered trigger terms; its only weakness is that the stated actions are abstract strategic goals rather than concrete operations.

Suggestions

Tighten the 'what' clause with more concrete actions (e.g. 'generate, score, and stack-rank 10x feature ideas') to lift specificity from abstract goals to tangible operations.

Consider trimming the long trigger list slightly so the most natural triggers ('10x', 'what would make this 10x better', 'product strategy') stand out rather than being diluted by adjacent phrasings.

Dimension	Reasoning	Score
Specificity	The description names the domain and two actions ('Find 10x product opportunities and high-leverage improvements'), but these are abstract goals rather than the multiple concrete, tangible actions (e.g. 'extract text, fill forms, merge documents') that anchor a 3.	2 / 3
Completeness	It explicitly answers both 'what' (find 10x opportunities and high-leverage improvements) and 'when' via an explicit 'Use when...' clause with concrete triggers, which is the level-3 pattern; a 2 would lack the explicit when-guidance.	3 / 3
Trigger Term Quality	It includes natural phrases a user would say — '10x', 'what would make this 10x better', 'product strategy', 'what should we build next' — giving good coverage of likely utterances, matching the level-3 anchor rather than the partial coverage of a 2.	3 / 3
Distinctiveness Conflict Risk	The '10x' framing carves a clear niche with distinct triggers unlikely to fire for unrelated skills; although 'what should we build next' is somewhat generic, the dominant 10x triggers keep it distinct from level-2 overlap.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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
Path: .agents/skills/game-changing-features/SKILL.md
Commit: f1cbf2f

Reviewed: about 11 hours ago

Table of Contents

Discovery Implementation Validation

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.