MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Apply before starting work on an existing branch. An agent skill from ZaxbyHub/opencode-swarm.
MITAuto-check passed
Install Parallel Work Check
$ npx skills add ZaxbyHub/opencode-swarm --skill parallel-work-check -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ZaxbyHub/opencode-swarm parallel-work-check --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/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opencode/skills/parallel-work-check .claude/skills/parallel-work-check && 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 "parallel-work-check" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/parallel-work-check into .claude/skills/parallel-work-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parallel-work-check", 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/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/parallel-work-checkType 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 ZaxbyHub/opencode-swarm --skill parallel-work-check -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ZaxbyHub/opencode-swarm parallel-work-check --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.opencode/skills/parallel-work-check .agents/skills/parallel-work-check && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "parallel-work-check" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/parallel-work-check into .agents/skills/parallel-work-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parallel-work-check", 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 ZaxbyHub/opencode-swarm --skill parallel-work-check -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ZaxbyHub/opencode-swarm parallel-work-check --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.opencode/skills/parallel-work-check .cursor/skills/parallel-work-check && 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 "parallel-work-check" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/parallel-work-check into .cursor/skills/parallel-work-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parallel-work-check", 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/ZaxbyHub/opencode-swarm.git --path .opencode/skills/parallel-work-check--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 ZaxbyHub/opencode-swarm --skill parallel-work-check -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ZaxbyHub/opencode-swarm parallel-work-check --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.opencode/skills/parallel-work-check .gemini/skills/parallel-work-check && 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 "parallel-work-check" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/parallel-work-check into .gemini/skills/parallel-work-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parallel-work-check", 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 ZaxbyHub/opencode-swarm parallel-work-checkInstalls 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 ZaxbyHub/opencode-swarm --skill parallel-work-check -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .github/skills && cp -r skills-src/.opencode/skills/parallel-work-check .github/skills/parallel-work-check && 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 "parallel-work-check" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/parallel-work-check into .github/skills/parallel-work-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parallel-work-check", 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 ZaxbyHub/opencode-swarm --skill parallel-work-check -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ZaxbyHub/opencode-swarm parallel-work-check --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.opencode/skills/parallel-work-check .opencode/skills/parallel-work-check && 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 "parallel-work-check" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/parallel-work-check into .opencode/skills/parallel-work-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parallel-work-check", 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
parallel-work-check- GitHub stars
- 493
- Token cost
- ~1.4k tokens
- SKILL.md length
- 556 words
- Files
- 1
- Skills in repo
- 91
- Repo updated
- First seen
- Licence
- MIT
At a glance
Apply before starting work on an existing branch. An agent skill from ZaxbyHub/opencode-swarm.
- Works in 5 steps: Check current branch state → Fetch remote state → Compare local vs remote → …
- SKILL.md covers Step 1 — Check current branch…, Step 2 — Fetch remote state, Step 3 — Compare local vs remote and Step 4 — Check for parallel…, plus 5 more sections
- Calls git
What it does
Parallel Work Check is an agent skill from ZaxbyHub/opencode-swarm. Apply before starting work on an existing branch. Checks for parallel work by other agents or developers that may supersede or conflict with your planned changes. Prevents wasted effort on stale branches.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Architect-centric agentic swarm plugin for OpenCode. Hub-and-spoke orchestration with SME consultation, code generation, and QA review. The licence is MIT.
Example prompts
- “/parallel-work-check”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit eee4534. 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:
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.
Context cost
Parallel Work Check loads about 1.4k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 556 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 ZaxbyHub/opencode-swarm at commit eee4534, republished under its MIT licence (© ZaxbyHub). 556 words, ~1,418 tokens.
Download SKILL.mdSave it as
.claude/skills/parallel-work-check/SKILL.md (or your agent's skills folder).- name
- parallel-work-check
- description
- Apply before starting work on an existing branch. Checks for parallel work by other agents or developers that may supersede or conflict with your planned changes. Prevents wasted effort on stale branches.
- audience
- swarm-plugin
- effort
- small
- source_knowledge_ids
- f07c1f4d-9bb0-4219-9804-26aa8efe8146
- generated_at
- 2026-06-14T16:50:00Z
- confidence
- 0.8
- status
- active
- version
- 4
- skill_origin
- generated
- provenance_note
- Re-linked to current knowledge entries (version 4). The original source ID b8fee776... is no longer present in the active knowledge store. The skill body and…
Parallel Work Check Protocol
Run this check before starting ANY work on an existing branch (not a fresh branch you just created). This applies to PR branches, feature branches, and any branch that may have concurrent contributors.
Step 1 — Check current branch state
- Determine the current branch name.
- Determine the remote tracking branch (usually
origin/<branch-name>).
Step 2 — Fetch remote state
Fetch the latest state from the remote for the current branch. Do NOT skip this step because "the branch looks recent" or "I just checked."
Step 3 — Compare local vs remote
Compare the local HEAD commit hash with the remote HEAD commit hash:
- Identical: Remote has not diverged. Proceed with your work.
- Remote ahead: The remote branch has commits you don't have locally.
- Read the new commit messages with
git log local..remote. - Check if any of those commits touch files you plan to modify.
- If yes: evaluate whether the parallel work supersedes your planned changes.
- If the parallel work is superior: reset your local branch to match remote and abandon your planned approach. Document the decision.
- If the parallel work is complementary: integrate it first, then proceed.
- Read the new commit messages with
- Local ahead: You have local commits not on remote. This is normal if you already started work. Proceed, but be aware that pushing may conflict with subsequent remote changes.
- Diverged: Both local and remote have unique commits. This requires integration. Merge or rebase as appropriate for the team's workflow.
Step 4 — Check for parallel swarm/agent work
If the remote has new commits:
- Check the commit authors. If commits are from a different swarm/agent (different author name/email pattern), treat this as parallel swarm work.
- Parallel swarm work is often superior because:
- It may have access to different context or tools
- It may have started earlier or had more iterations
- It may have taken a fundamentally better approach
- Default stance: prefer the parallel swarm's work unless you can clearly articulate why your approach is better.
Step 5 — Decision and documentation
Before proceeding, document your decision:
PARALLEL WORK CHECK:
- Branch: <name>
- Local HEAD: <hash> <message>
- Remote HEAD: <hash> <message>
- Diverged: yes/no
- New commits on remote: <count>
- Parallel swarm work detected: yes/no
- Decision: [proceed / integrate-then-proceed / abandon-use-remote / needs-review]
- Rationale: <one sentence>Show full SKILL.md (221 more words)Show less
Anti-patterns — do NOT do these
- Skip the fetch because "I'm sure nothing changed."
- Ignore remote commits because "my approach is probably better."
- Start fixing code without checking if the remote already fixed it.
- Blindly overwrite remote work with local changes without evaluating first.
Example: parallel swarm superseded local work
PARALLEL WORK CHECK:
- Branch: codex/issue-956-plan-completion-gate
- Local HEAD: 5aa34f88 fix(delegation-gate): block next task until completion is persisted
- Remote HEAD: 2b4e9266 fix: correct contradictory test title/comments
- Diverged: yes (remote is 8 commits ahead)
- New commits on remote: 8
- Parallel swarm work detected: yes (different commit author)
- Decision: abandon-use-remote
- Rationale: Parallel swarm restored file from main and re-integrated cleanly,
producing 486 passing tests vs our incremental patching which left 38 failures.Integration with swarm workflow
This check should run:
- At session start (MODE: RESUME or MODE: EXECUTE)
- Before creating a new plan for an existing branch
- Before dispatching the first coder task
- After any significant pause where parallel work could have occurred
Integration with other skills
The parallel-work-check skill is referenced by other skills that start work on an existing branch:
| Skill | Usage |
|---|---|
file:.swarm/bundled-skills/swarm-pr-feedback/SKILL.md | Checks before starting PR feedback fixes — ensures no parallel work has already addressed the same findings |
| Legacy pr-review-fix alias | Compatibility entry that delegates to the bundled swarm-pr-feedback protocol |
file:.swarm/bundled-skills/swarm-implement/SKILL.md | Checks before implementation Phase 1 — ensures the branch is up-to-date before planning |
| Any skill that starts work on an existing branch | Run the parallel-work-check protocol before beginning fixes or implementation |
When a skill references parallel-work-check, the checking agent must:
- Fetch and compare remote vs local state
- Read any new commits from parallel work
- Evaluate whether the parallel work supersedes, complements, or does not affect the planned work
- Document the decision using the PARALLEL WORK CHECK template
© ZaxbyHub, MIT. 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 .opencode/skills/parallel-work-check of ZaxbyHub/opencode-swarm.
Open the folder on GitHubat commit eee4534
Compare with similar skills
Parallel Work Check 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 |
|---|---|---|---|---|---|---|
| Parallel Work Check this skillZaxbyHub/opencode-swarm | 493 | — | ~1.4k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Vercel Composition Patternssupabase/supabase | 111k | 58 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Agent Browser CLIvercel-labs/agent-browser | 44k | 24 repos | ~864 | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 10 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 |
Similar skills
- Official
- Official
Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Finishing a Development Branch
obra/superpowers
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.
- Official
Agent Browser CLI
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking…
- Official
Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
More from ZaxbyHub/opencode-swarm
All 91 skills in this repoCodebase Review Swarm
ZaxbyHub/opencode-swarm
Runs an evidence-gated, quote-grounded audit of a codebase for security, QA, accessibility, performance and more, and writes a verified report without changing source files.
Issue Tracer
ZaxbyHub/opencode-swarm
Drives a bug report from validation and root-cause tracing through a critic-reviewed plan, an approved minimal fix and a PR-ready closure, never merging without recorded human approval.
Commit and PR Publishing for Codex
ZaxbyHub/opencode-swarm
Codex adapter for opencode-swarm that governs commits, pushes, draft PRs, PR body updates and CI closeout, deferring to the repo's canonical commit-pr protocol.
Durable Session State
ZaxbyHub/opencode-swarm
Keeps plans, decisions, evidence and reviewer verdicts in small files so long multi-phase tasks survive context compaction and session resumes.
Swarm PR Feedback Closer
ZaxbyHub/opencode-swarm
Ingests existing pull request feedback such as review comments and CI failures, verifies each claim, fixes confirmed issues and reports closure status for every item.
Swarm PR Subscribe
ZaxbyHub/opencode-swarm
Monitor a pull request after creation and act autonomously on pushed PR activity.
Questions about Parallel Work Check
What does Parallel Work Check do?
Apply before starting work on an existing branch. An agent skill from ZaxbyHub/opencode-swarm. Parallel Work Check is an agent skill from ZaxbyHub/opencode-swarm. Apply before starting work on an existing branch.
How do I install Parallel Work Check in Claude Code?
Run `npx skills add ZaxbyHub/opencode-swarm --skill parallel-work-check -a claude-code`. Or copy the skill folder (.opencode/skills/parallel-work-check in ZaxbyHub/opencode-swarm) into .claude/skills/parallel-work-check in your project. Claude Code loads it when a task matches its description.
How do I install Parallel Work Check in Codex?
Run `npx skills add ZaxbyHub/opencode-swarm --skill parallel-work-check -a codex`. Or copy the skill folder (.opencode/skills/parallel-work-check in ZaxbyHub/opencode-swarm) into .agents/skills/parallel-work-check in your project. Codex loads it when a task matches its description.
Can I use Parallel Work Check 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 ZaxbyHub/opencode-swarm --skill parallel-work-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/parallel-work-check, .gemini/skills/parallel-work-check, .github/skills/parallel-work-check and .opencode/skills/parallel-work-check in your project.
What does Parallel Work Check need to run?
Going by SKILL.md and its folder, Parallel Work Check needs the command-line tools its instructions call (git).
Does Parallel Work Check 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 Parallel Work Check 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 Parallel Work Check use?
Parallel Work Check is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Parallel Work Check use?
About 1.4k tokens (SKILL.md is roughly 5.7k 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 Parallel Work Check?
Skills that share tags, products or a category with Parallel Work Check: MCP Server Builder (anthropics/skills, 180k stars), Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars) and Agent Browser CLI (vercel-labs/agent-browser, 44k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Parallel Work Check?
ZaxbyHub (a GitHub organization) maintains it in ZaxbyHub/opencode-swarm, which has 493 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on October 9, 2026.
Source: ZaxbyHub/opencode-swarm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.