Name: tc-tracker
Rating: 68 (1 reviews)
Author: alirezarezvani

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.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is tc-tracker in alirezarezvani/claude-skills

Quality

Content

75%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 highly actionable with concrete commands and clear validation, and it uses one-level-deep references well. The main weaknesses are repeated validation content across sections and an implicit rather than explicit retry loop.

Suggestions

Consolidate the validation/atomic-write/sequential-ID rules into one canonical section and have other sections link to it instead of restating them in the update, validator, and anti-patterns areas.

Add an explicit validate→fix→retry step in the workflow (e.g., after tc_update or before close: run tc_validator.py, if it fails fix the record and re-run) to surface the error-recovery loop.

Move the full handoff field enumeration into references/handoff-format.md and keep only a brief pointer in SKILL.md to avoid duplicating that detail inline.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of basic-concept padding, but the validation/atomic-write/sequential-ID rules are restated across the update section, the validator section, the 'Validation Rules' list, and the Anti-Patterns table, which could be consolidated.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands for every workflow (tc_init, tc_create, tc_update, tc_status, tc_validator) with real flags and concrete examples covering common cases.	5 / 5
Workflow Clarity	Numbered workflows are clearly sequenced with validation checkpoints (state machine, validator, atomic writes) and an 8-rule checklist, but an explicit validate→fix→retry feedback loop is not spelled out in the main workflow steps.	4 / 5
Progressive Disclosure	SKILL.md acts as an overview with well-signaled one-level-deep references (lifecycle.md, tc-schema.md, handoff-format.md), but the inlined validation rules and handoff-field list partially duplicate the referenced files, a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

92%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 strong: it states concrete capabilities, gives an explicit 'Use when' trigger clause, and carves out a distinct niche. The only minor gap is trigger-term synonym breadth.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'track technical changes, create change records, manage TC lifecycles, hand off work' plus 'init/create/update/status/resume/close/export workflows' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both what ('structured code change documentation' via named workflows) and when (a 'Use when the user asks to...' clause with concrete trigger phrases).	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('track technical changes', 'create change records', 'hand off work between AI sessions') but misses some synonyms and has no file-extension cues, so a few natural terms are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (TC records, lifecycle state machine, AI session handoff) with distinct triggers and minimal overlap with sibling skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 6 missing	Warning
referenced_paths_exist	Referenced path issues: 21 missing	Warning

	Total	14 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/tc-tracker/SKILL.md
Commit: 19392f7

Reviewed: ~5 hours ago

Table of Contents

Discovery Implementation Validation

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.