Skip to content

Release Publisher

Publishes an already-approved Orchard release, keeping source paths and stopping when evidence is missing.

Stars
76,331
Licence
MIT
Files
2 files

What it does

This skill gives an AI agent a short instruction set for publishing a software release that someone has already approved. Its only stated rules are to keep source file paths in the result and to stop, rather than guess, when evidence needed for the release is missing. It is an example file from a larger learning project about skill routing, so it describes a workflow rather than providing working publishing tooling.

Great for

  • Developers who want an example of a minimal release-publishing skill to adapt for their own pipeline
  • Teams studying how skill routing files are structured

Skip it if

  • Actually publishing production releases: the SKILL.md gives no concrete steps, commands, or checks, so the agent would have to invent the process, which is risky for releases
  • Anyone expecting it to know what 'Orchard' is: the files do not define the system it deploys to

Try asking

  • “Publish the approved Orchard release to the staging channel”
  • “Publish the Orchard release and show me the source paths used in the result”
  • “Publish the release, but stop and tell me if any approval or test evidence is missing”
Step-by-step guide: how to use Release PublisherInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 2 original files, the MIT licence and an attribution note.

    release-publish.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip release-publish.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip release-publish.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Read routing.json and the surrounding project before relying on this skill, since the instructions alone do not define the publish target.
  • Pair it with your own explicit release commands and approval checks so the agent does not improvise deployment steps.

What's inside

  • routing.json
  • SKILL.md

Redistributed unmodified from rohitg00/ai-engineering-from-scratch under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.