Skip to content
Skills Library
AI & agents · Automation

claude

/claude

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 the current `opus` alias and `high`.

Author
dzhng ↗
Repository
jevgrep ↗
Licence
MIT
Last repository change
12.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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 the current `opus` alias and `high`.

Original author description

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 the current `opus` alias and `high`.

How it works

  1. Defaults
  2. Prompting Claude
  3. Consultation
  4. Implementation — explicit ask only
  5. Liveness
  6. Rules
Original SKILL.md headings · 127 lines, 943 words
SKILL.md preview
---
name: claude
description: 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 the current `opus` alias and `high`.
---

# 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. Keep `opus` as an alias so Claude Code
resolves the current Opus release; do not pin a dated model ID in this skill.

- **Model:** prefer aliases such as `opus`, `sonnet`, or `fable`, which follow
  the current Claude releases. Accept a full model name only when the user or
  task requires that specific model, and verify it is current first. 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-change: 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>` — take low-risk interpretations and continue;
    stop only when a missing detail changes correctness, safety, or an
    irreversible action.
  - `<verification_loop>` — inspect the result against requirements and revise
    before finalizing.
  - `<grounding>` — ground every claim in code or tool output; label
    inferences.
  - `<action_safety>` — keep the diff tightly scoped; no drive-by refactors.
- **Anti-patterns:** vague prompts, mixed jobs, no output contract, asking it
  to "think harder" instead of tightening the task, and accepting its answer
  without checking the evidence.

## Consultation

Use Claude for consultation when the user asks for Claude's view or when a
second-agent read would materially reduce risk. Keep it read-oriented unless
the user explicitly asks it to edit.

1. Ask for evidence, not vibes: require file paths, observed behavior, command
   output, or labelled inferences.
2. Prefer a read-only tool surface for reviews:
   `--tools "Read,Grep,Glob,Bash" --permission-mode dontAsk`.
3. **Never grant fewer tools than your output contract requires.** Read your
   own prompt and ask which tool produces each claim you demanded. A judge that
   cannot run a command will still answer a question posed in numbers — with
   numbers, self-consistent and measured from nothing, and with the artifacts
   it says it wrote. Trimming the tool surface does not make the answer
   cautious; it makes the fabrication harder to spot. Either grant the tool or
   stop asking for the claim.
4. Require the receipt with the number: any quantity in the response must
   arrive with the command that produced it and that command's output. Findings
   that fail this are struck, not discounted.
5. Triage every finding against the code before acting. Report what Claude
   flagged, what you accepted, and what you dismissed.

## Implementation — explicit ask only

Delegate implementation to Claude only when the user names Claude for the task.
Never hand it work on your own initiative, and never re-delegate follow-up work
without a fresh ask.

1. Slice the task sharply: goal, constraints, allowed scope, and verification.
   An underspecified task stays with you until a fresh agent could not misread
   it.
2. Start from a clean tree or record the baseline commit so Claude's diff is
   separable from yours. Tell Claude to keep scratch files (probes, dumps,
   notes) out of the tree — its diff must contain only the deliverable.
3. Choose permissions by what the task must do:
   - Read/review: `--tools "Read,Grep,Glob,Bash" --permission-mode dontAsk`.
   - Narrow edits: add edit tools and keep the prompt's allowed paths explicit.
   - Broad autonomous work: use `--dangerously-skip-permissions` only in a
     dedicated worktree, with a self-authored prompt and a mandatory diff
     review after.
4. Capture the response with `--output-format text` by default. Use
   `--output-format json` only when the caller needs structured metadata.
5. You own the result: inspect the diff, run the relevant tests, and only then
   report it. "Claude says it's done" is not done.

## Liveness

`claude -p` is a networked, authenticated non-interactive run. If it fails,
classify the failure before retrying.

- Auth failure: do not repair credentials unless the user asks; report the
  blocker. If sandboxed `claude -p` says `Not logged in`, retry once with the
  required approval because local auth can depend on keychain/session access.
- Sandbox/network failure: rerun with the required approval if the command is
  important to the task.
- Long run: prefer `--max-budget-usd` or a narrower prompt before raising
  effort.
- Workspace trust: `-p` skips the interactive trust dialog, so run it only from
  a repo or worktree you intentionally trust.

## Rules

- Use `claude -p --model opus --effort high` as the default invocation; keep
  the alias unversioned so it follows the current Opus release.
- Let the user override model and effort in plain language; translate that to
  `--model` and `--effort`.
- Keep Claude's writes out of the working tree unless delegation was explicit.
- Do not touch the same working tree while Claude is making edits.
- Treat Claude output as evidence to verify, not authority to relay.
- Match the tool surface to the output contract; a claim shape you granted no
  tool for comes back invented.

Versions

RepositoryScoreLicence
This page · dzhng/jevgrep100MIT
chrishuffman5/domain-expert100MIT
puck-muling/peer-agent100MIT
puck-muling/peer-agent100MIT
dzhng/skills100MIT
S3YED/appie-kit100MIT
alesha-pro/quorum100MIT

Database snapshot: 13.11.2026 · package version dcb341b5c3b6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100use-claude
    Delegate independent codebase analysis, review, debugging, implementation, or patching to Claude Code CLI. Use when the user explicitly asks to use Claude or Claude Code, requests a Claude second opinion, wants Claude to patch files, or asks to delegate a well-scoped task to…
  • 100review
    Cross-model orchestration between Claude Code and a local Codex CLI. Claude orchestrates, plans, and reviews; Codex implements and provides an independent second opinion. Use when you want two different model families to cross-check work rather than one model reviewing itself.
  • 100model-picker
    Choose the right Claude model (Haiku 5.5, Sonnet 5.5, Opus 5.5, Fable 5.2) and effort level for a task, subagent, API integration, or an app that hosts an agent through the Agent SDK. Use when the user asks which model to use, wants to cut cost or latency, is configuring…
  • 95dev_invoke_claude-code
    Codex-native adapter for invoking Anthropic Claude Code CLI as an independent read-only QAQC reviewer using markdown file handoff. Use when the user explicitly asks Codex to ask Claude, Claude Code, Opus, or Anthropic for a QAQC/code review, second-model review, or independent…
  • 100netlify-agent-runner
    Run AI agent tasks remotely on Netlify using Claude, Codex, or Gemini. Use when the user wants to run an AI agent on their site, get a second opinion from another model, or delegate development tasks to run remotely against their repo.
  • 100claude-delegate
    Route a task to a native Claude subagent on the model that fits it (Haiku, Sonnet, Opus or Fable), and decide between a Claude subagent and the external delegate workers (Codex, Kiro, Gemini, Qwen, Copilot). Use whenever you are about to hand off work or spawn a subagent. Follow…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.