tc

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/tc/SKILL.md

Quality

Content

82%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 tight, highly actionable command dispatch with executable scripts, validation checkpoints, and sensible deferral of detail to a related skill. Main gaps are a couple of missing validation steps and minor trims.

Dimension	Reasoning	Score
Conciseness	The dispatch is lean — executable bash, numbered steps, terse iron rules — with only minor trimmable prose such as 'There is no automatic HTML export in this skill.'	4 / 5
Actionability	Every subcommand ships a fully executable, copy-paste-ready command with complete flags, covering the common cases concretely.	5 / 5
Workflow Clarity	Sequences are clear with explicit validation checkpoints (non-zero exit surfaces the error and stops; close verifies 'tested'; export re-validates), but a few subcommands like resume lack an explicit validate/feedback step.	4 / 5
Progressive Disclosure	A well-sectioned overview defers the full schema/lifecycle to the engineering/tc-tracker skill and lists related skills one level deep; no bundle files exist in this skill, and minor organization gaps remain.	4 / 5
	Total	17 / 20 Passed

Description

58%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 conveys a clear, specific purpose with concrete mechanisms and a command surface, but it lacks an explicit 'Use when…' trigger clause and leans on technical terms over natural synonyms. Adding trigger phrases would lift completeness and trigger-term quality.

Suggestions

Append a 'Use when…' clause naming natural triggers, e.g. 'Use when tracking a technical change across sessions, recording status transitions, or handing off in-progress work.'

Broaden trigger terms with synonyms users actually say ('track changes', 'change log per change', 'pick up where I left off', 'approval workflow').

Reframe 'state machine' and 'session handoff' in plainer language alongside the technical terms to improve naturalness without losing specificity.

Dimension	Reasoning	Score
Specificity	Names the domain plus three concrete mechanisms ('structured records, a state machine, and session handoff') and enumerates the subcommand surface, listing several specific actions with only minor coverage gaps.	4 / 5
Completeness	The 'what' is clear, but there is no 'Use when…' trigger clause — only a 'Usage:' syntax line — so per the guideline missing explicit trigger guidance caps completeness at 3.	3 / 5
Trigger Term Quality	'Track technical changes' is a natural phrase, but terms like 'state machine' and 'session handoff' skew technical and common synonyms/variations are absent.	3 / 5
Distinctiveness Conflict Risk	The TC-tracking-via-state-machine niche is distinct with clear triggers; only minor overlap risk with adjacent changelog or tech-debt skills.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

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

Reviewed: ~17 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.