Agent skill · Backend & API

devin-handoff

Spin off parallel cloud Devin sessions. Hand off a task to a fresh cloud Devin session that runs in the background — each gets its own VM with shell, browser, and full repo access — so you can fan out several sessions at once and keep working locally while they run. Use for parallel or long-running work and anything needing Devin's full environment: multi-file changes, running servers, CI work, browser automation, migrations, or large refactors. Also an API for reading and interacting with current sessions — given a session URL or ID, the check/poll commands return its PR, status, branch, and

club-coggithub.com/club-cogGitHub ↗
claude-codecodexcursorships scriptsMIT
Install
npx skills add club-cog/devin-handoff --skill devin-handoff --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 3 KB
Bundled scripts: yes
Path: .agents/skills/devin-handoff/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 54
Language: Shell

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Devin Handoff Hand off a task to Devin. Devin gets its own VM with shell, browser, and full repo access. You get a URL to watch progress, or can poll until the session completes. All `scripts/devin-handoff.sh` paths below are relative to this skill's directory. If installed as a Claude Code or Codex plugin, use `"${CLAUDE_PLUGIN_ROOT}/.agents/skills/devin-handoff/scripts/devin-handoff.sh"`. ## Prerequisites - `DEVIN_API_KEY` env var (get one at https://app.devin.ai/settings/api-keys) - `curl`, `jq` in PATH - `git` (optional, for auto-detecting repo/branch/diff) ## When to use - Task needs a running server, database, or Docker - Task requires browser interaction (OAuth, screenshots, E2E tests) - Task involves CI/CD pipelines or deployments - Task is long-running and the user wants to continue locally - You need parallel execution on a separate machine ## Steps ### 1. Gather context From the current working directory: 1. **Repo**: Run `git remote get-url origin`, extract `owner/repo` 2. **Branch**: Run `git rev-parse --abbrev-ref HEAD` 3. **Diff**: Run `git diff HEAD` (truncated to 100KB automatically) 4. **Task**: The user's request, concise and specific 5. **Context** (optional):

What's inside
Steps it walks through
  1. Prerequisites
  2. When to use
  3. Steps
  4. 1. Gather context
  5. 2. Create the session
  6. 3. Report the URL and poll
  7. 4. Archive when done (optional)
Ships with 1 file
  • scripts/devin-handoff.sh
Commands it runs
scripts/devin-handoff.sh create \
scripts/devin-handoff.sh poll SESSION_ID --interval 15
scripts/devin-handoff.sh archive SESSION_ID --org-id ORG_ID
scripts/devin-handoff.sh poll SESSION_ID --interval 15 --archive --org-id ORG_ID
About this skill
What does the devin-handoff skill do?

Spin off parallel cloud Devin sessions. Hand off a task to a fresh cloud Devin session that runs in the background — each gets its own VM with shell, browser, and full repo access — so you can fan out several sessions at once and keep working locally while they run. Use for parallel or long-running work and anything needing Devin's full environment: multi-file changes, running servers, CI work, browser automation, migrations, or large refactors. Also an API for reading and interacting with current sessions — given a session URL or ID, the check/poll commands return its PR, status, branch, and

How do I install it?

Run `npx skills add club-cog/devin-handoff --skill devin-handoff --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From club-cog/devin-handoff, a repository with 54 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going