review-docs

A documentation review process for Markdown projects, especially Docus and Nuxt Content sites. It checks project type, organization, technical validity, writing quality, search visibility, and translation structure, then produces a report.

In plain words
What is it for?
Auditing documentation structure, front matter, MDC syntax, naming, technical correctness, SEO, readability, and internationalization, with prioritized recommendations.
Why use it?
It reveals documentation errors and clarity or discoverability problems before someone changes the files.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/nuxt-content/docus/review-docs
Any agent
npx skills add nuxt-content/docus --skill review-docs
Clone the repo
git clone --depth 1 https://github.com/nuxt-content/docus

Made for: Claude Code, Codex.

Per session 108 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,694 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00108 $0.03694
Opus 5 $0.00054 $0.01847
Sonnet 5 $0.00022 $0.00739
Haiku 4.5 $0.00011 $0.00369

Measured 2d ago against content hash 4dadf688ddd1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

review-docs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

docs/skills/review-docs/SKILL.md · 480 lines

How it starts

The opening of the file, as written. The whole thing — 480 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Review Docs

Comprehensive documentation review, optimized for Docus/Nuxt Content but compatible with any Markdown documentation.

Workflow Overview

This skill performs a 5-step review process:

  1. Detect Project Type - Identify Docus/Nuxt Content vs generic Markdown
  2. Analyze Structure - Map documentation organization, locales, sections
  3. Technical Validation - Check frontmatter, MDC syntax (if applicable), file naming
  4. Content Quality Review - Evaluate clarity, SEO, structure, i18n
  5. Generate Report - Provide categorized, actionable recommendations

Priority Levels

  • Critical - Blocks deployment or causes errors (missing frontmatter, invalid MDC syntax)
  • Important - Significantly impacts UX/SEO (poor metadata, passive voice, unclear headings)
  • Nice-to-have - Polish and optimization suggestions (add callouts, improve examples)

Expectations

This skill generates a detailed report only. After reviewing, it offers to fix identified issues if requested.


Step 1: Detect Project Type

Goal: Determine if this is a Docus/Nuxt Content project or generic Markdown documentation.

Detection Indicators

Check for Docus/Nuxt Content:

  1. package.json dependencies:

    • "docus" - Docus theme
    • "@nuxt/content" - Nuxt Content module
    • "@nuxtjs/mdc" - MDC support
  2. Configuration files:

    • nuxt.config.ts or nuxt.config.js with @nuxt/content module
    • content.config.ts - Content collections configuration
  3. Content structure:

    • content/ or docs/content/ directory
    • .navigation.yml files in subdirectories
    • MDC syntax in markdown files (::component-name)
  4. Project structure:

    • Numbered directories (1.getting-started/, 2.guide/)
    • Frontmatter with navigation, seo fields

Project Type Classification

Type A: Docus/Nuxt Content Project

  • All Docus-specific validations apply
  • MDC component syntax checks (u- prefix requirement)
  • Nuxt Content frontmatter structure
  • Navigation files (.navigation.yml)
  • Full technical validation

Read the full file on GitHub · 480 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 480 lines · 108 tokens per session scan A 4dadf688ddd1

Subscribe to this mod's changes

review-docs is a skill published in the GitHub repository nuxt-content/docus (3,025 stars, last pushed 4d ago), licensed MIT. It adds 108 tokens to every session and 3,694 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

firehose-summary

Summarize recent social mentions from the Nuxt firehose Slack channel and flag items that need team attention.

nuxt/nuxt.com · 22 tokens

html-ppt-zhangzara-coral

OpenDesign's community-growth campaign across GitHub, Discord, and X: the loops, the content calendar, and the pipeline math. Built as a decision-grade marketing & GTM deck for growth team, community lead.

nexu-io/open-design · 55 tokens

ads

When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad…

coreyhaines31/marketingskills · 175 tokens

co-marketing

When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership…

coreyhaines31/marketingskills · 92 tokens

x-mastery-mentor

$10K/hr级X/Twitter运营导师。基于Nicolas Cole、Dickie Bush、Sahil Bloom、Justin Welsh、 Dan Koe、Alex Hormozi六位顶级创作者的方法论 + X开源算法深度分析 + AI/科技赛道专精策略, 提炼6个核心心智模型、10条决策启发式、完整的选题-写作-增长操作手册。 通用方法论为底座,AI/科技赛道为专精。 当用户提到「X运营」「推特」「Twitter」「怎么写推文」「怎么涨粉」「X策略」「推特选题」「tweet」「thread」「X算法」时使用。 即使用户只是说「这条推文怎么写」「帮我想个X内容」「推特增长」「发推」「write a tweet」「X…

alchaincyf/nuwa-skill · 197 tokens

geo-schema

Schema.org structured data audit and generation optimized for AI discoverability — detect, validate, and generate JSON-LD markup.

zubair-trabzada/geo-seo-claude · 26 tokens