Doc Gap Finder

v1.0.0

扫描文档目录、标题结构与文件分布,找缺失章节、重复内容和过时区域。;use for docs, audit, knowledge workflows;do not use for 读取无权限目录, 直接修改原文档.

0· 146·0 current·0 all-time
byvx:17605205782@52yuanchangxing
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (document gap finder) align with the provided files and the included scripts: the repo contains a template, spec.json, examples and a Python script that performs directory/csv/pattern/skill audits. Requiring only python3 is proportionate.
Instruction Scope
SKILL.md correctly instructs running the local script and also supports producing output from the bundled template when execution isn't possible. The script legitimately reads files under a supplied input directory and extracts headings and file lists. Caution: if given an arbitrary root path (e.g., /), the script will read many file types (.md, .py, .sh, .json, etc.) — which is expected for a directory audit but could expose sensitive files if the user supplies paths they don't own. The SKILL.md warns about not scanning unauthorized directories; that warning should be followed.
Install Mechanism
No install spec; this is instruction/script-based and only requires python3 on PATH. No network downloads or external package installs are present.
Credentials
The skill requests no environment variables or credentials. The script includes heuristics to detect secret-like patterns and redacts matched secret substrings in its findings (limiting accidental disclosure in output). There is no unexplained access to unrelated services.
Persistence & Privilege
Skill is not always-enabled and does not request persistent privileges or modify other skills/system configs. It is user-invocable and runs locally when invoked.
Assessment
This appears to be a coherent local, read-only documentation-audit skill. Before running: (1) run it against a limited test directory or use --dry-run to verify output, (2) avoid pointing it at system or production roots (e.g., /, home of other users, or repos containing secrets), (3) review outputs before sharing (the tool redacts obvious secret-like strings but you should still verify), and (4) prefer running in a least-privileged environment (separate container or workspace) when scanning unknown repositories.

Like a lobster shell, security has layers — review code before you run it.

latestvk9749m64bmersdb58753e8acv9831tfd

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

📚 Clawdis
OSmacOS · Linux · Windows
Binspython3

Comments