agentskills
Agent Skills Open Standard reference (agentskills.io). Use when creating portable skills for Claude Code, Cursor, Gemini CLI, OpenAI Codex, VS Code, Roo Code, and 20+ compatible agents. Covers frontmatter schema, naming rules, directory structure, progressive disclosure, validation, and authoring. Load before creating cross-agent skills.
88
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 is a strong description that clearly identifies its niche (the Agent Skills Open Standard), lists specific capabilities it covers, names concrete tools/agents as trigger terms, and provides explicit 'Use when' guidance. It is concise, uses third-person voice, and would be easily distinguishable from other skills in a large collection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: frontmatter schema, naming rules, directory structure, progressive disclosure, validation, and authoring. These are concrete, identifiable aspects of the standard. | 3 / 3 |
Completeness | Clearly answers both what ('Agent Skills Open Standard reference covering frontmatter schema, naming rules, directory structure, progressive disclosure, validation, and authoring') and when ('Use when creating portable skills for Claude Code, Cursor, Gemini CLI... Load before creating cross-agent skills'). | 3 / 3 |
Trigger Term Quality | Includes highly natural trigger terms users would say: 'portable skills', 'Claude Code', 'Cursor', 'Gemini CLI', 'OpenAI Codex', 'VS Code', 'Roo Code', 'cross-agent skills', 'agentskills.io', 'frontmatter schema'. Good coverage of tool names and concepts users would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche — specifically about the Agent Skills Open Standard (agentskills.io) for cross-agent portable skill authoring. Very unlikely to conflict with other skills given the specific standard name and the enumerated compatible agents. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%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-structured reference skill that provides concrete, actionable guidance for creating portable agent skills. Its main strengths are excellent progressive disclosure, thorough field references, and executable validation examples. Its weaknesses are moderate verbosity in the authoring best practices section and the lack of an explicit step-by-step authoring workflow with validation checkpoints integrated into the sequence.
Suggestions
Add an explicit numbered workflow for creating a new skill (e.g., 1. Create directory, 2. Write frontmatter, 3. Write body, 4. Run skilllint, 5. Fix issues, 6. Validate with skills-ref) with validation as a gate before completion.
Trim the 'Authoring Best Practices' section by removing the 'Reason:' explanations — these restate general agent design principles Claude already knows — and keep just the bolded principles with one-line guidance each.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some content Claude likely already knows (e.g., explaining what scripts, references, and assets directories are for). The field reference table and comparison table are useful but the authoring best practices section restates general principles with 'Reason:' explanations that add bulk without proportional value. | 2 / 3 |
Actionability | Provides concrete, executable examples throughout: exact YAML frontmatter blocks, directory structures, validation commands (both CLI and Python API), valid/invalid name examples, and good/weak description comparisons. The guidance is specific and copy-paste ready. | 3 / 3 |
Workflow Clarity | The skill describes a creation workflow implicitly (create directory, write frontmatter, add body, validate) but doesn't present it as a clear sequential process with explicit validation checkpoints. The validation section exists but isn't integrated into a step-by-step authoring workflow with feedback loops for fixing issues. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure: the SKILL.md provides a comprehensive overview with clear one-level-deep references to `references/specification.md`, `references/best-practices.md`, and `references/integration.md`. The content appropriately splits detailed material into separate files while keeping the main document navigable. | 3 / 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
- Jamie-BitFlight/claude_skills
- Commit
11ec483
- 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.