Agent Release Manager
ruvnet/ruflo
Agent skill for release-manager - invoke with $agent-release-manager
Runs rolling beta releases, stable patches, and complete stable-line cutovers.
Custom licenceAuto-check passed
Install Managing Archestra Releases
$ npx skills add archestra-ai/archestra --skill managing-archestra-releases -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install archestra-ai/archestra managing-archestra-releases --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/archestra-ai/archestra.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/managing-archestra-releases .claude/skills/managing-archestra-releases && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "managing-archestra-releases" agent skill from https://github.com/archestra-ai/archestra/tree/main/.agents/skills/managing-archestra-releases into .claude/skills/managing-archestra-releases/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-archestra-releases", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/archestra-ai/archestra/tree/main/.agents/skills/managing-archestra-releasesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add archestra-ai/archestra --skill managing-archestra-releases -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install archestra-ai/archestra managing-archestra-releases --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/archestra-ai/archestra.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/managing-archestra-releases .agents/skills/managing-archestra-releases && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "managing-archestra-releases" agent skill from https://github.com/archestra-ai/archestra/tree/main/.agents/skills/managing-archestra-releases into .agents/skills/managing-archestra-releases/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-archestra-releases", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add archestra-ai/archestra --skill managing-archestra-releases -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install archestra-ai/archestra managing-archestra-releases --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/archestra-ai/archestra.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/managing-archestra-releases .cursor/skills/managing-archestra-releases && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "managing-archestra-releases" agent skill from https://github.com/archestra-ai/archestra/tree/main/.agents/skills/managing-archestra-releases into .cursor/skills/managing-archestra-releases/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-archestra-releases", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/archestra-ai/archestra.git --path .agents/skills/managing-archestra-releases--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add archestra-ai/archestra --skill managing-archestra-releases -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install archestra-ai/archestra managing-archestra-releases --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/archestra-ai/archestra.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/managing-archestra-releases .gemini/skills/managing-archestra-releases && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "managing-archestra-releases" agent skill from https://github.com/archestra-ai/archestra/tree/main/.agents/skills/managing-archestra-releases into .gemini/skills/managing-archestra-releases/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-archestra-releases", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install archestra-ai/archestra managing-archestra-releasesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add archestra-ai/archestra --skill managing-archestra-releases -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/archestra-ai/archestra.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/managing-archestra-releases .github/skills/managing-archestra-releases && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "managing-archestra-releases" agent skill from https://github.com/archestra-ai/archestra/tree/main/.agents/skills/managing-archestra-releases into .github/skills/managing-archestra-releases/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-archestra-releases", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add archestra-ai/archestra --skill managing-archestra-releases -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install archestra-ai/archestra managing-archestra-releases --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/archestra-ai/archestra.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/managing-archestra-releases .opencode/skills/managing-archestra-releases && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "managing-archestra-releases" agent skill from https://github.com/archestra-ai/archestra/tree/main/.agents/skills/managing-archestra-releases into .opencode/skills/managing-archestra-releases/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-archestra-releases", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
managing-archestra-releases- GitHub stars
- 4.4k
- Token cost
- ~3.3k tokens
- SKILL.md length
- 1,871 words
- Files
- 5
- Skills in repo
- 23
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Runs rolling beta releases, stable patches, and complete stable-line cutovers.
- Works in 5 steps: Preflight And Stable-Cut Approval → Create And Protect The Branch → Prepare And Cut X.Y.0 → …
- Backporting fixes
- SKILL.md covers Publication Paths, Backporting Fixes, Cutting A New Stable Line End… and Safety And Recovery Rules
- Runs JavaScript scripts from its folder
What it does
Managing Archestra Releases is an agent skill from archestra-ai/archestra. Runs rolling beta releases, stable patches, and complete stable-line cutovers. Use when backporting fixes, cutting or retiring release branches, configuring release protections, testing artifacts, recovering failed runs, or approving releases.
Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files.
The repository describes itself as: Enterprise AI Platform with guardrails, MCP registry, gateway & orchestrator.
When your agent uses it
- Backporting fixes
- Retiring release branches
- Configuring release protections
- Testing artifacts
Example prompts
- “/managing-archestra-releases”
Requirements
- Node.js
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Preflight And Stable-Cut Approval
- Create And Protect The Branch
- Prepare And Cut X.Y.0
- Commit The Cutover And Publish
- Start The Next Beta Line
What it can do on your machine
Read from SKILL.md and the folder at commit df802e7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (JavaScript), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Managing Archestra Releases loads about 3.3k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 1,871 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,871 words (~3,349 tokens).
“Always read platform/dev/RELEASE.md first. It is the authoritative release checklist. Do not assume release/1.3 is always the active branch. Check current branches, tags, and settings before acting.”
- name
- managing-archestra-releases
Files
SKILL.md and 4 other files in .agents/skills/managing-archestra-releases of archestra-ai/archestra.
- SKILL.md
- test/fixture-agent.mjs
- test/mock-github-server.mjs
- test/release-harness.test.mjs
- test/tool-client.mjs
Open the folder on GitHubat commit df802e7
Compare with similar skills
Managing Archestra Releases next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Managing Archestra Releases this skillarchestra-ai/archestra | 4.4k | — | ~3.3k | Automated safety check: Pass | Custom licence | |
| Agent Release Managerruvnet/ruflo | 74k | 2 repos | ~3.1k | Automated safety check: Pass | MIT | |
| Patch Release CheckClickHouse/ClickHouse | 50k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| Implementing Patch Management For Ot Systemsmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~3.2k | Automated safety check: Pass | Apache-2.0 | |
| Implementing Patch Management Workflowmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Release Openclaw Maintaineropenclaw/openclaw | 392k | — | ~2.9k | Automated safety check: Pass | MIT |
Similar skills
Patch Release Check
ClickHouse/ClickHouse
Check whether ClickHouse's supported versions (last 3 majors + latest LTS) have recent stable patch releases, diagnose why the scheduled AutoReleases pipeline failed, and identify which releases…
Implementing Patch Management For Ot Systems
mukul975/Anthropic-Cybersecurity-Skills
Implements a structured patch management program for OT/ICS environments where IT-style patching can cause process disruption or safety hazards, covering vendor compatibility testing, risk-based…
Implementing Patch Management Workflow
mukul975/Anthropic-Cybersecurity-Skills
Patch management is the systematic process of identifying, testing, deploying, and verifying software updates to remediate vulnerabilities across an organization's IT infrastructure.
Release Openclaw Maintainer
openclaw/openclaw
Prepare, publish, recover, or verify OpenClaw beta, stable, and extended-stable releases, including approved backports.
Release Openclaw Announcement
openclaw/openclaw
Draft or post OpenClaw beta, stable, or extended-stable Discord release announcements from changelog, tag, registry, and validation evidence.
More from archestra-ai/archestra
All 23 skills in this repoMigrate To Archestra
archestra-ai/archestra
Migrate an existing agentic PoC/pilot (Claude Code project files, MCP configs, hooks, local tools, openclaw config, or similar hand-rolled setup artifacts) into an Archestra instance.
Archestra Dev Testing
archestra-ai/archestra
A skill your agent uses for test selection and quality across backend, frontend, and e2e; load its backend reference for Vitest projects, mocking, DB fixtures, and performance.
Archestra Dev Backend
archestra-ai/archestra
A skill your agent uses when adding or changing Archestra backend routes, models, services, API request/response schemas, endpoint permissions, or OpenAPI/codegen for the generated API client.
Archestra Dev E2E
archestra-ai/archestra
A skill your agent uses when writing, debugging, or running Archestra Playwright e2e tests, API/UI fixtures, WireMock-backed tests, local/CI e2e setup, or test selectors.
Archestra Dev Frontend
archestra-ai/archestra
A skill your agent uses when modifying Archestra frontend Next.js/React code, UI components, forms, TanStack Query hooks, generated API client usage, frontend copy, or documentation links.
Archestra Dev LLM Providers
archestra-ai/archestra
A skill your agent uses when adding an LLM provider, changing proxy adapters or provider routes, fixing streaming/tool-call translation bugs, editing model fetchers or model handling, or touching…
Questions about Managing Archestra Releases
What does Managing Archestra Releases do?
Runs rolling beta releases, stable patches, and complete stable-line cutovers. Managing Archestra Releases is an agent skill from archestra-ai/archestra. Runs rolling beta releases, stable patches, and complete stable-line cutovers.
When should I use Managing Archestra Releases?
Managing Archestra Releases fits situations like: backporting fixes; retiring release branches; configuring release protections; testing artifacts.
How do I install Managing Archestra Releases in Claude Code?
Run `npx skills add archestra-ai/archestra --skill managing-archestra-releases -a claude-code`. Or copy the skill folder (.agents/skills/managing-archestra-releases in archestra-ai/archestra) into .claude/skills/managing-archestra-releases in your project. Claude Code loads it when a task matches its description.
How do I install Managing Archestra Releases in Codex?
Run `npx skills add archestra-ai/archestra --skill managing-archestra-releases -a codex`. Or copy the skill folder (.agents/skills/managing-archestra-releases in archestra-ai/archestra) into .agents/skills/managing-archestra-releases in your project. Codex loads it when a task matches its description.
Can I use Managing Archestra Releases in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add archestra-ai/archestra --skill managing-archestra-releases -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/managing-archestra-releases, .gemini/skills/managing-archestra-releases, .github/skills/managing-archestra-releases and .opencode/skills/managing-archestra-releases in your project.
What does Managing Archestra Releases need to run?
Going by SKILL.md and its folder, Managing Archestra Releases needs JavaScript for the scripts in its folder. Our summary lists: Node.js.
Does Managing Archestra Releases access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Managing Archestra Releases safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Managing Archestra Releases use?
Managing Archestra Releases has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Managing Archestra Releases use?
About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Managing Archestra Releases?
Skills that share tags, products or a category with Managing Archestra Releases: Agent Release Manager (ruvnet/ruflo, 74k stars), Patch Release Check (ClickHouse/ClickHouse, 50k stars), Implementing Patch Management For Ot Systems (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Implementing Patch Management Workflow (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Managing Archestra Releases?
archestra-ai (a GitHub organization) maintains it in archestra-ai/archestra, which has 4,368 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 10, 2026.
Source: archestra-ai/archestra on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.