Publishing Skills
How to get your skills into the APM registry
Overview
Publish skills to APM by connecting a GitHub repo from your dashboard. APM scans the repo, imports your SKILL.md files, and optionally auto-syncs on every push.
GitHub Sync (recommended)
The fastest way to publish. No CLI needed.
1. Create an organization
If you haven't already, sign up and create an org. This gives you a namespace like @myorg.
2. Go to your namespace page
From your dashboard, click your org, then click your namespace (e.g. @myorg).
3. Connect a GitHub repo
Click Connect GitHub Repository, search for your repo, and select it. APM scans the repo for SKILL.md files using the Git tree API — no indexing delay.
4. Select and import
Review the found SKILL.md files, check the ones you want to import, and click Import. Each file is parsed, validated, and published under your namespace.
5. Enable auto-sync
After your first import, an Auto-sync section appears. Click Enable Auto-sync to set up a GitHub webhook. From now on, any push to your repo automatically updates the affected skills in the registry.
Auto-sync uses SHA-based change detection — only modified SKILL.md files are re-processed.
Automatic indexing (coming soon)
APM will also index public GitHub repos containing valid SKILL.md files automatically — no account or publishing step needed. Your GitHub username or org name becomes the scope.
This feature is not yet active. For now, use GitHub Sync to publish your skills.
Managing packages
From your namespace page in the dashboard, you can:
- View packages — see all skills published under your namespace with download counts
- Delete packages — remove a skill from the registry (requires typing the package name to confirm)
- Re-sync — click "Connect GitHub Repository" again to import new skills or update existing ones
Updating published skills
How updates work depends on your publishing method:
| Method | Update process |
|---|---|
| Auto-sync | Push to GitHub → webhook fires → registry updates automatically |
| Manual sync | Go to namespace page → re-scan the repo → import updated files |
Version tracking
APM tracks versions for each package:
- If your SKILL.md frontmatter includes a
versionfield, APM uses that value - If not, APM auto-increments the patch version on each change (e.g.
1.0.0→1.0.1) - New packages start at
1.0.0
Opting out
If your public repo has a SKILL.md but you'd rather not be indexed, see Opting Out.