mcpbeat

Docs Workflows

tencentcloudbase/docs-workflows

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

22k tokens
context cost
the whole folder, loaded on every use
14
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1066
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/TencentCloudBase/CloudBase-AI-Toolkit --skill docs-workflows

The instruction itself

5 sections, as written by the author

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.

How to use it

Copy the folder

Take tencentcloudbase/docs-workflows from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.