Ccb GitHub
SeemSeam/claude_codex_bridge
Maintain this CCB project's GitHub-facing release and npm publication surface.
A skill your agent uses when preparing, cutting, promoting, tagging, or validating a Manor public OSS release, beta/stable release, changelog entry, release notes, docs publish, or post-release…
Install Manor Release
$ npx skills add manor-os/manor-ai --skill manor-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install manor-os/manor-ai manor-release --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/manor-os/manor-ai.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/manor-release .claude/skills/manor-release && 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 "manor-release" agent skill from https://github.com/manor-os/manor-ai/tree/main/.agents/skills/manor-release into .claude/skills/manor-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manor-release", 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/manor-os/manor-ai/tree/main/.agents/skills/manor-releaseType 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 manor-os/manor-ai --skill manor-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install manor-os/manor-ai manor-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manor-os/manor-ai.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/manor-release .agents/skills/manor-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "manor-release" agent skill from https://github.com/manor-os/manor-ai/tree/main/.agents/skills/manor-release into .agents/skills/manor-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manor-release", 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 manor-os/manor-ai --skill manor-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install manor-os/manor-ai manor-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manor-os/manor-ai.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/manor-release .cursor/skills/manor-release && 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 "manor-release" agent skill from https://github.com/manor-os/manor-ai/tree/main/.agents/skills/manor-release into .cursor/skills/manor-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manor-release", 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/manor-os/manor-ai.git --path .agents/skills/manor-release--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 manor-os/manor-ai --skill manor-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install manor-os/manor-ai manor-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manor-os/manor-ai.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/manor-release .gemini/skills/manor-release && 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 "manor-release" agent skill from https://github.com/manor-os/manor-ai/tree/main/.agents/skills/manor-release into .gemini/skills/manor-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manor-release", 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 manor-os/manor-ai manor-releaseInstalls 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 manor-os/manor-ai --skill manor-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/manor-os/manor-ai.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/manor-release .github/skills/manor-release && 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 "manor-release" agent skill from https://github.com/manor-os/manor-ai/tree/main/.agents/skills/manor-release into .github/skills/manor-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manor-release", 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 manor-os/manor-ai --skill manor-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install manor-os/manor-ai manor-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manor-os/manor-ai.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/manor-release .opencode/skills/manor-release && 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 "manor-release" agent skill from https://github.com/manor-os/manor-ai/tree/main/.agents/skills/manor-release into .opencode/skills/manor-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manor-release", 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
manor-release- GitHub stars
- 162
- Token cost
- ~529 tokens
- SKILL.md length
- 209 words
- Files
- 2
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
A skill your agent uses when preparing, cutting, promoting, tagging, or validating a Manor public OSS release, beta/stable release, changelog entry, release notes, docs publish, or post-release…
- Works in 6 steps: Determine release type: beta/candidate,… → Inspect changes since the last relevant… → Update CHANGELOG.md with user-facing OSS… → …
- Validating a Manor public OSS release
- SKILL.md covers Release model, Release preparation, Required validation before… and Tag safety, plus 1 more section
- Calls git, npm and python
What it does
Manor Release is an agent skill from manor-os/manor-ai. Use when preparing, cutting, promoting, tagging, or validating a Manor public OSS release, beta/stable release, changelog entry, release notes, docs publish, or post-release announcement.
Its SKILL.md is about 530 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Development, covering Changelog and release notes. It works with GitHub Actions. The repository describes itself as: Source-available, self-hosted AI agent workspace for small businesses and lean teams — with BYOK, workflows, tools, and human approvals.
When your agent uses it
- Validating a Manor public OSS release
- Beta/stable release
- Changelog entry
- Post-release announcement
Example prompts
- “/manor-release”
Requirements
- Python 3
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Determine release type: beta/candidate, stable tag, or promote existing candidate.
- Inspect changes since the last relevant tag
- Update CHANGELOG.md with user-facing OSS changes only.
- Confirm README/docs-site describe current self-hosted setup, model keys, governance, and operations.
- Confirm public media and docs render in GitHub and the docs site.
- Confirm docs publishing behavior in .github/workflows/deploy-docs.yml if the release should update the public docs site.
What it can do on your machine
Read from SKILL.md and the folder at commit 140c09a. 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
Shell commands in SKILL.md call:
gitnpmpython
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and npm, which can reach the network depending on how they are called.
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
Manor Release loads about 529 tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 209 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 209 words (~529 tokens).
“Use this skill to coordinate a public Manor release while keeping release notes, docs, and checks self-hosted focused.”
- name
- manor-release
Files
SKILL.md and 1 other file in .agents/skills/manor-release of manor-os/manor-ai.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 140c09a
Compare with similar skills
Manor Release 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 |
|---|---|---|---|---|---|---|
| Manor Release this skillmanor-os/manor-ai | 162 | — | ~529 | Automated safety check: Pass | Custom licence | |
| Ccb GitHubSeemSeam/claude_codex_bridge | 3.6k | — | ~4.9k | Automated safety check: Pass | Custom licence | |
| Cline Desktop App Releasecline/cline | 70k | — | ~4.5k | Automated safety check: Pass | Apache-2.0 | |
| Cut Releasedelexw/claude-code-trace | 377 | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| ReleaseXGHeaven/homebox | 817 | — | ~1.4k | Automated safety check: Pass | None | |
| ZCF Release AutomationUfoMiao/zcf | 6.1k | — | ~3.4k | Automated safety check: Pass | MIT |
Similar skills
Cline Desktop App Release
cline/cline
Covers preparing, tagging and publishing a Cline desktop app release on the stable, beta or nightly channel through the desktop-publish GitHub workflow.
Cut Release
delexw/claude-code-trace
Cuts a new versioned release of claude-code-trace end-to-end without asking any questions.
Release
XGHeaven/homebox
Prepare, verify, and publish Homebox releases through the repository's tag-driven GitHub Actions workflow.
ZCF Release Automation
UfoMiao/zcf
Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.
Release
ankit/stylebot
Cut a Stylebot release — CHANGELOG entry, version bump, release PR, tag, and store zips.
More from manor-os/manor-ai
All 21 skills in this repoPDF
manor-os/manor-ai
A skill your agent uses whenever the user wants to do anything with PDF files.
Manor Workspace Blueprint
manor-os/manor-ai
A skill your agent uses when creating, exporting, hand-authoring, installing, upgrading, reverting, reviewing, or debugging any Manor Workspace Blueprint, especially when Workspace behavior differs…
PPTX
manor-os/manor-ai
A skill your agent uses to generate high-quality editable PowerPoint/PPTX decks from user requirements, topic prompts, or provided text/Markdown.
Video Edit
manor-os/manor-ai
Default workflow for editing, composing, or creating a finished video from screenshots, UI captures, uploaded clips, images, audio, or a written brief.
Intro
manor-os/manor-ai
Public English guide to the Manor AI OSS self-hosted product, its visible capabilities, and end-user workflows.
Skill Creator
manor-os/manor-ai
Create, update, review, and evaluate reusable Manor Skills. An agent skill from manor-os/manor-ai.
Related
Works with
Categories
Questions about Manor Release
What does Manor Release do?
A skill your agent uses when preparing, cutting, promoting, tagging, or validating a Manor public OSS release, beta/stable release, changelog entry, release notes, docs publish, or post-release…. Manor Release is an agent skill from manor-os/manor-ai. Use when preparing, cutting, promoting, tagging, or validating a Manor public OSS release, beta/stable release, changelog entry, release notes, docs publish, or post-release announcement.
When should I use Manor Release?
Manor Release fits situations like: validating a Manor public OSS release; beta/stable release; changelog entry; post-release announcement.
How do I install Manor Release in Claude Code?
Run `npx skills add manor-os/manor-ai --skill manor-release -a claude-code`. Or copy the skill folder (.agents/skills/manor-release in manor-os/manor-ai) into .claude/skills/manor-release in your project. Claude Code loads it when a task matches its description.
How do I install Manor Release in Codex?
Run `npx skills add manor-os/manor-ai --skill manor-release -a codex`. Or copy the skill folder (.agents/skills/manor-release in manor-os/manor-ai) into .agents/skills/manor-release in your project. Codex loads it when a task matches its description.
Can I use Manor Release 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 manor-os/manor-ai --skill manor-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/manor-release, .gemini/skills/manor-release, .github/skills/manor-release and .opencode/skills/manor-release in your project.
What does Manor Release need to run?
Going by SKILL.md and its folder, Manor Release needs the command-line tools its instructions call (git, npm and python). Our summary lists: Python 3.
Does Manor Release access the network?
SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Manor Release 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 Manor Release use?
Manor Release 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 Manor Release use?
About 529 tokens (SKILL.md is roughly 2.1k 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 Manor Release?
Skills that share tags, products or a category with Manor Release: Ccb GitHub (SeemSeam/claude_codex_bridge, 3.6k stars), Cline Desktop App Release (cline/cline, 70k stars), Cut Release (delexw/claude-code-trace, 377 stars) and Release (XGHeaven/homebox, 817 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Manor Release?
manor-os (a GitHub organization) maintains it in manor-os/manor-ai, which has 162 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on September 7, 2026.
Source: manor-os/manor-ai on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.