Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
Prepare or publish a Crimson patch, minor, or development release with changelog notes, version and lock updates, validation, and tag-triggered publishing.
Install Crimson Release
$ npx skills add banteg/crimson --skill crimson-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install banteg/crimson crimson-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/banteg/crimson.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/crimson-release .claude/skills/crimson-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 "crimson-release" agent skill from https://github.com/banteg/crimson/tree/master/.codex/skills/crimson-release into .claude/skills/crimson-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crimson-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/banteg/crimson/tree/master/.codex/skills/crimson-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 banteg/crimson --skill crimson-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install banteg/crimson crimson-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/banteg/crimson.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/crimson-release .agents/skills/crimson-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 "crimson-release" agent skill from https://github.com/banteg/crimson/tree/master/.codex/skills/crimson-release into .agents/skills/crimson-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crimson-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 banteg/crimson --skill crimson-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install banteg/crimson crimson-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/banteg/crimson.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/crimson-release .cursor/skills/crimson-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 "crimson-release" agent skill from https://github.com/banteg/crimson/tree/master/.codex/skills/crimson-release into .cursor/skills/crimson-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crimson-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/banteg/crimson.git --path .codex/skills/crimson-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 banteg/crimson --skill crimson-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install banteg/crimson crimson-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/banteg/crimson.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/crimson-release .gemini/skills/crimson-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 "crimson-release" agent skill from https://github.com/banteg/crimson/tree/master/.codex/skills/crimson-release into .gemini/skills/crimson-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crimson-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 banteg/crimson crimson-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 banteg/crimson --skill crimson-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/banteg/crimson.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/crimson-release .github/skills/crimson-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 "crimson-release" agent skill from https://github.com/banteg/crimson/tree/master/.codex/skills/crimson-release into .github/skills/crimson-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crimson-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 banteg/crimson --skill crimson-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 banteg/crimson crimson-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/banteg/crimson.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/crimson-release .opencode/skills/crimson-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 "crimson-release" agent skill from https://github.com/banteg/crimson/tree/master/.codex/skills/crimson-release into .opencode/skills/crimson-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crimson-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
crimson-release- GitHub stars
- 185
- Token cost
- ~896 tokens
- SKILL.md length
- 456 words
- Files
- 2
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- None found
At a glance
Prepare or publish a Crimson patch, minor, or development release with changelog notes, version and lock updates, validation, and tag-triggered publishing.
- Works in 5 steps: Inspect the branch and git status… → Run just check before changing the… → Review commits since the previous… → …
- Tasks that involve Changelog and release notes
- SKILL.md covers Scope and version, Prepare and Publish when authorized
- Calls uv, git and just
What it does
Crimson Release is an agent skill from banteg/crimson. Prepare or publish a Crimson patch, minor, or development release with changelog notes, version and lock updates, validation, and tag-triggered publishing.
Its SKILL.md is about 900 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. The repository describes itself as: a faithful rewrite of crimsonland 1.9.93 from 2003.
When your agent uses it
- Tasks that involve Changelog and release notes
Example prompts
- “/crimson-release”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Inspect the branch and git status --porcelain. Use an up-to-date master or a clean isolated worktree based on it; preserve unrelated work…
- Run just check before changing the version. Resolve new failures before continuing. For gameplay changes, also check the final gameplay…
- Review commits since the previous release. Add ## to CHANGELOG.md, using its existing player-facing style and an Under the hood section…
- Run uv version --bump (or the explicit version), then uv lock. Inspect the diff: the package and its editable lock entry should match…
- Validate the release section exactly as the workflow extracts it
What it can do on your machine
Read from SKILL.md and the folder at commit f8e7434. 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:
uvgitjust
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv and git, 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
Crimson Release loads about 896 tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 456 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 456 words (~896 tokens).
“Read the extracted notes and run uv lock --check, uv build, and checks appropriate to any additional edits. Confirm the wheel/sdist version matches. If preparation is all that was requested, present the diff and validation results here.”
- name
- crimson-release
Files
SKILL.md and 1 other file in .codex/skills/crimson-release of banteg/crimson.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit f8e7434
Compare with similar skills
Crimson 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 |
|---|---|---|---|---|---|---|
| Crimson Release this skillbanteg/crimson | 185 | — | ~896 | Automated safety check: Pass | None | |
| Simple Englishmoeru-ai/airi | 50k | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| StarRocks Release NotesStarRocks/starrocks | 12k | — | ~1.9k | Automated safety check: Notes | Apache-2.0 | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Mole CLI Release Flowtw93/Mole | 70k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
StarRocks Release Notes
StarRocks/starrocks
Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.
Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
Release
PrefectHQ/fastmcp
Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.
More from banteg/crimson
Ast Grep
banteg/crimson
Use ast-grep for Python structural code exploration, mechanical codemods, and rule maintenance in this repo.
Related
Categories
Questions about Crimson Release
What does Crimson Release do?
Prepare or publish a Crimson patch, minor, or development release with changelog notes, version and lock updates, validation, and tag-triggered publishing. Crimson Release is an agent skill from banteg/crimson. Prepare or publish a Crimson patch, minor, or development release with changelog notes, version and lock updates, validation, and tag-triggered publishing.
When should I use Crimson Release?
Crimson Release fits situations like: tasks that involve Changelog and release notes.
How do I install Crimson Release in Claude Code?
Run `npx skills add banteg/crimson --skill crimson-release -a claude-code`. Or copy the skill folder (.codex/skills/crimson-release in banteg/crimson) into .claude/skills/crimson-release in your project. Claude Code loads it when a task matches its description.
How do I install Crimson Release in Codex?
Run `npx skills add banteg/crimson --skill crimson-release -a codex`. Or copy the skill folder (.codex/skills/crimson-release in banteg/crimson) into .agents/skills/crimson-release in your project. Codex loads it when a task matches its description.
Can I use Crimson 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 banteg/crimson --skill crimson-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/crimson-release, .gemini/skills/crimson-release, .github/skills/crimson-release and .opencode/skills/crimson-release in your project.
What does Crimson Release need to run?
Going by SKILL.md and its folder, Crimson Release needs the command-line tools its instructions call (uv, git and just).
Does Crimson Release access the network?
SKILL.md contains no URLs. Its commands use uv and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Crimson 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 Crimson Release use?
No licence was found for Crimson Release or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Crimson Release use?
About 896 tokens (SKILL.md is roughly 3.6k 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 Crimson Release?
Skills that share tags, products or a category with Crimson Release: Simple English (moeru-ai/airi, 50k stars), StarRocks Release Notes (StarRocks/starrocks, 12k stars), Cutting A Release (TriliumNext/Trilium, 38k stars) and Mole CLI Release Flow (tw93/Mole, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Crimson Release?
banteg (a GitHub user) maintains it in banteg/crimson, which has 185 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 9, 2026.
Source: banteg/crimson on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.