CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tracker-discipline

Use when creating, decomposing, claiming, closing, or blocking on a work item (bead) — and whenever the words "deferred", "out of scope", or "follow-up" are about to leave your mouth. Defines bead anatomy for agent consumers, the standing meta-beads, follow-up capture, dependency hygiene, and the tracker as an inter-session message bus.

Quality

81%

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

71%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 unusually dense, high-signal process skill: nearly every sentence states a specific rule, check, or template, and validation checkpoints (`br ready --json`, the audit script, twice-verified structural claims) are woven throughout. The main weaknesses are a dangling script reference with no bundle behind it, inlined template content that belongs in a reference file, and anecdotal padding that could be tightened.

Suggestions

Ship the referenced scripts/tracker-audit.bb in a scripts/ directory (or drop the path from the Mechanical audit section) — the body instructs running a file that does not exist in the bundle.

Move the eight-section bead anatomy template (plus the Risk/DO NOT extensions) into a references/ file and keep a one-line summary in SKILL.md, shortening the main file and making the template directly linkable from other beads.

Trim the field-evidence anecdotes (the 92-bead port, the "slice 1.5" relocation) to a single clause each; the rules they justify are already self-contained.

DimensionReasoningScore

Conciseness

Dense, rule-per-sentence prose that assumes an intelligent reader ("the anti-NIH payload", "Negative results are the most expensive knowledge to regenerate"). Minor trimmable padding: the field-evidence anecdotes ("a 92-bead port closed 74 of them in four days", the "slice 1.5" relocation story) justify rules but run long.

4 / 5

Actionability

Gives concrete, executable guidance: specific checks ("retarget the dep to the specific sub-bead, verify with `br ready --json`"), a command (`scripts/tracker-audit.bb [issues.jsonl]`), and filled-in templates (FOUNDATION WARNING block, close-reason contents). Minor gap: the referenced audit script does not exist in the bundle, and quoted examples are illustrative rather than copy-paste ready.

4 / 5

Workflow Clarity

Each core procedure is clearly sequenced with checkpoints: the deferral rule (stop → search the tracker → create the bead → reference its id in the close-reason), dependency audit with `br ready --json` verification, and the mechanical audit with documented false-positive triage. Falls short of 5 because the skill is a set of parallel disciplines rather than one end-to-end workflow, and some checks (e.g., the twice-verified structural claim) describe the check without a command.

4 / 5

Progressive Disclosure

Well-sectioned with clear headers, but it is a ~175-line single file with the full bead-anatomy template inlined that could live in a reference file, and it cites "scripts/tracker-audit.bb" while no scripts/ directory exists in the bundle — a dangling reference. This matches the anchor of having structure with content that should be separate left inline.

3 / 5

Total

15

/

20

Passed

Description

83%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: it names concrete operations, defines its content scope, and gives unusually natural trigger phrases including the exact words that precede a deferral. Its only weaknesses are a second-person idiom in the trigger clause and a slight dependence on project jargon ("bead", "meta-beads") that the parenthetical only partially demystifies.

DimensionReasoningScore

Specificity

Enumerates five concrete operations ("creating, decomposing, claiming, closing, or blocking on a work item") plus the content it defines (bead anatomy, meta-beads, follow-up capture, dependency hygiene, message bus) — comprehensive coverage. One point deducted per the voice guideline for the second-person trigger phrasing "about to leave your mouth".

4 / 5

Completeness

Explicitly answers both: "Defines bead anatomy… follow-up capture, dependency hygiene, and the tracker as an inter-session message bus" (what) and "Use when creating, decomposing, claiming, closing, or blocking… and whenever the words 'deferred', 'out of scope', or 'follow-up'…" (when, with concrete trigger phrases).

5 / 5

Trigger Term Quality

Quotes natural phrases users actually say — "deferred", "out of scope", "follow-up" — plus "work item" and "tracker". A few natural synonyms (task, backlog, TODO, ticket) are missing, so it falls just short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche (bead/tracker discipline) with distinct triggers, but the broad deferral keywords ("out of scope", "follow-up") could fire on general task-management or scoping skills, giving minor overlap risk.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 possibly missing (scripts/tracker-audit.bb)

Warning

Total

15

/

16

Passed

Repository

igouss/gitweb-rs

Path

.claude/skills/tracker-discipline/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.