CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skills-and-instructions

Design, write, and maintain skills and agent instructions. Use when the user asks to create, revise, evaluate, or troubleshoot skills or agent instructions, including investigating selection behavior to improve the guidance and deciding where guidance belongs.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

An unusually strong instruction-only skill: lean prose carrying non-obvious judgment, a concrete collaborative workflow with explicit validation and regression feedback, and a well-structured bundle where every reference is real and conditionally signaled. The only gap is the absence of worked examples (e.g. a before/after description rewrite) that would make the abstract guidance fully concrete.

DimensionReasoningScore

Conciseness

The body is dense judgment with no padding: it never explains what a skill or frontmatter is, never restates the obvious, and every rule carries a reason ("This gives future agents a useful action to take and a principle they can apply to new cases"). It assumes Claude's competence throughout, matching the 5 anchor ("every token earns its place") rather than the 4 anchor's trimmable over-explanation.

5 / 5

Actionability

Mostly concrete: an executable symlink command, exact file paths (".agents/skills/<name>/SKILL.md"), precise formatting directives ("Put the **Current** wording in a blockquote and the **Proposed** wording in a copyable writing block"), and stepwise description rules ("Begin the second sentence with 'Use when'"). It falls short of the 5 anchor's "specific examples cover the common cases" because several passages (e.g. "Find the instruction's owner") give decision rules without a worked example showing them applied.

4 / 5

Workflow Clarity

The "Shape a change together" section is a clear numbered sequence whose step 4 is an explicit assembly check ("Read the assembled whole. Check it against the intended behavior and for clarity, repetition..."), and the "Check what changed" section adds targeted validation ("Check affected links after moving references; check frontmatter and intended-host discovery after changing skill names") plus an error-recovery loop ("When behavior is uncertain or regresses, compare actual work with the previous version"). This matches the 5 anchor's sequence + validation + feedback-loop pattern.

5 / 5

Progressive Disclosure

Scored against the actual bundle: both referenced files (references/evaluation.md, references/composition-audit.md) exist, contain real content, and are linked with concrete read conditions ("Read [evaluation](references/evaluation.md) when investigating selection or behavior, comparing versions, or asked for evidence of improvement"); the scripts they invoke (run-trigger-eval.ts, audit-skill-links.ts, audit-routing-collisions.ts, skill-catalog.ts) all exist in scripts/. References are one level deep, the ~130-line core stays readable on its own, and the skill practices its own rule ("Link to a reference with a concrete reason to read it"), matching the 5 anchor.

5 / 5

Total

19

/

20

Passed

Description

87%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 model description for this rubric: a first-sentence capability statement followed by an explicit "Use when" clause with concrete user intents. It would both select correctly and stay distinct from neighboring skills; the only room to grow is adding a few more natural synonyms (file names like SKILL.md or CLAUDE.md) to the trigger set.

DimensionReasoningScore

Specificity

"Design, write, and maintain skills and agent instructions" plus the enumerated tasks ("create, revise, evaluate, or troubleshoot", "investigating selection behavior", "deciding where guidance belongs") list several specific actions with comprehensive coverage of the skill-authoring lifecycle. A notch below the 5 anchor because the verbs (design/write/maintain) are broader than the concrete manipulations in the top exemplar.

4 / 5

Completeness

Explicitly answers both questions: the first sentence states what it does ("Design, write, and maintain skills and agent instructions") and an explicit "Use when the user asks to create, revise, evaluate, or troubleshoot skills or agent instructions" clause gives concrete trigger phrases. This matches the 5 anchor's what-and-when-with-triggers structure exactly, and neither half is missing or vague.

5 / 5

Trigger Term Quality

Natural phrases users would say are present — "create, revise, evaluate, or troubleshoot skills or agent instructions", "selection behavior" — giving good keyword coverage. A few natural terms a user might say are missing (e.g. "SKILL.md", "CLAUDE.md/AGENTS.md", "prompts", "description/frontmatter"), so it falls between the 3 and 5 anchors, clearly above the midpoint.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche — authoring and maintaining skills/agent instructions — with triggers ("skills", "agent instructions", "selection behavior", "where guidance belongs") that few other skills would claim. This mirrors the 5 anchor's clear-niche/minimal-conflict pattern rather than the 4 anchor, which requires noticeable overlap risk with closely related skills.

5 / 5

Total

18

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

EpicenterHQ/epicenter

Path

.agents/skills/skills-and-instructions/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.