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 orchestration skill body: lean, policy-dense, with a clear phase sequence, explicit validation for config resolution and grounding failure, and disciplined delegation to a verified, appropriately-sized reference bundle. The main gaps are that the workflow's later phases and part of the bundle are only discoverable by chaining reads, and a little redundancy could be trimmed.

Suggestions

Add a short bundle map (one line per file, including agents/) so files like html-rendering.md, markdown-rendering.md, publishing.md, and the agent briefs are discoverable from SKILL.md instead of only via chained reads through other references.

Name phases 3-5 in the body — even one line each before the post-ideation-workflow.md handoff — so the full workflow shape is visible up front rather than emerging through reference chaining.

Trim the repeated "The read is required" assertions and condense the marker-comment blocks (ce-docs-root, ce-config-layers) to recover tokens without losing the policies they encode.

DimensionReasoningScore

Conciseness

The body is dense operational policy with no explanation of concepts Claude already knows, but carries minor trimmable redundancy: "The read is required" is asserted repeatedly, the ce-docs-root/ce-config-layers marker blocks add bulk, and some lawyerly sentences ("Presence in the current tool list is proof the tool exists") could be tightened. It is not 5 because of that residual slack, and not 3 because nothing is concept-explanation padding.

4 / 5

Actionability

Concrete, executable coordination guidance throughout: exact paths (`<root>/ideation/`, `/tmp/compound-engineering-<uid>`), a real command (`git rev-parse --show-toplevel`), and specific directives ("Generate one 8-hex `<run-id>`"), with ordered required reads per phase. It is not 5 because the body alone is not copy-paste executable for the core generation work (fleet, frames, and rules are delegated to references), and not 3 because the guidance actually present is specific and executable rather than high-level hints.

4 / 5

Workflow Clarity

Phases 0→1→1.5→2 are clearly sequenced with explicit read-ordering and real validation checkpoints ("Otherwise stop with an error naming `docs_root` and the value -- never fall back", "Warn and proceed when grounding fails"). It is not 5 because phases after Phase 2 are invisible in the body and the handoff sentence ("continue with `references/post-ideation-workflow.md`, which it names as the next required read") is convoluted; it is not 3 because sequence and checkpoints are explicit for everything the body covers.

4 / 5

Progressive Disclosure

The body is a lean phase index whose seven directly referenced files (output-mode.md, scope-gates.md, grounding.md, decomposition.md, divergent-ideation.md, universal-ideation.md, post-ideation-workflow.md) all exist and contain real, well-sized content (27-247 lines each), with references clearly signaled. It is not 5 because several bundle files (html-rendering.md, markdown-rendering.md, ideation-sections.md, publishing.md, and agents/*) are reachable only by chaining through other references, and reference files cross-reference each other extensively (post-ideation-workflow.md alone points to six more), so navigation extends beyond one level; it is not 3 because the structure and signaling are clearly good.

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: explicit 'what' and 'when' with natural trigger terms, third-person imperative voice, and unusually good explicit disambiguation from sibling skills. The only weakness is that the 'what' stops at two actions, leaving the ranked-artifact and critique-all mechanics implicit.

DimensionReasoningScore

Specificity

"Generate and evaluate grounded ideas" names two concrete actions, but "grounded" is abstract and the ranking/critique process is never stated in the description itself — matching the anchor for 1-2 concrete actions without comprehensive coverage. It is not 4 because only two actions appear, and not 2 because the stated actions are concrete rather than generic.

3 / 5

Completeness

The description explicitly answers both what ("Generate and evaluate grounded ideas") and when ("Use when the user wants ideas, improvements, or surprising directions before choosing one to develop") with concrete trigger phrases. It is not 4 because the 'when' clause is already fully explicit and specific, which is exactly what the 4-anchor flags as lacking.

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. It is not 5 because common variations like "feature suggestions" or "give me options" are absent, and not 3 because the terms present are natural user language rather than jargon.

4 / 5

Distinctiveness Conflict Risk

Negative triggers explicitly route edge cases to sibling skills ("Not for refining an idea they already have (ce-brainstorm) or judging one already on the table (ce-pov)"), carving out a clear ideation niche with minimal conflict risk. This matches the 5-anchor (clear niche with distinct triggers) rather than 4, where only minor overlap risk exists without explicit disambiguation.

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.