Setup guide
From download to first audit.
Five steps. Most people finish the first run in one sitting. Paths and commands below match the planned release and are confirmed against the shipped archive before launch.
1. Download and unpack
After checkout you receive a download link for the kit archive. Unpack it anywhere. Inside you will find the skill folder, the scripts folder, the setup guide, the sample report, and the license.
crawlkind-kit-1.0.0/ ├── skill/crawlkind/ # the Claude Code skill: SKILL.md, scripts/, references/ ├── sample-audit/ # fictional site, its report, the editorial review ├── tests/smoke.sh ├── README.md ├── SETUP.md ├── KNOWN-LIMITATIONS.md └── LICENSE.md
2. Install the skill
Copy the skill folder into your Claude Code skills directory. To make it available in every project on this machine:
cp -r crawlkind-kit-1.0.0/skill/crawlkind ~/.claude/skills/crawlkind
To keep it with one project only, copy it into that project's .claude/skills/ folder instead. Both locations are read by Claude Code at startup; restart Claude Code after copying.
3. Open your project
Start Claude Code in the folder that holds your website files. For a plain HTML site that is the folder with index.html at the top. Check that /crawlkind appears in the command list.
4. Run the first audit
Run the command and give it the public URL of the site. The skill reads the project files, runs the checking scripts, fetches the public pages it is allowed to, and writes a report.
> /crawlkind audit https://your-site.example CrawlKind 1.0.0 · local files + public URL fetch · 13 pages ! 2 blockers △ 5 improvements ✓ 8 passed ○ 7 not checked Report written to crawlkind/report.md and report.json
The first run is audit-only. Nothing in your project changes until you ask for it in the next step. The skill then adds an editorial review of your key pages' first screens, using only facts already on your site.
5. Review, apply, verify
Open crawlkind/report.md. Pick the findings you want to act on and run /crawlkind fix ACCESS-02 for one check ID at a time; the skill shows the diff and waits for a yes before writing anything. Publish the change yourself, then rerun the checks:
> /crawlkind verify ACCESS-02 ✓ ACCESS-02 passed method: public URL fetch
If the public site has not been redeployed yet, the verification line says method: local files instead. It never reports a local change as live. The script also runs on its own from any terminal; the setup guide in the kit has the commands.
If something breaks
Check the requirements page first, then the support page for how to get in touch. Include the report file, your project type, and the command you ran.