Mission control resume agents
Resume paused Mission Control agents or projects when safe. Use when the user wants paused work restarted but approvals, safety conditions, and current status should be checked first.From its SKILL.md
npx -y skills add MN755/Codex-Mission_Control --skill mission-control-resume-agentsAssembled 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.
SKILL.md
1.9 KB, 351 tokens by cl100k_base, as published. Nobody here has run it
Mission Control Resume Agents
Purpose
Resume paused work only after checking safety and pending approvals.
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 wants paused agents resumed.
- A pause has already happened and work can continue.
- Safety conditions must be verified before restarting.
Workflow
- Check current status and pending decisions.
- Confirm the work is actually paused and not already running.
- Call
mission_control_resumeonly if safe. - Summarize the post-resume state and next checkpoint.
Mission Control calls
Tools:
mission_control_get_statusmission_control_get_pending_decisionsmission_control_resume
Resources:
mission-control://projects/{project_id}/orchestrations/{orchestration_id}/statusmission-control://projects/{project_id}/pending-decisionsmission-control://projects/{project_id}/agents
User-facing output
- Show whether resume is safe, what approvals are still pending, and which agents or tasks are active again after resume.
- Explain clearly if resume is blocked.
Approval behavior
If pending approvals still block execution, present them first instead of resuming blindly.
Never do
- Do not resume work that was paused for unresolved risk without user awareness.
- Do not treat resume as a status check only.
- Do not restart already-running work.
Failure and fallback
If granular agent resume is not supported, explain whether resume applies at project or orchestration level and use the safest available scope.
Example invocation
Resume the paused Mission Control agents if it is safe.
What ships with it: 1 file
135 B alongside SKILL.md
agents/
- openai.yaml135 B
Gives 0 of the 12 instructions most hr recruiting skills give in 351 tokens
Counted across 356 of the 357 authors here whose files we hold, read 2026-08-07
- Quantify achievements with specific metricsin 14 of 356, across 6 files
- Keep the resume under two pagesin 14 of 356, across 6 files
- Request the full job description if not providedin 12 of 356, across 4 files
- Extract keywords and prioritize job requirementsin 12 of 356, across 4 files
- Stop and ask for clarification if required inputs are missingin 12 of 356, across 5 files
- Map candidate experience to job requirementsin 11 of 356, across 3 files
- Ask if the user wants adjustmentsin 11 of 356, across 3 files
- Provide strengths and gap analysis after the resumein 10 of 356, across 2 files
- Request candidate background details if not providedin 10 of 356, across 2 files
- Format experience bullets as action verb plus resultin 10 of 356, across 2 files
- Ask for missing inputs before startingin 10 of 356, across 9 files
- Use exact job description terminologyin 9 of 356, across 1 file
Said here and by no other author read
- check current status and pending decisions
- confirm work is paused and not running
- present pending approvals before resuming
- call mission_control_resume only if safe
- summarize the post-resume state and next checkpoint
- explain if resume is blocked
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.