Offload
Make this session the ARCHITECT and hand implementation to a builder harness you can watch (codex, claude, opencode, pi, grok or a custom command), judged slice by slice on frozen gates and an independent review. Use when the user says "offload", "hand this to codex", "hand this to a builder", "architect mode", "have codex build this", or invokes /offload.
Install
/plugin marketplace add borkweb/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add borkweb/skills --skill offloadgit clone --depth 1 https://github.com/borkweb/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/core/offload ~/.claude/skills/offloadPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
You are the **ARCHITECT**. The **BUILDER** is whichever harness `~/.borkweb-skills/config.json` resolves to (see *Resolve the builder harness*). The repo's commits are the permanent code record; the **session handoff** is the reasoning record. The human is the final judge. ## Resolve the handoff CLI and session key The external bridge supports native Claude and Codex architect identities. `handoff.mjs key` reads `$CLAUDE_CODE_SESSION_ID`, or namespaced `$CODEX_SESSION_ID` when Claude's variable is absent. Never copy a Codex identity into a Claude variable. Do not run bridge commands during unrelated tasks. - Locate `handoff.mjs` beside this loaded `SKILL.md`, check that it exists, and run it with `node` by absolute path. Startup notices from older versions may name stale paths; this skill's location is authoritative. If it is gone after an upgrade, refresh skill discovery and load the current offload skill; never guess a cache version or write a replacement helper. Resolve your session key with `SID=$(node "<…>/handoff.mjs" key)` and use it for explicit identity arguments. - **Resolve your handoff on each turn** (shell variables do not survive turns): `HANDOFF=$(node "<…>/handoff.mjs" resolve "$PWD" "<project/slice title>")`. It derives one canonical path from the native session environment, creating the doc on the first turn (the title applies only then). The SessionStart hook's `Your handoff: <path>`
Details
- Skill name
offload- Repository
- borkweb/skills
- Path
skills/core/offload/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Offload skill do?
Make this session the ARCHITECT and hand implementation to a builder harness you can watch (codex, claude, opencode, pi, grok or a custom command), judged slice by slice on frozen gates and an independent review. Use when the user says "offload", "hand this to codex", "hand this to a builder", "architect mode", "have codex build this", or invokes /offload.
How do I install the Offload skill?
Claude Code plugin: /plugin marketplace add borkweb/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Offload popular?
It lives in borkweb/skills, which has 9 GitHub stars and 0 forks.
Related skills
Prototype
9borkweb/skills
Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".
Agents Md Lint
9borkweb/skills
Audit and trim AI agent instruction files (AGENTS.md, CLAUDE.md, CONVENTIONS.md, .cursorrules, etc.) by testing which facts an AI agent can discover from code alone. Use when asked to lint, audit, optimize, prune, or trim any agent instruction file in a repository. Removes redundant documentation that wastes context tokens. Supports a dry-run mode that reports findings without modifying files.
Auto Scope
9borkweb/skills
Scopes a coding task before implementation — names the handful of files actually relevant (read/edit these), the areas to leave alone, and any open scope questions, so work doesn't start by reading the whole repo. Fires proactively at the start of substantive, multi-file, or unfamiliar-area work; stays silent on single-file edits, one-line fixes, questions, and continued work in an area already scoped this session. Use when beginning a feature, bug fix, or refactor that could plausibly touch several files or an area not yet seen this session.
Plan Devex Review
9borkweb/skills
Review a plan for a developer-facing surface (API, CLI, SDK, config or install) for setup friction, ergonomics, error messages and compatibility. Use for 'devex review', 'review the API design', 'is this CLI ergonomic' or 'review the onboarding for developers'.
Complete
9borkweb/skills
Drive a coding goal with two or more slices to merge-ready through delegated builders, frozen gates and independent review. Use for '/complete', 'run the whole loop', 'take this to merge-ready' or a plan that needs a fleet of builders. One slice goes to offload instead.
Plan Eng Review
9borkweb/skills
Review an implementation plan's architecture, contracts, failure paths, concurrency and test strategy before code is written. Use for 'eng review this plan', 'review the architecture', 'is this plan sound' or when do runs plan reviews.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.