Mission control document workflow
Skill MN755/Codex-Mission_Control/.codex/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.
npx -y skills add MN755/Codex-Mission_Control --skill mission-control-document-workflowAssembled 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, 354 tokens by cl100k_base, 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
- Ask Mission Control to classify the document task and required tools.
- Identify whether built-in host document plugins or local libraries are needed.
- Route extraction, generation, or validation through approved runners.
- Return evidence, outputs, limitations, and next steps.
Mission Control calls
Tools:
mission_control_start_taskmission_control_get_status
Resources:
mission-control://projects/{project_id}/handoffmission-control://projects/{project_id}/validation-summarymission-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.
Gives 0 of the 12 instructions most docs writing skills give in 354 tokens
Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-07
- announce the skill at startin 54 of 1637, across 26 files
- convert legacy doc files before editingin 45 of 1637, across 7 files
- Predict questions readers might askin 42 of 1637, across 4 files
- Generate clarifying questions for initial contextin 42 of 1637, across 3 files
- Create document scaffold with placeholder textin 42 of 1637, across 3 files
- Brainstorm content options for each sectionin 42 of 1637, across 3 files
- Test document with fresh context-less instancein 42 of 1637, across 3 files
- include exact file paths in every taskin 42 of 1637, across 15 files
- ask interview questions one at a timein 42 of 1637, across 27 files
- Apply surgical edits during refinementin 41 of 1637, across 2 files
- Offer structured workflow or freeformin 40 of 1637, across 1 file
- Ask for document meta-contextin 40 of 1637, across 2 files
Said here and by no other author read
- Ask Mission Control to classify the document task
- Identify needed built-in plugins or local libraries
- Route operations through approved runners
- Return evidence, outputs, limitations, and next steps
- Ask before overwriting documents or exporting sensitive data
- State document type, tool path, files, and validation status
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.