CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ce-help

Help and orientation for Compound Engineering: place the user's work on the compounding loop and recommend the next command, without running it. Use when the user invokes ce-help to ask which skill fits, what comes next, how setup, configuration, cost, or upgrades work, or why a skill misbehaved.

Quality

88%

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

86%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 routing/orientation skill: concrete per-host syntax, exact paths and URLs, explicit error-handling paths, and a clean overview-to-references split with all referenced files present. The only trims available are minor redundancy between the intro and the recommendation rules and a few overlong sentences.

DimensionReasoningScore

Conciseness

The body is dense and functional — a routing table, a named loop sequence, and precise output rules with no concept explanations Claude already knows. Minor instances of over-explanation remain: the intro ("recommend the command that moves them forward, and say why it is the right one") restates rules spelled out again under "The recommendation", and a few multi-clause sentences (e.g., the preference-handling passage) could be tightened. This places it at anchor 4 ("Efficient; minor instances of over-explanation that could be trimmed") rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

For an instruction-only skill the guidance is fully executable: a decision table mapping question types to exact reference paths, exact URLs (github.com/EveryInc/compound-engineering-plugin/...), per-host invocation syntax (/skill-name, $skill-name on Codex, /skill:<name> on omp, /compound-engineering:<skill> on Devin), the named loop order, and concrete evidence sources to read (branch, uncommitted changes, open PR, <root>/plans/). The "The recommendation" section is effectively a fill-in template (command in a code block, done-check placeholder, backing link), covering the common cases as anchor 5 requires; per the scoring notes, absence of code is not penalized when guidance is this actionable.

5 / 5

Workflow Clarity

The flow — classify the question via the routing table, fall back to a blocking question with enumerated options when no row fits, read evidence to place the work on the loop, then render the recommendation — is clear, and failure paths are handled explicitly (invalid docs_root: "stop with an error naming docs_root... never fall back"; unfetchable page: "answer from the references... and say you did not check the page"). However, the sequence across sections is implied by section order rather than stated as an ordered procedure, and there are no explicit validation checkpoints, matching anchor 4 ("Clear sequence with most checkpoints present; minor validation gaps") rather than anchor 5's explicit validate/recover loops. No destructive or batch cap applies since the skill changes no files.

4 / 5

Progressive Disclosure

The body is a genuine overview that routes to four real, one-level-deep bundle files, each referenced in the table with what it holds (references/skill-map.md, workflow.md, starting-and-running.md, troubleshooting.md — all verified present); deeper detail lives in public docs pages whose URLs are given inline, and the reference files do not nest into further skill files. This matches anchor 5 ("Clear overview with well-signaled one-level-deep references... easy navigation"); anchor 4 would require buried or less-clearly-signaled references, which is not the case.

5 / 5

Total

18

/

20

Passed

Description

87%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, concise, with an explicit 'Use when' clause carrying concrete, natural trigger phrases tied to the named ce-help invocation. The only soft spot is that the action list, while precise, is brief rather than comprehensive.

DimensionReasoningScore

Specificity

Names the domain ("Help and orientation for Compound Engineering") and several concrete actions — "place the user's work on the compounding loop and recommend the next command, without running it" — plus an explicit non-goal that sharpens scope. It falls between anchor 3 (1-2 actions, not comprehensive) and anchor 5 (comprehensive coverage): the action list is concrete but brief, so 4 is the best fit, noticeably above the bare 1-2-action anchor yet short of full coverage.

4 / 5

Completeness

Explicitly answers both: what ("place the user's work on the compounding loop and recommend the next command, without running it") and when ("Use when the user invokes ce-help to ask which skill fits, what comes next, how setup, configuration, cost, or upgrades work, or why a skill misbehaved") with concrete trigger phrases. This is a direct match for the anchor-5 example pattern; anchor 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Includes natural user phrasings like "which skill fits", "what comes next", "setup, configuration, cost, or upgrades", and "why a skill misbehaved", plus the literal invocation "ce-help". Good coverage, but a few natural variants (e.g., "getting started", "how does X work") are absent, matching anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The triggers are scoped to a named system ("Compound Engineering") and a named invocation ("ce-help"), giving it a clear niche with minimal overlap against generic help or documentation skills. Matches anchor 5 ("Clear niche with distinct triggers; minimal conflict risk"); anchor 4's 'minor overlap risk with closely related skills' does not apply since the description is tied to this specific plugin.

5 / 5

Total

18

/

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-help/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.