Typescript Style
tjx666/vscode-mcp
TypeScript code style and repo conventions for VSCode MCP — inference vs explicit types, ESM import suffixes, zod schema contracts, async VSCode/Node APIs, JSON-safe IPC results, JSDoc for public…
A skill your agent uses when auditing repository documentation for drift, stale statements, broken references, or README mismatches, especially across published docs under doc/ and key entry…
Install Doc Freshness Review
$ npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill doc-freshness-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install TencentCloudBase/CloudBase-AI-Toolkit doc-freshness-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/TencentCloudBase/CloudBase-AI-Toolkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/doc-freshness-review .claude/skills/doc-freshness-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "doc-freshness-review" agent skill from https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/skills/doc-freshness-review into .claude/skills/doc-freshness-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-freshness-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/skills/doc-freshness-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill doc-freshness-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install TencentCloudBase/CloudBase-AI-Toolkit doc-freshness-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TencentCloudBase/CloudBase-AI-Toolkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/doc-freshness-review .agents/skills/doc-freshness-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "doc-freshness-review" agent skill from https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/skills/doc-freshness-review into .agents/skills/doc-freshness-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-freshness-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill doc-freshness-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install TencentCloudBase/CloudBase-AI-Toolkit doc-freshness-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TencentCloudBase/CloudBase-AI-Toolkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/doc-freshness-review .cursor/skills/doc-freshness-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "doc-freshness-review" agent skill from https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/skills/doc-freshness-review into .cursor/skills/doc-freshness-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-freshness-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/TencentCloudBase/CloudBase-AI-Toolkit.git --path skills/doc-freshness-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill doc-freshness-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install TencentCloudBase/CloudBase-AI-Toolkit doc-freshness-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TencentCloudBase/CloudBase-AI-Toolkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/doc-freshness-review .gemini/skills/doc-freshness-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "doc-freshness-review" agent skill from https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/skills/doc-freshness-review into .gemini/skills/doc-freshness-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-freshness-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install TencentCloudBase/CloudBase-AI-Toolkit doc-freshness-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill doc-freshness-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/TencentCloudBase/CloudBase-AI-Toolkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/doc-freshness-review .github/skills/doc-freshness-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "doc-freshness-review" agent skill from https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/skills/doc-freshness-review into .github/skills/doc-freshness-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-freshness-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill doc-freshness-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install TencentCloudBase/CloudBase-AI-Toolkit doc-freshness-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TencentCloudBase/CloudBase-AI-Toolkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/doc-freshness-review .opencode/skills/doc-freshness-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "doc-freshness-review" agent skill from https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/skills/doc-freshness-review into .opencode/skills/doc-freshness-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-freshness-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
doc-freshness-review- GitHub stars
- 1.1k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 536 words
- Files
- 2 (incl. references)
- Skills in repo
- 49
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing repository documentation for drift, stale statements, broken references, or README mismatches, especially across published docs under doc/ and key entry…
- Works in 4 steps: Scope the surfaces → Evidence-based comparison → Severity and action → …
- Auditing repository documentation for drift
- SKILL.md covers When to use this skill, Workflow, Routing and Evaluation prompts, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Doc Freshness Review is an agent skill from TencentCloudBase/CloudBase-AI-Toolkit. Use when auditing repository documentation for drift, stale statements, broken references, or README mismatches, especially across published docs under doc/ and key entry surfaces such as README.md (English default), README.zh-CN.md, mcp/README.md, and mcp/README.zh-CN.md during periodic maintenance or before preparing corrective PRs.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/review-scope.md`).
It sits in Development, covering Technical documentation and MCP servers. It works with Model Context Protocol. The repository describes itself as: Backend for AI coding agents on CloudBase — database, auth, functions via Plugin, Skills & MCP. The licence is MIT.
When your agent uses it
- Auditing repository documentation for drift
- Stale statements
- Broken references
- README mismatches
Example prompts
- “/doc-freshness-review”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 21af91c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Doc Freshness Review loads about 1.1k tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 92 tokens; SKILL.md has 536 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from TencentCloudBase/CloudBase-AI-Toolkit at commit 21af91c, republished under its MIT licence (© TencentCloudBase). 536 words, ~1,060 tokens.
Download SKILL.mdSave it as
.claude/skills/doc-freshness-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- doc-freshness-review
- description
- Use when auditing repository documentation for drift, stale statements, broken references, or README mismatches, especially across published docs under `doc/` and key entry surfaces such as `README.md` (English default), `README.zh-CN.md`, `mcp/README.md`, and `mcp/README.zh-CN.md` during periodic maintenance or before preparing corrective PRs.
- alwaysApply
- false
Documentation Freshness Review
Review whether repository documentation still matches the current code, generated assets, and published entry points.
When to use this skill
Use this skill when you need to:
- Audit published documentation under
doc/for stale or wrong statements - Check whether
README.md,README.zh-CN.md,mcp/README.md, ormcp/README.zh-CN.mddrifted away from current behavior - Verify that linked scripts, files, commands, and workflows still exist and still match the repo
- Run a periodic docs health check before opening corrective PRs
- Separate mechanical doc drift from product ambiguity that still needs human confirmation
Do NOT use for:
- Marketing copy polish without a freshness or correctness question
- API contract review that depends on CloudBase control-plane docs first
- Feature planning or architecture design
- Rewriting large docs from scratch when the main need is a targeted drift audit
Workflow
Phase 1 — Scope the surfaces
- Read
references/review-scope.mdfirst. - Build the audit surface in two groups:
- published documentation under
doc/ - README surfaces such as
README.md,README.zh-CN.md, andmcp/README.md
- published documentation under
- Note which code, scripts, generated files, or workflows those docs claim to describe.
Phase 2 — Evidence-based comparison
- Verify whether referenced files, scripts, commands, and workflow names still exist.
- Compare the docs against the current implementation, generated outputs, and source-of-truth files.
- Mark each mismatch as one of:
- stale statement
- missing or stale reference
- outdated command
- drift between published docs and README surfaces
- drift between docs and actual implementation
Phase 3 — Severity and action
- Prefer concrete findings with exact file paths and the smallest useful rewrite direction.
- If the fix is mechanical and low-risk, prepare the doc updates for a focused PR.
- If the docs may be wrong because product behavior is unclear, write a report and issue instead of guessing.
- If the drift originates from a CloudBase API contract problem, hand off to
api-contract-reviewbefore updating the prose.
Show full SKILL.md (230 more words)Show less
Phase 4 — Follow-through
- Keep report sections separate for:
- published documentation
- README surfaces
- broken or missing references
- Prefer one focused PR per coherent doc drift batch.
- Route open-PR repair work to
pr-review-fixafter the doc finding is confirmed.
Routing
| Task | Read |
|---|---|
| Review docs and README freshness scope | references/review-scope.md |
| Review CloudBase API contract drift before changing related prose | api-contract-review |
| Fix an already-open PR after confirming the doc drift | pr-review-fix |
Evaluation prompts
Should-trigger
- Audit
doc/and the main README files for stale commands, missing files, and broken references. - Review whether
mcp/README.mdstill matches the current MCP tool behavior and linked files. - Help me prepare a corrective PR for docs that still reference scripts or workflows that no longer exist.
Should-not-trigger
- Review this TypeScript module for runtime validation gaps.
- Compare CloudBase action parameters against the official control-plane docs.
- Write a brand-new tutorial for a feature that does not exist yet.
Minimum self-check
- Did I separately review published documentation and README surfaces?
- Can I point to exact file paths for every stale or broken reference?
- Did I compare the docs against current code, scripts, and generated outputs instead of relying on memory?
- If I recommend a fix, is it a small, reviewable doc batch suitable for a PR?
- If the underlying product behavior was unclear, did I stop at report or issue instead of rewriting confidently?
© TencentCloudBase, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/doc-freshness-review of TencentCloudBase/CloudBase-AI-Toolkit.
- SKILL.md
- references/review-scope.md
Open the folder on GitHubat commit 21af91c
Compare with similar skills
Doc Freshness Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Doc Freshness Review this skillTencentCloudBase/CloudBase-AI-Toolkit | 1.1k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Typescript Styletjx666/vscode-mcp | 106 | — | ~961 | Automated safety check: Pass | Custom licence | |
| Source Command Unifi MCP Update Docsenuno/unifi-mcp-server | 282 | — | ~899 | Automated safety check: Pass | Apache-2.0 | |
| Githits MCPgithits-com/githits-cli | 114 | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Library Documentation Seekerwithkynam/vibecode-pro-max-kit | 1.1k | 2 repos | ~1k | Automated safety check: Notes | MIT | |
| Dashclaw Shipucsandman/DashClaw | 310 | — | ~7.2k | Automated safety check: Pass | MIT |
Similar skills
Source Command Unifi MCP Update Docs
enuno/unifi-mcp-server
Auto-generate and update API.md documentation from tool docstrings
Githits MCP
githits-com/githits-cli
Route public OSS code, documentation, examples, and package questions to GitHits tools.
Library Documentation Seeker
withkynam/vibecode-pro-max-kit
Looks up library and framework documentation through Context7 first, with bundled Node scripts as a fallback that fetch and analyze llms.txt files.
Dashclaw Ship
ucsandman/DashClaw
The single command that gets a DashClaw change ON MAIN AND LIVE — it resolves everything blocking production, never defers, and never hands back a checklist.
Score Harness
ruvnet/metaharness
5-dimension scorecard (0-100, grade A/B/C/F) for a scaffolded harness.
More from TencentCloudBase/CloudBase-AI-Toolkit
All 49 skills in this repoAI Model Nodejs
TencentCloudBase/CloudBase-AI-Toolkit
A skill your agent uses for Node.js backend AI via @cloudbase/node-sdk (=3.16.0) — cloud functions, CloudRun, Express/Koa/NestJS, serverless APIs, scheduled jobs, LLM proxies, agent orchestration.
HTTP API Cloudbase
TencentCloudBase/CloudBase-AI-Toolkit
CloudBase official HTTP API client guide. An agent skill from TencentCloudBase/CloudBase-AI-Toolkit.
Cloud API Recipe Authoring
TencentCloudBase/CloudBase-AI-Toolkit
Author or revise a cloud-api-operations recipe (config/source/skills/cloud-api-operations/references/recipes/).
Manage Local Skills
TencentCloudBase/CloudBase-AI-Toolkit
Analyze, standardize, validate, and sync locally maintained skills into agent skill directories with a skills CLI-aligned workflow.
Cloudbase Agent Python
TencentCloudBase/CloudBase-AI-Toolkit
Build production-ready AI agent backends using the CloudBase Agent Python SDK — create agents with LangGraph/CrewAI/LlamaIndex, serve them via FastAPI with AG-UI protocol streaming +…
Cloudbase
TencentCloudBase/CloudBase-AI-Toolkit
A skill your agent uses when you develop, design, build, deploy, debug, migrate, or troubleshoot CloudBase (腾讯云开发, 云开发, TCB, 微信云开发) projects — Web, 微信小程序, 小程序, uni-app, mobile (iOS, Android…
Related
Works with
Categories
Questions about Doc Freshness Review
What does Doc Freshness Review do?
A skill your agent uses when auditing repository documentation for drift, stale statements, broken references, or README mismatches, especially across published docs under doc/ and key entry…. Doc Freshness Review is an agent skill from TencentCloudBase/CloudBase-AI-Toolkit.md during periodic maintenance or before preparing corrective PRs.
When should I use Doc Freshness Review?
Doc Freshness Review fits situations like: auditing repository documentation for drift; stale statements; broken references; README mismatches.
How do I install Doc Freshness Review in Claude Code?
Run `npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill doc-freshness-review -a claude-code`. Or copy the skill folder (skills/doc-freshness-review in TencentCloudBase/CloudBase-AI-Toolkit) into .claude/skills/doc-freshness-review in your project. Claude Code loads it when a task matches its description.
How do I install Doc Freshness Review in Codex?
Run `npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill doc-freshness-review -a codex`. Or copy the skill folder (skills/doc-freshness-review in TencentCloudBase/CloudBase-AI-Toolkit) into .agents/skills/doc-freshness-review in your project. Codex loads it when a task matches its description.
Can I use Doc Freshness Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill doc-freshness-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/doc-freshness-review, .gemini/skills/doc-freshness-review, .github/skills/doc-freshness-review and .opencode/skills/doc-freshness-review in your project.
What does Doc Freshness Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Doc Freshness Review is instructions for the agent only.
Does Doc Freshness Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Doc Freshness Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Doc Freshness Review use?
Doc Freshness Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Doc Freshness Review use?
About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 310 tokens, read only when the agent opens those files.
What are the alternatives to Doc Freshness Review?
Skills that share tags, products or a category with Doc Freshness Review: Typescript Style (tjx666/vscode-mcp, 106 stars), Source Command Unifi MCP Update Docs (enuno/unifi-mcp-server, 282 stars), Githits MCP (githits-com/githits-cli, 114 stars) and Library Documentation Seeker (withkynam/vibecode-pro-max-kit, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Doc Freshness Review?
TencentCloudBase (a GitHub organization) maintains it in TencentCloudBase/CloudBase-AI-Toolkit, which has 1,133 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 7, 2026.
Source: TencentCloudBase/CloudBase-AI-Toolkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.