# Delegate Analysis

> Skill-driven exploration, targeted reading, web research, and deep-dive analysis for delegate agents. Use when the primary delegates investigation or information gathering rather than artifact review or code execution.

- Skill: `dasdigitalemomentum/delegate-analysis` (Agent Skill)
- Install (CLI): `npx skillmds@latest add dasdigitalemomentum/delegate-analysis`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dasdigitalemomentum/delegate-analysis/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- License: MIT
- Author: DasDigitaleMomentum (https://skillmd.com/u/dasdigitalemomentum)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/dasdigitalemomentum/delegate-analysis

---


# Skill: Delegate Analysis

Use one of the following modes. The primary should name the mode, scope, and question explicitly.

## Modes

### `code-exploration`

- Orient with file search, then read only the key files.
- Trace dependencies one level further only when needed.
- Return findings with concrete file paths and symbols.

### `targeted-reading`

- Use the named files as scoped starting points and retrieve only what answers the question.
- Extract only the facts needed to answer the question.
- Organize the result by topic or file, with line references where useful.

### `web-research`

- Prefer authoritative primary sources.
- Cross-check important claims when practical.
- Return a concise synthesis with source URLs and explicit uncertainty.
- This is delegate work: use `retriever` only to crawl or fetch already-selected sources, not for open-ended search, source selection, or cross-source judgment.

### `deep-dive`

- Start at the named entry point and follow relevant indirections until the question is answered.
- Map the code or data path with file and symbol evidence.
- Highlight non-obvious behavior, assumptions, and unresolved gaps.

## Rules

- Default to read/analyze/verify. Do not edit files.
- Stay within the delegated scope.
- Directly read scoped source, docs/plans, symbols, and compact targeted evidence. Keep uncurated bulk evidence out of the delegate context: use a reliable focused filter when sufficient; otherwise route the raw artifact, command, or path plus a focused question to `retriever`, including coherent multi-file evidence. Numeric tool truncation is a safety net, not the routing rule.
- Spool potentially verbose command output to a predictable path under `/tmp/opencode/`; retain only path, command, exit status, and compact metadata/evidence. This supports same-machine continuation after an interruption, not reboot durability.
- The parent owns synthesis and verifies only evidence that materially supports its conclusions rather than repeating broad retrieval.
- If the task becomes a review, artifact authoring task, or implementation task, stop and ask the primary to route through the matching skill.
- After an analysis digest/message diagnoses an evidence-backed defect, the Primary may accept it and explicitly instruct remediation by resuming this session through `review-fix`. That skill owns eligibility, writes, and the one-pass stop; analysis itself remains read-only. Reuse correct and sufficient diagnosis context to avoid collecting secured evidence again; otherwise follow its fresh-session fallback with a finding-source hint. Conversation-owned plan corrections still route to `update-plan`.
- Return a compact digest, not raw file contents or long logs.