to-idea

Turn the current conversation into an idea document — no interview, just synthesis of what you've already discussed.

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/to-idea/SKILL.md

Quality

Content

90%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 is a tight, highly actionable single-purpose skill: a complete idea-document template with concrete field-level guidance and no concept padding. Minor room for improvement only in making the deliverable-channel sequencing slightly more explicit.

Suggestions

Add a one-line explicit sequence for the deliverable, e.g. '1. Synthesize the conversation into the template. 2. Present it via an office-hours skill. 3. Optionally save to the project if the environment allows files.'

Clarify how to choose between presenting inline vs. saving to a file when both are available.

Dimension	Reasoning	Score
Conciseness	The body is lean: a single dense markdown template and a tight instruction ('Do not invent details or scores missing from the current conversation'), with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Provides a complete, copy-paste-ready template with explicit per-field guidance, concrete enumerated options (verdict PROCEED/TEST FIRST/PIVOT/KILL; effort S/M/L/XL), and a measurable Assignment constraint (complete within 7 days).	5 / 5
Workflow Clarity	It is a single-deliverable synthesis skill with an unambiguous action (present the doc via an office-hours skill, optionally save it), so the simple-skill exception applies; minor gap is the channel-choice sequencing ('present through... or also save') could be more explicit.	4 / 5
Progressive Disclosure	The content is well-organized into one labeled template section with no external bundle files needed; the monolithic template is appropriate as it is the deliverable format rather than reference material to split out.	4 / 5
	Total	18 / 20 Passed

Description

53%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 conveys what the skill does clearly and concisely but omits any 'Use when...' trigger guidance, which caps its completeness and trigger quality. It is reasonably distinct from other skills.

Suggestions

Add a 'Use when...' clause naming the concrete trigger phrases a user would say (e.g. 'Use when the user wants to capture a discussed idea as a structured doc, summarize an office-hours session into an idea document, or draft a design doc from the current conversation').

List 1-2 more concrete actions (e.g. 'synthesize, structure, and present') to lift specificity from a single named action to several.

Include a natural synonym or keyword like 'design doc' or 'idea doc' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('idea document') and one concrete action ('Turn the current conversation into... synthesis of what you've already discussed'), but lists only that single action rather than multiple specific capabilities.	3 / 5
Completeness	Has a clear 'what' (synthesize the conversation into an idea doc without an interview) but no explicit 'when to use it' clause; per the rubric, a missing 'Use when...' trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Contains some relevant natural terms ('idea document', 'synthesis', 'interview'), but lacks a 'Use when...' clause with the trigger phrases a user would actually say when needing this skill.	3 / 5
Distinctiveness Conflict Risk	The 'turn conversation into idea document' framing is a fairly distinct niche with only minor overlap risk against general brainstorming or office-hours skills.	4 / 5
	Total	13 / 20 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: choegyumin/agent-skills
Path: skills/to-idea/SKILL.md
Commit: a6a5aba

Reviewed: 9 days 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.