clawlite-doc-sync
v1.0.0中文：发布后文档同步技能，自动对齐 README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md 与实际变更，清理 TODO，优化 Changelog 语气，并可同步完成版本更新，提升交付一致性。 日本語：リリース後のドキュメントを同期するスキル。README/ARCHITECTURE/C...
⭐ 0· 61·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 match the instructions: the SKILL.md only asks to inspect diffs, read and edit Markdown docs, tidy TODOs, optimize changelog phrasing, and optionally update VERSION. It does not request unrelated credentials, binaries, or external services.
Instruction Scope
Runtime instructions explicitly limit automated edits to factual changes, require AskUserQuestion for subjective/risky edits (version bump, large rewrites, security/philosophy changes), and prescribe specific git/find/diff commands. The skill reads many repo files (README, CHANGELOG, VERSION, TODOS, package.json, etc.) which is appropriate for a doc-sync workflow but means it will access and modify repository content.
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is written to disk by an installer. Lowest-risk install profile.
Credentials
No environment variables, credentials, or external config paths are requested. All file and git access is local to the repository and proportionate to the described task.
Persistence & Privilege
always:false and normal model invocation are used. The skill instructs creating git commits limited to doc files and explicitly forbids broad staging (no git add -A). It does not request persistent system-wide privileges or alter other skills.
Assessment
This skill appears coherent and focused: it will read repository files, run git diff/status commands, make fact-based edits to Markdown files, and create a single commit of doc changes. Before installing or enabling autonomous invocation, consider: (1) grant it write/commit permission only on repositories you trust; (2) ensure the agent runs on the intended feature branch (instructions abort on base branch); (3) expect the skill to open AskUserQuestion prompts for subjective/risky changes — review and approve those answers; (4) review any automatic edits in CI or a staging branch before merging to avoid unexpected doc commits. No credentials are requested, but treat repository write access as sensitive.Like a lobster shell, security has layers — review code before you run it.
latestvk9717t86q0pzk5h55ftj3789cd83tpm9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.