Nm Sanctum Doc Updates
PassAudited by VirusTotal on May 9, 2026.
Overview
Type: OpenClaw Skill Name: nm-sanctum-doc-updates Version: 1.0.2 The nm-sanctum-doc-updates skill bundle is a comprehensive documentation maintenance tool designed for an AI agent. It facilitates a multi-step workflow for updating READMEs, ADRs, and docstrings, incorporating quality gates such as style enforcement, AI 'slop' detection, and accuracy verification against the codebase. The bundle utilizes standard Unix utilities (grep, jq, find, comm) and git commands to audit plugin versions and file counts, and it includes logic for consolidating redundant documentation (e.g., in modules/consolidation-integration.md). All high-risk actions, such as file deletions or modifications, are strictly aligned with the stated purpose of documentation management and include requirements for user approval or previewing changes.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If approved incorrectly, useful documentation files could be removed or staged for commit.
The workflow includes direct repository-mutating shell steps for deleting and staging documentation files. This is aligned with the consolidation purpose, but users should review the proposed file list before allowing these commands.
Remove file: `rm <file>` 4. Add deletion to git staging: `git add -u`
Use the documented dry-run or selective processing options, review the candidate list, and check `git diff`/`git status` before committing.
If a local script with that name exists, the agent may be asked to run code not included in this reviewed artifact set.
The module references a runnable helper script path, but the provided package manifest contains only Markdown files and no such script. This is a completeness/provenance note rather than a demonstrated unsafe behavior.
bash plugins/sanctum/skills/doc-updates/modules/capabilities-sync-check.sh
Before running the referenced helper, confirm that the file exists in the intended repository and inspect its contents; otherwise use the inline commands or documented parser workflow instead.