dos-setup

Verify DOS plugin installation and workspace wiring via Python imports and doctor checks.

18|4|Updated Jun 10, 2026

Search Tags:#hooks #mcp #plugin #diagnostics #claude-code #dos

Ready to run

npx skills add https://github.com/anthony-chaudhary/dos-kernel --skill dos-setup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dos-setup
Source: https://github.com/anthony-chaudhary/dos-kernel/tree/main/claude-plugin/skills/dos-setup
Command: npx skills add https://github.com/anthony-chaudhary/dos-kernel --skill dos-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill confirms that the DOS plugin is correctly installed and wired in the current workspace, so you can diagnose why hooks, MCP tools, or bundled skills are not behaving as expected.

Core Features & Use Cases

Verifies that the dos-kernel package imports in the active Python interpreter.
Runs the DOS doctor check to confirm the workspace layout and lane detection.
Surfaces the bundled hooks, MCP tools, and next recommended skill so you know what the plugin provided.
Useful after installation, when Claude Code cannot see MCP tools, or when hooks appear to fail silently.

Quick Start

Ask the assistant to verify the DOS plugin wiring in this workspace, summarize the bundled hooks, MCP tools, and skills, and point you to the next DOS skill to use.

Frequently Asked Questions about dos-setup

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

FAQPage Schema

How do I verify DOS plugin installation and workspace wiring?▼

To verify DOS plugin installation, the tool checks that the active Python interpreter imports the dos-kernel package and runs a doctor check to confirm workspace lane detection and path configuration.

Why does Claude Code fail to import dos-kernel or see MCP tools?▼

Claude Code fails to import dos-kernel or see MCP tools when the workspace wiring is incomplete. Running a doctor check diagnoses the hook and MCP failures by surfacing lane, path, and stamp data.

What is the best way to diagnose silent hook failures in a DOS workspace?▼

The best way to diagnose silent hook failures is to run the DOS doctor check. It exposes the workspace layout, verifies the active repo, and surfaces bundled hooks and MCP tools to pinpoint wiring issues.

Does the DOS doctor check require a specific Python environment?▼

Yes, the DOS doctor check requires the active Python interpreter to successfully import both the dos and dos_mcp modules before it can generate a readout exposing lanes, paths, and stamp data.

How do I discover bundled skills and tools after installing the DOS plugin?▼

To discover bundled skills and tools after installation, run the verification process. It surfaces the bundled hooks, MCP tools, and recommends the next DOS skill to use based on the doctor check readout.