Skill library
A canonical Skill lives in .agents/skills/<name>/SKILL.md. Its frontmatter contains only portable metadata: a lowercase, hyphenated name that matches the directory and a specific description that explains both purpose and trigger conditions.
Use references/ for detailed material, scripts/ for deterministic operations, and assets/ for reusable resources. Keep the main Skill focused; do not repeat permanent repository instructions or add agent-specific permissions to it.
Available Skills
| Skill | Use it for | Direct URL |
|---|---|---|
pelagornis-code-review |
Evidence-based review of a pull request, diff, or implementation. | SKILL.md |
pelagornis-repository-audit |
Prioritized architecture, quality, security, and maintenance audit. | SKILL.md |
pelagornis-git-workflow |
Safe commits, pull requests, conflict investigation, and cleanup. | SKILL.md |
pelagornis-test-debug |
Reproducing failures and validating the smallest reliable fix. | SKILL.md |
pelagornis-docs-maintenance |
Documentation, navigation, links, and example maintenance. | SKILL.md |
pelagornis-skill-authoring |
Creating or improving a portable reusable workflow. | SKILL.md |
Validation and maintenance
Run the lightweight structural validation from the repository root:
ruby scripts/validate_skills.rb
It checks required manifests, YAML frontmatter, names, directory matches, unique names, and relative links. Review Skill changes like code: inspect their instructions and scripts, keep secrets out of the library, and require explicit authorization for destructive actions.
For reproducible downstream installs, publish a Git tag and install that tag, for example pelagornis/styleguide@v1.0.0. Use npx skills check and npx skills update in consumer projects to review updates.