CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ideate

Use when the user asks to widen, open or rethink a field of ideas that is empty, narrowed too early, or thin; a field merely looking narrow does not start it. The user can then see one map from their words and what they name — frames, branches, idea origins, the unexplored — and take it, nothing chosen.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./heuresis/skills/ideate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

48%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 defines a coherent, precisely gated workflow with well-signaled occasion-bound references, but it buries that clarity under a 500-line inline formal contract and heavy cross-section redundancy, and it never concretely exemplifies its central output artifact. It reads as a specification to be studied rather than guidance that can be executed directly.

Suggestions

Move the Lean formal block into a references/ file (e.g. references/formal-contract.md) and keep SKILL.md to the Protocol, Rules, and U-BINDING sections, cutting the most-repeated invariants (the no-selection rule appears ~6 times) to a single authoritative statement.

Add one worked example of a rendered round map — even a compact mock dialogue showing entry relay, a map with frames/branches/origins/unexplored, and the round offer — so the skill's central artifact is concrete rather than described.

Tighten the longest axiom doc comments (e.g. `candidates`, `targets`, `ClosingSupported`, each 10-15 lines of nested subclauses) into short statements of what is judged, moving edge-case detail into the relevant reference file.

DimensionReasoningScore

Conciseness

The 558-line body is noticeably verbose: the no-selection invariant ("never eliminates, ranks, or scores") is restated roughly six times across the Definition, MORPHISM invariants, the `generate` op, the `candidates` axiom, and the Rules; axiom doc comments run to 15+ lines of nested subclauses; and the Lean block's prose restates what the Protocol and Rules sections say again in natural language. It avoids score 1 only because none of this explains concepts Claude already knows — it is original, if heavily padded, content.

2 / 5

Actionability

There is some genuinely concrete guidance — U-BINDING's five worked invocation examples ("/ideate 'topic or fragments' → U = the argument"), the frame-map options template in references/blank-entry.md, and the explicit offer ordering ("continue first and 'Take this field as it stands' second") — but the skill's central artifact, the rendered round map, is never shown by example, only characterized in one dense 200-word paragraph ("It shows the whole field: the frames and the branches dug under them…"), leaving key execution details abstract. That matches 'some concrete guidance but incomplete' rather than the mostly-executable level of 4.

3 / 5

Workflow Clarity

The multi-step process is clearly sequenced (FLOW's arrow notation, the `start`/`ideate` recursion, and the Protocol section) with explicit checkpoints: the frame-map gate before any candidate ("until the person has chosen frames, no candidate of yours is shown"), every round ending on its offer, and "Before every round's offer, say first what continuing would cost to review and what taking keeps". It falls short of 5 because the same loop is stated in three different notations (arrow flow, Lean definitions, prose) that the reader must reconcile.

4 / 5

Progressive Disclosure

The three reference files exist and are well-signaled with occasion-bound triggers ("read `references/blank-entry.md` before presenting it"; "for `Seeded`, read `references/seeded-entry.md` before the first pass"; "Read `references/round-composition.md` before composing when…") and are one level deep, pointing back to SKILL.md rather than to each other. However, the ~500-line Lean formal contract — content that clearly belongs in a separate reference file — is inlined in full in the always-loaded SKILL.md, matching 'some structure … content that should be separate is inline'.

3 / 5

Total

12

/

20

Passed

Description

62%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 clearly answers 'when' with explicit trigger conditions and a useful anti-trigger, and stays in third person, but the 'what' is stated in abstract, metaphorical language and the most natural user synonyms for ideation requests are missing. It is serviceable and distinctive but would benefit from more concrete capability language.

DimensionReasoningScore

Specificity

The description names the domain and a couple of actions — "widen, open or rethink a field of ideas" and a map showing "frames, branches, idea origins, the unexplored" — but the actions are phrased metaphorically rather than as concrete operations, matching 'names domain and 1-2 concrete actions, but not comprehensive'. It falls short of 4 because the capability is not enumerated in crisp, concrete terms a reader could act on.

3 / 5

Completeness

Both parts are present: an explicit "Use when the user asks to widen, open or rethink a field of ideas that is empty, narrowed too early, or thin" (with an anti-trigger: "a field merely looking narrow does not start it") and a stated outcome — "see one map from their words and what they name … and take it, nothing chosen". It is not 5 because the 'what' is outcome-phrased and abstract rather than a clear, explicit statement of the skill's capability.

4 / 5

Trigger Term Quality

Phrases like "widen", "rethink", "narrowed too early", and "thin" are ones a user might naturally say, giving some relevant keywords, but the most common everyday synonyms for an ideation skill — "brainstorm", "more ideas", "expand options", "come up with ideas" — are absent, matching 'some relevant keywords but missing common variations or synonyms' rather than the good coverage of 4.

3 / 5

Distinctiveness Conflict Risk

The niche is well carved — divergent-only widening of an underexpanded idea field, user-initiated, with an explicit non-trigger for a field that merely looks narrow — leaving only minor overlap risk with general brainstorming/idea-generation skills. Not 5 because the abstract phrasing leaves some ambiguity against adjacent ideation helpers.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (559 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

jongwony/epistemic-protocols

Path

heuresis/skills/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.