CtrlK
BlogDocsLog inGet started
Tessl Logo

ce-setup

Check Compound Engineering health and repo-local config.

58

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ce-setup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 content is a well-structured, actionable multi-phase setup workflow that defers detail to real, clearly labeled reference files and uses executable commands. Its only real weakness is that error-recovery feedback loops are not made fully explicit.

DimensionReasoningScore

Conciseness

The body is mostly lean imperative instruction with no basic-concept padding, though the interaction-method paragraph and the inline Artifact Root Resolution block contain some explanatory prose that could be trimmed, matching the score-4 anchor.

4 / 5

Actionability

It provides real executable bash (SKILL_DIR resolution, if/else script invocation, --version handling) and explicit display strings, with minor gaps from placeholders (VERSION, <rendered invocation>) and fix details deferred to references/repo-fixes.md.

4 / 5

Workflow Clarity

A clear 3-phase sequence with numbered steps and explicit report-gated branching (writable checkout vs remote vs skip) plus remediation triggers is present; it falls short of 5 because the validate->fix->retry feedback loop is not as explicit as the anchor requires.

4 / 5

Progressive Disclosure

The body is an overview that clearly signals one-level-deep references to real bundle files (references/repo-fixes.md for Steps 4-8, scripts/check-health) with their contents labeled, and content is appropriately split with easy navigation.

5 / 5

Total

17

/

20

Passed

Description

53%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 states a clear purpose but omits any explicit 'when to use' trigger guidance and uses only a couple of generic keywords. It is distinct within the CE niche yet would benefit from concrete trigger phrases.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when setting up or repairing a Compound Engineering checkout, or when the user asks to check CE environment health').

Expand keywords with natural synonyms users say ('setup', 'install', 'environment', 'repair', 'config.yaml') to improve trigger matching.

Concretize the actions beyond 'check health' and 'repo-local config' (e.g., 'runs the CE health check, resolves the artifact root, and offers to repair repo-local config').

DimensionReasoningScore

Specificity

Names the domain ('Compound Engineering health', 'repo-local config') and two coarse actions ('Check health', handle config), but the actions are abstract categories rather than a list of specific concrete steps, matching the score-3 anchor.

3 / 5

Completeness

It states a clear 'what' (check health and repo-local config) but provides no 'when/Use when...' trigger guidance; per the rubric a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

'health' and 'config' are relevant natural keywords, but common synonyms and variations a user would actually say (setup, install, environment, repair) are absent, matching the score-3 anchor.

3 / 5

Distinctiveness Conflict Risk

Tying the trigger to the specific 'Compound Engineering' platform gives it a clear niche with only minor overlap risk against closely related CE skills, though the bare words 'health'/'config' are broad enough to keep it from a 5.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
EveryInc/compound-engineering-plugin
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.