CtrlK
BlogDocsLog inGet started
Tessl Logo

idea-refine

Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or "stress-test my plan".

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 ./skills/idea-refine/SKILL.md

The canonical home for this skill is idea-refine in addyosmani/agent-skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%Scale 1-5

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 ideation skill with a clear three-phase workflow, concrete guidance, and good progressive disclosure through external file references. Its main weaknesses are moderate verbosity (the philosophy section, duplicated anti-patterns/red flags, and some motivational language that doesn't add actionable value) and minor workflow gaps around phase transition criteria. The output template is a strong anchor that makes the skill's deliverable unambiguous.

Suggestions

Consolidate the 'Anti-patterns to Avoid' and 'Red Flags' sections — they overlap significantly and could be merged into a single concise list to save tokens.

Trim or remove the 'Philosophy' section; these are stylistic preferences Claude can infer from the tone and process instructions, and they consume tokens without adding actionable guidance.

DimensionReasoningScore

Conciseness

The skill is reasonably well-written but includes some unnecessary verbosity. The 'Philosophy' section with Apple-esque platitudes ('Say no to 1,000 things', 'The parts you can't see should be as beautiful as the parts you can') adds flavor but limited actionable value. The anti-patterns section partially duplicates the red flags section. The tone section tells Claude how to behave in ways it could infer from the instructions themselves.

3 / 5

Actionability

The skill provides concrete, specific guidance: exact questions to ask, specific ideation lenses with examples, a complete markdown template for output, and clear tool references (AskUserQuestion, Glob, Grep, Read). However, since this is primarily a conversational/thinking skill rather than a code-execution skill, the actionability is strong but not fully 'copy-paste executable' — it's appropriately concrete for an instruction-only skill with a clear output template.

4 / 5

Workflow Clarity

The three-phase workflow is clearly sequenced with explicit gates (e.g., 'Do NOT proceed until you understand who this is for'). The verification checklist at the end provides validation. However, the transitions between phases could be more explicit about what constitutes readiness to move forward — Phase 2 says 'after the user reacts' but doesn't specify what to do if the user doesn't engage meaningfully. The user confirmation before saving is a good checkpoint.

4 / 5

Progressive Disclosure

The skill references external files (frameworks.md, refinement-criteria.md, examples.md) for supplementary content, keeping the main SKILL.md focused on the core process. References are clearly signaled with context about when to use them. However, no bundle files were provided, so we can't verify these references actually exist, and the references could be slightly better organized (e.g., grouped in a 'Supporting Files' section rather than scattered inline).

4 / 5

Total

15

/

20

Passed

Description

78%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.

This is a well-structured description that excels in completeness with a clear 'Use when...' clause and explicit trigger terms. Its main weakness is that the capabilities described are somewhat abstract — 'refines raw ideas into sharp, actionable concepts' is more of a promise than a list of concrete actions. Adding a few more natural trigger synonyms like 'brainstorm' would further strengthen discoverability.

Suggestions

Add more concrete action verbs describing what the skill actually produces, e.g., 'generates alternative framings, identifies hidden assumptions, produces a ranked shortlist of options'.

Include additional natural trigger synonyms users might say, such as 'brainstorm', 'flesh out this idea', 'explore options', or 'develop this concept'.

DimensionReasoningScore

Specificity

Names the domain (idea refinement) and mentions concrete approaches ('divergent and convergent thinking', 'stress-test assumptions', 'expand options before converging'), but the actual actions are somewhat abstract — it doesn't list specific concrete outputs or steps like 'generates alternative framings' or 'produces a ranked shortlist'.

3 / 5

Completeness

Clearly answers both 'what' (refines raw ideas into sharp, actionable concepts through structured thinking) and 'when' (explicit 'Use when...' clause with three concrete trigger scenarios plus explicit trigger phrases). This is a well-structured description covering both dimensions thoroughly.

5 / 5

Trigger Term Quality

Includes good natural trigger terms like 'ideate', 'refine this idea', 'stress-test my plan', and phrases like 'vague idea' and 'expand options'. Missing some common synonyms users might say such as 'brainstorm', 'flesh out', 'explore options', or 'develop this concept'.

4 / 5

Distinctiveness Conflict Risk

Fairly distinct with its focus on idea refinement through divergent/convergent thinking, but could overlap with brainstorming skills, strategic planning skills, or general creative thinking skills. The specific trigger terms help reduce conflict risk somewhat.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
finlay611/agent-skills
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.