Contributing to the Apollo Corporate Plugin

This plugin is a living knowledge base. Everyone is encouraged to contribute.

What goes where?

You want to...	Add it to...
Add a quick-lookup slash command	commands/your-command.md
Create a department expert persona	agents/your-dept.md
Document tribal knowledge Claude can invoke	skills/your-topic/SKILL.md
Register an MCP server your team maintains	.mcp.json
Add an automation hook	hooks/hooks.json

Adding a new Skill (most common)

1. Create a folder: skills/your-topic-name/
2. Add a SKILL.md file with frontmatter:

   ---
   description: One-line summary of what this skill covers
   triggers:
     - keyword1
     - keyword2
   ---

3. Write the content in plain markdown. Be specific to Apollo.
4. Open a PR. Tag the relevant team for review.

Adding a new Agent

1. Create agents/your-dept.md
2. Use the frontmatter format:

   ---
   description: What this agent knows about
   capabilities:
     - "Capability 1"
     - "Capability 2"
   ---

3. Write the agent prompt. Focus on Apollo-specific knowledge.

Adding an MCP Server

Edit .mcp.json and add your server config:

{
  "your-server-name": {
    "command": "npx",
    "args": ["@your-package/mcp-server"],
    "env": {}
  }
}

Guidelines

• Be specific. "We use X because Y" beats "consider using X."
• Name names. Slack channels, team names, specific people/rotations.
• Keep it current. If something changes, update the file. Stale knowledge is worse than no knowledge.
• One topic per skill. Don't cram everything into one file.
• Version your changes. Update CHANGELOG.md for meaningful additions.