Docs Workflows

Documents

docs-workflows

Docs Workflows is an Agent Skill for documents published in the TencentCloudBase/CloudBase-MCP repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Documentation and extension workflows derived from local slash commands (docs, explanation, issues, prototypes, tutorials, MCP design review).

View on GitHub ↗

QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

Open your project in Codex.
Copy and paste the prompt below.
Review files and risks before approving any action.

Prompt to paste

Inspect the Agent Skill at https://github.com/TencentCloudBase/CloudBase-MCP/blob/HEAD/skills/docs-workflows/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/docs-workflows, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Docs Workflows (docs / explanation / issue / prototype / extension)

This skill groups the repo's documentation-oriented slash commands into reusable workflows.

When to use this skill

Use this skill when the user asks to:

create or standardize documentation
produce a structured explanation of changes
draft an issue
create a quick prototype plan or outline
add an article/video tutorial entry
add AI IDE / skill / command templates
run MCP design quality review

Source of truth

references/add_article_tutorial.md
references/create_doc.md
references/doc_type.md
references/explanation.md
references/issue.md
references/prototype.md
references/add_video_tutorial.md
references/add_aiide.md
references/add_skill.md
references/add_command.md
references/mcp_design_review.mdc

Execution rules

Read the relevant command template from this skill's references/.
Apply the template structure and required fields as the output contract.
Keep edits minimal and consistent with repo doc locations (e.g. doc/, specs/).
Prefer clarity and auditability over verbosity.

Command mapping

See references/command-catalog.md.