CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-methodology

A rigorous 10-step methodology for creating expert-level Claude skills. Use when developing new skills that require deep domain expertise, when existing skills feel like 'instruction manuals' rather than expertise transfer, or when skills need systematic quality improvement. Implements the 4 Core Truths: Expertise Transfer (not instructions), Flow (not friction), Voice Matches Domain, and Focused Beats Comprehensive.

Quality

73%

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 ./SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

A genuinely useful, opinionated methodology with concrete worksheets, checklists, and feedback loops — the expertise-transfer intent is realized in the writing style itself. Its weaknesses are structural rather than conceptual: repeated restatement of the same four principles, a 9-step process labeled as 10, and a bundle whose referenced paths and orphaned files don't line up with the SKILL.md.

Suggestions

Fix the bundle linkage: create (or remove references to) templates/SKILL-TEMPLATE.md and worksheets/exploration-log.md, and add explicit links from SKILL.md to the existing but currently orphaned references/anti-patterns.md, references/transformation-examples.md, and scripts/validate_skill.py.

Correct the '10-Step Process' heading (and frontmatter description) to match the 9 steps actually defined, or add the missing 10th step.

Consolidate the 4 Core Truths: keep the opening table and one deep treatment (e.g., the Step 5 BAD/GOOD examples), and cut the redundant Anti-Patterns table / Quick Reference restatements or fold them into the existing reference files.

Update the Directory Structure diagram to list the actual bundle files instead of examples.md and edge-cases.md, so it serves as accurate navigation.

DimensionReasoningScore

Conciseness

The body is mostly efficient — no explaining of concepts Claude already knows, and the BAD/GOOD contrast blocks earn their tokens — but the 4 Core Truths are restated four times (opening table, Step 5 example blocks, Anti-Patterns table, Quick Reference questions), which is more than the 'minor instances' of anchor 4. It stays above anchor 2 because each restatement adds a different framing and no section is pure padding.

3 / 5

Actionability

Guidance is mostly executable for an instruction-only skill: fill-in worksheets (Skill Definition Worksheet, Synthesis Output), concrete BAD/GOOD examples, a checkbox quality checklist, and a numbered test protocol. It misses anchor 5 because two key steps point to files that do not exist in the bundle ('Use the template at templates/SKILL-TEMPLATE.md' and 'Record failures in worksheets/exploration-log.md'), leaving those steps without their promised material.

4 / 5

Workflow Clarity

The phases and steps are clearly sequenced with real validation checkpoints and feedback loops (Step 6 checklist, Step 7 gap analysis against Step 2 failures, Step 8 test-then-update cycle). It misses anchor 5 because the headline says 'The 10-Step Process' while only 9 steps are defined (Steps 1–9), an internal inconsistency that undermines the sequence's precision.

4 / 5

Progressive Disclosure

The SKILL.md body itself is well-sectioned and appropriately sized, and one reference is real and clearly signaled ('references/quality-checklist.md'). But bundle navigation is misaligned: 2 of 3 referenced paths (templates/SKILL-TEMPLATE.md, worksheets/exploration-log.md) don't exist, 3 of the 4 actual bundle files (anti-patterns.md, transformation-examples.md, scripts/validate_skill.py) are never mentioned, and the Directory Structure diagram shows files (examples.md, edge-cases.md) that aren't the real ones.

3 / 5

Total

14

/

20

Passed

Description

70%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 well-structured description with an explicit multi-condition 'Use when' clause and a clearly stated purpose. Its main weaknesses are action-level specificity — the methodology's steps are summarized rather than named — and trigger conditions that are somewhat abstract compared to natural, concrete phrasings.

Suggestions

Enumerate one or two concrete capabilities in the description (e.g., 'Diagnose why a skill reads like an instruction manual and rebuild it as expertise transfer') so the 'what' goes beyond naming the methodology.

Add natural trigger variations users would actually type, such as 'writing a skill', 'authoring SKILL.md', or 'reviewing/improving an existing skill', to broaden keyword coverage.

Tighten the third trigger condition ('when skills need systematic quality improvement') to a more concrete scenario, e.g., 'when a skill works but output feels generic or mechanical'.

DimensionReasoningScore

Specificity

The description names the domain ('creating expert-level Claude skills') and the deliverable ('A rigorous 10-step methodology', 'Implements the 4 Core Truths') but never enumerates concrete actions the way anchor-5 examples do (extract, fill, merge). It sits above anchor 2 because the methodology and the four named principles are concrete, but below anchor 4 because the actual steps/capabilities are not listed.

3 / 5

Completeness

Both parts are explicit: the 'what' ('A rigorous 10-step methodology for creating expert-level Claude skills') and a three-condition 'Use when...' clause. Falls short of anchor 5 because the trigger conditions lean abstract ('require deep domain expertise', 'systematic quality improvement') rather than the concrete, sayable trigger phrases in the anchor-5 example.

4 / 5

Trigger Term Quality

Natural trigger phrases are present — 'Use when developing new skills', "when existing skills feel like 'instruction manuals'", 'when skills need systematic quality improvement' — phrases a user plausibly would say. Not anchor 5 because common variations like 'writing/authoring skills', 'creating a SKILL.md', or 'skill quality' phrasing are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — building Claude skills specifically — and the distinctive trigger about skills that 'feel like instruction manuals rather than expertise transfer' is unlikely to fire for unrelated skills. Not anchor 5 because it could overlap with other generic skill-authoring or prompt-engineering skills given the breadth of 'systematic quality improvement'.

4 / 5

Total

15

/

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

KennethJefferson/templates-skills-cc-10step4core

Path

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.