Agent skill

Work On

by goern in goern/forgejo-mcp

Start focused work on a bead — rename the tab and the Claude session, create the worktree, and load the issue

GPL-3.0-or-laterAuto-check passedDevelopment

Install Work On

skills CLI
$ npx skills add goern/forgejo-mcp --skill work-on -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install goern/forgejo-mcp work-on --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/goern/forgejo-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/work-on .claude/skills/work-on && rm -rf skills-src

Use ~/.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/

Facts

Skill name
work-on
GitHub stars
141
Token cost
~1k tokens
SKILL.md length
499 words
Files
3 (incl. scripts)
Skills in repo
15
Repo updated
First seen
Licence
GPL-3.0-or-later

At a glance

Start focused work on a bead — rename the tab and the Claude session, create the worktree, and load the issue

  • Works in 5 steps: no argument means stop → load the bead (this is also the validity… → rename the herdr tab to the bead id → …
  • Tasks that involve Git worktrees
  • SKILL.md covers Model, Argument, Step 0 — no argument means stop and Step 1 — load the bead (this…, plus 4 more sections
  • Runs Shell scripts from its folder; calls git

What it does

Work On is an agent skill from goern/forgejo-mcp. Start focused work on a bead — rename the tab and the Claude session, create the worktree, and load the issue

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `scripts/herdr-rename-tab.sh` and `scripts/session-title.sh`). Compatibility notes: Requires the bd, wt and herdr CLIs, plus the wt-switch-create skill; the session rename additionally needs the UserPromptSubmit hook from the README

It sits in Development, covering Git worktrees. The repository describes itself as: MIRROR ONLY!! This Model Context Protocol (MCP) server provides tools and resources for interacting with the Forgejo (specifically Codeberg.org) REST API. The licence is GPL-3.0-or-later.

When your agent uses it

  • Tasks that involve Git worktrees

Example prompts

  • “/work-on”

Requirements

  • A Bash shell
  • Compatibility (from SKILL.md): Requires the `bd`, `wt` and `herdr` CLIs, plus the `wt-switch-create` skill; the session rename additionally needs the `UserPromptSubmit` hook from the README

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. no argument means stop
  2. load the bead (this is also the validity check)
  3. rename the herdr tab to the bead id
  4. create the worktree and enter it
  5. report

What it can do on your machine

Read from SKILL.md and the folder at commit 1f51f83. 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 2 files in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use 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.

  • Compatibility

    Requires the `bd`, `wt` and `herdr` CLIs, plus the `wt-switch-create` skill; the session rename additionally needs the `UserPromptSubmit` hook from the README

    From compatibility in the SKILL.md frontmatter.

Context cost

Work On loads about 1k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 499 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~29
When it runs · the whole SKILL.md, loaded when a task matches
~1k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from goern/forgejo-mcp at commit 1f51f83, republished under its GPL-3.0-or-later licence (© goern). 499 words, ~1,045 tokens.

Download SKILL.mdSave it as .claude/skills/work-on/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
work-on
description
Start focused work on a bead — rename the tab and the Claude session, create the worktree, and load the issue
compatibility
Requires the `bd`, `wt` and `herdr` CLIs, plus the `wt-switch-create` skill; the session rename additionally needs the `UserPromptSubmit` hook from the README
argument-hint
<bead-id>
license
GPL-3.0-or-later

Model

Run this skill's steps on Sonnet. Skills can't pin a model via frontmatter (that's a Command-only field) — this is a best-effort instruction to the invoking agent, not an enforced constraint.

Argument

Bead id: $ARGUMENTS

Step 0 — no argument means stop

If $ARGUMENTS is empty, print exactly the help text below and do nothing else. No tools, no worktree, no renames.

/work-on <bead-id>

Sets up a focused work session for one bead:
  1. bd show <bead-id>              — validate the id and load it into context
  2. herdr tab rename               — THIS session's tab label becomes the bead id
  2b. session title queued          — the Claude session takes the same name
  3. /wt-switch-create <bead-id>    — worktree + branch named after the bead,
                                      session cwd moves into it

Example: /work-on myrepo-5jwr
Find work with: bd ready

Step 1 — load the bead (this is also the validity check)

bash
bd show $ARGUMENTS

If the bead does not exist, stop here and report it — do not create a worktree or rename anything for a bogus id.

Step 2 — rename the herdr tab to the bead id

bash
scripts/herdr-rename-tab.sh "$ARGUMENTS"

(Run it from the skill's own directory, or by absolute path — it lives next to this file.)

The script renames the tab hosting this session, resolved from the HERDR_PANE_ID that herdr exports into every pane it spawns. Never resolve the tab from herdr api snapshot's focused_tab_id: that is whichever tab is in front at the moment the command lands, so switching tabs while the skill runs renames a bystander.

Best effort — every failure is non-fatal, report it and carry on with the remaining steps:

exitmeaning
0renamed
3HERDR_PANE_ID unset — session is not inside a herdr pane, nothing to rename
4pane unknown to the server (herdr not running, or the pane is gone)
5herdr rejected the rename
Show full SKILL.md (274 more words)Show less

Step 2b — give the Claude session the same name

bash
scripts/session-title.sh queue "$ARGUMENTS"

The tab label and the session name should never disagree, so this runs right after Step 2 with the same argument.

A session cannot rename itself mid-turn — Claude Code accepts sessionTitle only from the UserPromptSubmit and SessionStart hooks, and /rename is a human-only builtin. The script therefore queues the label; the UserPromptSubmit hook (see the README) applies it when the user sends their next message. Tell the user that in the Step 4 report: the tab flips now, the session name one message later.

Best effort, same as the tab rename:

exitmeaning
0queued
3CLAUDE_CODE_SESSION_ID unset — not a Claude Code session, nothing to queue

If the hook is not installed the label is queued and never consumed, which is harmless: the file is dropped after seven days. Do not try to work around a missing hook by editing ~/.claude/sessions/*.json — that registry is owned by the running session and your write will be overwritten.

Step 3 — create the worktree and enter it

Invoke the wt-switch-create skill with the bead id as the branch name:

Skill(skill: "wt-switch-create", args: "$ARGUMENTS")

Follow that skill exactly — it owns worktree creation, the already-exists/denied/unreachable recovery paths, and the cleanup contract. Do not hand-roll wt switch or git worktree add here.

No task text is passed after --: the bead body from Step 1 is the task, and the user drives from there.

Step 4 — report

One line: bead id, title, worktree path, branch, plus the tab/session rename outcome (and, when the session name was only queued, that it lands on the next message). Then state what the bead asks for and wait for the user.

© goern, GPL-3.0-or-later. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts) in .agents/skills/work-on of goern/forgejo-mcp.

  • SKILL.md
  • scripts/herdr-rename-tab.sh
  • scripts/session-title.sh

Open the folder on GitHubat commit 1f51f83

Compare with similar skills

Work On 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.

Work On compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Work On this skillgoern/forgejo-mcp141—~1kAutomated safety check: PassGPL-3.0-or-later
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Migrate Core Code to Submodulestinyhumansai/openhuman42k—~2.6kAutomated safety check: PassGPL-3.0
Finishing A Development Branchfarm-fe/farm5.6k34 repos~1.8kAutomated safety check: PassMIT
Git Worktree Cleanuplobehub/lobehub83k—~2.8kAutomated safety check: PassCustom licence
Keep Codex Fastvibeforge1111/keep-codex-fast1.6k—~3.1kAutomated safety check: PassMIT

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Migrate Core Code to Submodules

    tinyhumansai/openhuman

    Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.

    42k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed
  • A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…

    5.6k GitHub starsUsed in 34 repos~1.8k tokens
    DevelopmentAuto-check passed
  • Git Worktree Cleanup

    lobehub/lobehub

    Audits stale Git worktrees and branches with a bundled script, classifies each one, and deletes only after you approve the exact candidates.

    83k GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Keep Codex Fast

    vibeforge1111/keep-codex-fast

    A skill your agent uses when Codex feels slow or bloated, when local sessions/logs/worktrees/config have grown over time, or when a user wants safe maintenance for Codex Desktop/CLI state.

    1.6k GitHub stars~3.1k tokensUpdated 5 mo ago
    DevelopmentAuto-check passed
  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from goern/forgejo-mcp

All 15 skills in this repo
  • Release Openspec

    goern/forgejo-mcp

    A skill your agent uses when releasing OpenSpec: audit merged work and changeset coverage, decide whether a catch-up changeset PR is needed, prepare or resume the Changesets Version Packages PR, cut…

    141 GitHub starsUsed in 1 repo~3.2k tokens
    Auto-check passed
  • Unified Notifications

    goern/forgejo-mcp

    Fetch and display notifications from both GitHub and Codeberg in a unified markdown view with clickable links.

    141 GitHub stars~802 tokensUpdated today
    Auto-check passed
  • Caveman Compress

    goern/forgejo-mcp

    Compress a memory file such as CLAUDE.md or a todo list into caveman format to save input tokens, keeping a readable backup.

    141 GitHub starsUsed in 1 repo~1.2k tokens
    Auto-check: notes
  • Draft Openspec Docs

    goern/forgejo-mcp

    Collaborative page-drafting mode for the OpenSpec docs. An agent skill from goern/forgejo-mcp.

    141 GitHub starsUsed in 1 repo~815 tokens
    Auto-check passed
  • Verify Openspec Docs

    goern/forgejo-mcp

    Fact-checks OpenSpec user documentation with a fresh-context subagent that re-runs commands and checks claims against source.

    141 GitHub starsUsed in 1 repo~1.1k tokens
    Auto-check passed
  • Wt Switch Create

    goern/forgejo-mcp

    Create a new worktrunk worktree (optionally in another repo) and switch this session's working directory into it.

    141 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed

Categories

Questions about Work On

What does Work On do?

Start focused work on a bead — rename the tab and the Claude session, create the worktree, and load the issue. Work On is an agent skill from goern/forgejo-mcp.

When should I use Work On?

Work On fits situations like: tasks that involve Git worktrees.

How do I install Work On in Claude Code?

Run `npx skills add goern/forgejo-mcp --skill work-on -a claude-code`. Or copy the skill folder (.agents/skills/work-on in goern/forgejo-mcp) into .claude/skills/work-on in your project. Claude Code loads it when a task matches its description.

How do I install Work On in Codex?

Run `npx skills add goern/forgejo-mcp --skill work-on -a codex`. Or copy the skill folder (.agents/skills/work-on in goern/forgejo-mcp) into .agents/skills/work-on in your project. Codex loads it when a task matches its description.

Can I use Work On 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 goern/forgejo-mcp --skill work-on -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/work-on, .gemini/skills/work-on, .github/skills/work-on and .opencode/skills/work-on in your project.

What does Work On need to run?

Going by SKILL.md and its folder, Work On needs a shell for the scripts in its folder and the command-line tools its instructions call (git). Our summary lists: A Bash shell. Compatibility (from SKILL.md): Requires the `bd`, `wt` and `herdr` CLIs, plus the `wt-switch-create` skill; the session rename additionally needs the `UserPromptSubmit` hook from the README.

Does Work On access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Work On 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Work On use?

Work On is published under the GPL-3.0-or-later licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Work On use?

About 1k tokens (SKILL.md is roughly 4.2k 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 Work On?

Skills that share tags, products or a category with Work On: Finishing a Development Branch (obra/superpowers, 296k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars), Finishing A Development Branch (farm-fe/farm, 5.6k stars) and Git Worktree Cleanup (lobehub/lobehub, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Work On?

goern (a GitHub user) maintains it in goern/forgejo-mcp, which has 141 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 8, 2026.

Source: goern/forgejo-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.