CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ce-explain

Explain how and why something has its current shape, or what happened over a window of work, grounded in evidence. Use when the user asks for an explanation. Use ce-pov for a judgment or recommendation.

Quality

76%

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 ./skills/ce-explain/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 tightly written orchestration skill: a phased workflow with explicit edge-case handling, defensive executable scaffolding, and disciplined offloading of detail to well-signposted, verified reference files. The residual gaps are minor — error-recovery loops and artifact verification are delegated to references rather than stated inline, and a couple of reference chains nest two levels deep without an index.

Suggestions

State the dispatch-failure fallback and a one-line post-write artifact check inline in Phase 2/Phase 3 so the recovery loop does not depend on a reference round-trip.

Add a brief bundle index (or inline mention of `references/publishing.md` in Phase 4) so second-level files are discoverable without traversing the destinations reference.

Fold the recap-mode inline-fallback rule's key budgets (extraction tier, sources) into a single sentence in Phase 2 instead of implying them through the scout seed reference.

DimensionReasoningScore

Conciseness

The 81-line body is dense and assumes Claude's competence: no concept tutorials, no library recommendations, no filler — every section adds policy Claude could not infer (e.g. "Publication is a separate action, not a condition of having explained the subject"). The 10-line bash block and the docs-root rules are executable content encoding safety constraints, not padding, so this matches anchor 5 ("Lean and efficient; assumes Claude's competence; every token earns its place") rather than anchor 4's "minor instances of over-explanation".

5 / 5

Actionability

Concrete and executable where it counts: a copy-paste-ready scratch-directory script with hard failure exits, exact paths ("Write `$RUN_DIR/explainer.html` or `explainer.md`"), timed read directives ("Read `references/intake.md` now"), and explicit per-case rules for empty ranges, empty windows, and dispatch failure. As an instruction-only orchestration skill this meets anchor 4 ("Mostly executable guidance; concrete code or commands with minor gaps"); it falls short of 5 because several operational specifics (model tiers, publisher selection, format metadata) are delegated to references rather than demonstrated inline, and directives like "check every factual claim against its source" are process rules rather than runnable steps.

4 / 5

Workflow Clarity

Four sequenced phases with a Done criterion, explicit validation checkpoints (symlink/ownership checks with `exit 1`, "Before delivery, check every factual claim against its source", the consent gate where "If confirmation cannot be obtained, do not publish"), and enumerated edge cases. This is solidly anchor 4 ("Clear sequence with most checkpoints present; minor validation gaps"); it is not 5 because the error-recovery loops are pointers ("If dispatch fails, follow the fallback rule in `references/orchestration.md`") rather than inline feedback loops, and no inline verification of the written artifact is specified before delivery.

4 / 5

Progressive Disclosure

The body is a genuine overview: all format/tier/intake detail lives in seven small reference files that are explicitly signposted at the point of need, and every referenced path resolves to a real file in the bundle. This matches anchor 4 ("Good structure; most content is appropriately placed; references mostly clear; minor organization gaps"). Not 5: references are one level deep from SKILL.md, but two chains go a second level (`references/destinations.md` → `references/publishing.md`; `references/orchestration.md` → `references/agents/behavior-trace-scout.md`), and there is no consolidated index of the bundle, so discovery of `publishing.md` depends on landing in the destinations flow.

4 / 5

Total

17

/

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.

A well-formed description with an explicit 'Use when' clause, third-person voice, and a deliberate boundary pointer to a sibling skill. Its main weakness is trigger breadth and abstraction: the 'when' condition is a single generic phrase and the capability statement characterizes rather than enumerates concrete actions, leaving moderate overlap risk with general explanation-shaped requests.

Suggestions

Make the 'when' clause concrete with the phrases users actually say, e.g. "Use when the user asks why something works a certain way, how a design came to be, what happened over a window of work, or asks to be caught up on changes."

Add the common synonyms that are currently missing — 'walk me through', 'recap', 'what changed' — so natural variations of the request trigger the skill.

Fence off one more neighboring case in the description itself (e.g. "a diagnosis or fix attempt belongs to ce-debug") to reduce routing overlap beyond the ce-pov boundary.

DimensionReasoningScore

Specificity

The description names the domain and two capabilities — "Explain how and why something has its current shape, or what happened over a window of work, grounded in evidence" — but these are abstract characterizations rather than the multiple concrete, verb-level actions of the top anchors (cf. "Extract text and tables from PDF files, fill forms, merge documents"). It matches anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive"): more defined than a bare domain label (2), but it does not enumerate several specific actions with only minor gaps (4).

3 / 5

Completeness

Both parts are explicit: the "what" ("Explain how and why something has its current shape, or what happened over a window of work, grounded in evidence") and the "when" ("Use when the user asks for an explanation"), plus a boundary pointer ("Use ce-pov for a judgment or recommendation"). This matches anchor 4 ("Has both 'what' and 'when'; 'when' could be more explicit or specific") — the trigger clause is a single generic condition rather than the concrete trigger phrases of anchor 5 (e.g. "...or when the user mentions PDFs, forms, or document extraction").

4 / 5

Trigger Term Quality

Natural terms present are "Explain", "how and why", "what happened", and "asks for an explanation", which are words a user would plausibly say. However common variations and synonyms are missing — e.g. "why does X work this way", "walk me through", "recap", "what changed", "catch me up" — so it fits anchor 3 ("Some relevant keywords but missing common variations or synonyms"), not the good coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

The evidence-grounding qualifier and the explicit disambiguation "Use ce-pov for a judgment or recommendation" carve out a clear niche versus its sibling skill, matching anchor 4 ("Mostly distinct; minor overlap risk with closely related skills"). It is not a 5: the trigger "the user asks for an explanation" is broad enough that general Q&A or teaching requests could route here, and no other neighboring skills (e.g. ce-debug's factual explanations) are fenced off in the description itself.

4 / 5

Total

14

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

EveryInc/compound-engineering-plugin

Path

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