[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AYP8AX3GM2SABMBQVGD15Q":3,"skill-same:01M7AYP8AX3GM2SABMBQVGD15Q":71},{"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":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M7AYP8AX3GM2SABMBQVGD15Q","hermes-web-backends",null,"Fix or configure Hermes web_search\u002Fweb_extract backends.","oat431\u002Fhermes_config_backup","oat431","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54722120?v=4","01M7AYD07EH8SYPMYY8CGZKS22","Oralita","01M7AYD0816QDF77E3TWCRSQC9",1,"MIT","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fhermes-main-profile\u002Fhermes-web-backends\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: hermes-web-backends\ndescription: \"Fix or configure Hermes web_search\u002Fweb_extract backends.\"\nversion: 1.0.0\nauthor: OraMesLita (curator)\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [hermes, web, search, extract, backend, searxng, firecrawl, tavily, exa, config]\n    related_skills: [hermes-agent, mcp-server-patterns]\n---\n\n# Hermes Web Search & Extract Backends\n\nConfiguring and troubleshooting which provider powers `web_search` \u002F `web_extract` in Hermes. Providers are plugins under `$HERMES_HOME\u002Fhermes-agent\u002Fplugins\u002Fweb\u002F\u003Cname>\u002F` (built-in, `kind: backend`), selected via `web.*` config keys. Reference: `references\u002Fweb-provider-docs.md` (verbatim docs excerpt).\n\n## Provider capability matrix\n\n| Provider | Env var (in $HERMES_HOME\u002F.env) | Search | Extract | Key needed? |\n|---|---|---|---|---|\n| firecrawl (default) | FIRECRAWL_API_KEY (or FIRECRAWL_API_URL self-hosted) | ✔ | ✔ | yes (or self-host) |\n| searxng | SEARXNG_URL | ✔ | — | no (self-hosted) |\n| parallel | PARALLEL_API_KEY | ✔ | ✔ | yes |\n| tavily | TAVILY_API_KEY | ✔ | ✔ | yes (free tier: app.tavily.com) |\n| exa | EXA_API_KEY | ✔ | ✔ | yes (free tier: exa.ai) |\n| ddgs | (pip install ddgs) | ✔ | — | no |\n| brave-free | — | ✔ | — | no |\n\n**Hard fact: there is NO keyless extract backend.** Extract always needs firecrawl\u002Ftavily\u002Fexa\u002Fparallel (or self-hosted Firecrawl). Search can be free via searxng\u002Fddgs\u002Fbrave-free.\n\n## Config keys & resolution\n\n```yaml\nweb:\n  backend: searxng            # fallback: firecrawl | searxng | parallel | tavily | exa | ddgs | brave-free\n  search_backend: searxng     # optional per-capability override (mix free search + paid extract)\n  extract_backend: firecrawl  # optional per-capability override\n  extract_char_limit: 15000\n```\n\n- Explicit `web.search_backend` \u002F `web.extract_backend` win for their capability.\n- If `web.backend` is unset → auto-detect from keys: SEARXNG_URL → searxng; EXA_API_KEY → exa; TAVILY_API_KEY → tavily; PARALLEL_API_KEY → parallel; else firecrawl.\n- Registry fallback order (filtered by capability): firecrawl → parallel → tavily → exa → searxng → brave-free → ddgs.\n\n## Fix recipe: \"ddgs is a search-only backend and cannot extract\"\n\nSymptom: `web_extract` errors with `Set web.extract_backend to firecrawl, tavily, exa, or parallel` (because `web.backend: ddgs` is search-only).\n\n1. **Search** — point at the user's searxng (free, works live):\n   ```bash\n   H=\"$HERMES_HOME\"\n   printf '\\nSEARXNG_URL=http:\u002F\u002F\u003Cinstance-ip:port>\\n' >> \"$H\u002F.env\"\n   hermes config set web.backend searxng\n   ```\n2. **Extract** — needs a keyed provider. User signs up (free tiers: Tavily 1k credits\u002Fmo, Firecrawl 500\u002Fmo, Exa), then:\n   ```bash\n   printf '\\nTAVILY_API_KEY=\u003Ckey>\\n' >> \"$H\u002F.env\"\n   hermes config set web.extract_backend tavily\n   ```\n3. **Verify**: call `web_search` — results mean provider resolution worked.\n\n**`web.*` config changes take effect LIVE (per-call registry resolution) — no session reset needed** (verified 2026-08-06). This differs from toolset changes, which need `\u002Freset`.\n\n## Pitfalls\n\n- **$HOME trap**: `~\u002F.hermes` may NOT be the real home. Always use `$HERMES_HOME` (on Panomete's box: `C:\\Users\\Admin\\AppData\\Local\\hermes`; `~\u002F.hermes` does not exist). `hermes config get web` reads the right file regardless.\n- Use `hermes config set KEY VAL` — never hand-edit config.yaml.\n- `.env` vars are read via config-aware lookup (os.environ first, then `$HERMES_HOME\u002F.env`) so gateway sessions\u002Fdelegate children see them too.\n- The searxng **MCP** server config (config.yaml → `mcp.servers.searxng.env.SEARXNG_URL`) is SEPARATE from the native web backend — fixing one does not fix the other. MCP searxng's `web_url_read` CAN extract, so it's the workaround while native extract is unconfigured.\n- Never print `.env` values; list key names only: `grep -oE '^[A-Z_0-9]+=' \"$H\u002F.env\"`.\n- Docs: https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Fconfiguration → \"Web Search Backends\". If `web_extract` is broken, curl the docs page and strip HTML with python (`re.sub(r'\u003C[^>]+>', ' ', ...)`) — avoids the broken extract path entirely.\n- Self-hosted Firecrawl: set FIRECRAWL_API_URL, key becomes optional (server-side `USE_DB_AUTHENTICATION`). Needs Docker — check daemon state first (Panomete's Docker was DOWN at 2026-08-05).\n- Provider plugins only advertise capabilities they implement (`supports_search` \u002F `supports_extract`); registry routes each call to the right provider.\n- **Do NOT retry `web_extract` when the error is \"search-only backend.\"** Retrying with the same backend (or another search-only backend) returns the same error. The only productive paths are: (a) `curl -sL \"\u003Curl>\"` to bypass the extract path entirely, (b) `web_search` for finding information, or (c) asking the user to set up a keyed extract backend (tavily\u002Ffirecrawl\u002Fexa\u002Fparallel). A retry loop wastes turns.\n\n## Signup links\n\n- Tavily: https:\u002F\u002Fapp.tavily.com\u002Fhome · Exa: https:\u002F\u002Fexa.ai · Firecrawl: https:\u002F\u002Ffirecrawl.dev · Parallel: https:\u002F\u002Fparallel.ai\n","# Hermes Web Search & Extract Backends\n\nConfiguring and troubleshooting which provider powers `web_search` \u002F `web_extract` in Hermes. Providers are plugins under `$HERMES_HOME\u002Fhermes-agent\u002Fplugins\u002Fweb\u002F\u003Cname>\u002F` (built-in, `kind: backend`), selected via `web.*` config keys. Reference: `references\u002Fweb-provider-docs.md` (verbatim docs excerpt).\n\n## Provider capability matrix\n\n| Provider | Env var (in $HERMES_HOME\u002F.env) | Search | Extract | Key needed? |\n|---|---|---|---|---|\n| firecrawl (default) | FIRECRAWL_API_KEY (or FIRECRAWL_API_URL self-hosted) | ✔ | ✔ | yes (or self-host) |\n| searxng | SEARXNG_URL | ✔ | — | no (self-hosted) |\n| parallel | PARALLEL_API_KEY | ✔ | ✔ | yes |\n| tavily | TAVILY_API_KEY | ✔ | ✔ | yes (free tier: app.tavily.com) |\n| exa | EXA_API_KEY | ✔ | ✔ | yes (free tier: exa.ai) |\n| ddgs | (pip install ddgs) | ✔ | — | no |\n| brave-free | — | ✔ | — | no |\n\n**Hard fact: there is NO keyless extract backend.** Extract always needs firecrawl\u002Ftavily\u002Fexa\u002Fparallel (or self-hosted Firecrawl). Search can be free via searxng\u002Fddgs\u002Fbrave-free.\n\n## Config keys & resolution\n\n```yaml\nweb:\n  backend: searxng            # fallback: firecrawl | searxng | parallel | tavily | exa | ddgs | brave-free\n  search_backend: searxng     # optional per-capability override (mix free search + paid extract)\n  extract_backend: firecrawl  # optional per-capability override\n  extract_char_limit: 15000\n```\n\n- Explicit `web.search_backend` \u002F `web.extract_backend` win for their capability.\n- If `web.backend` is unset → auto-detect from keys: SEARXNG_URL → searxng; EXA_API_KEY → exa; TAVILY_API_KEY → tavily; PARALLEL_API_KEY → parallel; else firecrawl.\n- Registry fallback order (filtered by capability): firecrawl → parallel → tavily → exa → searxng → brave-free → ddgs.\n\n## Fix recipe: \"ddgs is a search-only backend and cannot extract\"\n\nSymptom: `web_extract` errors with `Set web.extract_backend to firecrawl, tavily, exa, or parallel` (because `web.backend: ddgs` is search-only).\n\n1. **Search** — point at the user's searxng (free, works live):\n   ```bash\n   H=\"$HERMES_HOME\"\n   printf '\\nSEARXNG_URL=http:\u002F\u002F\u003Cinstance-ip:port>\\n' >> \"$H\u002F.env\"\n   hermes config set web.backend searxng\n   ```\n2. **Extract** — needs a keyed provider. User signs up (free tiers: Tavily 1k credits\u002Fmo, Firecrawl 500\u002Fmo, Exa), then:\n   ```bash\n   printf '\\nTAVILY_API_KEY=\u003Ckey>\\n' >> \"$H\u002F.env\"\n   hermes config set web.extract_backend tavily\n   ```\n3. **Verify**: call `web_search` — results mean provider resolution worked.\n\n**`web.*` config changes take effect LIVE (per-call registry resolution) — no session reset needed** (verified 2026-08-06). This differs from toolset changes, which need `\u002Freset`.\n\n## Pitfalls\n\n- **$HOME trap**: `~\u002F.hermes` may NOT be the real home. Always use `$HERMES_HOME` (on Panomete's box: `C:\\Users\\Admin\\AppData\\Local\\hermes`; `~\u002F.hermes` does not exist). `hermes config get web` reads the right file regardless.\n- Use `hermes config set KEY VAL` — never hand-edit config.yaml.\n- `.env` vars are read via config-aware lookup (os.environ first, then `$HERMES_HOME\u002F.env`) so gateway sessions\u002Fdelegate children see them too.\n- The searxng **MCP** server config (config.yaml → `mcp.servers.searxng.env.SEARXNG_URL`) is SEPARATE from the native web backend — fixing one does not fix the other. MCP searxng's `web_url_read` CAN extract, so it's the workaround while native extract is unconfigured.\n- Never print `.env` values; list key names only: `grep -oE '^[A-Z_0-9]+=' \"$H\u002F.env\"`.\n- Docs: https:\u002F\u002Fhermes-agent.nousresearch.com\u002Fdocs\u002Fuser-guide\u002Fconfiguration → \"Web Search Backends\". If `web_extract` is broken, curl the docs page and strip HTML with python (`re.sub(r'\u003C[^>]+>', ' ', ...)`) — avoids the broken extract path entirely.\n- Self-hosted Firecrawl: set FIRECRAWL_API_URL, key becomes optional (server-side `USE_DB_AUTHENTICATION`). Needs Docker — check daemon state first (Panomete's Docker was DOWN at 2026-08-05).\n- Provider plugins only advertise capabilities they implement (`supports_search` \u002F `supports_extract`); registry routes each call to the right provider.\n- **Do NOT retry `web_extract` when the error is \"search-only backend.\"** Retrying with the same backend (or another search-only backend) returns the same error. The only productive paths are: (a) `curl -sL \"\u003Curl>\"` to bypass the extract path entirely, (b) `web_search` for finding information, or (c) asking the user to set up a keyed extract backend (tavily\u002Ffirecrawl\u002Fexa\u002Fparallel). A retry loop wastes turns.\n\n## Signup links\n\n- Tavily: https:\u002F\u002Fapp.tavily.com\u002Fhome · Exa: https:\u002F\u002Fexa.ai · Firecrawl: https:\u002F\u002Ffirecrawl.dev · Parallel: https:\u002F\u002Fparallel.ai\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"description":7},"OraMesLita (curator)","1.0.0",{"hermes":27},{"tags":28,"related_skills":39},[29,30,31,32,33,34,35,36,37,38],"hermes","web","search","extract","backend","searxng","firecrawl","tavily","exa","config",[40,41],"hermes-agent","mcp-server-patterns","main","2988869c5a7d7be2225c9ea7a54a4a56a59b0d45","workflow\u002Fhermes-main-profile\u002Fhermes-web-backends",0,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup","https:\u002F\u002Fgithub.com\u002Foat431","https:\u002F\u002Fpanomete.com\u002F","Hope and Luck is not a part of the strategy, \r\n\r\nSoftskill produces plan Hard skill produce product.","2026-11-03 00:43:08",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add oat431\u002Fhermes_config_backup --skill hermes-web-backends",{"tool":57,"command":58},"bunx","bunx skills add oat431\u002Fhermes_config_backup --skill hermes-web-backends",{"tool":60,"command":61},"pnpm","pnpm dlx skills add oat431\u002Fhermes_config_backup --skill hermes-web-backends","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fhermes-main-profile\u002Fhermes-web-backends\u002FSKILL.md",true,[65],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fweb-provider-docs.md","REFERENCE","参考文档",2847,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fhermes-main-profile\u002Fhermes-web-backends\u002Freferences\u002Fweb-provider-docs.md",[72,79,86,94,101,108],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7AYZ2JY3NFKAPQSC39N5F3F","project-spec-docs","Fill\u002Fupdate project_spec docs (templates, MM handoffs).","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fproject-spec-docs\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7AYYRZPE7HQX7778558X52S","penpot-mcp","Penpot MCP: connect, verify, and fix streaming via nginx.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fpenpot-mcp\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7AYYNKP61CN2281VMJDXMB5","nginx-streaming-proxy","Configure nginx for streaming endpoints (SSE, MCP, WS).","Unlicense","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fnginx-streaming-proxy\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7AYYJP0MDV1D3WVEEZB3SGA","branding-ci","Use for brand\u002FCI identity, style guides, and brand docs.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fbranding-ci\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7AYYGCXVT97DDTCM0ZJT6F6","yuanbao","Yuanbao (元宝) groups: @mention users, query info\u002Fmembers.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fshared-skills\u002Fyuanbao\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7AYYC2Y65NMGMD4GQXAZMMS","slidev","Create and present web-based slidedecks for developers using Slidev with Markdown, Vue components, code highlighting, animations, and interactive features. Use when building technical presentations, conference talks, code walkthroughs, teaching materials, or developer decks.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fshared-skills\u002Fslidev\u002FSKILL.md",[],[]]