Menu
Switch to Knowledge Work mode for research and writing — use when task is non-code focused
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Smoke-test fixture for the stdio MCP integration tests. Returns a constant body when called.
Multi-AI requirements scoping using Codex and Gemini CLIs (Double Diamond Define phase). Use when: AUTOMATICALLY ACTIVATE when user requests clarification or scoping:. "define the requirements for X". "clarify the scope of Y"
Multi-AI validation, scoring, and review using Codex and Gemini CLIs (Double Diamond Deliver phase). Use when: AUTOMATICALLY ACTIVATE when user requests validation, scoring, or review:. "review X" or "validate Y" or "test Z". "score this", "quality check", "validate before shipping"
Multi-AI implementation using Codex and Gemini CLIs (Double Diamond Develop phase). Use when: AUTOMATICALLY ACTIVATE when user requests building or implementation:. "build X" or "implement Y" or "create Z". "develop a feature for X"
Multi-AI research using Codex and Gemini CLIs (Double Diamond Discover phase). Use when: AUTOMATICALLY ACTIVATE when user requests research or exploration:. "research X" or "explore Y" or "investigate Z". "what are the options for X" or "what are my choices for Y"
NLSpec authoring — structured specification from multi-AI research
| name | skill-knowledge-work |
| version | 1.0.0 |
| description | Switch to Knowledge Work mode for research and writing — use when task is non-code focused |
Claude Octopus now auto-detects work context! The system analyzes your prompt and project to determine whether you're in a Dev Context (code-focused) or Knowledge Context (research/strategy-focused).
You typically don't need this skill - context is detected automatically when you use:
octo research X - Auto-detects dev vs knowledge researchocto build X - Auto-detects code vs document buildingocto review X - Auto-detects code vs document reviewUse ONLY when auto-detection is wrong:
/octo:km on
All subsequent workflows will use Knowledge Context until reset.
/octo:km off
All subsequent workflows will use Dev Context until reset.
/octo:km auto
Context detection returns to automatic mode.
/octo:km
Shows current mode (auto, knowledge, or dev).
When you use any octo workflow, context is detected by analyzing:
Prompt Content (strongest signal):
Project Type (secondary signal):
package.json, Cargo.toml, go.mod → Dev Context.md, .docx, .pdf files → Knowledge ContextExplicit Override (if set via /octo:km):
When workflows run, you'll see the detected context in the banner:
Dev Context:
🐙 **CLAUDE OCTOPUS ACTIVATED** - Multi-provider research mode
🔍 [Dev] Discover Phase: Technical research on caching patterns
Knowledge Context:
🐙 **CLAUDE OCTOPUS ACTIVATED** - Multi-provider research mode
🔍 [Knowledge] Discover Phase: Market analysis for APAC expansion
User: "octo research caching strategies for our Node.js API"
Claude: (auto-detects Dev Context from "Node.js API")
🐙 **CLAUDE OCTOPUS ACTIVATED** - Multi-provider research mode
🔍 [Dev] Discover Phase: Technical research on caching strategies
[Researches with technical/implementation focus]
User: "octo research market opportunities in healthcare AI"
Claude: (auto-detects Knowledge Context from "market opportunities")
🐙 **CLAUDE OCTOPUS ACTIVATED** - Multi-provider research mode
🔍 [Knowledge] Discover Phase: Strategic research on healthcare AI market
[Researches with business/strategic focus]
User: "octo research React patterns"
Claude: (auto-detects Dev) 🔍 [Dev] Discover Phase...
User: "Actually, this is for a presentation. Force knowledge mode."
Claude: "Setting context override to Knowledge Mode."
/octo:km on
User: "octo research React patterns"
Claude: (uses override) 🔍 [Knowledge] Discover Phase... (focuses on trends, adoption, strategic implications)
User: "What context mode am I in?"
Claude:
Current mode: Auto-detection (no override set)
Last detected context: Dev (based on project having package.json)
To override: /octo:km on (force Knowledge) or /octo:km off (force Dev)
To return to auto: /octo:km auto
| Workflow | Focus |
|---|---|
octo research X | Technical implementation, libraries, code patterns |
octo build X | Code generation, architecture, tests |
octo review X | Code quality, security, performance |
| Agents | codex, backend-architect, code-reviewer, security-auditor |
| Workflow | Focus |
|---|---|
octo research X | Market analysis, competitive research, literature synthesis |
octo build X | PRDs, strategy docs, presentations, reports |
octo review X | Document quality, argument strength, completeness |
| Agents | strategy-analyst, ux-researcher, exec-communicator, product-writer |
After running knowledge workflows, export to professional formats:
Just say: "Export this to Word" or "Create a PowerPoint presentation"
| Command | Description |
|---|---|
/octo:km | Show current status (auto, on, or off) |
/octo:km on | Force Knowledge Context for all workflows |
/octo:km off | Force Dev Context for all workflows |
/octo:km auto | Return to auto-detection (default) |
Don't override if:
Override is for:
At the end of significant work sessions, extract learnings:
Store learnings in .claude-octopus/learnings/<date>-<summary>.json:
{
"date": "2026-03-21",
"task_type": "debugging",
"approach": "Traced the error from the test failure back to the API handler",
"outcome": "success",
"lesson": "Always check middleware ordering before investigating handler logic"
}
Each learning file captures: task_type, approach, outcome, and lesson.
At session start, check for relevant learnings:
.claude-octopus/learnings/ directory/octo:discover - Research workflow (auto-detects context)/octo:develop - Build workflow (auto-detects context)/octo:deliver - Review workflow (auto-detects context)/octo:docs - Document export (works in both contexts)