CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ce-ideate

Generate and evaluate grounded ideas. Use when the user wants ideas, improvements, or surprising directions before choosing one to develop. Not for refining an idea they already have (ce-brainstorm) or judging one already on the table (ce-pov).

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-built orchestrator skill: lean, phase-sequenced, host-agnostic, and heavily grounded in concrete paths, commands, and config resolution rules, with every named reference verified to exist. Scores are capped at 4 across dimensions by minor gaps — unspecified temp/cost-line details, checkpoints delegated to references, and second-tier files unreachable without traversing other references.

Suggestions

Name the second-tier reference files (ideation-sections.md, markdown-rendering.md, html-rendering.md, agents/*.md) somewhere in SKILL.md — or add a short phase-to-file map — so every bundle file is discoverable in one hop instead of requiring traversal of other references.

Specify the fallback "CE temp path" concretely, and define the cost line the skill must show before dispatching (what it contains and where it is displayed), rather than leaving both implicit.

Trim the repeated "The read is required" phrasing and merge the Artifact Root paragraph with the embedded ce-docs-root block, which restate the same path-resolution rules.

DimensionReasoningScore

Conciseness

The 75-line body is dense with operational rules and explains nothing Claude already knows, with all detail correctly pushed to references. Minor redundancy keeps it below fully lean: "The read is required" is repeated for multiple phases, and the Artifact Root paragraph overlaps the embedded ce-docs-root block's resolution rules.

4 / 5

Actionability

Concrete, executable guidance dominates: exact commands ("git rev-parse --show-toplevel"), exact paths ("/tmp/compound-engineering-<uid>", "<root>/ideation/"), config keys, an 8-hex run-id spec, and a per-phase read order. Minor gaps remain — "a CE temp path" is never specified, and the cost line the skill must show has no defined format or location.

4 / 5

Workflow Clarity

Phases 0 through 2 are clearly sequenced, each gated by a named required read, with validation rules present in the body (docs_root validation with a named error, "Warn and proceed when grounding fails", precedence chain for output mode). However, most checkpoints live in delegated reference files, and the body ends at Phase 2, handing the critique/rank/menu half of the workflow off to post-ideation-workflow.md, so the full sequence is not visible here.

4 / 5

Progressive Disclosure

SKILL.md is a genuine overview that splits detail into 13 reference files, all of which exist, with clear per-phase signals ("Read references/grounding.md before dispatching any grounding agent"). The gap: several real bundle files (ideation-sections.md, html-rendering.md, markdown-rendering.md, issue-intelligence.md, user-research-artifacts.md, web-research-cache.md, agents/*) are never named in SKILL.md and are only discoverable through other reference files, adding a second hop for that content.

4 / 5

Total

16

/

20

Passed

Description

82%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: third-person, lean, with an explicit 'Use when' clause carrying concrete trigger phrases and negative boundary guidance that disambiguates sibling skills. Its only weakness is that the 'what' clause covers just two actions (generate, evaluate) rather than the fuller set of behaviors the skill actually performs.

DimensionReasoningScore

Specificity

"Generate and evaluate grounded ideas" names the domain plus exactly two concrete actions, but omits the critiquing, ranking, and next-steps-menu behaviors the body performs. This matches the anchor for naming a domain with 1-2 actions without comprehensive coverage, and falls short of the several-action level above.

3 / 5

Completeness

It explicitly answers both: the what ("Generate and evaluate grounded ideas") and the when ("Use when the user wants ideas, improvements, or surprising directions before choosing one to develop") with concrete trigger phrases. The additional negative triggers ("Not for refining... or judging...") make the when-clause even more precise than the anchor requires.

5 / 5

Trigger Term Quality

"ideas, improvements, or surprising directions" are phrases a user would naturally say when they need this skill, giving good keyword coverage. A few common variations (e.g., "options", "suggestions", "possibilities") are missing, so it does not reach comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"before choosing one to develop" carves a clear pre-selection niche, and the explicit exclusions of ce-brainstorm ("refining an idea they already have") and ce-pov ("judging one already on the table") minimize wrong-skill triggering. It fits the clear-niche/minimal-conflict anchor; the anchor below would require unresolved overlap with sibling skills, which is not the case.

5 / 5

Total

17

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

EveryInc/compound-engineering-plugin

Path

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