Diagnosing Superpowers Sessions
obra/superpowers
Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.
Pick up a GitHub issue and run the full investigate-build-review-merge pipeline for Forge from Codex.
Install Work On
$ npx skills add RapierCraftStudios/ForgeDock --skill work-on -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install RapierCraftStudios/ForgeDock work-on --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/RapierCraftStudios/ForgeDock.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/work-on .claude/skills/work-on && 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 "work-on" agent skill from https://github.com/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-on into .claude/skills/work-on/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-on", 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/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-onType 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 RapierCraftStudios/ForgeDock --skill work-on -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install RapierCraftStudios/ForgeDock work-on --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RapierCraftStudios/ForgeDock.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/work-on .agents/skills/work-on && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "work-on" agent skill from https://github.com/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-on into .agents/skills/work-on/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-on", 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 RapierCraftStudios/ForgeDock --skill work-on -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install RapierCraftStudios/ForgeDock work-on --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RapierCraftStudios/ForgeDock.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/work-on .cursor/skills/work-on && 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 "work-on" agent skill from https://github.com/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-on into .cursor/skills/work-on/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-on", 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/RapierCraftStudios/ForgeDock.git --path .agents/skills/work-on--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 RapierCraftStudios/ForgeDock --skill work-on -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install RapierCraftStudios/ForgeDock work-on --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RapierCraftStudios/ForgeDock.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/work-on .gemini/skills/work-on && 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 "work-on" agent skill from https://github.com/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-on into .gemini/skills/work-on/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-on", 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 RapierCraftStudios/ForgeDock work-onInstalls 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 RapierCraftStudios/ForgeDock --skill work-on -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/RapierCraftStudios/ForgeDock.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/work-on .github/skills/work-on && 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 "work-on" agent skill from https://github.com/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-on into .github/skills/work-on/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-on", 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 RapierCraftStudios/ForgeDock --skill work-on -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install RapierCraftStudios/ForgeDock work-on --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RapierCraftStudios/ForgeDock.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/work-on .opencode/skills/work-on && 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 "work-on" agent skill from https://github.com/RapierCraftStudios/ForgeDock/tree/main/.agents/skills/work-on into .opencode/skills/work-on/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-on", 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
work-on- GitHub stars
- 117
- Token cost
- ~750 tokens
- SKILL.md length
- 293 words
- Files
- 3
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Pick up a GitHub issue and run the full investigate-build-review-merge pipeline for Forge from Codex.
- Agent Workflows work in your project
- SKILL.md covers Repo Resolution Override, Codex Runtime Overrides, Forge Repo File Scope and Subcommand Mapping, plus 1 more section
- Calls gh
What it does
Work On is an agent skill from RapierCraftStudios/ForgeDock. Pick up a GitHub issue and run the full investigate-build-review-merge pipeline for Forge from Codex.
Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `build/SKILL.md` and `build/validate/SKILL.md`).
It sits in Agent Workflows. It works with GitHub. The repository describes itself as: ForgeDock — autonomous AI dev pipeline for Claude Code. GitHub as agent memory: issue in, PR out. The licence is AGPL-3.0.
When your agent uses it
- Agent Workflows work in your project
Example prompts
- “/work-on”
What it can do on your machine
Read from SKILL.md and the folder at commit 4b189df. 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:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, 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
Work On loads about 750 tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 293 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 RapierCraftStudios/ForgeDock at commit 4b189df, republished under its AGPL-3.0 licence (© RapierCraftStudios). 293 words, ~750 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
- Pick up a GitHub issue and run the full investigate-build-review-merge pipeline for Forge from Codex.
Forge Repo Adapter: work-on
Use commands/work-on.md as the authoritative state-machine source, but apply the Forge repo overrides below when running from Codex in this repository.
Repo Resolution Override
Inside the Forge repo, resolve issue targets like this unless the user explicitly prefixes another project:
| Input | Repo |
|---|---|
123, #123, next, empty | RapierCraftStudios/forgedock |
forge:123 | RapierCraftStudios/forgedock |
Satellite prefixes (e.g. mcp:5, sdk:12) are project-specific and defined in forge.yaml → repos.satellites. See commands/work-on.md Phase 0B for multi-repo routing.
For Forge repo issues, set:
GH_REPO=RapierCraftStudios/forgedockGH_FLAG=--repo RapierCraftStudios/forgedockREPO_PATH=/home/mrdubey/projects/forgedockSTAGING_BRANCH=stagingDEFAULT_BRANCH=main
Codex Runtime Overrides
- Treat any
.claude/worktrees/...example path in the shared command spec as.codex/worktrees/...for Codex execution in this repo. - Create and reuse worktrees under
/home/mrdubey/projects/forgedock/.codex/worktrees. - Prefer
gh api repos/{GH_REPO}/issues/{NUMBER}/commentsfor comment reads instead ofgh issue view --comments. - Treat GitHub Project-board sync as best-effort only for Forge issues. Do not block the pipeline if Forge-specific board/component mappings are absent.
- Create missing
workflow:*labels on demand if the Forge repo does not already have them. - Skill names: resolve
{FORGE_SKILL_PREFIX}asforge-with-nesting ({FORGE_SKILL_PREFIX}work-on:build->forge-work-on-build), perSkill Name Resolutionincommands/work-on.md. Do not use theforgedock:prefix or:nesting under Codex.
Forge Repo File Scope
When the shared workflow says to inspect domain files, prioritize Forge repo files instead:
commands/**/*.mddocs/**/*.mdscripts/**/*.shinstall.sh,install-codex.sh,update.shAGENTS.md,CLAUDE.md,CHANGELOG.md.agents/skills/**/*.md
Subcommand Mapping
When commands/work-on.md invokes nested skills, use these Codex adapters:
work-on:investigate-> repo-local.agents/skills/work-on/investigate/SKILL.mdwork-on:build-> repo-local.agents/skills/work-on/build/SKILL.mdwork-on:review-> repo-local.agents/skills/work-on/review/SKILL.mdwork-on:close-> installedforge-work-on-closework-on:decompose-> installedforge-work-on-decompose
If an installed forge-* skill exists for the nested command, use it. Otherwise read the referenced shared command file directly and continue manually.
Execution Rule
Preserve the shared Forge behavior from commands/work-on.md: GitHub state is the memory layer, FORGE:* comments remain machine-readable, and the routing loop continues until an explicit terminal condition is reached.
© RapierCraftStudios, AGPL-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
SKILL.md and 2 other files in .agents/skills/work-on of RapierCraftStudios/ForgeDock.
- SKILL.md
- build/SKILL.md
- build/validate/SKILL.md
Open the folder on GitHubat commit 4b189df
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Work On this skillRapierCraftStudios/ForgeDock | 117 | — | ~750 | Automated safety check: Pass | AGPL-3.0 | |
| Diagnosing Superpowers Sessionsobra/superpowers | 296k | 3 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Auto Skill Buildertradecatlabs/vibe-coding-cn | 17k | 1 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Agentic Workflow Designerdotnet/Open-XML-SDK | 4.6k | 2 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Skill Seekers Builderyusufkaraaslan/Skill_Seekers | 15k | — | ~760 | Automated safety check: Pass | MIT | |
| Repomix Codebase Packeryamadashy/repomix | 29k | — | ~1.3k | Automated safety check: Notes | MIT |
Similar skills
Auto Skill Builder
tradecatlabs/vibe-coding-cn
Meta-skill that turns docs, APIs, code or specs into a reusable skill with references and a quality gate, and refactors skills that are unclear or misfire.
- Official
Agentic Workflow Designer
dotnet/Open-XML-SDK
Interviews you one question at a time about goal, trigger, permissions and data needs, then drafts a single agentic workflow markdown file.
Skill Seekers Builder
yusufkaraaslan/Skill_Seekers
Detects the type of a knowledge source and uses the Skill Seekers MCP tools to turn docs, repos, PDFs or videos into packaged AI skills.
Repomix Codebase Packer
yamadashy/repomix
Packs a local directory or remote GitHub repository into one AI-friendly file with Repomix, then searches it to explore structure, find patterns and count tokens.
DBS Skill Maker
dontbesilent2025/dbskill
Turns a problem you keep running into into a single installable, tested skill, and prepares a GitHub repository only when you ask to share it.
More from RapierCraftStudios/ForgeDock
Quality Gate
RapierCraftStudios/ForgeDock
Run a Forge-aware pre-commit quality gate from Codex. An agent skill from RapierCraftStudios/ForgeDock.
ForgeDock PR Review Adapter
RapierCraftStudios/ForgeDock
Adapts a shared pull request review flow to the ForgeDock repository, with its own change categories, shell and installer checks, and optional sub-agent fan-out.
Forge Issue Investigator
RapierCraftStudios/ForgeDock
Repo adapter that runs the investigation step of the ForgeDock work-on pipeline on a GitHub issue and posts a FORGE:INVESTIGATOR report comment.
Work On Review
RapierCraftStudios/ForgeDock
Push a Forge worktree branch, create a PR, and delegate review through the Forge Codex review adapter.
Related
Works with
Categories
Questions about Work On
What does Work On do?
Pick up a GitHub issue and run the full investigate-build-review-merge pipeline for Forge from Codex. Work On is an agent skill from RapierCraftStudios/ForgeDock. Pick up a GitHub issue and run the full investigate-build-review-merge pipeline for Forge from Codex.
When should I use Work On?
Work On fits situations like: agent Workflows work in your project.
How do I install Work On in Claude Code?
Run `npx skills add RapierCraftStudios/ForgeDock --skill work-on -a claude-code`. Or copy the skill folder (.agents/skills/work-on in RapierCraftStudios/ForgeDock) 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 RapierCraftStudios/ForgeDock --skill work-on -a codex`. Or copy the skill folder (.agents/skills/work-on in RapierCraftStudios/ForgeDock) 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 RapierCraftStudios/ForgeDock --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 the command-line tools its instructions call (gh).
Does Work On access the network?
SKILL.md contains no URLs. Its commands use gh, 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. Review the folder before installing.
What licence does Work On use?
Work On is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Work On use?
About 750 tokens (SKILL.md is roughly 3k 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: Diagnosing Superpowers Sessions (obra/superpowers, 296k stars), Auto Skill Builder (tradecatlabs/vibe-coding-cn, 17k stars), Agentic Workflow Designer (dotnet/Open-XML-SDK, 4.6k stars) and Skill Seekers Builder (yusufkaraaslan/Skill_Seekers, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Work On?
RapierCraftStudios (a GitHub organization) maintains it in RapierCraftStudios/ForgeDock, which has 117 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.
Source: RapierCraftStudios/ForgeDock on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.