CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

completion-check

Completion Check: Verify Infrastructure Is Wired

Quality

57%

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 ./.claude/skills/completion-check/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 body is a well-structured, actionable instruction skill: numbered checks with concrete bash commands, a DON'T list, and a completion checklist give clear execution guidance. Its main weakness is token efficiency — a concept re-explanation and session-specific sections add tokens without reusable value, and one code example (the ast-grep dead-code search) is not actually executable.

Suggestions

Remove the "Pattern" concept explanation (Claude already knows that untested/unwired code isn't complete) and the session-specific "Source Sessions" section; the DO/DON'T/checklist already carry the guidance.

Fix or replace the orphaned-implementation search: the `ast-grep --pattern 'async function $NAME() { $$$ }' | xargs -I {} grep -r "{}" src/` pipe won't work because ast-grep emits `file:line:match` lines, not bare names — use a targeted, tested command or drop the step.

Generalize the end-to-end step's placeholder (`uv run python -m my_feature`) into a concrete, adaptable recipe, and add a brief "if the check fails" recovery note to close the workflow-clarity gap.

DimensionReasoningScore

Conciseness

The "Pattern" section re-explains a concept Claude already knows ("Infrastructure is not done when the code is written - it's done when it's wired... Dead code... is wasted effort"), and the "Source Sessions" section ("This session: Architecture gap discovery - DAG built but not wired...") is session-specific clutter with no reusable value. This is more than the "minor instances" of anchor 4, but the DO/DON'T/checklist core is efficient, so it sits at anchor 3.

3 / 5

Actionability

Steps ship concrete, mostly executable commands (e.g., `grep -r "claude -p" src/`, `ls -la .claude/hooks/my-hook.sh`, the debug-log then trigger then `cat /tmp/debug.log` loop). Minor gaps: the `ast-grep --pattern ... | xargs -I {} grep -r "{}" src/` pipe is not sound as written (ast-grep emits `file:line:match`, not bare function names), and `uv run python -m my_feature` is a placeholder, so it stops short of anchor 5's copy-paste-ready coverage.

4 / 5

Workflow Clarity

Five clearly sequenced numbered steps plus an explicit validation mechanism — the "Completion Checklist" ("Before declaring infrastructure complete" with checkboxes) and a step-4 end-to-end verification. Not a destructive/batch skill, so no cap applies; it falls short of anchor 5 only because there is no error-recovery/feedback-loop guidance for what to do when a check fails.

4 / 5

Progressive Disclosure

A single-file skill with no bundle files and well-organized sections (Pattern / DO / DON'T / Checklist / Example) with no nested references. Minor placement gaps — the project-specific "Example: DAG Task Graph" and the "Source Sessions" section are session artifacts that dilute the general overview, keeping it at anchor 4 rather than 5.

4 / 5

Total

15

/

20

Passed

Description

28%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 is a bare title that neither conveys concrete capabilities nor provides any trigger guidance for when to use it. Users searching for this skill's actual concerns (dead code, unwired hooks, end-to-end verification) would not find it. It needs a rewritten description listing what it checks and a "Use when..." clause.

Suggestions

List the concrete capabilities in the description, e.g., "Traces execution paths to find dead code, verifies hooks are registered in settings, confirms the right database backend, and runs end-to-end tests before declaring infrastructure complete."

Add an explicit trigger clause, e.g., "Use when building infrastructure, wiring new components into the system, or before marking infrastructure/feature work as complete."

Include natural user phrases like "dead code", "wired in", "actually called", and "end-to-end test" so the skill matches how users express the underlying problem.

DimensionReasoningScore

Specificity

"Verify Infrastructure Is Wired" names a domain but gives only one generic action; no concrete capabilities like tracing execution paths, checking hook registration, or running end-to-end tests are mentioned. It falls below anchor 3, which requires 1-2 concrete actions, and above anchor 1 because a domain is at least named.

2 / 5

Completeness

The description is a vague title-style "what" ("Verify Infrastructure Is Wired") with no "when" or "Use when..." clause at all, which also triggers the completeness cap of 3. It matches anchor 2 ("Has a vague 'what' and no 'when'") — not 3, which requires a clear "what".

2 / 5

Trigger Term Quality

Only "Completion Check" and "infrastructure" appear — one or two generic keywords, with none of the natural phrases a user would say when needing this skill (e.g., "is my code actually wired up", "verifying setup", "dead code"). Missing common variations keeps it at anchor 2 rather than 3.

2 / 5

Distinctiveness Conflict Risk

"Completion Check" is a somewhat distinctive name, but "verify infrastructure" is broad and could overlap with CI/CD, testing, and general dev-infrastructure skills. Anchor 3 ("somewhat specific but could still overlap with similar skills") fits better than anchor 4, which requires only minor overlap risk.

3 / 5

Total

9

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

parcadei/Continuous-Claude-v3

Path

.claude/skills/completion-check/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.