CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

editing-rules-and-skills

Use when editing or creating rules or skills (global or project). Routes to the correct voice and process based on whether the work is correction-driven (encoding a behavioral lesson) or informative (documenting a capability).

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/editing-rules-and-skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 well-written, lean router: it classifies the work into two clearly defined flavors, gives a concrete fallback question, and lists precise firing conditions and guardrails. Its critical weakness is that all three files it delegates its core content to (correction-driven.md, informative-capability.md, placement.md) are missing from the bundle, leaving the actual voice, process, and placement guidance unavailable.

Suggestions

Ship the three referenced files in the bundle (e.g., under references/): the body routes to correction-driven.md, informative-capability.md, and placement.md, but none exist, so the skill's core voice/process and placement guidance is unreachable.

Inline a one-or-two-line summary of each referenced file's key guidance (e.g., the headline rule for correction voice vs informative voice) so the skill remains actionable even when a reference fails to load.

Add a post-edit validation checkpoint to the workflow, such as re-reading the edited rule in its target file to confirm placement and voice, or confirming the landing location with Josh before finishing.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and explains nothing Claude already knows — sections carry real payload (classification criteria, concrete file paths, guardrails). One or two sentences are motivational rather than instructional ("classifying wrong is the single biggest way this skill gets misapplied", "The two flavors look superficially similar..."), keeping it at the 4 anchor's 'minor instances that could be trimmed' rather than the 5 anchor's every-token-earns-its-place.

4 / 5

Actionability

Concrete guidance exists — explicit classification criteria, a literal fallback question ("Is this you correcting a behavior, or you wanting me to know about a capability?"), and exact paths like `claude/CLAUDE.md` and `claude/agents/implementer.md` — but the core execution details (the voice and process for each flavor, placement rules) are deferred to `correction-driven.md`, `informative-capability.md`, and `placement.md`, none of which exist in the bundle. That matches the 3 anchor ('some concrete guidance but incomplete; missing key details') rather than the 4 anchor's minor gaps.

3 / 5

Workflow Clarity

The entry sequence is clear and ordered ("Before touching anything, identify which kind of work this is" → load the flavor-specific file → decide placement via `placement.md`), and there is one explicit checkpoint (ask Josh if unsure). But everything after the routing step is opaque because the referenced files are absent, and there is no validation of the edited artifact, fitting the 3 anchor ('sequence present but checkpoints missing or implicit') better than the 4 anchor's 'most checkpoints present'.

3 / 5

Progressive Disclosure

The SKILL.md itself is well structured with clear sections and one-level-deep, clearly signaled references ("Load **`correction-driven.md`** before editing"), which would suggest a 4. However, none of the three referenced files exist anywhere in the bundle (no references/ directory), so the disclosure chain is broken and the promised detail is unreachable — structure is present but incomplete, matching the 3 anchor.

3 / 5

Total

13

/

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 description: it explicitly states what the skill does and when to use it, defines its two classification categories concretely, and stays lean without buzzwords. Trigger coverage is good but misses a few natural phrasings users might use when asking for rules/skill documentation work.

DimensionReasoningScore

Specificity

The description names the domain ("editing or creating rules or skills") and several concrete actions — edit, create, and "Routes to the correct voice and process" — and concretely defines the two work categories ("correction-driven (encoding a behavioral lesson)" vs "informative (documenting a capability)"). It falls short of the 5 anchor because it doesn't enumerate the specific voice/process steps it routes to, but it lists more than the 1-2 actions of the 3 anchor.

4 / 5

Completeness

Both halves are explicit: what it does ("Routes to the correct voice and process based on whether the work is correction-driven... or informative") and when ("Use when editing or creating rules or skills (global or project)"). The 'when' clause is concrete and specific, so it does not fit the 4 anchor's 'when could be more explicit or specific'.

5 / 5

Trigger Term Quality

Natural keywords a user would say are present: "editing", "creating", "rules", "skills", "correction", "behavioral lesson", "documenting a capability". A few natural variants are missing (e.g., "updating", "document this so it doesn't happen again", "CLAUDE.md", "memory"), matching the 4 anchor's 'good coverage, a few natural terms missing' rather than the 5 anchor's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — editing the user's rules/skills infrastructure (CLAUDE.md rules, agent defs, skill files) — with distinctive triggers like "correction-driven" and "behavioral lesson". Minor overlap risk remains with generic documentation or writing skills, which fits the 4 anchor ('mostly distinct; minor overlap risk') better than the 5 anchor's minimal-conflict profile.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

joshmanders/dotfiles

Path

.claude/skills/editing-rules-and-skills/SKILL.md

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.