CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tlc-spec-lean

Spec-driven feature work that freezes obligations instead of the plan: one human-reviewed plan with EARS criteria, path, entities, interface and one-way doors, then proof-backed checks, then build, then an independent Verifier. Use when the user says "tlc-spec-lean", "plan feature", "specify feature", "write the checks", "build this plan", or "verify work". Do NOT use for standalone design documents unattached to a feature, architecture decomposition analysis, or work that already has a task list or checklist to execute.

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

An exceptionally well-structured process skill: every phase has a concrete script gate, artifacts have literal formats, and detail is cleanly deferred to existing one-level references. The only cost of its extreme compression is long multi-clause rules and slight overlap between the Rules section and the summary tables.

DimensionReasoningScore

Conciseness

The body is densely packed with operational content and explains nothing Claude already knows — e.g. rule 6 specifies proof formats in a single sentence, and "Run a script rather than read it: its messages say what to change" wastes no tokens. Not 5 because several rules run very long with stacked clauses and there is mild redundancy between the Rules section and the "Who checks what" table (rule 5 vs. the Verifier row, rule 9 vs. the screens row).

4 / 5

Actionability

Fully executable guidance: exact per-gate commands (`validate_checks.py <feature> --execute`, `check_commit.py --message "<msg>"`), a literal invocation convention (`python3 <skill-dir>/scripts/<name>.py` with `--root` and Windows fallbacks), and copy-paste-ready artifact formats (`Run <name>: <command>`, `Proof: run <name> | <line>`, `**Approved**: <date> - user: "<their words>"`, `<capture>.running.png`). Specific examples cover the common cases, matching the top anchor.

5 / 5

Workflow Clarity

The PLAN → CHECKS → BUILD → VERIFY sequence is diagrammed, tabulated per phase with its reference, and gated by scripts at every transition ("Before presenting the plan", "Before starting to build", "Before each commit", "Before declaring done"). Validation is explicit and machine-checked ("validate_verification.py exits 0", "A non-zero exit means stop and fix") with error-recovery feedback loops ("a red gate is said first", findings "closed by a commit"), matching the top anchor.

5 / 5

Progressive Disclosure

The body is a genuine overview: rules, tables, and an artifact tree, with per-phase details split into one-level-deep references (references/plan.md, checks.md, build.md, verify.md, verify-screens.md, memory.md) that all exist and point back to SKILL.md rather than nesting further. Scripts are likewise referenced by purpose, not inlined. Navigation is easy via the Phases and Scripts tables.

5 / 5

Total

19

/

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: concrete staged capabilities, explicit trigger phrases, and unusually good negative scoping that reduces conflict risk. The only weakness is mildly abstract framing language and a few missing natural synonyms ("spec", "define requirements").

DimensionReasoningScore

Specificity

Quotes several concrete actions — "one human-reviewed plan with EARS criteria, path, entities, interface and one-way doors, then proof-backed checks, then build, then an independent Verifier" — naming distinct deliverables per stage. Not 5 because the framing "freezes obligations instead of the plan" is abstract and the actions are process stages rather than fully concrete capabilities; not 3 because it clearly lists multiple specific actions, not just 1-2.

4 / 5

Completeness

Explicitly answers both what ("one human-reviewed plan with EARS criteria... then proof-backed checks, then build, then an independent Verifier") and when ("Use when the user says...") with concrete trigger phrases, and adds negative scope ("Do NOT use for standalone design documents..."). Clearly matches the top anchor; nothing missing on either axis.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say: "plan feature", "write the checks", "build this plan", "verify work", plus the explicit skill name "tlc-spec-lean". Not 5 because common variations like "spec", "write a spec", or "define requirements" are missing; not 3 because coverage goes well beyond one or two generic keywords.

4 / 5

Distinctiveness Conflict Risk

Clear niche — spec-driven feature work with an independent Verifier — with a distinct skill-name trigger and explicit exclusions ("Do NOT use for... architecture decomposition analysis, or work that already has a task list"), minimizing wrong-skill triggering. Neighboring anchor 4 would require some overlap risk, which the carve-outs eliminate.

5 / 5

Total

18

/

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

tech-leads-club/agent-skills

Path

packages/skills-catalog/skills/(development)/tlc-spec-lean/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.