Openclaw Doc Sync
v1.0.1Post-release documentation sync skill that automatically aligns README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md with actual changes, cleans up TODOs, polishes Cha...
⭐ 0· 49·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description claim to sync documentation after code changes and the SKILL.md contains step-by-step git + file audit/edit/commit instructions that match that purpose. It does not request unrelated binaries, environment variables, or external services.
Instruction Scope
Instructions explicitly run git commands, scan the working tree, read and edit .md files, and create a commit. These actions are expected for a doc-sync skill but constitute write operations on the repository; the document contains many safety checks (AskUserQuestion for risky/subjective changes and rules about CHANGELOG and VERSION) which reduces risk.
Install Mechanism
Instruction-only skill with no install spec and no code files; nothing is downloaded or installed to disk by the skill itself.
Credentials
No environment variables, credentials, or config paths are requested. The skill uses local git and filesystem access only, which is proportionate to its stated function.
Persistence & Privilege
always:false and no installs are set. However, the skill instructs the agent to perform repository modifications and create commits. If the agent is allowed to invoke the skill autonomously, it could make repo-local changes without further human review; the SKILL.md does not instruct an automatic push, but commits still alter the working tree and history.
Assessment
This skill appears to do exactly what it says: analyze diffs, update Markdown docs, and create a commit with the changes. Before installing or enabling autonomous invocation, consider: (1) run it first in a fork/feature branch to verify edits, (2) ensure the agent's permissions are limited (it doesn't need push rights to be useful), (3) confirm you want automated commits created by an agent, and (4) verify AskUserQuestion behavior so subjective or security-related changes require explicit human approval. There are no declared external credentials or downloads, but repository-write behavior is the primary operational risk — review and test in a safe environment.Like a lobster shell, security has layers — review code before you run it.
latestvk9761nj0352q5td2gb9fzeqtx983ye9e
License
MIT-0
Free to use, modify, and redistribute. No attribution required.