[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B0DJD3TS79Y2FQGT8YZHM5":3,"skill-same:01M7B0DJD3TS79Y2FQGT8YZHM5":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M7B0DJD3TS79Y2FQGT8YZHM5","daemon-mcp-server-setup",null,"Wire a local daemon-backed stdio MCP server into an agent.","dbillion\u002Fhermes-skills-public","dbillion","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F49393855?v=4","01M7AVH8QPGCM8WKWS22TRT0T6","Oludayo Adeoye","01M7AVH8RD1JJWA0YS9CFEWAV9",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Fmcp\u002Fdaemon-mcp-server-setup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: daemon-mcp-server-setup\ndescription: \"Wire a local daemon-backed stdio MCP server into an agent.\"\nversion: 1.0.0\nauthor: Hermes Agent\nlicense: MIT\nplatforms: [linux, macos]\nmetadata:\n  hermes:\n    tags: [mcp, open-design, od, daemon, node, native-modules, setup]\n---\n\n# Daemon-backed MCP Server Setup\n\n## When to Use\n- The user wants to `mcp install` \u002F wire a local MCP server that proxies to a running\n  local daemon (Open Design \u002F `od`, or any Node-based local service with an MCP entry).\n- You have a pasted MCP config block and must register it in `~\u002F.hermes\u002Fconfig.yaml`\n  without clobbering existing servers or using the wrong launcher binary.\n\nUse when the user wants to install\u002Fwire an MCP server that is a **stdio proxy to a\nlocal daemon** (Open Design \u002F `od` is the canonical case, but the pattern fits any\nNode-based local service that exposes an MCP entrypoint). The server process talks\nto a separate long-running daemon over HTTP; if the daemon isn't up, the MCP tools\nwill register but return nothing.\n\n## Workflow\n\n1. **Inventory existing config before editing.**\n   Grep `~\u002F.hermes\u002Fconfig.yaml` for `^mcp_servers:` and list current servers. You\n   must *append*, never clobber. (Hermes already had zapier_youtube, lightpanda,\n   substack-api, nova3d, mcp-cli in this user's setup.)\n2. **Resolve the real launcher binary — do NOT trust the name in a pasted config.**\n   A pasted `command: \"od\"` is almost certainly wrong: `\u002Fusr\u002Fbin\u002Fod` is GNU\n   coreutils' *octal dump*, not Open Design. Find the real CLI:\n   `command -v opendesign`, `which \u003Calias>`, or trace the symlink with `ls -la`.\n   Prefer the alias the user already set up over re-inventing the entrypoint.\n3. **Start the daemon first** (needed for an exact install spec and for the tools\n   to actually work). Run it in the background (`terminal(background=true)`), then\n   **verify it bound the port** — see Verification below. Do not declare success\n   until `curl \u002Fapi\u002Fhealth` returns 200.\n4. **Prefer the server's own built-in installer** when one exists. For Open Design:\n   `opendesign mcp install hermes --dry-run --json` resolves the byte-exact launch\n   command from the running daemon's `\u002Fapi\u002Fmcp\u002Finstall-info` endpoint. That endpoint\n   returns `{command, args, env, daemonUrl, ...}` — use those exact values in config\n   rather than guessing. (Falls back to a minimal `od mcp --daemon-url \u003Curl>` if the\n   daemon is down, but a running daemon gives the precise match.)\n5. **Register in config via surgical Python insertion** (never `patch`\u002F`write_file`\n   on `~\u002F.hermes\u002Fconfig.yaml` — both are blocked as security-sensitive). Insert the\n   block as raw YAML text before the next top-level key; `yaml.safe_dump` would strip\n   comments\u002Freorder keys. After insertion, `python3 -c \"import yaml; yaml.safe_load(open(path))\"`\n   to validate. (The insertion pattern + why `yaml.safe_dump` is forbidden is detailed\n   in the native-mcp skill's `references\u002Fverify-and-edit-mcp.md`.)\n6. **Verify the MCP server with a real stdio JSON-RPC handshake** (initialize +\n   tools\u002Flist) before claiming installed — see native-mcp skill.\n\n## Critical Pitfalls\n\n### P1 — `write_file`\u002F`patch` FOLLOW symlinks to the real target\nIf the launcher path is a symlink (e.g. `opendesign -> node_modules\u002F.bin\u002Fod ->\napps\u002Fdaemon\u002Fbin\u002Fod.mjs`), writing to it **overwrites the underlying file**, not the\nsymlink. In this session that corrupted OD's actual entrypoint (`od.mjs`) and made\n`opendesign` hang.\n**Fix:** always `ls -la` the target first. If it's a symlink, move it to trash\n(`mv` to `~\u002F.trash\u002F...`, never hard `rm -rf`), then write a *real file* (e.g. a\nNode-24-pinned bash wrapper) at that path. Restore any corrupted target via\n`git checkout` or its known-good content.\n\n### P2 — Node native-module ABI mismatch (ERR_DLOPEN_FAILED)\nA Node app with native deps (e.g. `better-sqlite3`) compiled for one Node ABI will\ncrash on another: `was compiled against a different Node.js version using\nNODE_MODULE_VERSION 137. This version of Node.js requires NODE_MODULE_VERSION 141.`\nThis happens when the active `node` on PATH differs from the Node the module was\nbuilt for (the user has v20\u002Fv24\u002Fv25 installed via nvm; the repo targets ~24).\n**Fix (pick one):**\n- Pin the launcher to the Node the module was built for: a wrapper that does\n  `export PATH=\"\u002Fpath\u002Fto\u002Fnode\u002Fv24.x\u002Fbin:$PATH\"; exec node \u003Centry> \"$@\"`.\n- Or rebuild the module for the active Node: `cd \u003Crepo> && export PATH=\u003CnodeX>\u002Fbin:$PATH\n  && pnpm rebuild better-sqlite3` (verify with `node -e \"require('better-sqlite3')\"`).\nNever run `pnpm rebuild` under a Node version other than the one that will actually\nrun the app — it recompiles the module for *that* Node and can make things worse.\n\n### P3 — Silent daemon != dead daemon\nWhen stdout is piped\u002Fredirected, Node **buffers** output, so a daemon that prints\nnothing can still be healthy and listening. Also, the daemon may take 30–60s to bind\nafter launch; an early `ss | grep \u003Cport>` can race and falsely report \"nothing\".\n**Fix:** confirm binding with `ss -tlnp | grep \u003Cpid>` (the daemon's PID owns the\nLISTEN socket) rather than grepping the port string. If you need to know what it's\ndoing: `cat \u002Fproc\u002F\u003Cpid>\u002Ftask\u002F*\u002Fwchan` (main thread in `do_epoll_wait` = idle\u002Fhealthy);\n`strace` is often absent on minimal systems, so use `\u002Fproc\u002F\u003Cpid>\u002Fnet\u002Ftcp` to confirm\na LISTEN socket exists. For a JS-level hang, `kill -USR1 \u003Cpid>` opens the inspector\non :9229 (`curl http:\u002F\u002F127.0.0.1:9229\u002Fjson`).\n\n## Notes\n- The MCP server config must use the entrypoint the daemon reports, e.g.\n  `command: \u002Fpath\u002Fto\u002Fnode\u002Fv24\u002Fbin\u002Fnode`, `args: [dist\u002Fcli.js, mcp, --daemon-url,\n  http:\u002F\u002F127.0.0.1:7456]` — NOT `od` (coreutils) and NOT a bare `npx` guess.\n- After registering, MCP tools only work while the daemon is running. The OD MCP\n  server re-discovers the daemon URL at each spawn, so restarts are tolerated.\n\n## References\n- `references\u002Fopen-design-example.md` — full worked example: exact paths, ports,\n  the launch spec the daemon reports, the Node-24-pinned launcher, and the gotchas\n  (symlink corruption, ABI mismatch, silent-but-healthy daemon) from a real install.\n","# Daemon-backed MCP Server Setup\n\n## When to Use\n- The user wants to `mcp install` \u002F wire a local MCP server that proxies to a running\n  local daemon (Open Design \u002F `od`, or any Node-based local service with an MCP entry).\n- You have a pasted MCP config block and must register it in `~\u002F.hermes\u002Fconfig.yaml`\n  without clobbering existing servers or using the wrong launcher binary.\n\nUse when the user wants to install\u002Fwire an MCP server that is a **stdio proxy to a\nlocal daemon** (Open Design \u002F `od` is the canonical case, but the pattern fits any\nNode-based local service that exposes an MCP entrypoint). The server process talks\nto a separate long-running daemon over HTTP; if the daemon isn't up, the MCP tools\nwill register but return nothing.\n\n## Workflow\n\n1. **Inventory existing config before editing.**\n   Grep `~\u002F.hermes\u002Fconfig.yaml` for `^mcp_servers:` and list current servers. You\n   must *append*, never clobber. (Hermes already had zapier_youtube, lightpanda,\n   substack-api, nova3d, mcp-cli in this user's setup.)\n2. **Resolve the real launcher binary — do NOT trust the name in a pasted config.**\n   A pasted `command: \"od\"` is almost certainly wrong: `\u002Fusr\u002Fbin\u002Fod` is GNU\n   coreutils' *octal dump*, not Open Design. Find the real CLI:\n   `command -v opendesign`, `which \u003Calias>`, or trace the symlink with `ls -la`.\n   Prefer the alias the user already set up over re-inventing the entrypoint.\n3. **Start the daemon first** (needed for an exact install spec and for the tools\n   to actually work). Run it in the background (`terminal(background=true)`), then\n   **verify it bound the port** — see Verification below. Do not declare success\n   until `curl \u002Fapi\u002Fhealth` returns 200.\n4. **Prefer the server's own built-in installer** when one exists. For Open Design:\n   `opendesign mcp install hermes --dry-run --json` resolves the byte-exact launch\n   command from the running daemon's `\u002Fapi\u002Fmcp\u002Finstall-info` endpoint. That endpoint\n   returns `{command, args, env, daemonUrl, ...}` — use those exact values in config\n   rather than guessing. (Falls back to a minimal `od mcp --daemon-url \u003Curl>` if the\n   daemon is down, but a running daemon gives the precise match.)\n5. **Register in config via surgical Python insertion** (never `patch`\u002F`write_file`\n   on `~\u002F.hermes\u002Fconfig.yaml` — both are blocked as security-sensitive). Insert the\n   block as raw YAML text before the next top-level key; `yaml.safe_dump` would strip\n   comments\u002Freorder keys. After insertion, `python3 -c \"import yaml; yaml.safe_load(open(path))\"`\n   to validate. (The insertion pattern + why `yaml.safe_dump` is forbidden is detailed\n   in the native-mcp skill's `references\u002Fverify-and-edit-mcp.md`.)\n6. **Verify the MCP server with a real stdio JSON-RPC handshake** (initialize +\n   tools\u002Flist) before claiming installed — see native-mcp skill.\n\n## Critical Pitfalls\n\n### P1 — `write_file`\u002F`patch` FOLLOW symlinks to the real target\nIf the launcher path is a symlink (e.g. `opendesign -> node_modules\u002F.bin\u002Fod ->\napps\u002Fdaemon\u002Fbin\u002Fod.mjs`), writing to it **overwrites the underlying file**, not the\nsymlink. In this session that corrupted OD's actual entrypoint (`od.mjs`) and made\n`opendesign` hang.\n**Fix:** always `ls -la` the target first. If it's a symlink, move it to trash\n(`mv` to `~\u002F.trash\u002F...`, never hard `rm -rf`), then write a *real file* (e.g. a\nNode-24-pinned bash wrapper) at that path. Restore any corrupted target via\n`git checkout` or its known-good content.\n\n### P2 — Node native-module ABI mismatch (ERR_DLOPEN_FAILED)\nA Node app with native deps (e.g. `better-sqlite3`) compiled for one Node ABI will\ncrash on another: `was compiled against a different Node.js version using\nNODE_MODULE_VERSION 137. This version of Node.js requires NODE_MODULE_VERSION 141.`\nThis happens when the active `node` on PATH differs from the Node the module was\nbuilt for (the user has v20\u002Fv24\u002Fv25 installed via nvm; the repo targets ~24).\n**Fix (pick one):**\n- Pin the launcher to the Node the module was built for: a wrapper that does\n  `export PATH=\"\u002Fpath\u002Fto\u002Fnode\u002Fv24.x\u002Fbin:$PATH\"; exec node \u003Centry> \"$@\"`.\n- Or rebuild the module for the active Node: `cd \u003Crepo> && export PATH=\u003CnodeX>\u002Fbin:$PATH\n  && pnpm rebuild better-sqlite3` (verify with `node -e \"require('better-sqlite3')\"`).\nNever run `pnpm rebuild` under a Node version other than the one that will actually\nrun the app — it recompiles the module for *that* Node and can make things worse.\n\n### P3 — Silent daemon != dead daemon\nWhen stdout is piped\u002Fredirected, Node **buffers** output, so a daemon that prints\nnothing can still be healthy and listening. Also, the daemon may take 30–60s to bind\nafter launch; an early `ss | grep \u003Cport>` can race and falsely report \"nothing\".\n**Fix:** confirm binding with `ss -tlnp | grep \u003Cpid>` (the daemon's PID owns the\nLISTEN socket) rather than grepping the port string. If you need to know what it's\ndoing: `cat \u002Fproc\u002F\u003Cpid>\u002Ftask\u002F*\u002Fwchan` (main thread in `do_epoll_wait` = idle\u002Fhealthy);\n`strace` is often absent on minimal systems, so use `\u002Fproc\u002F\u003Cpid>\u002Fnet\u002Ftcp` to confirm\na LISTEN socket exists. For a JS-level hang, `kill -USR1 \u003Cpid>` opens the inspector\non :9229 (`curl http:\u002F\u002F127.0.0.1:9229\u002Fjson`).\n\n## Notes\n- The MCP server config must use the entrypoint the daemon reports, e.g.\n  `command: \u002Fpath\u002Fto\u002Fnode\u002Fv24\u002Fbin\u002Fnode`, `args: [dist\u002Fcli.js, mcp, --daemon-url,\n  http:\u002F\u002F127.0.0.1:7456]` — NOT `od` (coreutils) and NOT a bare `npx` guess.\n- After registering, MCP tools only work while the daemon is running. The OD MCP\n  server re-discovers the daemon URL at each spawn, so restarts are tolerated.\n\n## References\n- `references\u002Fopen-design-example.md` — full worked example: exact paths, ports,\n  the launch spec the daemon reports, the Node-24-pinned launcher, and the gotchas\n  (symlink corruption, ABI mismatch, silent-but-healthy daemon) from a real install.\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":36,"description":7},"Hermes Agent","1.0.0",{"hermes":27},{"tags":28},[29,30,31,32,33,34,35],"mcp","open-design","od","daemon","node","native-modules","setup",[37,38],"linux","macos","master","f341c46fed021656175d5c9ccc67a72126e50bfb","skills\u002Fmcp\u002Fdaemon-mcp-server-setup","https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public","https:\u002F\u002Fgithub.com\u002Fdbillion","I enjoy writing codes,teaching programming, solving problems, tasted automation in Python and never looked back😋😋😋💞","2026-10-14 03:31:55",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add dbillion\u002Fhermes-skills-public --skill daemon-mcp-server-setup",{"tool":52,"command":53},"bunx","bunx skills add dbillion\u002Fhermes-skills-public --skill daemon-mcp-server-setup",{"tool":55,"command":56},"pnpm","pnpm dlx skills add dbillion\u002Fhermes-skills-public --skill daemon-mcp-server-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Fmcp\u002Fdaemon-mcp-server-setup\u002FSKILL.md",true,[60],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fopen-design-example.md","REFERENCE","参考文档",3035,"https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Fmcp\u002Fdaemon-mcp-server-setup\u002Freferences\u002Fopen-design-example.md",[67,74,81,90,97,104],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7B25T0V7RBKES86Y3RTXQRN","blocked-page-recovery","Use when a fetch fails: 403\u002F429, paywall, WAF, bot wall.","https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Fweb\u002Fblocked-page-recovery\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7B25DSBBMZRHVD28MAX7N5X","gemini-vision-fallback","Vision fallback: Gemini REST API if vision_analyze blocked.","https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Fvision\u002Fgemini-vision-fallback\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7B22XW9QXT2ZWWXVZDFWYZP","twitter-cli","Use twitter-cli for ALL Twitter\u002FX operations — reading tweets, posting, replying, quoting, liking, retweeting, following, searching, user lookups. Invoke whenever user requests any Twitter interaction.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Ftwitter-cli\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Ftwitter-cli\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7B22QMWY1B4F7BC114RG4S6","prism-scan","Structural analysis through dynamically generated cognitive lenses. Generates the optimal analytical lens for the specific code\u002Fartifact, then executes it. Finds conservation laws, structural invariants, and concrete bugs that vanilla analysis misses. Use on any code file, system design, or text artifact.","https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Fts-superhermes-prism-scan\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7B22JA5XCAP1ACT6V50WYR1","prism-reflect","Constraint transparency: analyzes an artifact structurally, then analyzes what its own analysis concealed. Produces a conservation law AND a constraint report showing what was maximized, what was sacrificed, and what to investigate next. The only AI skill that knows what it can't see.","https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Fts-superhermes-prism-reflect\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M7B22EB15M75M4X3C52YGDCC","prism-full","Full Prism: multi-pass structural analysis with mandatory adversarial self-correction. Designs custom analytical passes, executes them with chaining, then attacks its own findings before synthesizing. Use for maximum depth on important code or artifacts.","https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Fts-superhermes-prism-full\u002FSKILL.md",[],[]]