claude

Solid

Use Claude Code as an independent `claude -p` subagent when the user explicitly asks for Claude, wants a second-agent opinion from Claude, or asks to delegate a well-scoped task to Claude. Supports selecting `--model` and thinking/effort level with defaults of `opus` and `high`.

AI & Automation 43 stars 4 forks Updated 2 days ago Apache-2.0

Install

View on GitHub

Quality Score: 84/100

Stars 20%
55
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Claude Claude Code is an independent agent on PATH (`claude`), sharing this working tree and already authenticated. Use it as a second opinion or delegated worker, not as ground truth: verify its claims, own any changes, and keep its task contract narrow. ## Defaults Use `claude -p --model opus --effort high` unless the user or task calls for a different model or thinking level. - **Model:** accept aliases such as `opus`, `sonnet`, or `fable`, or a full model name. Default `opus`. - **Thinking level:** pass Claude Code's `--effort` flag. Valid levels are `low`, `medium`, `high`, `xhigh`, and `max`. Default `high`. - **Cost guard:** for exploratory asks, add `--max-budget-usd <amount>` when the user gives a budget or the task is likely to sprawl. Example: ```sh claude -p --model opus --effort high "<prompt>" ``` ## Prompting Claude Prompt Claude like an operator: compact, block-structured, and explicit about the artifact you need. A sharper contract beats higher effort. - **One task per run.** Split review, implementation, and docs into separate prompts. - **Name repo skills when relevant.** Claude can read repo files; say "follow write-docs for the doc" or "obey refactor-clean: no compatibility wrappers" instead of pasting those skills into the prompt. - **Blocks, added only where useful:** - `<task>` — the concrete job, context, and expected end state. - `<output_contract>` — exact response shape, highest-value first. - `<default_follow_through>`...

Details

Author
dzhng
Repository
dzhng/duet-agent
Created
5 months ago
Last Updated
2 days ago
Language
TypeScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

delegate-to-claude-code

Call the Claude Code CLI (`claude`) as a delegated reviewer, second opinion, or edit worker. Use for Claude Code subagent-style delegation with `claude-rc-spawn`, `claude -p`, `--bg`, `--worktree`, `--tmux`, plan/read-only reviewers, acceptEdits/auto edit workers, JSON/stream-json capture, resume flows, and gotchas around permission modes, worktree cleanup, agent personas, and `--dangerously-skip-permissions`. For persistent `claude remote-control` repo servers, use the claude-remote-control-server skill instead.

1 Updated today
T0mSIlver
AI & Automation Listed

claude-discuss

Iterative non-code discussion between the local agent and Claude Code CLI on any open-ended topic: diet, fitness, writing, decisions, strategy, study plans, life choices, brainstorming. Orchestrates an automatic back-and-forth debate where both agents critique, propose alternatives, and iterate on the user's idea until reaching consensus. Claude Code runs READ-ONLY (headless plan mode), forms its own opinions, and normally does not navigate the filesystem unless the user provides file paths. Use when the user says discuss with claude, iterate with claude, consult claude, debate with claude, ask claude for a second opinion, get claude's take, or brainstorm with claude, including pasting or describing a plan, draft, idea, decision, or proposal and wanting a critical iterative review. Does NOT trigger on code review, plan review of implementation plans, architecture discussions, or any technical software-engineering analysis; use claude-review for those.

4 Updated 1 weeks ago
mryll
AI & Automation Listed

claude-review

Iterative code review and planning discussion between the local agent and Claude Code CLI. Orchestrates an automatic back-and-forth debate where both agents discuss findings, architecture decisions, or implementation plans until reaching consensus. Claude Code runs READ-ONLY (headless plan mode) and never modifies files; model and effort come from the user's local Claude Code config. Supports plan review: when the local agent has a plan ready, Claude evaluates and iterates on it before implementation, producing an updated consensus plan. Use when the user asks to review with claude, analyze with claude, discuss code with claude, iterate with claude, consult claude, ask claude, review the plan with claude, validate plan with claude, or any Claude Code request for code review, architecture review, plan review, or implementation strategy. Does NOT trigger on non-code topics like diet, fitness, writing, life decisions, or general strategy; use claude-discuss for those.

4 Updated 1 weeks ago
mryll