This file provides guidance to AI coding agents (Claude Code, Codex, Cursor, etc.) when working with code in this repository.
This repository publishes open-source agent skills to skills.sh. Skills are discovered and installed via the npx skills CLI, which scans the skills/ directory for valid SKILL.md files.
Each skill follows the Agent Skills specification:
skills/
└── <skill-name>/
├── SKILL.md # Required: YAML frontmatter + markdown instructions
├── scripts/ # Optional: Python/Bash executables
├── references/ # Optional: Documentation loaded on-demand
└── assets/ # Optional: Templates, images, etc.
Every SKILL.md must have:
- YAML frontmatter with
name(lowercase, hyphens only, must match directory name) anddescription(used by agents to decide when to activate the skill) - Markdown body with instructions the agent follows when the skill is active
The description field is critical — it's always in the agent's context and determines auto-invocation.
- Keep SKILL.md under 500 lines (move detailed docs to
references/) - Directory name must exactly match the
namefield in frontmatter - Use relative paths (
./scripts/,./references/) for portability across agents - Generalize for any repository — avoid hardcoded project-specific logic
- Create/modify skill in
skills/<skill-name>/ - Test locally:
npx skills add .(installs from local repo) - Commit and push to GitHub (repo must be public)
- Trigger indexing:
npx skills add SepantaJoshani/agents-skills
Skills.sh automatically indexes via anonymous telemetry — no registration required.
Test a skill before publishing:
# Install from local directory
npx skills add . --skill <skill-name>
# Verify it installed
npx skills list
# Remove after testing
npx skills remove <skill-name>Installed skills appear in .claude/skills/, .cursor/skills/, etc. depending on detected agents.
Skills can reference other skills without hard dependencies. Example pattern from address-pr-comments:
"Examine recent commits (
git log --oneline -10) to understand the repository's commit message style. If a commit message generation skill is installed, use it. Otherwise, write a concise commit message from the staged diff that follows the same conventions."
This allows skills to work independently while being enhanced when paired.
When creating commits in this repository:
- Check if
generate-commit-messageskill is installed (or any commit message generation skill) - If available, use it to generate commit messages
- If not, examine recent commits (
git log --oneline -10) to match the repo's style - Follow the cbea.ms conventions: imperative mood, ≤50 char subject, capitalized, no trailing period
- GitHub CLI (
gh): Required foraddress-pr-commentsskill - Python 3.8+: Required for
address-pr-comments/scripts/list_comments.py
Skills should document their dependencies in the repo README, not in SKILL.md (which is consumed by agents, not users).