Build and maintain ZERO-COST, Hermes-automated online income systems — multiple independent "streams" (affiliate blog, Gumroad products, tools hub, Fiverr guides), each with a generator + self-running cron, hosted free on GitHub Pages. Use when the user wants to "make money online for free", "passive/automated income", or have "Hermes do everything". Encodes the proven architecture, the affiliate-token pattern, and the gotchas (Pages /docs, clean-on-build, f-string braces, MSYS paths, ad-hoc verification) that broke a real build.
Build and operate a zero-cost, fully-automated multi-stream money system (affiliate + digital products + POD + traffic + support) maintained by Hermes Agent crons. Use when the user wants to make money online for free with automation, or to extend/verify the money-engine project.
Configure, extend, or contribute to Hermes Agent.
Stand up a local autonomous "agent company" — Paperclip (the orchestrator) + Hermes Agent employees (via the hermes_local adapter) — on Windows via the Hermes terminal. Covers the verified pnpm/tsx build, the embedded-Postgres-vs-admin trap, and how the Hermes adapter is already bundled in Paperclip main (so you do NOT hand-wire it). Use when the user wants to "run a Paperclip company", "hire a Hermes agent in Paperclip", "build the agent-company stack", or references paperclipai/paperclip + NousResearch/hermes-paperclip-adapter.
Drive Autodesk Fusion 360 via its MCP server to programmatically build, simulate, and export parametric CAD / robot models. Also covers STATIC code+math engineering verification of a payload WITHOUT running Fusion (no MCP needed) — servo torque margins, mass/COM/stability, structural safety factors, 3D-printability, power budget. Use when a project sends Python payloads to Fusion 360 over MCP (e.g. a run_simulation.py controller + versioned optimus_*.py / model_*.py payloads), when asked to "run the vN simulation", to "analyze which version is best", or to "review/verify the engineering" of a CAD script.
Deploy, build, verify, and operate a Next.js site on Cloudflare Workers via the OpenNext adapter (@opennextjs/cloudflare), and set up the Cloudflare MCP server. Covers the build pipeline, multi-worker split configs, auth (wrangler login OAuth token OR CLOUDFLARE_API_TOKEN), headless-deploy pitfalls (stdin is not a tty, IPv6 DNS), the diff-based resumable asset upload, the Cloudflare MCP server (run <accountId> + OAuth token reuse), and how to verify a project is "completely working". Use when deploying/building/verifying for Cloudflare, wiring up the Cloudflare MCP, or hitting Cloudflare auth/deploy errors.
Pitfalls, examples, and edge cases for Hermes Kanban workers. The lifecycle itself is auto-injected into every worker's system prompt as KANBAN_GUIDANCE (from agent/prompt_builder.py); this skill is what you load when you want deeper detail on specific scenarios.
Install, configure, and run OpenClaw (openclaw/openclaw) — a self-hosted multi-channel AI assistant gateway — on a Windows dev box, wired to a FREE OpenRouter model (tencent/hy3:free). Covers the exact config schema (env.OPENROUTER_API_KEY + agents.defaults.model.primary), the reasoning-model token gotcha, where the existing OpenRouter key lives, and the low-RAM boot-failure debugging path (wmic vs /proc, timeout-bounded commands). Use when the user says "install openclaw", "set up the openclaw agent", "run openclaw with my openrouter key", or references openclaw.ai.