MN755
UserAn 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.
Categories
Indexed Skills (63)
mission-control-codebase-intake-burst
Use when Mission Control should recommend a read-only codebase intake burst with Repo Mapper, Test Finder, Docs Reader, Risk Scanner, and Dependency Mapper.
mission-control-import-codebase
Import or attach an existing codebase into Mission Control. Use when the workspace already contains a repo and Codex should let Mission Control scan, understand, and classify it before edits.
mission-control-import
Use when Codex should attach an existing repo or folder to Mission Control and keep the first pass read-only until the user authorizes more.
mission-control-install-from-github
Install or repair Mission Control for headless Codex use from a repo checkout or GitHub clone.
mission-control-orchestrate
Use when Codex should route a workspace task through Mission Control instead of acting like the Manager AI.
mission-control-subagent-burst
Recommend or review Mission Control Codex subagent bursts for bounded read-heavy work. Use when the user wants parallel exploration, review, planning, handoff audit, or failure diagnosis without replacing the normal worker system.
mission-control
Use when Codex should act as the bridge into Mission Control instead of acting like the Manager AI itself.
mission-control-compiler-autotuning-guidance
Request compiler and autotuning guidance for GPU code through Mission Control with bounded iteration and evidence requirements.
mission-control-cuda-kernel-generation
Route CUDA kernel generation or repair through Mission Control with GPU-aware validation and infrastructure checks.
mission-control-cuda-tile-refactor
Use when CUDA Tile or tile-shaped GPU refactors need Mission Control planning, validation, and benchmark discipline.
mission-control-debug
Diagnose stuck or failed Mission Control orchestration. Use when runs are blocked, failing repeatedly, waiting too long, missing evidence, or unclear about the next recovery step.
mission-control-autowire-providers
Use when Codex should detect and safely autowire local Mission Control runners without enabling unsafe billing paths by default.
mission-control-headless-health
Use when Codex should diagnose Mission Control plugin, daemon, MCP, runtime, or runner health from chat without opening the standalone app.
mission-control-bridge
Use when Codex should relay user intent to Mission Control instead of acting as the Manager itself.
mission-control-agents-md
Generate or review AGENTS.md from Mission Control understanding. Use when the user wants AGENTS.md proposed from the codebase map, existing instructions reviewed, or a safe draft prepared before writing.
mission-control-approve
Relay Mission Control approvals and questions to the user. Use when there are pending command approvals, tool approvals, write permissions, Manager questions, swarm approvals, recovery decisions, or handoff review gates.
mission-control-failure-diagnosis-burst
Use when Mission Control should recommend a read-only failure diagnosis burst across logs, recent changes, tests, dependencies, and recovery planning.
mission-control-handoff-audit-burst
Use when Mission Control should recommend a read-only handoff audit burst for run instructions, validation evidence, limitations, docs quality, and security caveats.
mission-control-handoff
Retrieve and present the final Mission Control handoff. Use when the user asks for the finished result, final summary, what changed, how to run it, evidence, limitations, or next tasks.
mission-control-manager
Manager behavior for Codex Mission Control projects. Use when the manager needs to restate a project idea, run an interview, refine plans, create worker tasks, route follow-up work, or prepare final handoff notes.
mission-control-resume
Use when a new Codex chat needs to reconnect to a recent Mission Control orchestration safely.
mission-control-review-burst
Use when Mission Control should recommend a bounded read-only review burst across correctness, security, testing, maintainability, and docs.
mission-control-review-handoff
Use when Codex should retrieve Mission Control status, evidence, and final handoff notes for review with the user.
mission-control-safe-mode
Use when the user wants Mission Control to operate in a stricter approval-heavy safety posture.
mission-control-status
Use when the user wants a compact Mission Control status summary, blocker report, or agent activity check.
mission-control-swarm
Use when the user wants to inspect or adjust Mission Control swarm strategy from Codex chat.
mission-control-uninstall
Use when Codex should remove the Mission Control plugin bundle, synced skills, and managed Codex MCP registration.
mission-control-update
Use when Codex should refresh an existing Mission Control install, resync the plugin and skills, and rerun headless repair/bootstrap.
mission-control-agent-contracts
Show or request Mission Control agent contracts. Use when the user wants to inspect a worker mission, allowed paths, forbidden paths, tools, validation obligations, stop conditions, or escalation rules.
mission-control-agent-graph-workflows
Design graph-style agent workflows with nodes, edges, gates, retries, checkpoints, and human approvals through Mission Control.
mission-control-agent-stuck
Diagnose a stuck Mission Control agent. Use when an agent shows no output, repeats errors, times out, asks for the same approval repeatedly, or stops making progress events.
mission-control-api-provider-mode
Use or explain API-provider mode through Mission Control. Use when the user explicitly wants API-backed execution, needs billing implications explained, or wants confirmation that configured secret storage rather than chat-provided keys will be used.
mission-control-brand-comms
Coordinate brand-guideline, internal-communications, announcement, and stakeholder-message work through Mission Control with tone, audience, and evidence constraints.
mission-control-change-request
Run a post-handoff or mid-project Mission Control change request flow. Use when the user wants additional work classified, impact-estimated, task-created, validated, and folded into the current handoff or milestone safely.
mission-control-claude-cli-mode
Use or prefer Claude CLI runner mode through Mission Control. Use when the user explicitly wants Claude CLI if configured and Codex should verify availability and fallback rather than assuming setup exists.
mission-control-codebase-knowledge-graph
Build or inspect a Mission Control codebase knowledge graph. Use for file/function/class maps, dependency relationships, architectural layers, guided tours, and searchable understanding.
mission-control-codex-cli-mode
Use or prefer Codex CLI runner mode through Mission Control. Use when the user wants Codex CLI as the runner, needs its status explained, or wants the distinction between subscription auth and API-based providers kept clear.
mission-control-conflict-resolution
Resolve Mission Control agent or merge conflicts safely. Use when paths overlap, outputs disagree, or Mission Control needs a user-visible conflict-resolution path instead of hidden reassignment.
mission-control-context-pack
Show or build Mission Control context packs for agents. Use when the user wants to know which files, docs, and constraints are being packaged for a task, why they were selected, and where context coverage is still missing.
mission-control-continue-handoff
Continue work after a Mission Control handoff without losing continuity. Use when the user wants another iteration, wants limitations preserved, or needs the next change request to build on the previous handoff and evidence.
mission-control-creative-web-artifacts
Plan creative web artifacts, themed pages, demos, and visual prototypes through Mission Control while preserving project guardrails and validation.
mission-control-decision-ledger
Show important Mission Control decisions and assumptions. Use when the user wants to review user decisions, Manager assumptions, auto-decisions, rejected options, or approval history without searching raw events.
mission-control-diff-impact
Analyze the impact of current changes or a pull request through Mission Control. Use for ripple effects, affected tests, ownership, risk, and review focus.
mission-control-docs-heavy
Switch the project toward documentation-heavy Mission Control work. Use when the user wants the swarm or plan to prioritize README, guides, examples, docs review, or public-facing written material more than feature code.
mission-control-document-workflow
Coordinate document, PDF, Word, slide, spreadsheet, and report workflows through Mission Control. Use for document generation, conversion plans, extraction, validation, and evidence-backed summaries.
mission-control-domain-map
Extract business domains, flows, process steps, and domain vocabulary from a codebase or knowledge base through Mission Control.
mission-control-evals-observability
Design or run evaluation, tracing, callback, telemetry, and regression-observability workflows for Mission Control agents.
mission-control-event-digest
Summarize recent Mission Control events without raw logs. Use when the user wants the last 5 minutes, last 15 minutes, since last interaction, or since orchestration start summarized in bridge-safe markdown.
mission-control-benchmark-comparison
Compare before-and-after performance evidence through Mission Control without turning benchmark claims into theater.
mission-control-evidence-check
Check whether Mission Control claims have backing evidence. Use when the user wants to know whether tests, builds, screenshots, artifacts, or handoff confidence are real, missing, weak, or dry-run only.
mission-control-existing-repo-fix
Run a direct Mission Control fix workflow for an existing repo. Use when the task is a bugfix or targeted change in a non-empty codebase and the Manager should classify the request, plan narrowly, request write permission, and execute safely.
mission-control-explain-codebase
Explain an unfamiliar codebase from Mission Control understanding. Use when the user wants stack detection, structure, entry points, how it likely runs, how tests work, risky areas, or recommended exploration next.
mission-control-generate-runbook
Generate an operational runbook through Mission Control. Use when the user wants RUNBOOK.md or a chat-native runbook covering startup, tests, build, debugging, local reset, logs, and deployment notes.
mission-control-github-ready-docs
Prepare Mission Control docs for public GitHub. Use when documentation should be cleaned for publication, internal AI notes removed, secrets and private paths scrubbed, and install or run guidance made public-ready.
mission-control-interview
Run a full Mission Control Manager interview. Use when the project is ambiguous, project-specific intake matters, or the user wants the Manager to ask clarifying questions with budgeted depth before planning or build work.
mission-control-keras-finetuning
Route Keras fine-tuning and transfer-learning work through Mission Control with explicit baseline, unfreeze, and evaluation steps.
mission-control-keras-tuning
Route KerasTuner and other bounded hyperparameter searches through Mission Control with explicit budgets and evidence.
mission-control-knowledge-base-map
Build or inspect a graph-style map of docs, wiki pages, claims, entities, and relationships through Mission Control.
mission-control-local-first
Switch Mission Control toward local-first behavior. Use when the user wants local files, local models, no cloud deployment, and no external APIs unless explicitly approved.
mission-control-mcp-builder
Design, build, or audit MCP servers and tool/resource/prompt contracts through Mission Control. Use for MCP schemas, stdio startup, auth boundaries, plugin packaging, and smoke tests.
mission-control-memory-state-policy
Define memory, state, checkpoints, resumability, and retention policy for Mission Control workflows and agents.
mission-control-model-policy
Inspect or update Mission Control model-assignment policy. Use when the user wants to understand or change cost-saving, balanced, best-quality, local-first, or custom model routing across Manager, coding, docs, review, and fallback roles.
mission-control-nsight-profiling
Coordinate Nsight-based GPU profiling through Mission Control with safe evidence capture and approval-aware command use.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.