agentsclimarketplace
Sign in

Mission control github ready docs

Skill MN755/Codex-Mission_Control/plugins/mission-control/skills/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.From its SKILL.md

Install
npx -y skills add MN755/Codex-Mission_Control --skill mission-control-github-ready-docs

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.

SKILL.md

2.0 KB, 355 tokens by cl100k_base, as published. Nobody here has run it

Mission Control Github Ready Docs

Purpose

Prepare documentation for a public GitHub audience through Mission Control-aware review.

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 repo may go public.
  • The user wants README-friendly documentation.
  • Docs need secret and private-path cleanup before sharing.

Workflow

  1. Review handoff, codebase map, and current docs outputs.
  2. Ask Mission Control to prepare GitHub-ready docs or treat the request as a docs-heavy change set.
  3. Summarize what will be cleaned, added, or redacted before any file write.

Mission Control calls

Tools:

  • mission_control_start_task
  • mission_control_get_handoff_summary

Resources:

  • mission-control://projects/{project_id}/handoff
  • mission-control://projects/{project_id}/codebase-map
  • mission-control://projects/{project_id}/risk-register

User-facing output

  • Call out removal of internal AI notes, secrets, and private paths.
  • Include install, run, test, limitations, and screenshot-placeholder expectations if relevant.

Approval behavior

Ask before overwriting public-facing docs or removing existing internal notes that the user still wants preserved elsewhere.

Never do

  • Do not leak private paths or tokens.
  • Do not leave internal-only AI workflow notes in public docs.
  • Do not claim screenshots or examples exist if they do not.

Failure and fallback

If no dedicated docs-publication tool exists, route the task through Mission Control with a docs-heavy and GitHub-ready objective, then summarize the planned cleanup items.

Example invocation

Use Mission Control to make the docs GitHub-ready.

What ships with it: 1 file

159 B alongside SKILL.md

agents/

Gives 0 of the 12 instructions most docs writing skills give in 355 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 the document with a 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

  • review handoff codebase map and docs
  • ask Mission Control to prepare GitHub-ready docs
  • summarize planned cleanup before writing files
  • call out removal of internal notes and secrets
  • include install run and test guidance
  • ask before overwriting public-facing docs

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.

Keep looking

Skills are one crate of 326,546. 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.