# Skill Knowledge Work

Switch to Knowledge Work mode for research and writing, use when task is non-code focused

- Repository: https://github.com/nyldn/claude-octopus (4351 stars)
- Category: Writing
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add nyldn/claude-octopus --skill skill-knowledge-work -g -a claude-code -y`
Codex: `npx skills add nyldn/claude-octopus --skill skill-knowledge-work -g -a codex -y`
Cursor: `npx skills add nyldn/claude-octopus --skill skill-knowledge-work -g -a cursor -y`
Gemini CLI: `npx skills add nyldn/claude-octopus --skill skill-knowledge-work -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add nyldn/claude-octopus`

## Description

Switch to Knowledge Work mode for research and writing, use when task is non-code focused

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Knowledge Work Mode - Context Override Skill

## Context Auto-Detection (v7.8+)

**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 research
- `octo build X` - Auto-detects code vs document building
- `octo review X` - Auto-detects code vs document review

## When to Use This Override

**Use ONLY when auto-detection is wrong:**
- Auto-detection chose Dev but you want Knowledge behavior
- Auto-detection chose Knowledge but you want Dev behavior
- You want to force a specific context for the entire session

## Override Commands

### Force Knowledge Context
```bash
/octo:km on
```
All subsequent workflows will use Knowledge Context until reset.

### Force Dev Context
```bash
/octo:km off
```
All subsequent workflows will use Dev Context until reset.

### Return to Auto-Detection
```bash
/octo:km auto
```
Context detection returns to automatic mode.

### Check Current Status
```bash
/octo:km
```
Shows current mode (auto, knowledge, or dev).

## How Auto-Detection Works

When you use any `octo` workflow, context is detected by analyzing:

1. **Prompt Content** (strongest signal):
   - Knowledge indicators: "market", "ROI", "stakeholders", "strategy", "personas", "presentation", "report", "PRD"
   - Dev indicators: "API", "endpoint", "database", "implementation", "code", "function", "deploy"

2. **Project Type** (secondary signal):
   - Has `package.json`, `Cargo.toml`, `go.mod` → Dev Context
   - Mostly `.md`, `.docx`, `.pdf` files → Knowledge Context

3. **Explicit Override** (if set via `/octo:km`):
   - Overrides all auto-detection until reset to "auto"

## Visual Indicator Shows Context

When workflows run, you'll see the detected context in the banner:

The rest: https://github.com/nyldn/claude-octopus/blob/HEAD/.claude/skills/skill-knowledge-work/SKILL.md