Agent Skills
Curated collection of AI agent skills for Hermes and other agent frameworks
magnus919 · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add magnus919/agent-skills技能说明
name: agent-skills description: >- Use this skill when creating, reviewing, or editing Agent Skills-format skills, or when implementing skill discovery and loading in an agent client. It covers directory structure, SKILL.md metadata, progressive disclosure, evals, and repository conventions. Do not use this skill for general software work that does not involve the Agent Skills format or lifecycle. license: MIT
Agent Skills Standard Reference
This skill documents the Agent Skills open format — a standardized way to give AI agents new capabilities and expertise. Follow this workflow when creating or editing skills in this repository.
Authoritative source: agentskills.io/specification. The bundled specification is a working snapshot; check the authoritative source when currentness matters.
Directory Structure
A skill is a directory containing, at minimum, a SKILL.md file:
skill-name/
├── SKILL.md # Required: metadata + instructions
├── evals/ # Required for new skills in this repository
├── scripts/ # Optional: executable code
├── references/ # Optional: documentation
├── assets/ # Optional: templates, resources
└── ... # Any additional files or directories
Required Workflow
Create or edit a skill
- Read the specification before changing
SKILL.mdmetadata or directory structure. - Ground instructions in real domain knowledge, project artifacts, and observed failure modes. Read best practices when designing or materially revising instructions.
- Keep the skill a coherent, triggerable unit. Put only essential instructions in
SKILL.md; put conditional detail in focused reference files and state exactly when to read each one. - Use a precise
descriptionthat says what the skill does, when it applies, and when it does not apply. For skills with meaningful overlap, name the nearest alternative or prerequisite in a## When not to usesection. Test the boundary with at least three should-trigger prompts and two should-not-trigger near-misses; keep these harness-specific trigger checks separate from portable output-quality evals. Read optimizing descriptions for trigger design. - For every new skill, create
evals/evals.jsonwith at least five representative output-quality cases. Each case needs a realistic prompt, an expected outcome, and observable assertions. Include edge cases that exercise risky or ambiguous behavior. Read evaluating skills for the eval format and iteration workflow. - When bundling executable code, read using scripts. Document prerequisites and non-interactive invocation in the skill.
- Before handoff, run the validation checks in this skill and correct every finding.
Review a skill
- Validate the required frontmatter, field constraints, parent-directory/name match, and YAML syntax against the specification.
- Check that the description has both positive and negative trigger boundaries, the workflow is actionable, and resource references are conditional and reachable.
- Check that any script has documented dependencies, safe non-interactive inputs, clear errors, and structured output where useful.
- For this repository, also verify its required human-facing
README.md: title, Why Install This Skill, What You Get, Quick Start (unless genuinely reference-only), Triggers, and Requirements. Keep it human-facing, concise, and free of agent-only instructions. - Verify every new skill has
evals/evals.jsonwith at least five output-quality cases, and check that their expected outcomes and assertions test meaningful behavior. For an existing skill without evals, flag the gap but do not block the review solely for that legacy absence. Read evaluating skills before declaring the work complete.
Client implementation work
When implementing skill discovery, activation, or context management in an agent product, read client implementation guidance. Do not apply client conventions such as search paths as universal format requirements.
SKILL.md Format
The SKILL.md file must contain YAML frontmatter followed by Markdown body content.
Frontmatter Fields
| Field | Required | Constraints |
|---|---|---|
name | Yes | Max 64 chars. Lowercase letters, numbers, and hyphens only. Must not start or end with a hyphen. Must match the parent directory name. |
description | Yes | Max 1024 chars. Non-empty. Describes what the skill does and when to use it. |
license | No | License name or reference to a bundled license file. |
compatibility | No | Max 500 chars. Indicates environment requirements. |
metadata | No | Arbitrary key-value mapping. |
allowed-tools | No | Space-separated string of pre-approved tools. (Experimental) |
name field rules
- 1–64 characters
- Only lowercase unicode alphanumeric (
a-z,0-9) and hyphens (-) - Must not start or end with a hyphen
- Must not contain consecutive hyphens (
--) - Must match the parent directory name
description field rules
- 1–1024 characters
- Should describe both what the skill does and when to use it
- Should include specific keywords that help agents identify relevant tasks
compatibility field rules
- If present, it must be 1–500 characters
- Include it only for concrete environment requirements, such as a required product, system package, network access, or runtime
metadata field rules
- Must be a map of string keys to string values
- Use reasonably unique keys to avoid collisions with other clients or tools
Body Content
The Markdown
阅读完整来源 ↗