r-doc
Project documentation governance: automatically initialize, index, audit, and maintain AGENTS.md, docs/, and planning, requirements, design, API, testing, release, and deployment documents. Use when users ask to manage project documentation, check documentation consistency, update AGENTS.md, or t...
Install this skill
or
75/100
Security score
The r-doc skill was audited on Sep 14, 2026 and we found 1 security issue across 1 threat category, including 1 critical. Review the findings below before installing.
Categories Tested
Security Issues
critical line 35
Security bypass instruction
SourceSKILL.md
| 33 | 4. Keep each topic document focused on one subject. Split mixed, hard-to-locate, or overlong topics. Do not create empty documents just to fill a directory. |
| 34 | 5. Keep documentation synchronized with code, configuration, interfaces, processes, deployment, and decision changes. Record important constraints, pitfalls, and non-obvious decisions. |
| 35 | 6. Never write secrets, tokens, passwords, sensitive personal information, or real values that could bypass security controls. Stop writing and report suspected sensitive information. |
| 36 | 7. Merge non-destructively when `AGENTS.md`, `docs/`, or existing documents are present: preserve facts and history instead of overwriting or deleting them. Report conflicts and propose a single source of truth. |
| 37 | 8. By default, modify only documents, indexes, templates, metadata, and documentation comments. Read code and Git diffs only to determine documentation impact; do not modify business code. |
Scanned on Sep 14, 2026
View Security Dashboard