Verify Docs
Validate JSON, file paths, and settings keys across all docs
Install
$ agentstack add skill-paulo-yamagishi-claude-code-setup-verify-docs ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ● Filesystem access Used
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-paulo-yamagishi-claude-code-setup-verify-docs) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Verify Docs
Validate all documentation files in the repo for correctness.
Steps
- Collect files: Glob all
.mdfiles in these directories:
core/projects/templates/skill/.claude/skills/.claude/rules/
- Validate JSON code blocks: For each file, extract all
jsonfenced code blocks and validate each one:
- Use
Bash(node -e 'JSON.parse(require("fs").readFileSync("/dev/stdin","utf8"))' < tmpfile)or inline the JSON string - Flag: trailing commas, comments (
//or/* */), single quotes, unquoted keys - Record file path and line number of each invalid block
- Validate file paths: Extract all relative file paths referenced in the docs (patterns like
core/,.claude/,projects/,templates/,skill/):
- Grep for path-like references
- Verify each referenced file or directory actually exists using Glob
- Flag broken references with file and line number
- Validate settings keys: Extract settings keys used in JSON examples (e.g.,
permissions,allow,deny,hooks,mcpServers):
- Cross-check against
skill/SKILL.mdSection 4 (Config Reference) as the source of truth - Flag any key not present in the reference
- Validate hook events: Extract hook event names (e.g.,
PreToolUse,PostToolUse,Stop,SubagentStop):
- Cross-check against known valid events in
core/hooks-guide.md - Flag unrecognized events
- Report: Group all issues by file. For each issue, show:
- File path and line number
- Issue type:
INVALID_JSON,BROKEN_PATH,UNKNOWN_KEY,UNKNOWN_EVENT - Description of the problem
- If no issues found, report: "All docs passed verification."
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: paulo-yamagishi
- Source: paulo-yamagishi/claude-code-setup
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.