docs-guard is a skill in amElnagdy/guard-skills, last changed 4 Jul 2026. It can run shell commands and name web addresses.

From the author
Review generated or changed documentation before it ships — READMEs, API references, docstrings, PHPDoc/JSDoc, changelogs, tutorials, and doc sites. Best used reactively after an agent writes or edits docs, after code changes documented behavior, or before publishing docs. Use when the user says 'review the docs', 'is this documentation accurate', 'update the docs', 'write a README', 'document this API', 'add a docstring', or 'add a changelog entry'. Core job: verify every referenced function, flag, endpoint, config key, and code sample against the source; catch docs-vs-code drift; strip filler and unverifiable claims. DO NOT USE for production code review (use clean-code-guard), test review (use test-guard), marketing copy or blog posts, prose style editing of non-technical writing, or documentation site theming.

At a glance

What it can touch

How much a skill can do, not whether it is risky.

Pattern check

Nothing flagged

That isn't proof the skill is harmless.

Commit ffa2603 · 29 Oct 2026

How the check works

Pattern check: nothing flagged

That isn't proof the skill is harmless.

Install

Each tab says whether it installs commit ffa2603, the one we checked, or the latest version.

Read SKILL.md first
MIT
Licence
1.3k
Repo stars
Publisher
Files

What it can touch

From the files and frontmatter at commit ffa2603. This is how much a skill can do, not whether it is risky.

  • Runs shell commands

    Its instructions or files give the agent commands to run on your computer.

  • Names web addresses

    It mentions outside web addresses the agent may visit. We list them but don't follow them.

    Outside links we did not follow

Pattern check

Pattern check: nothing flagged · commit ffa2603 · 29 Oct 2026

We checked every text file in this skill, at commit ffa2603 on 29 Oct 2026, against 45 published patterns such as download-and-run commands, hidden text and credential access. We don't run the skill, we don't read the web pages it points to, and we can't judge everything its instructions might lead an agent to do. In published tests, pattern checks like this one missed most malicious skills. Read the skill before you install it — especially anything it asks you to download or run.

How the check worksReport an incorrect finding

  • https://dl.acm.org/doi/10.1145/3613904.3642596
  • https://arxiv.org/abs/2407.09726
  • https://arxiv.org/abs/2401.01701
  • https://www.usenix.org/conference/usenixsecurity25/presentation/spracklen
  • https://diataxis.fr/
  • https://www.writethedocs.org/guide/writing/style-guides/
  • https://www.rfc-editor.org/rfc/rfc5737
  • https://developers.google.com/style

Format check

Each agent reads SKILL.md a little differently. We check the file against each one's published rules; we don't run the skill in any agent.

  • Agent Skills specPasses

    The open format from agentskills.io, held to what the strictest agents enforce, so one folder loads everywhere.

    • Note

      There is no license field, so readers can't tell whether they may reuse the skill. O2

      Fix: Add license: with an SPDX name such as MIT or Apache-2.0, or the name of a bundled licence file.

  • Claude CodePasses
  • Claude apps & API uploadPasses

    Uploading to claude.ai or the Claude API, or packaging with Anthropic's script, accepts only the six spec fields and stops on anything else.

    • Note

      The description is 825 characters. The claude.ai Help Center says 200 at most, though Anthropic's API docs and validator allow 1,024. D4

      Fix: If the claude.ai upload refuses it, trim the description to 200 characters.

  • OpenAI (Codex & API)Passes
  • VS Code & CopilotPasses

SKILL.md

Files

More from amElnagdy/guard-skills

SkillWhat it can touchPattern checkLicenceUpdated
clean-code-guardReview generated or changed production code before it ships, using Clean Code, SOLID, DRY, KISS, YAGNI, and LLM-specific failure-mode checks in any programming language. Best used reactively after an agent writes, edits, refactors, or fixes code, before presenting, committing, or merging the result. Use when the user asks "review this PR", "is this safe to merge?", "make this cleaner", "audit this code", "refactor this", "fix this bug", or after a coding agent produced implementation code. Can also guide writing when explicitly invoked before a risky edit. Invoke it on your own initiative the moment you finish writing, editing, or refactoring non-trivial production code, before presenting or committing — don't wait to be asked. DO NOT USE for factual/conceptual questions, CI/tooling config, git workflow, running/debugging tests, pure architecture discussion, prose writing, data analysis, or test-code review (use test-guard).
  • Names web addresses

Pattern check: Nothing flaggedMITUpdated 4 Jul 2026

  • Names web addresses
Pattern check: Nothing flaggedMIT4 Jul 2026
test-guardReview generated or changed test code against universal testing rules before it ships. Best used reactively after an agent writes, edits, generates, or refactors tests, before presenting, committing, or merging them. Use for pytest (test_*.py, *_test.py), PHPUnit/Pest (*Test.php), Jest/Vitest (*.test.ts, *.spec.js), Go (*_test.go), files under tests/, __tests__/, or spec/, and review requests like 'write tests for X', 'add tests', 'test this', 'review these tests', or PR diffs containing tests. Can also guide test writing when explicitly invoked before the work. This skill is the quality gate that prevents AI-generated test bloat. DO NOT USE for production or implementation code review (use clean-code-guard), CI or test-runner configuration, running or debugging tests, or general architecture discussion.
  • Reaches the network

Pattern check: Nothing flaggedMITUpdated 4 Jul 2026

  • Reaches the network
Pattern check: Nothing flaggedMIT4 Jul 2026
woo-guardReview generated or changed WooCommerce code — extensions, payment and shipping integrations, checkout customizations, and order/product logic — before it ships. Best used reactively after an agent writes, edits, or reviews code touching WooCommerce APIs: wc_get_order, wc_get_orders, wc_get_product, WC() cart or session, woocommerce_* hooks, Store API endpoints, payment gateways, order or product meta, HPOS, subscriptions, or bookings. Use on 'review this Woo plugin', 'is this HPOS compatible', or after tasks like 'write a WooCommerce extension', 'add a checkout field', 'hook into the order flow', or 'update stock'. Enforces HPOS-safe order access, CRUD over direct meta, feature-compatibility declarations, server-side checkout validation, money-handling discipline, and hooks over template overrides. DO NOT USE for WordPress code without WooCommerce APIs (use wp-guard), generic code review (use clean-code-guard), test review (use test-guard), or store configuration and admin-screen questions.
  • Names web addresses

Pattern check: Nothing flaggedMITUpdated 7 Jun 2026

  • Names web addresses
Pattern check: Nothing flaggedMIT7 Jun 2026
wp-guardReview generated or changed WordPress code — plugins, themes, and blocks — before it ships. Best used reactively after an agent writes, edits, or reviews code touching WordPress APIs: add_action/add_filter, shortcodes, meta boxes, AJAX handlers, REST routes, WP_Query or $wpdb, widgets, or WP-CLI commands. Use on 'review this plugin', 'is this safe to ship', 'make this translatable', 'speed up this query', or after tasks like 'write a plugin' or 'add an endpoint/shortcode/meta box'. Enforces escaping and sanitization, nonces plus capability checks, prepared database queries, core-API-first development, translation-ready strings, and query/caching discipline. DO NOT USE for WooCommerce-specific order, product, or checkout logic (use woo-guard), non-WordPress PHP, generic code quality review (use clean-code-guard), test code review (use test-guard), server or hosting configuration, or conceptual WordPress questions.
  • Names web addresses

Pattern check: Nothing flaggedMITUpdated 7 Jun 2026

  • Names web addresses
Pattern check: Nothing flaggedMIT7 Jun 2026

Other Writing & content skills

Same category, most repo stars first.

SkillWhat it can touchPattern checkLicenceUpdated
  • Instructions only
Pattern check: Nothing flaggedMIT27 Sept 2026
  • Runs shell commands
Pattern check: Nothing flaggedMIT11 Jun 2026
academy-guideStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

anthropics/skills

  • Names web addresses

Pattern check: Nothing flaggedApache 2.0Updated 18 Aug 2026

  • Names web addresses
Pattern check: Nothing flaggedApache 2.018 Aug 2026
discernment-nudgeAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

anthropics/skills

  • Names web addresses

Pattern check: Nothing flaggedApache 2.0Updated 17 Aug 2026

  • Names web addresses
Pattern check: Nothing flaggedApache 2.017 Aug 2026
document-generateGenerate missing documentation from scratch for a feature, module, or entire project. (gstack)

garrytan/gstack

  • Runs shell commands
  • +2 more

Pattern check: 1 item to reviewMITUpdated 27 Oct 2026

  • Runs shell commands
  • Reaches the network
  • +1 more
Pattern check: 1 item to reviewMIT27 Oct 2026
document-releaseRelease documentation audit. (gstack)

garrytan/gstack

  • Touches credentials
  • +4 more

Pattern check: 1 item to reviewMITUpdated 27 Oct 2026

  • Touches credentials
  • Runs shell commands
  • +3 more
Pattern check: 1 item to reviewMIT27 Oct 2026