CtrlK
BlogDocsLog inGet started
Tessl Logo

tc-tracker

Use when the user asks to track technical changes, create change records, manage TC lifecycles, or hand off work between AI sessions. Covers init/create/update/status/resume/close/export workflows for structured code change documentation.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

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.

A highly actionable, well-organized skill body with executable scripts, explicit validation, and clean one-level references. The only slack is minor redundancy between the validation-rules and anti-patterns sections.

Suggestions

De-duplicate the 'Validation Rules' list against the 'Anti-Patterns' table so each rule appears once, trimming token cost.

DimensionReasoningScore

Conciseness

Efficient and assumes competence throughout, with executable commands and tables rather than filler; minor overlap between the 'Validation Rules' list and the 'Anti-Patterns' table could be trimmed.

4 / 5

Actionability

Copy-paste-ready invocations for every workflow (tc_init/tc_create/tc_update/tc_status/tc_validator) with concrete flags and expected outputs, covering the common cases.

5 / 5

Workflow Clarity

Clear sequenced workflow (init -> create -> update -> status -> validate) with explicit validation checkpoints, schema/state-machine enforcement, atomic writes, and a validator feedback loop for recovery.

5 / 5

Progressive Disclosure

Overview-first body with well-signaled one-level-deep references (lifecycle.md, tc-schema.md, handoff-format.md), all of which exist in ./references/; detail is appropriately split out of SKILL.md.

5 / 5

Total

19

/

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, well-structured description that clearly states capabilities and explicit use-when triggers. It could improve by adding synonyms/file extensions and briefly disambiguating from adjacent changelog/debt-tracking skills.

Suggestions

Add a few natural synonyms or file cues (e.g. 'docs/TC/', JSON records) so users mention concrete artifacts.

Include a one-clause boundary note (e.g. 'Not for git-derived changelog or tech-debt items') to reduce overlap with related skills.

DimensionReasoningScore

Specificity

Lists several concrete actions ('track technical changes, create change records, manage TC lifecycles, or hand off work') plus eight named workflow subcommands (init/create/update/status/resume/close/export), with only minor abstraction in 'manage TC lifecycles'.

4 / 5

Completeness

Explicitly answers both 'what' ('structured code change documentation' covering named workflows) and 'when' ('Use when the user asks to...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('track technical changes', 'create change records', 'hand off work between AI sessions'), but relies on the 'TC' acronym and omits file extensions or common synonyms.

4 / 5

Distinctiveness Conflict Risk

The TC-record/session-handoff niche is mostly distinct, but 'technical changes'/'code change documentation' could overlap with changelog or tech-debt skills and the description itself does not state boundaries.

4 / 5

Total

17

/

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