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.
86
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 stating when to use the skill with explicit trigger phrases. Its main weakness is that the 'what' portion is somewhat vague—it says it 'enforces research-backed best practices' without specifying what those practices are or what concrete actions the skill performs beyond creating/updating files.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates concise agent instruction files, removes redundant content, structures sections for tool usage and constraints' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
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 concrete specific capabilities beyond these. 'Enforces research-backed best practices for minimal, high-signal agent documentation' is somewhat vague about what those best practices entail. | 2 / 3 |
Completeness | The description 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 a user might mention. | 3 / 3 |
Distinctiveness Conflict Risk | The skill is clearly scoped to AGENTS.md and CLAUDE.md agent documentation files, which is a distinct niche. The specific file names and 'agent docs' terminology make it unlikely to conflict with general documentation or markdown skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that provides clear, actionable guidance for creating and maintaining AGENTS.md files. Its strengths are the concrete templates, specific commands, and logical workflow from analysis to writing. Minor weaknesses include some redundancy (the 'When to Use' section, verbose anti-patterns list) and the content being slightly longer than necessary for what could be a more concise instruction set.
Suggestions
Remove the 'When to Use' section since it duplicates the skill's frontmatter description and the 'Limitations' boilerplate which adds generic filler.
Condense the anti-patterns into a tighter bullet list or merge key points into the Writing Rules section to reduce overall length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and well-structured with headers and bullets, but includes some unnecessary content like the 'When to Use' section (which duplicates frontmatter description), and the anti-patterns section is somewhat verbose listing things that could be more concise. The 'Limitations' boilerplate at the end adds little value. | 2 / 3 |
Actionability | Provides concrete, executable guidance throughout: specific commands for symlink creation, exact markdown templates for each required section, a complete example structure, and specific file names to check for project analysis. The file-scoped commands table and commit attribution examples are copy-paste ready. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced: File Setup → Before Writing (analysis steps) → Writing Rules → Required Sections → Optional Sections → Anti-Patterns. For this type of skill (document creation, not destructive operations), the sequence is unambiguous and the 'Before Writing' analysis checklist serves as a validation step before content creation. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections, but everything is inline in a single file that runs fairly long (~100 lines of content). The example structure section could potentially be a separate reference file. However, there are no nested references and the organization is logical with clear headers. | 2 / 3 |
Total | 10 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
1a9f5ac
- 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.