by ComposioHQ
A curated list of practical Codex skills for automating workflows across the Codex CLI and API.
# Add to your Claude Code skills
git clone https://github.com/ComposioHQ/awesome-codex-skillsA curated list of practical Codex skills for automating workflows across the Codex CLI and API.
Want skills that do more than generate text? Codex can send emails, create issues, post to Slack, and take actions across 1000+ apps. See how →
git clone https://github.com/ComposioHQ/awesome-codex-skills.git
cd awesome-codex-skills/awesome-codex-skills
# Install one or more skills into $CODEX_HOME/skills (defaults to ~/.codex/skills)
python skill-installer/scripts/install-skill-from-github.py --repo ComposioHQ/awesome-codex-skills --path meeting-notes-and-actions
The installer fetches the skill and places it in $CODEX_HOME/skills/<skill-name>. Restart Codex to pick up new skills.
./spreadsheet-formula-helper) into $CODEX_HOME/skills/ (defaults to ~/.codex/skills/).description frontmatter.No comments yet. Be the first to share your thoughts!
Codex skills are modular instruction bundles that tell Codex how to execute a task the way you want it done. Each skill lives in its own folder with a SKILL.md that includes metadata (name + description) and step-by-step guidance. Codex reads the metadata to decide when to trigger a skill and loads the body only after it fires, keeping context lean.
gh.$CODEX_HOME/skills (default ~/.codex/skills). Each subfolder needs a SKILL.md with name and description frontmatter.ls ~/.codex/skills) and inspect metadata (head ~/.codex/skills/<skill>/SKILL.md).Skill layout:
skill-name/
├── SKILL.md # Required: instructions + YAML frontmatter
├── scripts/ # Optional: helper scripts for deterministic steps
├── references/ # Optional: long-form docs loaded only when needed
└── assets/ # Optional: templates or files used in outputs
Basic SKILL.md template:
---
name: my-skill-name
description: What the skill does and when Codex should use it.
---
# My Skill Name
Clear instructions and steps for Codex to execute the task.
Best practices:
description exhaustive about when to trigger; keep the body focused on execution steps.references/ and call them out from SKILL.md only when needed.PRs welcome. Add real, reusable skills, keep descriptions precise, and include any needed scripts or references. If you add new skills, ensure the description clearly states when Codex should trigger and test that metadata fits within context limits.