/dev-external-context
Parallel external documentation lookup. Spawn multiple @scroll-docs agents simultaneously to fetch SDK refs, API docs, and framework guides for different topics in one pass.
$ npx -y skills add evolution-foundation/evo-nexus --skill dev-external-context --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/dev-external-context
Context preview
The summary Claude sees to decide when to auto-load this skill.
Parallel external documentation lookup. Spawn multiple @scroll-docs agents simultaneously to fetch SDK refs, API docs, and framework guides for different topics in one pass.
SKILL.md
dev-external-context.SKILL.mdname: dev-external-context
description: Parallel external documentation lookup. Spawn multiple @scroll-docs agents simultaneously to fetch SDK refs, API docs, and framework guides for different topics in one pass.
Dev External Context
Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.
Parallel external research. When a task needs multiple unrelated external lookups (SDK A + Framework B + Standard C), spawn `@scroll-docs` instances in parallel instead of serial.
Use When
- Task requires 3+ external doc lookups on different topics
- Time-sensitive research where serial lookups would be slow
- Cross-referencing multiple SDKs / frameworks for the same problem
Do Not Use When
- Single lookup → use `@scroll-docs` directly
- Internal codebase questions → use `@scout-explorer` instead
- The lookups are dependent (B needs A's result first) → run serial
Workflow
1. **Decompose** the research need into 2+ independent topics 2. **Spawn** `@scroll-docs` agents in parallel — one per topic 3. **Collect** the briefs as they return 4. **Synthesize** into a single research summary 5. Save to `workspace/development/research/[C]external-context-{topic}-{date}.md`
Output Format
## External Context — {topic}
### Lookup 1: {topic A}
[from @scroll-docs]
### Lookup 2: {topic B}
[from @scroll-docs]
### Lookup 3: {topic C}
[from @scroll-docs]
## Synthesis
[Combined understanding]
## Conflicts
[Where sources disagree]
## Recommendation
[Next step based on combined research]Pairs With
- `@scroll-docs` (parallel workers)
- `@compass-planner` (consumer of synthesized research)
- `@apex-architect` (consumer for architecture decisions)
Read more
name: dev-external-context description: Parallel external documentation lookup. Spawn multiple @scroll-docs agents simultaneously to fetch SDK refs, API docs, and framework guides for different topics in one pass.
Dev External Context
Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.
Parallel external research. When a task needs multiple unrelated external lookups (SDK A + Framework B + Standard C), spawn `@scroll-docs` instances in parallel instead of serial.
Use When
- Task requires 3+ external doc lookups on different topics
- Time-sensitive research where serial lookups would be slow
- Cross-referencing multiple SDKs / frameworks for the same problem
Do Not Use When
- Single lookup → use `@scroll-docs` directly
- Internal codebase questions → use `@scout-explorer` instead
- The lookups are dependent (B needs A's result first) → run serial
Workflow
1. **Decompose** the research need into 2+ independent topics 2. **Spawn** `@scroll-docs` agents in parallel — one per topic 3. **Collect** the briefs as they return 4. **Synthesize** into a single research summary 5. Save to `workspace/development/research/[C]external-context-{topic}-{date}.md`
Output Format
## External Context — {topic}
### Lookup 1: {topic A}
[from @scroll-docs]
### Lookup 2: {topic B}
[from @scroll-docs]
### Lookup 3: {topic C}
[from @scroll-docs]
## Synthesis
[Combined understanding]
## Conflicts
[Where sources disagree]
## Recommendation
[Next step based on combined research]Pairs With
- `@scroll-docs` (parallel workers)
- `@compass-planner` (consumer of synthesized research)
- `@apex-architect` (consumer for architecture decisions)
Other skills on evo-nexus.
- /ai-image-creator
Generate PNG images using AI (multiple models via OpenRouter including Gemini, FLUX.2, Riverflow, SeedDream, GPT-5 Image, proxied through Cloudflare AI Gateway BYOK). Also analyze/describe existing images using multimodal AI vision. Use when user asks to "generate an image",
Open skill - /create-agent
Create a new custom agent for the workspace. Guides the user through defining agent name, domain, personality, skills, model, and memory folder. Use when the user says 'create an agent', 'new agent', 'add an agent', 'I need a custom agent', or wants to create a specialized agent
Open skill - /create-command
Create a new slash command for Claude Code. Guides the user through defining the command name, what it does, and generates the markdown file in .claude/commands/. Use when the user says 'create a command', 'new command', 'add a slash command', 'I want a shortcut for', or wants
Open skill - /create-goal
Create a Mission, Project, or Goal (Mission → Project → Goal → Task hierarchy) in EvoNexus. Guides the user through picking a mission, choosing or creating a project, defining a measurable goal with metric_type and target_value. Writes to the SQLite goals tables via POST
Open skill - /create-heartbeat
Create a new heartbeat (proactive agent scheduled with a decision prompt) for EvoNexus. Guides the user through picking an agent, setting interval, wake triggers, and the decision prompt that governs when the agent acts. Writes to config/heartbeats.yaml with pydantic validation.
Open skill - /create-integration
Create a new custom integration (API/service wrapper) for the workspace. Guides the user through defining the integration's slug, display name, description, category, and required env keys. Writes .claude/skills/custom-int-{slug}/SKILL.md via POST /api/integrations/custom. Use
Open skill