What problem does it solve? After changing the newsletter crawler, you need a reliable way to prove the change works without burning LLM tokens or risking the user's real archive. This Skill provides the exact command sequence to smoke-test, run bounded crawls, verify cache behavior, export results, and validate the deploy pipeline. ## Core Features & Use Cases - Smoke and unit testing: npm run status boots the SQLite schema and imports every module; npm test runs 868+ tests with strict NC_HOME isolation so the user's real database is never touched. - Bounded crawl verification: npm run crawl -- --max-pages 1 --max-articles 3 exercises fetch, LLM, and extraction cheaply, and re-running proves the selector cache hit and resumability. - Export, deploy, and recovery: covers markdown/web export with secret redaction, the one-command npm run deploy flow with live-site polling, and restoring the archive from git history via ncrawl restore. - Use Case: You fixed a date-parsing bug and want to confirm it end to end — run the unit tests, a bounded crawl, inspect status counts, and export, all without touching production data. ## Quick Start Ask the assistant to run a bounded test crawl with npm run crawl using --max-pages 1 and --max-articles 3, then check the results with npm run status.