Scrubbed, public-ready documentation preparation for GitHub projects.
Install
mkdir -p .claude/skills/mission-control-github-ready-docs && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15472" && unzip -o skill.zip -d .claude/skills/mission-control-github-ready-docs && rm skill.zipInstalls to .claude/skills/mission-control-github-ready-docs
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Remove internal AI notes from documentation
- →Redact secrets from documentation
- →Scrub private paths from documentation
- →Prepare install guidance for public use
- →Prepare run guidance for public use
How it works
The skill prepares documentation for public GitHub by removing internal AI notes, redacting secrets, scrubbing private paths, and making install or run guidance public-ready.
Inputs & outputs
When to use mission-control-github-ready-docs
- →Prepare docs for public release
- →Redact internal paths from README
- →Clean AI notes from code docs
About this skill
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
- Review handoff, codebase map, and current docs outputs.
- Ask Mission Control to prepare GitHub-ready docs or treat the request as a docs-heavy change set.
- Summarize what will be cleaned, added, or redacted before any file write.
Mission Control calls
Tools:
mission_control_start_taskmission_control_get_handoff_summary
Resources:
mission-control://projects/{project_id}/handoffmission-control://projects/{project_id}/codebase-mapmission-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.
When not to use it
- →When documentation does not need to be cleaned for publication
- →When internal AI notes, secrets, or private paths should be preserved
Limitations
- →Does not leak private paths or tokens
- →Does not leave internal-only AI workflow notes in public docs
- →Does not claim screenshots or examples exist if they do not
How it compares
This skill automates the cleanup and standardization of documentation for public release, whereas a manual process would involve identifying and editing each sensitive piece of information.
Compared to similar skills
mission-control-github-ready-docs side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| mission-control-github-ready-docs (this skill) | 0 | 2mo | No flags | Intermediate |
| docs-write | 22 | 6mo | No flags | Beginner |
| content-research-writer | 15 | 10mo | No flags | Beginner |
| doc-coauthoring | 16 | 8mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by MN755
View all by MN755 →You might also like
docs-write
metabase
Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).
content-research-writer
ComposioHQ
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
doc-coauthoring
anthropics
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
research-grants
davila7
Write competitive research proposals for NSF, NIH, DOE, and DARPA. Agency-specific formatting, review criteria, budget preparation, broader impacts, significance statements, innovation narratives, and compliance with submission requirements.
teams-channel-post-writer
daymade
Creates educational Teams channel posts for internal knowledge sharing about Claude Code features, tools, and best practices. Applies when writing posts, announcements, or documentation to teach colleagues effective Claude Code usage, announce new features, share productivity tips, or document lessons learned. Provides templates, writing guidelines, and structured approaches emphasizing concrete examples, underlying principles, and connections to best practices like context engineering. Activates for content involving Teams posts, channel announcements, feature documentation, or tip sharing.
write-docs
tldraw
Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing guidance is needed. Applies to docs in apps/docs/content/.