skill-knowledge-work

Switch Claude Octopus sessions into Knowledge Work mode for non-code research tasks.

1|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/mhdxbilal/Ai --skill skill-knowledge-work-mhdxbilal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-knowledge-work
Source: https://github.com/mhdxbilal/Ai/tree/main/.claude/skills/skill-knowledge-work
Command: npx skills add https://github.com/mhdxbilal/Ai --skill skill-knowledge-work-mhdxbilal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables users to enforce a Knowledge Work context in Claude Octopus, streaming research and strategic tasks when prompts are non-code oriented.

Core Features & Use Cases

  • Auto-detects dev vs knowledge contexts to route workflows appropriately.
  • Provides explicit overrides to force Knowledge or Dev context for an entire session.
  • Supports status checks and auto-detection explanations for workflows like octo research, build, and review.

Quick Start

Switch the session to Knowledge Context for ongoing prompts.

Frequently Asked Questions about skill-knowledge-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I switch Claude Octopus to a research context for non-code tasks?

Knowledge Work mode optimizes non-code research tasks by switching Claude Octopus into a Knowledge context. It applies primarily to research, strategy, and writing prompts to improve outcomes.

How does context auto-detection work for research and writing workflows?

Context auto-detection automatically routes workflows by distinguishing between dev and knowledge-oriented prompts. This ensures research, strategy, and writing tasks are handled appropriately without manual configuration.

Can I force a specific context for an entire Claude Octopus session?

Yes, you can force a specific context for an entire session using explicit overrides. This allows you to manually enforce either Knowledge or Dev context to handle edge cases where auto-detection may not apply.

What is the best way to handle edge cases when auto-detection misroutes a knowledge work prompt?

The best way to handle edge cases in knowledge work is to use session overrides. They allow you to explicitly force Knowledge context, ensuring your research and strategic prompts are processed correctly.

Does knowledge work mode support status checks and workflow explanations?

Yes, knowledge work mode supports status checks and auto-detection explanations. This provides visibility into how workflows like research, build, and review are being routed and processed.