CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ideate

Generates, stress-tests, and evolves ideas for a stated problem with research-grounded divergent/convergent loops — persona generators, independent judges, recombination — at quick or deep depth. Triggers on "brainstorm", "give me ideas", "ideate on", "what could we build", "/ideate".

Quality

84%

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

77%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 well-engineered orchestrator index: lean tables, concrete dispatch parameters, phase gates, and evidence pointers rather than re-taught concepts, with workflow clarity at the top of the scale. Its central weakness is that the thin-index design rests on rules/*.md and templates/*.md files that are not present in the bundle, which undermines both progressive disclosure and the completeness of the delegated phase procedures.

Suggestions

Ship 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 cited but absent from the bundle, so the 'thin index' has no on-demand content to load — include them or inline the phase procedures.

Name the four scoring axes and the finalist admission bar inline in SKILL.md (currently only '4 independent axes' and 'the quality bar') so the Score and Validate phases stay actionable even when a rule file is unavailable.

Trim the redundancy between Core Principles and Anti-patterns (several entries restate the same rule negated) and shorten the subagent cost-expectation paragraph to a one-line table cell.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — mode/flag tables, numeric gates, and §-pointers to evidence instead of explanations. Minor redundancy (several Anti-patterns restate Core Principles in negated form; the subagent cost-expectation paragraph) keeps it below the 5 anchor's 'every token earns its place', but it is clearly above 3's 'unnecessary explanation'.

4 / 5

Actionability

Concrete, executable guidance throughout: exact memory.list payloads, burst configurations ("2 bursts × 8 ideas", "5 parallel persona subagents × 6 ideas"), explicit Skill() calls, and numeric gates (pool ≥ 12/≥ 25, ≤ 3 rounds, confidence ≥ 70). Not a 5 because key specifics — the four scoring axes and the finalist admission bar — are only gestured at ("4 independent axes", "the quality bar") and delegated to rules files that are absent from the bundle.

4 / 5

Workflow Clarity

Phases 0–7 are sequenced in a table with an explicit per-phase Gate column, feedback loops are present (evolution "stopped on flat external scores, never on self-assessed improvement"; unsure-triage names an escalation path), and a Definition of Done checklist closes the loop — matching the 5 anchor's explicit validation steps and checklists.

5 / 5

Progressive Disclosure

The design is exemplary — a self-declared "thin index", a Contents nav, and one-level §-pointers into references/ideation-research.md, which exists and whose § headers match every citation. But scored against the actual bundle, 6 of the 7 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 missing, so the on-demand files the whole structure depends on cannot be navigated to — beyond 4's 'minor organization gaps'.

3 / 5

Total

16

/

20

Passed

Description

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

A strong description: it states the full capability arc concretely, explains the mechanism, and pairs it with an explicit trigger list of natural user phrases. The only gaps are a few missing common synonyms and slightly broad triggers that could overlap adjacent planning skills.

DimensionReasoningScore

Specificity

"Generates, stress-tests, and evolves ideas" names the full action arc, and "persona generators, independent judges, recombination" plus "quick or deep depth" cover the mechanisms and modes — comprehensive concrete actions, not the 4-anchor's 'minor gaps in coverage'.

5 / 5

Completeness

Both parts are explicit: the "what" ("Generates, stress-tests, and evolves ideas…") and the "when" ("Triggers on 'brainstorm', 'give me ideas', …") with concrete trigger phrases, exactly matching the 5 anchor; not 4, whose 'when' is only implicit or less specific.

5 / 5

Trigger Term Quality

Natural trigger phrases are present ("brainstorm", "give me ideas", "what could we build", "/ideate") but common synonyms like "come up with ideas", "idea generation", or "think of options" are missing — good coverage, short of the 5 anchor's comprehensive synonym set.

4 / 5

Distinctiveness Conflict Risk

A clear ideation niche with distinct triggers, but "give me ideas" and "what could we build" are broad enough to also fire for product-planning or general creativity skills — minor overlap risk per the 4 anchor, short of 5's 'minimal conflict risk'.

4 / 5

Total

18

/

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

Path

skills/analysis/ideate/SKILL.md

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.