Co-Pilot
Updated a month ago

awesome-codex-skills

CComposioHQ
0.2k
composiohq/awesome-codex-skills
76
Agent Score

💡 Summary

A curated collection of Codex skills for automating various workflows across multiple applications.

🎯 Target Audience

Developers looking to streamline coding tasksProject managers needing efficient meeting summariesData analysts seeking automation in data handlingContent creators wanting to enhance their writing processTeams collaborating on projects requiring integrated tools

🤖 AI Roast:Powerful, but the setup might scare off the impatient.

Security AnalysisMedium Risk

Risk: Medium. Review: shell/CLI command execution; outbound network access (SSRF, data egress); filesystem read/write scope and path traversal. Run with least privilege and audit before enabling in production.

A 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 →


Quickstart: Add Skills to Codex

Install with the Skill Installer (recommended)

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.

Manual install

  1. Copy the desired skill folder (e.g., ./spreadsheet-formula-helper) into $CODEX_HOME/skills/ (defaults to ~/.codex/skills/).
  2. Restart Codex so it loads the new metadata.
  3. In your next session, describe the task or mention the skill name; Codex will trigger matching skills based on their description frontmatter.

Contents

What Are Codex Skills?

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.

Skills

Development & Code Tools

  • create-plan/ - Quickly draft concise execution plans for coding tasks.
  • gh-address-comments/ - Address review or issue comments on the open GitHub PR for the current branch using gh.
  • gh-fix-ci/ - Inspect failing GitHub Actions checks, summarize failures, and propose fixes.
  • mcp-builder/ - Build and evaluate MCP servers with best practices and an evaluation harness.
  • webapp-testing/ - Run targeted web app tests and summarize results.

Productivity & Collaboration

Communication & Writing

Data & Analysis

Meta & Utilities

Using Skills in Codex

  • Skills live in $CODEX_HOME/skills (default ~/.codex/skills). Each subfolder needs a SKILL.md with name and description frontmatter.
  • After installing or updating a skill, restart Codex so it reloads metadata.
  • In a session, describe the task naturally; Codex auto-triggers skills whose descriptions match the request. You can also mention a skill by name if you want it considered.
  • To verify installation, list installed skills (ls ~/.codex/skills) and inspect metadata (head ~/.codex/skills/<skill>/SKILL.md).

Creating Skills

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:

  • Keep the description exhaustive about when to trigger; keep the body focused on execution steps.
  • Use progressive disclosure: put detailed references in references/ and call them out from SKILL.md only when needed.
  • Include scripts for repeatable or deterministic operations; mention when Codex should run them.
  • Avoid extra docs (README, changelog) inside the skill folder to keep context lean.

Contributing

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.

Join the Community

  • Join our Discord - Chat with other developers building Codex skills.
  • Follow on X - Updates on new skills and features.
  • Questions? support@composio.dev

5-Dim Analysis
Clarity8/10
Novelty6/10
Utility9/10
Completeness8/10
Maintainability7/10
Pros & Cons

Pros

  • Offers a wide range of skills for various tasks
  • Facilitates integration with multiple applications
  • Modular structure allows for easy updates and additions

Cons

  • Installation process may be confusing for new users
  • Documentation could be more detailed
  • Requires restarting Codex for changes to take effect

Related Skills

pytorch

S
toolCode Lib
92/ 100

“It's the Swiss Army knife of deep learning, but good luck figuring out which of the 47 installation methods is the one that won't break your system.”

agno

S
toolCode Lib
90/ 100

“It promises to be the Kubernetes for agents, but let's see if developers have the patience to learn yet another orchestration layer.”

nuxt-skills

S
toolCo-Pilot
90/ 100

“It's essentially a well-organized cheat sheet that turns your AI assistant into a Nuxt framework parrot.”

Disclaimer: This content is sourced from GitHub open source projects for display and rating purposes only.

Copyright belongs to the original author ComposioHQ.