agentsclimarketplace

Mission control document workflow

Skill MN755/Codex-Mission_Control/apps/mcp-server/src/mission_control_mcp_server/_bundled/skills/mission-control-document-workflow

An Open Source Platform For Building Projects With OpenAI's Codex, Claude CLI, And Other Coding LLMs Using Multi-Agent Swarms And Customizable Workflows. Runs On Windows, MacOS, And Linux.

Install
npx -y skills add MN755/Codex-Mission_Control --skill mission-control-document-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Coordinate document, PDF, Word, slide, spreadsheet, and report workflows through Mission Control. Use for document generation, conversion plans, extraction, validation, and evidence-backed summaries.

SKILL.md

2.0 KB, as published. Nobody here has run it

Mission Control Document Workflow

Purpose

Plan document-heavy work without pretending Mission Control owns every file-format implementation internally.

The Codex chat agent is not the Mission Control Manager. It is the bridge between the user and the Mission Control Manager.

Use when

  • The user asks for PDF, DOCX, PPTX, XLSX, report, or document workflow help.
  • A document needs extraction, validation, summarization, or generated output.
  • The workflow depends on external document tooling.

Workflow

  1. Ask Mission Control to classify the document task and required tools.
  2. Identify whether built-in host document plugins or local libraries are needed.
  3. Route extraction, generation, or validation through approved runners.
  4. Return evidence, outputs, limitations, and next steps.

Mission Control calls

Tools:

  • mission_control_start_task
  • mission_control_get_status

Resources:

  • mission-control://projects/{project_id}/handoff
  • mission-control://projects/{project_id}/validation-summary
  • mission-control://projects/{project_id}/status

User-facing output

  • State document type, requested operation, tool path used, files created or inspected, and validation status.

Approval behavior

Ask before overwriting documents, exporting sensitive data, or using external services.

Never do

  • Do not claim document fidelity without checking the generated artifact.
  • Do not expose private document contents unnecessarily.
  • Do not reimplement specialized document tooling when an approved plugin already exists.

Failure and fallback

If document tooling is unavailable, produce a plan and list the exact missing capability.

Example invocation

Use Mission Control to extract the key claims from this PDF and create a validation checklist.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.