CtrlK
BlogDocsLog inGet started
Tessl Logo

ideate

Generates, stress-tests, and iteratively evolves ideas for a stated problem — product concepts, features, solution options, strategies — using research-grounded divergent/convergent agent loops: parallel persona generators (nominal-group simulation), independent judges scoring novelty, feasibility, impact, and fit on separate axes, and bounded recombination rounds gated by /confidence. Auto-triages run depth (quick in-context vs deep multi-agent; override with quick|deep). Use when brainstorming, exploring solution options, or pressure-testing a concept. Triggers on "brainstorm", "give me ideas", "help me come up with", "ideate on", "what could we build", "/ideate".

74

Quality

93%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A tightly edited orchestrator index with explicit gates, quantified defaults, and research grounding pushed to a reference file — the anti-verbosity pattern done well. The only material weakness is bundle integrity: the rule and template files the workflow depends on are not present alongside SKILL.md as provided, which caps both actionability and progressive disclosure.

Suggestions

Ship or verify the referenced bundle files: rules/divergence.md, rules/idea-scoring.md, rules/evolution-loop.md, rules/self-improvement-loop.md, rules/diagnostic-surface.md, and templates/ideation-report.md are linked from the phase table but missing from the bundle — the skill's core phases are non-executable without them.

Inline a minimal fallback for each rule file (or a one-line summary of the procedure it contains) so a reader without the bundle can still run a degraded quick-mode pass.

Verify every relative link resolves in the distributed package (e.g., add a bundle self-check step), since the §-pointer scheme only works if references/ideation-research.md and rules/*.md travel with SKILL.md.

DimensionReasoningScore

Conciseness

The body is a lean orchestration index: mode/flag/triage tables, an 8-phase gate table, terse principles, and research claims delegated to § pointers in the reference file instead of re-explained. It assumes Claude's competence throughout (e.g., "Restate the problem in one sentence and name the success criterion") with no primer content. Not a 4 because the few justificatory asides ("the width variation is the evidenced part (§2.5)") are provenance notes that earn their tokens.

5 / 5

Actionability

Mostly executable: exact generator burst sizes, subagent counts (~17 cost breakdown), concrete `memory.list` calls with scope/tags/limit, `Skill("confidence", "analysis")` composition calls, report path format, and first-match-wins triage rules. However, the procedures for phases 2–6 live in `rules/*.md` files that are not present in the provided bundle, so the body alone leaves key execution details (generator prompts, scoring rubric, recombination mechanics) unresolved. Not a 5 because copy-through executable guidance for the core phases depends on files the reader cannot open here; not a 3 because what is inline (intake, framing, triage, composition, gates) is fully concrete.

4 / 5

Workflow Clarity

The 8-phase table gives every phase an explicit gate (pool ≥ 12/25 unique ideas, "zero evaluation happened during generation", confidence ≥ 70, "stopped on flat external scores"), backed by a Definition of Done checklist and per-phase inline procedures for phases 0–1. Validation checkpoints and stopping conditions are explicit at each decision point. Not a 4 because checkpoints are not merely present — they are quantified and paired with an end-of-run checklist.

5 / 5

Progressive Disclosure

Textbook thin-index structure: a Contents nav, a phase table linking each procedure file by role, and one-level-deep references; the one bundled file (`references/ideation-research.md`) exists and its §-sections match every § pointer in the body. However, six referenced paths (`rules/divergence.md`, `rules/idea-scoring.md`, `rules/evolution-loop.md`, `rules/self-improvement-loop.md`, `rules/diagnostic-surface.md`, `templates/ideation-report.md`) are absent from the provided bundle, so navigation does not fully resolve as listed. Not a 5 solely because of those unresolvable paths; not a 3 because the structure, signaling, and depth discipline are otherwise exactly right.

4 / 5

Total

18

/

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.

An exemplary description: concrete multi-action capability statement, an explicit "Use when" clause, and a list of natural trigger phrases including the slash command. It is dense but not padded — every clause carries routing-relevant information.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Generates, stress-tests, and iteratively evolves ideas", "parallel persona generators", "independent judges scoring novelty, feasibility, impact, and fit on separate axes", "bounded recombination rounds gated by /confidence", "Auto-triages run depth" — with comprehensive coverage of the skill's capability surface. It names the domain, the mechanisms, and the depth override options; nothing is vague filler. Not a 4 because the action list is comprehensive rather than having minor gaps.

5 / 5

Completeness

It explicitly answers both questions: the "what" is the full generate → judge → recombine pipeline with mechanism detail, and the "when" is stated twice — "Use when brainstorming, exploring solution options, or pressure-testing a concept" and the explicit "Triggers on" phrase list. Not a 4 because the when-clause is explicit and concrete, not merely present.

5 / 5

Trigger Term Quality

Triggers include natural user phrasings: "brainstorm", "give me ideas", "help me come up with", "ideate on", "what could we build", plus "exploring solution options" and "pressure-testing a concept". These cover the common ways a user would naturally request ideation, including the slash-command form. Not a 4 because synonym-level variations (give me ideas / help me come up with / ideate on) are all present, not just one or two keywords.

5 / 5

Distinctiveness Conflict Risk

The niche (research-grounded ideation with divergent/convergent agent loops) and its trigger phrases are clearly distinct from evaluation, critique, or planning skills; "brainstorm" and "give me ideas" route here naturally with minimal overlap. The only adjacent surface ("pressure-testing a concept") is bounded by the ideation framing. Not a 4 because no closely related skill would plausibly capture these triggers.

5 / 5

Total

20

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 10 missing

Warning

Total

13

/

16

Passed

Repository
mthines/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.