By Jesse Raber — owner of Unique WoodWorx and builder of practical AI workflows for real-world businesses. Consulting · YouTube
An Agent Skill that teaches AI agents to set up skill repositories and release them right the first time: a version gate before any tag, deterministic packages for each AI host, draft-first publishing, verification that published bytes equal the tested build, and a dated per-host install log.
Before setup or release, record the owner-approved audience and reuse rights. Private projects keep their approved internal users and AI tools without public promotion; public visibility alone does not choose a license. See distribution scope and licensing. This skill retains its existing MIT license.
| Your AI app | Download |
|---|---|
| Claude app, ChatGPT/Codex standalone skills, Antigravity, local models, any skills folder | …-UNIVERSAL-skill.zip |
Claude Code /plugin install |
…-claude-code-plugin.zip |
| Codex / ChatGPT plugin | …-codex-chatgpt-plugin.zip |
| Microsoft Copilot agent, Grok | …-microsoft-copilot-agent-only.zip |
| Gemini Spark (not regular Gemini chat, which rejects skills with scripts) | …-gemini-apps-only.zip |
| Opal | …-opal-only.zip |
For ordinary repository edits, use Edit: confirm the base and scope, make the change, inspect the diff and run relevant checks, then stop at local review or the authorized push/PR/merge boundary. It skips the skill-release gate unless release preparation is requested; repository-required checks still apply. See the ordinary-edit workflow.
For a skill release:
flowchart LR
P[Prepare\ncandidate + checks] --> G[Gate\nG0-G14, read-only]
G -->|scope includes tag| T[Tag pushed\nworkflow builds DRAFT]
T --> V[Verify draft\nbytes == candidate]
V -->|scope includes publish| R[Published\nimmutable]
R --> H[Host installs\nlogged per channel]
- Record explicit approval of the concrete repository, changes, audience and intended steps once. Continue included ordinary steps without repeated prompts; preparation alone grants no remote action. Preserve validation, material-scope boundaries and mandatory host/security/irreversible-action confirmations. See approval scope.
- Gate first, tag second. The release workflow creates a draft; the draft's assets are verified against the local candidate before publication proceeds within the approved scope.
- Published bytes are never replaced. A defect ships as a new patch version.
- Every host rule carries a date and a source.
skills/github-release/ is the skill. packaging/ builds and checks releases of this repository with the skill's own templates.
I'm Jesse Raber, owner of Unique WoodWorx, a custom cabinet shop in Odon, Indiana. I built this skill because my own AI-driven releases kept going wrong in ways the agents couldn't see. If you want help putting AI agents to work in your business — CNC, cabinet software, or workflows like this one — that's what I do at jesseraber.net. Build and release walkthroughs: YouTube.
MIT licensed.