Skills

Author once. Ship to your whole team.

What's a skill?

A skill is a named, reusable AI capability. Think of it as a saved prompt + tools + guardrails, callable from chat with /skill-name.

Author a skill

Create .codexax/skills/review.md:

---
name: review
description: Review pending changes for security and correctness.
tags: [code-review, security]
tools: [readFile, runCommand]
---
You are a senior staff engineer reviewing a PR.

For each changed file:
- Highlight any obvious bugs
- Flag security issues (injection, auth, secrets)
- Suggest concrete improvements

Be terse. No "looks good!" filler.

Use it

In chat: /review. The skill content becomes the system prompt; tools listed are auto-allowed.

Sharing

  • Repo skills — committed to .codexax/skills/. Everyone on the project gets them.
  • User skills — in ~/.codexax/skills/. Personal across all projects.
  • Team skills (Pro/Team plans) — pushed via codexax skill publish, available to everyone in your org.

Best practices

  • One skill = one outcome. Don't bundle.
  • List the tools the skill needs. Restricting tools = faster + safer.
  • Write the prompt for an actual person. The model reads it the same way.