CtrlK
BlogDocsLog inGet started
Tessl Logo

agents-md

Use when reviewing, creating, shrinking, or refactoring AGENTS.md agent instructions, agent config files, routing rules, or repository guidance that need scoped routing, dedupe, contradiction fixes, progressive disclosure, and cleaned instruction surfaces.

64

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

70%

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

A well-structured, validation-aware instruction skill with clear sequencing and good progressive disclosure. It is held back by repeated preservation-contract restatements and unexplained domain jargon that weakens conciseness and actionability.

Suggestions

State the memory/handoff/validation/approval/security preservation contract once (e.g. in Constraints) and reference it from other sections instead of restating it verbatim six times.

Define or replace opaque terms in Workflow step 5 ("steering-uptake mechanisms", "systems-thinking mechanisms", "zero-setup setup") with concrete, recognizable guidance or link to where each is defined.

DimensionReasoningScore

Conciseness

The body is terse and avoids explaining concepts Claude already knows, but the memory/handoff/validation/approval/security preservation rule is restated roughly six times across Avoid, Workflow (steps 6 and 9), Constraints, Failure Mode, and Anti-Patterns, and could be consolidated.

2 / 3

Actionability

Concrete commands exist ("rg --files", "rg -n \"<command|path|handle>\" .", "pwd") and steps are specific, but workflow step 5 leans on unexplained jargon ("steering uptake", "systems-thinking mechanisms", "zero-setup setup") that is not executable without definitions.

2 / 3

Workflow Clarity

A numbered 10-step Workflow is clearly sequenced, with an explicit Validation section, a fail-fast checkpoint ("stop at first failed gate"), and a fix-and-rerun feedback loop for the destructive shrink/delete operations.

3 / 3

Progressive Disclosure

A dedicated Progressive Disclosure section signals one-level-deep references to verified real files (references/agents-md-guidance.md, references/discovery-interview.md) and defers other bundle files to on-demand loading.

3 / 3

Total

10

/

12

Passed

Description

85%

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, trigger-led description with concrete actions and a clear AGENTS.md niche. Its main weakness is trigger-term quality diluted by internal jargon and missing common user phrasings.

Suggestions

Trim internal jargon ("scoped routing", "progressive disclosure", "cleaned instruction surfaces") from the description and keep only terms a user would actually say.

Add common natural variations such as "clean up", "simplify", or "AGENTS file" alongside "shrinking/refactoring" to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "reviewing, creating, shrinking, or refactoring" plus "scoped routing, dedupe, contradiction fixes, progressive disclosure, and cleaned instruction surfaces" — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Opens with an explicit "Use when ..." trigger (the when) and names the actions and needs addressed (the what), satisfying both halves with an explicit trigger clause.

3 / 3

Trigger Term Quality

Natural verbs (reviewing, shrinking, refactoring) tied to "AGENTS.md" are present, but the second half leans on internal jargon ("scoped routing", "progressive disclosure", "cleaned instruction surfaces") users would not naturally say, and common phrasings like "clean up"/"simplify" are absent.

2 / 3

Distinctiveness Conflict Risk

Scoped to a distinct artifact (AGENTS.md / agent instruction files) with action-specific triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository
jscraik/Agent-Skills
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.