GPT Plugins
One Agent Plugins 1.0.0 collection for GPT-specific skills. The manifest plugin.json owns the plugin metadata and version.
| Path | Purpose |
|---|---|
plugin.json | Manifest. The checker checks it against the canonical schema at agent-plugins.org. |
skills/<name>/SKILL.md | Shipped skill copies. The archive carries these. |
refs/skills/<name>/SKILL.md | Readable sources. Keep these full. Compress shipped copies without losing rules. |
README.md | This file. It never ships. |
Skills
| Skill | Purpose |
|---|---|
| gpt-quirks | Apply verified GPT and connected tool quirks when they are relevant |
| gpt-handoff | Audit agent work and human-facing docs. Use Ponytail for code and docs audits. Own the final format or draft a handoff. |
| gpt-planning | Check requirements and completion before each plan, handoff, execution, and final report. |
| gpt-github | Apply the owner's git and GitHub rules to every git or GitHub action. |
Edit a skill
Skill sources live under refs/skills/. Compress shipped copies manually, preserving every rule, condition, exception, command and heading. Review each clause against its source. Increase the plugin version for every update. See maintenance/README.md for synchronization and validation.
Package
.github/workflows/artifacts.yml checks the collection on pull requests. A pull request that changes shipped plugin files must raise the plugin.json version above the base branch. Pushes to main write gpt-plugins.zip as a direct Actions artifact. A second workflow,
.github/workflows/release-gpt-plugins.yml, publishes the same archive as a GitHub Release
under the versioned tag gpt-plugins-v<version>, taken from plugin.json. A tag that exists
keeps its release and gets the fresh asset, so the download URL stays stable. The archive carries plugin.json and skills/ only, so refs/ and this README stay out of it. On-demand runs package only from main. The workflow fails on a missing or invalid plugin file.