Run any Skill in Manus with one click

cove-public-docs

Stars54

Forks29

UpdatedJune 17, 2026 at 19:05

Draft public COVE documentation for user-facing feature branches by comparing against dev, fetching relevant live public docs pages, and producing a concise copy-paste markdown draft in .public-docs.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

CDCgov

CDCgov/cdc-open-viz

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	cove-public-docs
description	Draft public COVE documentation for user-facing feature branches by comparing against dev, fetching relevant live public docs pages, and producing a concise copy-paste markdown draft in .public-docs.
metadata	{"short-description":"Draft public COVE docs"}

COVE Public Docs

Use this skill when the user asks to draft, generate, or prepare public COVE documentation for feature work in this repository.

Follow docs/PUBLIC_DOCUMENTATION_WORKFLOW.md. That tracked document is the source of truth for the workflow, URL index, output location, and draft format.

Key reminders:

Compare feature branches against dev unless the user specifies another base.
Fetch relevant live public documentation pages before drafting.
Save the draft to .public-docs/<branch-name>.md.
Also print the complete draft in the final response.
Keep the draft short and copy-paste-ready.
Match the fetched page shape: field-reference pages use bold-label entries and option bullets; concept/how-to pages may use short section prose.
Describe current editor behavior directly; avoid migration, legacy, deprecation, replacement-history framing, and transition phrases like now or no longer in public copy.

More from this repository

same repository

react-doctor

CDCgov/cdc-open-viz

Run React Doctor against a path and write a single markdown checklist grouped by rule type. Use this skill whenever the user wants to scan and review React issues, run react doctor, or get a prioritized list of React problems ready for fixing.

2026-06-1654

react-doctor-fix

CDCgov/cdc-open-viz

Read a React Doctor review file, let the user choose a rule type to work on, then apply fixes sequentially with confirmation at each step. Use this skill whenever the user wants to fix React Doctor issues, work through a review file, or asks to resolve a specific rule type or section of react doctor output.

2026-06-1054

yarn-audit

CDCgov/cdc-open-viz

Resolve `yarn audit --groups dependencies` findings in Yarn workspaces, especially when dependency versions drift across packages or a transitive vulnerability requires a targeted upgrade or `resolutions` entry. Use when Codex needs to investigate or fix dependency audit issues and should use `syncpack` when version mismatches are the real problem.

2026-04-1654

readme-maintainer

CDCgov/cdc-open-viz

Review and maintain README.md for accuracy against the current repository contents

2026-04-0854

name	cove-public-docs
description	Draft public COVE documentation for user-facing feature branches by comparing against dev, fetching relevant live public docs pages, and producing a concise copy-paste markdown draft in .public-docs.
metadata	{"short-description":"Draft public COVE docs"}

COVE Public Docs

Use this skill when the user asks to draft, generate, or prepare public COVE documentation for feature work in this repository.

Follow docs/PUBLIC_DOCUMENTATION_WORKFLOW.md. That tracked document is the source of truth for the workflow, URL index, output location, and draft format.

Key reminders:

Compare feature branches against dev unless the user specifies another base.
Fetch relevant live public documentation pages before drafting.
Save the draft to .public-docs/<branch-name>.md.
Also print the complete draft in the final response.
Keep the draft short and copy-paste-ready.
Match the fetched page shape: field-reference pages use bold-label entries and option bullets; concept/how-to pages may use short section prose.
Describe current editor behavior directly; avoid migration, legacy, deprecation, replacement-history framing, and transition phrases like now or no longer in public copy.