How do I install the Collaborating With Claude Code skill?

Run npx skillmds add zhenhuanglab/collaborating-with-claude-code in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Collaborating With Claude Code safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Collaborating With Claude Code?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Collaborating With Claude Code free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Collaborating With Claude Code?

ZhenHuangLab (@zhenhuanglab) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Collaborating With Claude Code by zhenhuanglab

Name: Collaborating With Claude Code
Rating: 4.2 (5 reviews)
Author: ZhenHuangLab

File contents

Collaborating with Claude Code

Use this skill for second opinions, code review, test design, or code implementations/alternatives. The bridge runs claude (Claude Code) non-interactively ("print" mode) and returns JSON.

The script is located at ~/.codex/skills/collaborating-with-claude-code/scripts/claude_code_bridge.py.

Timing

Claude Code often needs 1–2+ minutes per task.

Prefer running the bridge directly (no &); increase --timeout-s as needed (default: 1800s).
Do NOT redirect stdout to a file (e.g. > /tmp/out.json).
By default, the bridge streams Claude's assistant text to stderr, and prints only the final JSON envelope to stdout.

Context

Do NOT read the script unless you are modifying it;
Before running the script, ALWAYS use python <script_loc> --help to get the usage instructions.

Usage

please always require claude code to fully understand the codebase before responding or making any changes.
Put collaborating-with-claude-code terminal commands in the background terminal.
Always review claude code's responses (or changes it makes) and make sure they are correct, constructive and complete.
When claude code asks clarifying questions in a multi-turn session, always respond to its questions in that session based on current situation.

Default

full access (--full-access): use only in trusted repos/directories.
extended thinking ON (can disable via --no-extended-thinking).
step mode AUTO (can disable via --step-mode off).

Output format

The bridge prints JSON to stdout:

{"success": true, "SESSION_ID": "abc123", "agent_messages": "…Claude output…"}

Recommended delegation patterns

Guided coding: "Implement the code for [feature] following these specific steps/constraints."
Second opinion: "Propose an alternative approach and tradeoffs."
Code review: "Find bugs, race conditions, security issues; propose fixes."
Test design: "Write a test plan + edge cases; include example test code."
Diff review: "Review this patch; point out regressions and missing cases."

---name: collaborating-with-claude-codedescription: Delegate code implementation/review/debugging/alternatives to Claude Code via a JSON bridge script. Multi-turn via SESSION_ID.---# Collaborating with Claude CodeUse this skill for second opinions, code review, test design, or code implementations/alternatives. The bridge runs `claude` (Claude Code) non-interactively ("print" mode) and returns JSON.The script is located at `~/.codex/skills/collaborating-with-claude-code/scripts/claude_code_bridge.py`.## TimingClaude Code often needs **1–2+ minutes** per task.- Prefer running the bridge directly (no `&`); increase `--timeout-s` as needed (default: 1800s).- Do **NOT** redirect stdout to a file (e.g. `> /tmp/out.json`).- By default, the bridge streams Claude's assistant text to `stderr`, and prints only the final JSON envelope to `stdout`.## Context- Do **NOT** read the script unless you are modifying it; - Before running the script, ALWAYS use `python <script_loc> --help` to get the usage instructions.## Usage- please always require claude code to fully understand the codebase before responding or making any changes.- Put collaborating-with-claude-code terminal commands in the background terminal.- Always review claude code's responses (or changes it makes) and make sure they are correct, constructive and complete.- When claude code asks clarifying questions in a multi-turn session, always respond to its questions in that session based on current situation.## Default- **full access** (`--full-access`): use only in trusted repos/directories.- **extended thinking ON** (can disable via `--no-extended-thinking`).- **step mode AUTO** (can disable via `--step-mode off`).## Output formatThe bridge prints JSON to `stdout`:```json{"success": true, "SESSION_ID": "abc123", "agent_messages": "…Claude output…"}```## Recommended delegation patterns- **Guided coding**: "Implement the code for [feature] following these specific steps/constraints."- **Second opinion**: "Propose an alternative approach and tradeoffs."- **Code review**: "Find bugs, race conditions, security issues; propose fixes."- **Test design**: "Write a test plan + edge cases; include example test code."- **Diff review**: "Review this patch; point out regressions and missing cases."

Frequently asked questions