Skip to main content

Publish an extension

For the current alpha, publishing means making one repository that contains one readable .phonton pack. Keep the repository small and auditable.

The Review Gate reference repo shows the expected shape: https://github.com/phonton-dev/phonton-review-gate-extension.

Recommended layout:

phonton-review-gate-extension/
  README.md
  LICENSE
  .phonton/
    skills/
      review-gate/
        skill.toml
        SKILL.md
    steering.toml
    profiles.toml

Publishing checklist​

  • Use stable ids for every skill, rule, MCP server, and profile.
  • Keep permissions empty for text-only packs.
  • Document every MCP permission and environment variable.
  • Include file-copy configuration instructions and phonton extensions doctor in the README.
  • Include phonton mcp capabilities <server-id> --yes for MCP packs so users can preview negotiated tools before use.
  • Include a short "what this changes" section.
  • Avoid secrets, private paths, generated logs, or benchmark output with local data.

Good README shape​

# Review Gate Extension

What it adds:
- one review handoff skill
- two steering rules
- one profile

Configure:
```powershell
Copy-Item -Recurse .\.phonton C:\path\to\repo\.phonton
phonton extensions doctor
```

For MCP packs, include a capability-preview example:

phonton mcp capabilities <server-id> --yes

Open a pull request against the website repo with:

  • a gallery entry in src/pages/extensions.js that points to the extension repo;
  • docs updates if the extension introduces a new pattern.