skills/startup/SKILL.md
Post-boot health check — verify all services are running and auto-start anything that isn't. Mirror of the shutdown skill.
npx skillsauth add asets-gobizit/claude-skills startupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Verify every service on Danny's PC is running after boot (or after a crash). Auto-starts anything that isn't responding. Prints a color-coded dashboard.
/startup/shutdown and restartingsystemctl --user start nanoclaw)-SkipOpenClaw)PKAviewer.html) + cloudflared tunnel pka-viewer (routes pka.gobizit.ai and gmnr.gobizit.ai) + Python Flask backend on port 8789 (infra/api.py, kanban writes endpoint behind Caddy /api/* proxy). All three auto-start via VBS launchers in the Windows Startup folder (pka-caddy.vbs, pka-cloudflared.vbs, pka-api.vbs)./startup
Or directly:
powershell -File "C:\Users\dansk\.claude\skills\startup\startup.ps1"
powershell -File "C:\Users\dansk\.claude\skills\startup\startup.ps1" -SkipOpenClaw
Each service shows one of:
[OK] — running, no action needed[FAIL] — could not start, needs manual investigation[WARN] — started but uncertain, check manually[WAIT] — started but still booting (n8n is slow)[SKIP] — skipped by user flagWhen ANY new service is added to the shutdown skill, it MUST also be added here in the matching position.
/shutdown — the reverse: safely stop all services before PC shutdown/hermes-restart — Hermes-specific diagnostics and restart/n8n-doctor — n8n-specific health checksdata-ai
Automated backup skill for PKA + Obsidian + Claude memory. Snapshots pka.db (via SQLite .backup so WAL is handled safely), the Obsidian vault, Claude memory files, agent profiles, and the help-content Excel into a single timestamped zip in Zoho WorkDrive. Daily/weekly/monthly retention rotation built in. USE WHEN Danny says "backup", "run backup", "snapshot pka", or to recover from a snapshot.
testing
Run any question, idea, or decision through a council of 5 AI advisors who independently analyze it, peer-review each other anonymously, and synthesize a final verdict. Based on Karpathy's LLM Council methodology, packaged as the stress-test skill. MANDATORY TRIGGERS: 'stress-test this', 'stress test this', 'pressure-test this', 'pressure test this', 'war room this', 'council this', 'run the council', 'debate this'. STRONG TRIGGERS (use when combined with a real decision or tradeoff): 'should I X or Y', 'which option', 'what would you do', 'is this the right move', 'validate this', 'get multiple perspectives', 'I can't decide', 'I'm torn between'. Do NOT trigger on simple yes/no questions, factual lookups, or casual 'should I' without a meaningful tradeoff (e.g. 'should I use markdown' is not a stress-test question). DO trigger when the user presents a genuine decision with stakes, multiple options, and context that suggests they want it pressure-tested from multiple angles.
content-media
Weekly scan of Obsidian vault for empty/low-content notes. Moves them to zToBeDeleted/ for user review. Use when the user says "tidy obsidian", "clean obsidian", "obsidian cleanup", or on scheduled weekly run.
development
Design-first website builder. Accepts a Claude Design export (HTML or screenshot) as a visual blueprint, collects business inputs, calls Claude API to generate a design-matched index.html, and publishes to GitHub Pages. Falls back to vibe-based generation if no design is provided. Use when the user says "make-website-design", "design website", "build from design", or provides a Claude Design export for website generation.