CtrlK
BlogDocsLog inGet started
Tessl Logo

agents-md

This skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent instructions concise. Enforces research-backed best practices for minimal, high-signal agent documentation.

73

Quality

91%

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

The canonical home for this skill is agents-md in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

92%Scale 1-3

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

This is a high-quality skill that practices what it preaches—it's concise, actionable, and well-structured documentation about writing concise, actionable documentation. The 'Before Writing' research checklist and anti-patterns section are particularly strong, giving Claude clear guardrails. The only minor weakness is that all content lives in one file, though for a skill of this size it's borderline acceptable.

DimensionReasoningScore

Conciseness

The skill is lean and efficient throughout. It uses headers, bullets, and code blocks with no unnecessary explanation. It trusts Claude's intelligence—no definitions of what AGENTS.md is or why conciseness matters beyond the one research-backed claim. Every section earns its place.

3 / 3

Actionability

Provides concrete, copy-paste-ready examples including exact commands (`ln -s AGENTS.md CLAUDE.md`), markdown templates for each required section, table formats, and a complete example structure. The 'Before Writing' checklist gives specific files to look for rather than vague guidance.

3 / 3

Workflow Clarity

The workflow is clearly sequenced: File Setup → Before Writing (research phase with 5 specific checks) → Writing Rules → Required Sections → Optional Sections → Anti-Patterns. For a documentation-creation skill, this is a non-destructive operation, so explicit validation checkpoints aren't critical, and the sequence is unambiguous.

3 / 3

Progressive Disclosure

The content is well-structured with clear headers and logical sections, but it's all inline in a single file. At ~90 lines of content, some sections (like the full example structure or the anti-patterns list) could be split into referenced files. However, the content is organized well enough that navigation is straightforward.

2 / 3

Total

11

/

12

Passed

Description

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

This description has strong trigger terms and completeness, clearly specifying when to use the skill with explicit quoted phrases. Its main weakness is that the 'what it does' portion is somewhat abstract—'enforces research-backed best practices' doesn't convey the concrete actions performed. The distinctiveness is excellent due to the narrow, well-defined niche of agent documentation files.

Suggestions

Replace 'Enforces research-backed best practices for minimal, high-signal agent documentation' with specific concrete actions, e.g., 'Generates, updates, and trims AGENTS.md files to keep instructions concise and actionable.'

DimensionReasoningScore

Specificity

The description mentions some actions like 'create AGENTS.md', 'update AGENTS.md', 'maintain agent docs', and 'keep agent instructions concise', but it doesn't list specific concrete actions the skill performs (e.g., what it actually does to the files). 'Enforces research-backed best practices' is somewhat vague about the actual operations.

2 / 3

Completeness

Explicitly answers both 'what' (enforces best practices for minimal, high-signal agent documentation) and 'when' (with a clear 'Use when' equivalent listing specific trigger phrases like 'create AGENTS.md', 'update AGENTS.md', etc.).

3 / 3

Trigger Term Quality

Includes strong natural trigger terms users would actually say: 'create AGENTS.md', 'update AGENTS.md', 'maintain agent docs', 'set up CLAUDE.md', and 'agent instructions'. These cover multiple natural phrasings and file name variations.

3 / 3

Distinctiveness Conflict Risk

Clearly targets a specific niche: AGENTS.md and CLAUDE.md agent documentation files. The specific file names and 'agent docs' terminology make it highly unlikely to conflict with general documentation or markdown skills.

3 / 3

Total

11

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.