A public collection of reusable skills for local coding agents. Each skill packages task-specific instructions and, when needed, supporting references, templates, scripts, or examples.
These skills are designed to live at ~/.agents/skills, which is a common discovery path for agent tooling such as Codex, Claude Code, and Gemini CLI.
For macOS and Linux:
curl -fsSL https://raw.githubusercontent.com/ElyzeSolutions/skills/main/install.sh | bashFor Windows PowerShell:
iwr https://raw.githubusercontent.com/ElyzeSolutions/skills/main/install.ps1 | iexinstall.sh and install.ps1 are bootstrap scripts. They:
- Create
~/.agentsif it does not already exist. - Clone this repository into
~/.agents/skillson first install. - Update the existing checkout on later runs.
- Point the local checkout at
ElyzeSolutions/skillsbefore updating.
If you prefer to install manually:
git clone https://github.com/ElyzeSolutions/skills.git ~/.agents/skillsEach skill lives in its own directory and usually includes:
SKILL.md: the main skill definition and usage guidancereferences/: focused supporting documentationtemplates/: reusable starter filesscripts/: utility scripts used by the skillexamples/orassets/: optional examples and supporting assets
- Planning and delivery:
wayfinder,p4rd,to-spec,to-tickets,implement,prototype - Browser automation:
chrome-devtools,playwright-cli,playwright-generate-test,webwright - Frontend design and UX:
impeccable,design-taste-frontend,redesign-existing-projects,web-design-guidelines - React and state management:
react-state-management,tanstack-query-best-practices,tanstack-router-best-practices,tanstack-start-best-practices - Performance and refactoring:
react-performance-optimization,refactor-pass,vercel-react-best-practices,deslop - Specialized workflows:
ai-sdk,obsidian,polybot,polyx,remotion-to-hyperframes,websocket-engineer
If your tool does not automatically read ~/.agents/skills, you can symlink specific skills into project-local directories:
mkdir -p .claude
ln -s ~/.agents/skills/tdd .claude/tdd- Add or update a skill in its own directory.
- Keep
SKILL.mdconcise, explicit, and production-oriented. - Include only the references and scripts the skill actually needs.
- Avoid machine-specific paths, local state, generated caches, and secrets.