OpenParable
Skip to content
← Back to skills

Deepwork

Productivity
deepwork

Deepwork is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Start or continue DeepWork workflows using MCP tools

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/workflow/deepwork/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/deepwork, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

DeepWork Workflow Manager

Execute multi-step workflows with quality gate checkpoints.

Terminology

A job is a collection of related workflows. For example, a "code_review" job might contain workflows like "review_pr" and "review_diff". Users may use the terms "job" and "workflow" somewhat interchangeably when describing the work they want done — use context and the available workflows from get_workflows to determine the best match.

IMPORTANT: Use the DeepWork MCP server tools. All workflow operations are performed through MCP tool calls and following the instructions they return, not by reading instructions from files.

How to Use

  1. Call get_workflows to discover available workflows
  2. Call start_workflow with goal, job_name, and workflow_name
  3. Follow the step instructions returned
  4. Call finished_step with your outputs when done
  5. Handle the response: needs_work, next_step, or workflow_complete

Creating New Jobs

To create a new job, use the MCP tools:

  1. Call get_workflows to confirm the deepwork_jobs job is available
  2. Call start_workflow with:
    • job_name: "deepwork_jobs"
    • workflow_name: "new_job"
    • goal: a description of what the new job should accomplish
    • instance_id: a short name for the new job (e.g., "code_review")
  3. Follow the instructions returned by the MCP tools as you progress through the workflow

Intent Parsing

When the user invokes /deepwork, parse their intent:

  1. ALWAYS: Call get_workflows to discover available workflows
  2. Based on the available flows and what the user said in their request, proceed:
    • Explicit workflow: /deepwork <a workflow name> → start the <a workflow name> workflow
    • General request: /deepwork <a request> → infer best match from available workflows
    • No context: /deepwork alone → ask user to choose from available workflows