CtrlK
BlogDocsLog inGet started
Tessl Logo

disable

Disable a community skill installed through the hub without removing its files. Use when the user wants to temporarily quiet a community skill ("disable [skill]"), stop its hooks from firing while keeping its config, or re-enable a previously disabled skill.

70

Quality

86%

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

72%Weight 40%Scale 1-3

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

A well-organized, concise body that delegates the real workflow to a clearly signaled reference skill. It is concrete on safety and file targets but lacks an explicit post-rename verification step and inlines the mechanics only at a summary level.

Suggestions

Add an explicit verification step after renaming (e.g., confirm SKILL.md is gone and SKILL.md.disabled exists, and that hooks no longer fire) to turn the destructive workflow into a validate→fix→retry loop and lift workflow_clarity.

Either inline the concrete rename commands the skill-manager workflow runs, or add a one-line summary of the actual shell steps so the body is closer to copy-paste ready rather than redirecting to the reference.

State what Claude should do if the named skill is not found in the install log (e.g., abort and report) so the safety-rule path has a complete failure branch.

DimensionReasoningScore

Conciseness

Lean ~38-line body with no concept explanations Claude already knows; every line (rename targets, log path, safety rules) earns its place, matching the lean/efficient anchor.

3 / 3

Actionability

Names concrete file renames (SKILL.md → SKILL.md.disabled, hooks.json → hooks.json.disabled) and an exact log path, but defers the executable mechanics to "Run the disable workflow from the skill-manager reference skill," so guidance is concrete but incomplete rather than copy-paste ready.

2 / 3

Workflow Clarity

Steps and an explicit "Confirm before renaming ... get explicit yes" checkpoint are present, but for a destructive/reversible rename operation there is no verify-after feedback loop, which caps clarity at 2 per the destructive-operations guideline.

2 / 3

Progressive Disclosure

A simple under-50-line, single-purpose skill with well-organized sections and one clearly signaled one-level-deep reference (skill-manager), so it qualifies for the simple-skill exception with no nested references.

3 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 tight, third-person description that pairs concrete actions with explicit "Use when" triggers and a well-bounded scope. It avoids fluff and over-claims while remaining distinctive.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Disable a community skill ... without removing its files", "stop its hooks from firing while keeping its config", and "re-enable a previously disabled skill" — matching the multi-action anchor rather than the single-domain level 2.

3 / 3

Completeness

Explicitly answers what (disable/re-enable without removing files) and when, with a clear "Use when..." clause covering three trigger scenarios, so it is not capped at 2 by a missing trigger clause.

3 / 3

Trigger Term Quality

Includes natural phrasing users would say ("disable [skill]", "temporarily quiet a community skill", "stop its hooks", "re-enable"), giving good coverage of natural terms rather than the partial set at level 2.

3 / 3

Distinctiveness Conflict Risk

Scoped to "community skill installed through the hub" with distinct disable/quiet/re-enable triggers, occupying a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
anthropics/claude-for-legal
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.