CtrlK
BlogDocsLog inGet started
Tessl Logo

ce-setup

Check Compound Engineering health and repo-local config.

59

Quality

67%

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

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured, executable, and properly offloads detail to verified bundle files, with clear validation checkpoints on the riskier repair steps. The main weakness is verbosity in the complex repair sections, which could be condensed without losing clarity.

DimensionReasoningScore

Conciseness

The body is mostly action-oriented and avoids explaining concepts Claude already knows, but the dense prose in Steps 6a and 6b (e.g. detailing every docs_root fallback layer) could be tightened, fitting "mostly efficient but includes some unnecessary explanation" rather than the every-token-earns-its-place level 3.

2 / 3

Actionability

It provides copy-paste-ready executable bash throughout (the SKILL_DIR guard snippet, `git rev-parse`, `command -v`, `git check-ignore -q`, the .gitignore entry, and copy commands) with an explicit inline fallback when the bundled script is missing, matching "fully executable code/commands; copy-paste ready".

3 / 3

Workflow Clarity

The flow is sequenced into Phase 1/2/3 with numbered steps and explicit validation feedback loops ("Re-run the health check and require it to report…" in 6a and 6b, plus the Phase 1 gate), so destructive/batch operations are guarded rather than left unvalidated.

3 / 3

Progressive Disclosure

SKILL.md is an overview that delegates the heavy health logic to the bundled `scripts/check-health` and the config template to `references/config-template.yaml` — both real, one-level-deep, clearly signaled references — keeping the body navigable rather than monolithic.

3 / 3

Total

11

/

12

Passed

Description

50%Weight 40%Scale 1-3

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 is accurate and product-specific but thin: it states a single action and domain with no explicit trigger guidance, capping several dimensions at 2. Adding a "Use when…" clause and more concrete verbs would lift specificity, trigger quality, and completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when setting up or troubleshooting Compound Engineering in a repo, or when CE artifacts are not landing where expected."

Expand the single verb into concrete actions, e.g. "Checks Compound Engineering environment health, refreshes repo-local config, and repairs invalid docs_root or work-engine settings."

Replace jargon-only phrasing with natural user terms ("setup", "install", "configure") so the description matches what a user would actually say.

DimensionReasoningScore

Specificity

"Check Compound Engineering health and repo-local config" names a concrete domain and one action, but the single verb "Check" leaves capabilities non-comprehensive, matching the "names domain and some actions" anchor rather than the multi-action level 3.

2 / 3

Completeness

The description answers "what" but contains no "Use when…" clause or equivalent trigger guidance, so per the rubric completeness is capped at 2 even though the what is clear.

2 / 3

Trigger Term Quality

It surfaces "Compound Engineering", "health", and "config", but leans on jargon like "repo-local config" and omits common user variations such as "setup", "install", or "configure", fitting "some relevant keywords but missing common variations" rather than full natural-term coverage.

2 / 3

Distinctiveness Conflict Risk

The Compound Engineering framing carves a niche, but the absence of distinct triggers and the existence of a CE skill family mean it could still overlap with sibling skills, matching "somewhat specific but could still overlap".

2 / 3

Total

8

/

12

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.