This is a strong skill description that concisely covers specific actions (unpublish, remove dependencies, delete directory, clean topology, re-install), provides explicit trigger terms via a 'Use when' clause, and occupies a clear niche. It uses third person voice appropriately and avoids vague language or unnecessary verbosity.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: unpublish/delete from registry, remove dependencies, delete directory, clean topology references, re-install. These are detailed, actionable steps.	3 / 3
Completeness	Clearly answers both 'what' (fully delete a Tessl skill with specific steps) and 'when' (explicit 'Use when' clause with quoted trigger phrases).	3 / 3
Trigger Term Quality	Includes natural trigger terms users would actually say: 'delete skill', 'retire skill', 'remove skill', 'nuke skill'. These cover common variations of how a user would express wanting to fully remove a skill.	3 / 3
Distinctiveness Conflict Risk	Very specific niche: fully deleting/retiring a Tessl skill with registry and topology cleanup. The combination of 'Tessl skill' + 'delete/retire' + specific cleanup steps makes it highly distinct and unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Implementation

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, concise skill that clearly sequences a destructive multi-step operation with appropriate safety guardrails (confirmation requirement, inbound dependency check, fallback commands). The main weakness is that steps 3 and 5 lack the same level of concrete, executable detail as the other steps, leaving some ambiguity about exactly what to edit in tessl.json and brain-topology.md.

Suggestions

Add a concrete example or command for step 3 showing how to edit/remove the dependency entry from tessl.json (e.g., the JSON key to remove or a jq command).

Add a brief example for step 5 showing what a topology table entry and Prune Log entry look like after cleanup.

Dimension	Reasoning	Score
Conciseness	Every line serves a purpose. No unnecessary explanations of what deletion means or how registries work. The hard rules are essential safety constraints, and the steps are terse but complete.	3 / 3
Actionability	Provides concrete bash commands for registry removal, directory deletion, and grep-based reference checking. However, step 3 (remove dependency from tessl.json) and step 5 (clean topology references) lack specific commands or examples of what to edit, making them incomplete.	2 / 3
Workflow Clarity	Clear 7-step sequence with logical ordering (check dependencies first, then unpublish, then remove locally, then clean references, then verify). Includes explicit validation in step 7, user confirmation requirement in hard rules, and fallback paths for registry removal (unpublish → delete → archive).	3 / 3
Progressive Disclosure	Concise overview with a clear delegation to `tessl__skill-retirer-checklist` for detailed checklist, error recovery, and batch mode. For a skill of this size and scope, the single-level reference is appropriate and well-signaled.	3 / 3
	Total	11 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

2 days ago

Table of Contents

Discovery Implementation Validation