Nushell
ccusage/ccusage
Guides ccusage Nushell scripts. An agent skill from ccusage/ccusage.
A skill your agent uses to prepare a honk release and follow the maintainer's tag and publication sequence.
Install Honk Release
$ npx skills add daeuniverse/honk --skill honk-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install daeuniverse/honk honk-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/daeuniverse/honk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/honk-release .claude/skills/honk-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 "honk-release" agent skill from https://github.com/daeuniverse/honk/tree/main/.agents/skills/honk-release into .claude/skills/honk-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honk-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/daeuniverse/honk/tree/main/.agents/skills/honk-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 daeuniverse/honk --skill honk-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install daeuniverse/honk honk-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/daeuniverse/honk.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/honk-release .agents/skills/honk-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 "honk-release" agent skill from https://github.com/daeuniverse/honk/tree/main/.agents/skills/honk-release into .agents/skills/honk-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honk-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 daeuniverse/honk --skill honk-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install daeuniverse/honk honk-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/daeuniverse/honk.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/honk-release .cursor/skills/honk-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 "honk-release" agent skill from https://github.com/daeuniverse/honk/tree/main/.agents/skills/honk-release into .cursor/skills/honk-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honk-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/daeuniverse/honk.git --path .agents/skills/honk-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 daeuniverse/honk --skill honk-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install daeuniverse/honk honk-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/daeuniverse/honk.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/honk-release .gemini/skills/honk-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 "honk-release" agent skill from https://github.com/daeuniverse/honk/tree/main/.agents/skills/honk-release into .gemini/skills/honk-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honk-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 daeuniverse/honk honk-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 daeuniverse/honk --skill honk-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/daeuniverse/honk.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/honk-release .github/skills/honk-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 "honk-release" agent skill from https://github.com/daeuniverse/honk/tree/main/.agents/skills/honk-release into .github/skills/honk-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honk-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 daeuniverse/honk --skill honk-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 daeuniverse/honk honk-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/daeuniverse/honk.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/honk-release .opencode/skills/honk-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 "honk-release" agent skill from https://github.com/daeuniverse/honk/tree/main/.agents/skills/honk-release into .opencode/skills/honk-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honk-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
honk-release- GitHub stars
- 156
- Token cost
- ~353 tokens
- SKILL.md length
- 181 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
A skill your agent uses to prepare a honk release and follow the maintainer's tag and publication sequence.
- Works in 5 steps: Confirm the intended main tip has been… → Confirm its branch CI from… → The maintainer creates and pushes the… → …
- Prepare a honk release and follow the maintainers tag and publication sequence
- SKILL.md covers Steps and Checklist
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Honk Release is an agent skill from daeuniverse/honk. Use to prepare a honk release and follow the maintainer's tag and publication sequence.
Its SKILL.md is about 350 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud. It works with GitHub Actions and GitHub. The repository describes itself as: Inspired by dae & sing-box, it's an ebpf based proxy with clash-api. The licence is GPL-3.0.
When your agent uses it
- Prepare a honk release and follow the maintainers tag and publication sequence
Example prompts
- “/honk-release”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Confirm the intended main tip has been pushed.
- Confirm its branch CI from .github/workflows/ci.yml is green in GitHub Actions, through the web UI or API.
- The maintainer creates and pushes the next tag at that tip. Tag naming: .agents/rules/release.md, "Release process (standing convention)".
- The tag runs .github/workflows/release.yml. Wait for its test, build and release jobs to finish and create the GitHub Release.
- The maintainer edits the Release notes. Notes format and author attribution: .agents/rules/release.md, "Release process (standing…
What it can do on your machine
Read from SKILL.md and the folder at commit a8a74a4. 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
No scripts in the folder and no shell commands in SKILL.md.
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
Honk Release loads about 353 tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 181 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
The full file from daeuniverse/honk at commit a8a74a4, republished under its GPL-3.0 licence (© daeuniverse). 181 words, ~353 tokens.
Download SKILL.mdSave it as
.claude/skills/honk-release/SKILL.md (or your agent's skills folder).- name
- honk-release
- description
- Use to prepare a honk release and follow the maintainer's tag and publication sequence.
Read first: AGENTS.md and .agents/rules/release.md; then .github/workflows/release.yml.
Publication belongs to the maintainer. Contributors can prepare the notes without publishing.
Steps
- Confirm the intended
maintip has been pushed. - Confirm its branch CI from
.github/workflows/ci.ymlis green in GitHub Actions, through the web UI or API. - The maintainer creates and pushes the next tag at that tip. Tag naming:
.agents/rules/release.md, "Release process (standing convention)". - The tag runs
.github/workflows/release.yml. Wait for its test, build and release jobs to finish and create the GitHub Release. - The maintainer edits the Release notes. Notes format and author attribution:
.agents/rules/release.md, "Release process (standing convention)". For author lookup and note editing, use theghcommands there or the GitHub commit pages and Release editor in the web UI; the GitHub commits and releases APIs are another option.
Checklist
- The intended
maintip is pushed and its branch CI is green. - The maintainer created and pushed the next tag under the release rule.
- The tag workflow finished and created the Release.
- The maintainer edited the notes using the release rule's format and author attribution.
© daeuniverse, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/honk-release of daeuniverse/honk.
Open the folder on GitHubat commit a8a74a4
Compare with similar skills
Honk 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 |
|---|---|---|---|---|---|---|
| Honk Release this skilldaeuniverse/honk | 156 | — | ~353 | Automated safety check: Pass | GPL-3.0 | |
| Nushellccusage/ccusage | 19k | — | ~938 | Automated safety check: Pass | Custom licence | |
| Make GitHub Actions Workflowdotnet/efcore | 15k | — | ~2.1k | Automated safety check: Pass | MIT | |
| AI News RadarLearnPrompt/ai-news-radar | 1.8k | — | ~2.5k | Automated safety check: Notes | MIT | |
| Clawsweeperopenclaw/openclaw | 392k | — | ~3k | Automated safety check: Pass | MIT | |
| ONNX Runtime CI Managementmicrosoft/onnxruntime | 22k | — | ~4.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Make GitHub Actions Workflow
dotnet/efcore
Create GitHub Actions workflows for CI, automation, or PR management.
AI News Radar
LearnPrompt/ai-news-radar
A skill your agent uses when working on AI News Radar, 24 小时 AI 更新雷达, AI 更新雷达, 伯乐Skill, or Scout Skill: finding high-signal AI/tech sources, adding RSS/OPML/GitHub feeds, checking source health…
Clawsweeper
openclaw/openclaw
A skill your agent uses for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed…
- Official
ONNX Runtime CI Management
microsoft/onnxruntime
Triggers, re-runs and unblocks the CI checks on an ONNX Runtime pull request, after diagnosing whether a failure is transient or needs a code change.
CI Watchdog
latitude-dev/latitude-llm
Continuously monitor GitHub PR CI checks and automatically fix failures until all checks pass.
More from daeuniverse/honk
Honk Real Ebpf Tests
daeuniverse/honk
A skill your agent uses to choose native Linux, CI-shaped VM or unavailable-environment paths for real eBPF tests.
Honk Config Change
daeuniverse/honk
A skill your agent uses for configuration contracts, parsers, reference docs and their core or outbound consumers.
Honk Change
daeuniverse/honk
A skill your agent uses for any honk change to plan, review, verify and prepare the PR.
Related
Works with
Categories
Questions about Honk Release
What does Honk Release do?
A skill your agent uses to prepare a honk release and follow the maintainer's tag and publication sequence. Honk Release is an agent skill from daeuniverse/honk. Use to prepare a honk release and follow the maintainer's tag and publication sequence.
When should I use Honk Release?
Honk Release fits situations like: prepare a honk release and follow the maintainers tag and publication sequence.
How do I install Honk Release in Claude Code?
Run `npx skills add daeuniverse/honk --skill honk-release -a claude-code`. Or copy the skill folder (.agents/skills/honk-release in daeuniverse/honk) into .claude/skills/honk-release in your project. Claude Code loads it when a task matches its description.
How do I install Honk Release in Codex?
Run `npx skills add daeuniverse/honk --skill honk-release -a codex`. Or copy the skill folder (.agents/skills/honk-release in daeuniverse/honk) into .agents/skills/honk-release in your project. Codex loads it when a task matches its description.
Can I use Honk 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 daeuniverse/honk --skill honk-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/honk-release, .gemini/skills/honk-release, .github/skills/honk-release and .opencode/skills/honk-release in your project.
What does Honk Release need to run?
SKILL.md names no scripts, command-line tools or credentials: Honk Release is instructions for the agent only.
Does Honk Release 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 Honk 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 Honk Release use?
Honk Release is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Honk Release use?
About 353 tokens (SKILL.md is roughly 1.4k 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 Honk Release?
Skills that share tags, products or a category with Honk Release: Nushell (ccusage/ccusage, 19k stars), Make GitHub Actions Workflow (dotnet/efcore, 15k stars), AI News Radar (LearnPrompt/ai-news-radar, 1.8k stars) and Clawsweeper (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Honk Release?
daeuniverse (a GitHub organization) maintains it in daeuniverse/honk, which has 156 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 9, 2026.
Source: daeuniverse/honk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.