ideate

Clarifies a rough idea into a precise problem specification through structured dialogue. Asks targeted questions to surface assumptions, scope, constraints, and actors. Produces a specification document defining WHAT needs to change — not HOW to change it. Use when starting a new feature, brainstorming an idea, clarifying requirements, or when a user says "I have an idea", "let's think through", "ideate", "brainstorm", "I want to build", "help me think about", "what should we build".

Quality

85%

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

71%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 content is a well-structured, highly actionable ideation process with clear phased gating, but it loses points for repeated conceptual messaging and for referencing a spec-template.md file that is missing from the bundle.

Suggestions

Consolidate the 'WHAT not HOW' and progressive-layering messaging into a single authoritative section to remove the restatements across mindset, contract, writing principles, and rules.

Add a bundled spec-template.md file (the body references it but it is absent), or inline the template so the reference is not broken.

Add an explicit validation/review step in Phase 3 that verifies the written specification is complete and well-formed before suggesting next steps.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence, but the 'WHAT not HOW' theme and the progressive-layering concept are restated across multiple sections (mindset, contract, problem statement, writing principles, rules), which is more than minor padding but not severe verbosity.	3 / 5
Actionability	Provides copy-paste-ready concrete guidance: five numbered rounds with specific question bullets, an explicit problem-statement template with fill-in slots, a fixed spec section list, and a concrete output path with numbered next steps.	5 / 5
Workflow Clarity	A clear three-phase sequence with an explicit gating checkpoint ('GATE: Do NOT proceed to Phase 3 until the user explicitly agrees') and stop conditions, but it lacks an explicit validate/verify step for the produced specification artifact.	4 / 5
Progressive Disclosure	The body is well-organized into clear sections and signals a one-level-deep reference to spec-template.md, but that referenced file does not exist in the bundle, leaving a real navigation gap that prevents a higher score.	3 / 5
	Total	15 / 20 Passed

Description

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

The description is exemplary: it states concrete capabilities, includes a rich set of natural trigger phrases, and explicitly covers both what the skill does and when to use it. It is clearly distinct from downstream solution-design skills.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'Clarifies a rough idea into a precise problem specification', 'Asks targeted questions to surface assumptions, scope, constraints, and actors', 'Produces a specification document defining WHAT needs to change — not HOW' — giving comprehensive coverage rather than a minor-gaps list.	5 / 5
Completeness	Explicitly answers both WHAT (clarifies/produces a specification document defining WHAT needs to change — not HOW) and WHEN (Use when starting a new feature, brainstorming, or when a user says the listed trigger phrases).	5 / 5
Trigger Term Quality	Comprehensive coverage of natural trigger phrases including the skill's own name and common variations: 'I have an idea', 'let's think through', 'ideate', 'brainstorm', 'I want to build', 'help me think about', 'what should we build'.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (problem clarification via structured dialogue) with distinct conversational triggers that are unlikely to collide with implementation or solution-design skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: mock-server/mockserver-monorepo
Path: .opencode/skills/ideate/SKILL.md
Commit: 817ee95

Reviewed: 1 day 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.