Skip to content
Back to skills

W Docs

ASecurity

Document the current code or feature in the owning docs layer.

  • 428 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 20, 2026
ai-agents

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 20, 2026

npx -y skills add aiskillstore/marketplace --skill w-docs --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of W Docs?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for W Docs
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aiskillstore-w-docs/badge)](https://www.skillsdirectory.com/skills/aiskillstore-w-docs)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: w-docs
description: Document the current code or feature in the owning docs layer.
disable-model-invocation: true
---

Document the current code or feature. Follow the consuming repo's docs and README rules. Do not commit unless asked. Durable information architecture belongs in existing MDX; do not invent a second sitemap.

Write to the layer that owns the change:

| Layer | Role | Update when |
| --- | --- | --- |
| Technical docs (path in `AGENTS.md`) | Architecture, ADRs, how-to | Behavior, architecture, commands, conventions, or workflow changed |
| Agent rules | Short constraints | A convention the agent must not violate changed |
| Nearest README | How to run this app/package; links only | Scripts, setup, or package purpose changed |

Inline comments only when the code is otherwise misleading. Do not copy MDX into rules or READMEs. Do not `@`-attach MDX.

1. Identify the matching docs section, then an existing topic page (create a page only if none fits).
2. Write or patch MDX if the canonical explanation changed.
3. Patch README only for run/setup/scripts; link the MDX.
4. Patch the glob-matched rule only if a constraint changed.
5. For mechanical file or doc moves: propose the smallest from/to list grouped by related files; drop folder-name prefixes inside groups. Save only if the user gave a path. Do not move files unless they also asked to implement.

Files in this skill

  • SKILL.md1.4 KB
  • skill-report.json10.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…