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 a specific domain (Agent Skills Open Standard), lists concrete capabilities (schema, naming, directory structure, validation, authoring), and provides explicit trigger guidance with both a 'Use when' clause and a list of compatible agents. The description is concise, uses third person voice, and would be easily distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'frontmatter schema, naming rules, directory structure, progressive disclosure, validation, and authoring.' These are concrete, well-defined aspects of the skill 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'. Good coverage of agent names and the concept of portable/cross-agent skills. | 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 its specific domain and explicit mention of the standard name and URL. | 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 effectively teaches Claude how to create portable agent skills. Its strengths are strong actionability with concrete examples and excellent progressive disclosure. The main weaknesses are moderate verbosity (rationale annotations in best practices, some explanatory content Claude doesn't need) and a lack of explicit workflow sequencing for the skill creation process.
Suggestions
Remove the '**Reason:**' annotations from the authoring best practices list — Claude can infer why these matter, and the rationales nearly double the section's token count.
Add a brief numbered workflow for creating a new skill (e.g., 1. Create directory, 2. Write frontmatter, 3. Write body, 4. Run `skills-ref validate`, 5. Fix issues, 6. Re-validate) to improve workflow clarity with an explicit feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary content. The portable vs Claude Code comparison table is useful but lengthy, and some sections like 'Description Guidelines' explain things Claude already understands (third person writing, gerund forms). The authoring best practices section includes rationale explanations that add bulk without proportional value. | 2 / 3 |
Actionability | Provides concrete, executable guidance throughout: exact YAML frontmatter examples, directory structures, validation commands (both CLI and Python API), name validation rules with valid/invalid examples, and copy-paste ready code snippets for the skills-ref library. | 3 / 3 |
Workflow Clarity | The skill describes a reference/specification rather than a multi-step workflow, but the authoring process is only loosely sequenced. The validation section provides commands but doesn't integrate them into a clear create-validate-fix feedback loop. The 'Authoring Best Practices' lists principles but doesn't sequence them into a workflow with checkpoints. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure. The SKILL.md serves as a clear overview with well-signaled one-level-deep references to `references/specification.md`, `references/best-practices.md`, and `references/integration.md`. Content is appropriately split between the overview and detailed reference files, with external links for further exploration. | 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
b9f32ec
- 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.