Hermes-Full-Autonomous-Company

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.

Run Paperclip (paperclipai/paperclip) with the Hermes Agent adapter on a Windows dev machine NATIVELY (no Docker) — install the pnpm monorepo, build, create the Postgres DB, and start the server via tsx. Documents the Windows/MSYS/pnpm pitfalls that otherwise silently stall the install or crash startup with confusing errors.

Deploy, configure, and operate a Next.js (or any) site on Vercel from the Hermes agent terminal — zero-cost, no-backend strategy. Covers the Hermes-vs-OpenCode MCP distinction, project linking, env-var setup, deploy verification, Vercel Web Analytics via CLI, and keyless production-build verification. Use when a user asks to push/deploy to Vercel, set Vercel env vars, check deploy status, or read site analytics — especially when they hand you an "OpenCode / Vercel MCP" setup guide.

Deploy, verify, and performance-tune Vercel-hosted Next.js (App Router) apps. Covers fixing build errors (ssr:false-in-Server-Component, revalidate-in-client-component), confirming ISR/code-splitting live, pulling Vercel analytics/speed data when the MCP OAuth can't be driven, and verifying changes with typecheck + live curl probes. Use whenever you edit a Vercel-deployed Next.js project and must prove the change works in production.

Windows Git Credential Manager (GCM) operations: fix the 'Select an account' x-access-token modal, store/erase github.com identities, and recover from GitHub secret-scanning push rejections. Use when git push/fetch pops an account picker, or a push is blocked for containing a secret.

Grow an open-source repository's reach — GitHub stars, contributor funnel, and launch momentum. Use when the user wants an OSS repo to get more reach, go viral, get stars, attract contributors, or ship a launch on Product Hunt, Hacker News, Reddit, or X. Covers landing-page trust upgrades (real autoplaying demo, clean architecture diagram), opening contributor-friendly issues, and a spaced multi-platform launch sequence.

Deep end-to-end analysis of any GitHub repository: API metadata, file structure, tech stack, architecture, dependency security audit, mock-vs-real feature detection, and repo-health signals. Use for 'analyze / review / audit this repo' requests.

Autonomous job-hunting pipeline for a software/AI fresher: audit + fix GitHub repos (CI, descriptions, flagship pinning), improve a LaTeX resume, search real remote jobs (India/global) via Jina+DDG when Exa is down, and run a SUPERVISED apply flow. Encodes the hard limits (no banned auto-apply bots, login wall is the user's, the browser_navigate session is invisible to the user) so the agent sets expectations correctly instead of looping on a dead end.

End-to-end job-hunting pipeline for a fresher/switcher targeting high-salary remote roles — GitHub readiness, resume, FREE-board search, supervised apply, and portfolio-project building. Use whenever the user wants to find/get a job, apply to roles, build a portfolio project to improve offers, or asks about auto-apply/browser-takeover for jobs.

Research, verify, and document open-source project stacks as structured, evidenced blueprints. Use when the user wants to find free/self-hostable tools for a domain, build an "AI company stack", compare OSS alternatives, or produce a department→tool map. Emphasizes LIVE verification (GitHub API) and honest caveats — never fabricate star counts.

Build a verified open-source tool/agent stack for a given function or company blueprint. Use when a user asks "find all free projects for X", "what open-source tools do I need for Y", "search for the best project for Z", or wants a department-by-department tool map. Emphasizes LIVE GitHub verification, honest canonical-vs-verified marking, and the rate-limit workaround.

Route ALL internet search / research / lookup tasks through Agent Reach (agent-reach CLI) — the capability layer that installs, health-checks, and routes 15 platforms (Twitter, Reddit, YouTube, Bilibili, Xiaohongshu, GitHub, Exa full-web search, V2EX, LinkedIn, Xueqiu, Xiaoyuzhou, Facebook, Instagram, RSS, any web page). Use whenever the user asks to research / look up / search anything online, shares any platform URL, or wants web intelligence gathered. This is the DEFAULT research path for this user (explicit instruction: "use agent-reach for all search/research").

Research and assemble a fully open-source, AI-agent-operated company stack. Use when the user wants to build an autonomous or one-person AI company, map business departments to free self-hostable tools, compare agent frameworks (CrewAI, OpenHands, MetaGPT, AutoGen, LangGraph, OpenClaw), or produce a department-to-tool blueprint folder. Triggers include "AI company", "autonomous company", "agent-operated business", "open-source stack for a department", "which tool for this team", "map every department to a project".

Build, automate, and verify zero-cost affiliate/content web properties driven by Hermes Agent. Use when a user wants to "make money online free", run a hands-off content/affiliate site, or have Hermes autonomously research+write+publish on a schedule. Covers the full stack — stdlib-only static generator, affiliate-token templating, free GitHub Pages hosting, and a self-running weekly article cron.

Design, build, and maintain zero-cost, Hermes-agent-automated online income systems (affiliate blogs, Gumroad product factories, free tool hubs) that run hands-off via cron. Use when the user wants to "make money online for free / with zero investment / fully automated" and has only a laptop + internet + Hermes.

Operate the Hermes-Full-Autonomous-Company — a $0-budget AI company running on Paperclip (7-agent org) + Hermes Agent (executive) + OpenClaw (comms/computer-use) + hermes-paperclip-adapter, with GitHub as the single source of truth. Covers server launch, the 24/7 cron autonomy loop, Constitution-as-OS v3.0, the product research→build→test→push cycle, revenue-channel research, and the human-in-the-loop gates. Use when the user says "continue the company," "build/push a product," "start earning," "run 24/7," or anything about operating this autonomous company.

Build, verify, publish, and market high-quality agent-native products for ClawHub (skills) + Moltbook (agent social) with a professional CI/CD + verification workflow. Use when the user asks for "useful products", "ClawHub skills", "market on Moltbook", "CI/CD for my products", or any autonomous-product build for the Hermes/OpenClaw ecosystem.

Add REAL, asserting `self-test` subcommands to a portfolio of existing Python CLI tools and make a product/portfolio verification harness pass — without changing existing tool behavior. Use when a user says "add a self-test to N tools", "make the portfolio harness pass", "each tool needs a self-test subcommand", or when a verify_product/verify_portfolio script reports "self-test: none found" across many folders. Covers argparse vs manual argv parsing, the 7-axis harness contract, and the non-obvious traps that make self-tests silently FAIL.

Triage and eliminate npm dependency vulnerabilities: trace transitive CVEs to the one direct dep, remove dead deps, re-audit to 0, and lock the win with a CI audit gate. Includes Windows/MSYS edit-tool path pitfalls.

Recover when the `patch` tool silently fails or reports success without applying — especially on regex literals, backslashes, escaped characters, or generated code. Use a deterministic node `.cjs` script run via `terminal` instead of fuzzy replace. Also covers the isolate-verify-merge workflow for risky/credential-gated features.

Audit a developer's GitHub profile + flagship repos for job-hunting readiness and fix the code/README/CI parts autonomously. Use when a user wants to improve their GitHub to land a high-paying IT job, fix failing CI, or rewrite their profile README. Triggers on "improve my GitHub for jobs", "fix my CI", "make my profile job-ready".

Build and ship a production-grade TypeScript/Node project (CLI, agent, MCP server, RAG, SQLite) with green CI, tests, lint, and end-to-end verification. Covers scaffolding, the quality gate, keeping heavy/native deps from breaking CI, and confirming remote CI is green after push.

Verify an MCP (Model Context Protocol) server actually works over stdio — not just that it starts, but that it speaks JSON-RPC, lists tools/resources/prompts, and executes tool calls returning real data. Use when auditing, debugging, or proving an MCP server's connectivity ("check if the MCP connection works", "client connected but tools fail").

Verify an MCP (Model Context Protocol) server actually works over stdio — not just by reading code. Use when a user asks "does the MCP work", "check the MCP connection", or "audit the MCP server for errors". Covers the JSON-RPC handshake, tools/list, live tools/call, and the common safe-mode trap that makes write tools fail.

Scaffold and ship a production-grade Node.js CLI tool — ESM package, interactive prompts, config generation, npm distribution, free/pro tier structure. Covers bin entry setup, inquirer-based interactive flows, JSDoc-typed config builders, save-to-file output, and premium upgrade navigation.

Full improvement pass on a codebase — dependency vulnerability remediation (npm audit root-cause), dead-code removal, repo binary hygiene on Windows, fast integration tests, and README placeholder cleanup. Trigger when the user asks to "complete", "improve", "harden", "finish", or "clean up" a project, or wants a code review turned into concrete fixes.

Verify and debug code that cannot be fully executed in the current environment (external runtime, missing hardware, cloud/service dependencies, GUI apps). Use AST parsing, targeted ad-hoc scripts, and log-output pattern analysis instead of a full run. Trigger when the user asks to "test", "verify", "check everything", "make sure it works", or when a project depends on Fusion 360 / a browser / a live server / cloud creds that aren't available here.

Audit and verify an unfamiliar or untested codebase when there is NO canonical test/lint/build command. Covers version triage (which file/version is canonical), stale-doc detection, ad-hoc verification via disposable temp scripts, a three-axis verification framework (visual/logical/physical), and long-running background-sim monitoring. Use when asked to "analyze/test/verify/improve this project", "check everything", "which version is best", or when a repo lacks a test suite and you must still produce real evidence.

Verify a codebase that has NO test/lint/build/CI command — syntax, logic, visual, and domain correctness — using disposable temp-script checks. Use when a repo lacks a canonical verification path, when the harness flags "stale verification", or when asked to "test everything" / "verify the project" / "check it works".

Define, validate, and audit agent capability manifests for safe skill installation

Track LLM API spending per agent/session with budget alerts and CSV export

Enforce safety guardrails on agent actions: permission gates, allowlists, audit

Monitor agent endpoints, check liveness, collect metrics, alert on failures