[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B3RNWZK28126Q7J9CT1H18":3,"skill-same:01M7B3RNWZK28126Q7J9CT1H18":76},{"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":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M7B3RNWZK28126Q7J9CT1H18","har-derived-api-client",null,"Record a site's XHR into a HAR, derive an HTTP client.","merllinsbeard\u002Fmerlin-CTO","merllinsbeard","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F144795773?v=4","01M7B3C01C1PCBWFGB5T7YXSF8","merlin","01M7B3C023BBYDEPAPWBAGW9A7",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmerllinsbeard\u002Fmerlin-CTO\u002Fblob\u002Fmain\u002Fskills\u002Fweb-development\u002Fhar-derived-api-client\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: har-derived-api-client\ndescription: Record a site's XHR into a HAR, derive an HTTP client.\nversion: 0.1.0\nauthor: Hermes Agent\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [Browser, HAR, API, Reverse-Engineering, Playwright]\n    category: web-development\n---\n\n# HAR-Derived API Client\n\nDrive a website once with a real browser while recording its network traffic\nto a HAR file, then distill that HAR into the site's private JSON API so you\ncan call it directly with plain HTTP — far cheaper and faster than\nbrowser-controlling the page on every request. Credit: trick by Jared Longster,\npopularized by Dax (thdxr). This captures and replays; it does NOT bypass\nauth, solve CAPTCHAs, or defeat bot-detection — if the site needs a logged-in\nsession, you carry its headers\u002Fcookies forward, you don't forge them.\n\nThe scripts are stdlib-plus-Playwright: capture needs Playwright, derivation\nis pure stdlib, replay needs only `requests`\u002F`httpx` (or `curl`).\n\nCovers **every Hermes browser pathway**: the default local `browser_navigate`\nbackend, plus the cloud\u002Fremote backends (Browserbase, Browser-Use, Firecrawl)\nand any `\u002Fbrowser connect` CDP endpoint. There are two capture scripts — one\nfor a browser you launch, one for a browser you attach to over CDP — because\nHAR recording works differently in each case (see How to Run).\n\n## When to Use\n\n- \"Build a CLI\u002Fclient for \u003Cwebsite>\" — derive its API instead of scripting clicks.\n- \"This site has no public API but the page clearly fetches JSON.\"\n- You're about to loop `browser_navigate` for the same query repeatedly — stop and derive the endpoint once.\n- Reverse-engineering an autocomplete, search, feed, or checkout XHR.\n- You captured a session on a cloud backend (Browserbase \u002F Browser-Use \u002F Firecrawl) or via `\u002Fbrowser connect` and want the API without re-renting the browser.\n\n## Prerequisites\n\n- Playwright + a browser binary (capture step only):\n  - `pip install playwright` then `playwright install chromium`\n  - (If a system Playwright already has browsers under `~\u002F.cache\u002Fms-playwright`, reuse it.)\n- `requests` or `httpx` for the replay step (stdlib `urllib` also works).\n- No API keys. Any keys\u002Ftokens the client needs are the ones the HAR captured.\n- For the CDP path (`har_capture_cdp.py`): a reachable CDP endpoint. On Hermes,\n  run `\u002Fbrowser connect` to print the active endpoint, or read `BROWSER_CDP_URL`\n  \u002F `browser.cdp_url` in config. Cloud backends expose it as `cdpUrl`\u002F`connectUrl`.\n\n## How to Run\n\nScripts under this skill's `scripts\u002F`, invoked through the `terminal` tool.\n**Pick the capturer by pathway** — this is the part that trips people up:\n\n| Browser pathway | How Hermes reaches it | Capturer |\n|---|---|---|\n| Local `browser_navigate` (default, agent-browser\u002FPlaywright) | launched locally | `har_capture.py` |\n| Camofox (`CAMOFOX_URL` set) | local REST\u002FCDP | `har_capture_cdp.py` if it exposes CDP, else drive it yourself |\n| Browserbase \u002F Browser-Use \u002F Firecrawl (cloud) | **CDP** (`cdpUrl`) | `har_capture_cdp.py` |\n| `\u002Fbrowser connect \u003Curl>` \u002F `BROWSER_CDP_URL` | **CDP** | `har_capture_cdp.py` |\n\nRule of thumb: **if Hermes *launched* the browser, use `har_capture.py`; if it\n*connected to* one over CDP, use `har_capture_cdp.py`.** `har_capture.py` uses\nPlaywright's `record_har_path`, which only works on a locally-owned context.\n`har_capture_cdp.py` attaches with `connect_over_cdp()` and assembles the HAR\nfrom `page.on(\"request\"\u002F\"response\")` events, because `record_har_path` is\nunavailable on a connected browser.\n\nThen, for either path:\n\n- `har_to_client.py` — filters the HAR to XHR\u002Ffetch\u002FJSON, groups by endpoint, and prints params, headers, bodies, and replay hints (User-Agent \u002F cookie \u002F auth).\n\nResolve paths against this skill's directory. Canonical loop:\n\n```bash\n# 1a. Capture, LOCAL browser (Hermes launched it)\npython3 scripts\u002Fhar_capture.py \"https:\u002F\u002FSITE\u002F\" out.har \\\n  --action \"fill:input[name=search]:my query\" --action \"sleep:3\" --wait 2\n\n# 1b. Capture, CDP browser (cloud backend or \u002Fbrowser connect)\n#     get the endpoint from \u002Fbrowser connect or BROWSER_CDP_URL\npython3 scripts\u002Fhar_capture_cdp.py \"ws:\u002F\u002FHOST\u002Fdevtools\u002Fbrowser\u002F...\" out.har \\\n  --goto \"https:\u002F\u002FSITE\u002F\" --action \"fill:input[name=search]:my query\" \\\n  --action \"sleep:3\" --wait 2\n\n# 2. Derive — read the endpoints out of the HAR\npython3 scripts\u002Fhar_to_client.py out.har --host SITE --max-body 400\n\n# 3. Replay — write a tiny client from the printed endpoint (see Procedure)\n```\n\n## Quick Reference\n\n```\nhar_capture.py \u003Curl> \u003Cout.har> [--wait S] [--headed] [--action SPEC ...]\n  action SPEC:  fill:SELECTOR:TEXT | press:SELECTOR:KEY | click:SELECTOR\n                goto:URL | sleep:SECONDS      (run in order after page load)\n  use when Hermes LAUNCHED the browser (local browser_navigate default)\n\nhar_capture_cdp.py \u003Ccdp_url> \u003Cout.har> [--goto URL] [--wait S] [--action SPEC ...]\n  same action SPEC; attaches to an existing CDP browser and does NOT close it\n  use for cloud backends (Browserbase\u002FBrowser-Use\u002FFirecrawl) & \u002Fbrowser connect\n\nhar_to_client.py \u003Cin.har> [--host SUBSTR] [--include-static] [--max-body N]\n  default: keeps only XHR\u002Ffetch\u002FJSON; --host narrows to one domain\n  prints per endpoint: query params, non-boring req headers, req body sample,\n                       response status\u002Fcontent-type + body sample\n  prints \"### Replay hints\": the browser User-Agent, cookie\u002Fauth presence\n```\n\n## Procedure\n\n0. **Pick the capturer by pathway** (see How to Run table). Launched-locally → `har_capture.py`; reached over CDP → `har_capture_cdp.py`. On Hermes, `\u002Fbrowser connect` tells you the CDP endpoint when a cloud\u002Fremote backend is active.\n1. **Find the interaction.** Open the site with `browser_navigate` (or `--headed` capture) to see which selector to type into \u002F click, and confirm a JSON XHR fires in devtools\u002Fnetwork.\n2. **Capture the HAR** via the `terminal` tool. Order `--action` to reach the request: `fill` the box, then `sleep` long enough for the debounced XHR, and always leave `--wait` at the end so late responses flush. Both capturers embed response bodies, so the derived client sees real payload shapes.\n3. **Derive** with `har_to_client.py --host \u003Cdomain>`. Read off: the method, the URL\u002Fpath template (numeric\u002FUUID segments collapse to `{id}`), query params, request-body JSON, and the `### Replay hints` block.\n4. **Write the client.** Recreate the request exactly — same method, path, query params, body. Send the headers the site actually needs: at minimum copy the **User-Agent** from the replay hints. If hints report cookies or an auth\u002Ftoken header, resend those too.\n5. **Test browserless.** Run the client with the `terminal` tool and confirm it returns the same data the browser saw. This is the payoff: no browser in the loop.\n6. **(Optional) Wrap as a CLI** — a small `argparse` script over the derived call, e.g. `search.py \"frank herbert\"`.\n\nWorked example (Wikipedia search-title, derived + replayed live):\n\n```python\nimport requests\nr = requests.get(\n    \"https:\u002F\u002Fen.wikipedia.org\u002Fw\u002Frest.php\u002Fv1\u002Fsearch\u002Ftitle\",\n    params={\"q\": \"frank herbert\", \"limit\": 5},\n    headers={\"accept\": \"application\u002Fjson\",\n             \"User-Agent\": \"Mozilla\u002F5.0 ... Chrome\u002F131 Safari\u002F537.36\"},  # from HAR\n    timeout=15,\n)\nfor p in r.json()[\"pages\"]:\n    print(p[\"title\"], \"-\", p.get(\"description\"))\n```\n\n## Pitfalls\n\n- **Default library User-Agent gets 403.** Many sites (Wikipedia, Cloudflare-fronted APIs) reject `python-requests\u002Fx.y`. Always send the browser UA from the replay hints. This is the #1 reason a derived client fails when the browser succeeded.\n- **A failed `--action` aborts before the HAR flushes** — you get no file. If capture errors on a selector, the run produced nothing; fix the selector (use `--headed` to watch) and rerun. Don't debug a missing HAR.\n- **Server-rendered pages have no XHR** to derive — `har_to_client.py` prints \"No API-looking entries\". The data came in the HTML; scrape it or find the interaction that does fetch JSON.\n- **Debounced\u002Ftypeahead XHRs need a real pause.** Add `--action \"sleep:3\"` after `fill`; typing alone won't have fired the request when the HAR closes.\n- **Auth\u002Fsession endpoints** need the captured `Cookie`\u002F`Authorization` header, and those expire. The derived client is only as durable as the credential; re-capture when it 401s. HARs contain live secrets — treat `out.har` as sensitive and delete it after deriving.\n- **`record_har_content=\"embed\"` makes big HARs.** Use `--max-body` to cap what's printed; the file itself can be large for media-heavy pages.\n- **Endpoints shift.** Sites change private APIs without notice. Re-run the capture→derive loop when a client breaks rather than patching URLs by hand.\n- **Wrong capturer = empty\u002Fno HAR.** `har_capture.py` on a cloud\u002FCDP backend records nothing (it launches its own local browser instead of the one you meant). `har_capture_cdp.py` needs the endpoint; on Hermes get it from `\u002Fbrowser connect` or `BROWSER_CDP_URL`. Match the capturer to the pathway (How to Run table).\n- **Headless-Chrome UA is a weak tell.** Local\u002Fagent-browser capture yields a `HeadlessChrome\u002F...` User-Agent; some sites sniff the \"Headless\" token. Cloud backends (Browserbase\u002FBrowser-Use) send a real desktop-Chrome UA, so a client derived from a cloud capture replays more reliably. If a headless-derived client 403s where the browser didn't, swap the \"Headless\" UA for a normal Chrome UA string before assuming the endpoint changed.\n- **CDP capture doesn't close the browser.** `har_capture_cdp.py` attaches to a browser it doesn't own and leaves it running — correct for cloud\u002Fremote sessions Hermes manages. Don't add a close; let the owning backend tear it down.\n\n## Verification\n\nEnd-to-end proof against a live site with no API key:\n\n```bash\npython3 scripts\u002Fhar_capture.py \"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMain_Page\" \u002Ftmp\u002Fwiki.har \\\n  --action \"fill:input[name=search]:dune messiah\" --action \"sleep:3\" --wait 2\npython3 scripts\u002Fhar_to_client.py \u002Ftmp\u002Fwiki.har --host wikipedia.org --max-body 200\n```\n\nExpect the derivation to print `GET https:\u002F\u002Fen.wikipedia.org\u002Fw\u002Frest.php\u002Fv1\u002Fsearch\u002Ftitle`\nwith `q` and `limit` params and a JSON `pages` response — then replay it with the\nProcedure snippet and confirm matching titles come back over plain HTTP.\n","# HAR-Derived API Client\n\nDrive a website once with a real browser while recording its network traffic\nto a HAR file, then distill that HAR into the site's private JSON API so you\ncan call it directly with plain HTTP — far cheaper and faster than\nbrowser-controlling the page on every request. Credit: trick by Jared Longster,\npopularized by Dax (thdxr). This captures and replays; it does NOT bypass\nauth, solve CAPTCHAs, or defeat bot-detection — if the site needs a logged-in\nsession, you carry its headers\u002Fcookies forward, you don't forge them.\n\nThe scripts are stdlib-plus-Playwright: capture needs Playwright, derivation\nis pure stdlib, replay needs only `requests`\u002F`httpx` (or `curl`).\n\nCovers **every Hermes browser pathway**: the default local `browser_navigate`\nbackend, plus the cloud\u002Fremote backends (Browserbase, Browser-Use, Firecrawl)\nand any `\u002Fbrowser connect` CDP endpoint. There are two capture scripts — one\nfor a browser you launch, one for a browser you attach to over CDP — because\nHAR recording works differently in each case (see How to Run).\n\n## When to Use\n\n- \"Build a CLI\u002Fclient for \u003Cwebsite>\" — derive its API instead of scripting clicks.\n- \"This site has no public API but the page clearly fetches JSON.\"\n- You're about to loop `browser_navigate` for the same query repeatedly — stop and derive the endpoint once.\n- Reverse-engineering an autocomplete, search, feed, or checkout XHR.\n- You captured a session on a cloud backend (Browserbase \u002F Browser-Use \u002F Firecrawl) or via `\u002Fbrowser connect` and want the API without re-renting the browser.\n\n## Prerequisites\n\n- Playwright + a browser binary (capture step only):\n  - `pip install playwright` then `playwright install chromium`\n  - (If a system Playwright already has browsers under `~\u002F.cache\u002Fms-playwright`, reuse it.)\n- `requests` or `httpx` for the replay step (stdlib `urllib` also works).\n- No API keys. Any keys\u002Ftokens the client needs are the ones the HAR captured.\n- For the CDP path (`har_capture_cdp.py`): a reachable CDP endpoint. On Hermes,\n  run `\u002Fbrowser connect` to print the active endpoint, or read `BROWSER_CDP_URL`\n  \u002F `browser.cdp_url` in config. Cloud backends expose it as `cdpUrl`\u002F`connectUrl`.\n\n## How to Run\n\nScripts under this skill's `scripts\u002F`, invoked through the `terminal` tool.\n**Pick the capturer by pathway** — this is the part that trips people up:\n\n| Browser pathway | How Hermes reaches it | Capturer |\n|---|---|---|\n| Local `browser_navigate` (default, agent-browser\u002FPlaywright) | launched locally | `har_capture.py` |\n| Camofox (`CAMOFOX_URL` set) | local REST\u002FCDP | `har_capture_cdp.py` if it exposes CDP, else drive it yourself |\n| Browserbase \u002F Browser-Use \u002F Firecrawl (cloud) | **CDP** (`cdpUrl`) | `har_capture_cdp.py` |\n| `\u002Fbrowser connect \u003Curl>` \u002F `BROWSER_CDP_URL` | **CDP** | `har_capture_cdp.py` |\n\nRule of thumb: **if Hermes *launched* the browser, use `har_capture.py`; if it\n*connected to* one over CDP, use `har_capture_cdp.py`.** `har_capture.py` uses\nPlaywright's `record_har_path`, which only works on a locally-owned context.\n`har_capture_cdp.py` attaches with `connect_over_cdp()` and assembles the HAR\nfrom `page.on(\"request\"\u002F\"response\")` events, because `record_har_path` is\nunavailable on a connected browser.\n\nThen, for either path:\n\n- `har_to_client.py` — filters the HAR to XHR\u002Ffetch\u002FJSON, groups by endpoint, and prints params, headers, bodies, and replay hints (User-Agent \u002F cookie \u002F auth).\n\nResolve paths against this skill's directory. Canonical loop:\n\n```bash\n# 1a. Capture, LOCAL browser (Hermes launched it)\npython3 scripts\u002Fhar_capture.py \"https:\u002F\u002FSITE\u002F\" out.har \\\n  --action \"fill:input[name=search]:my query\" --action \"sleep:3\" --wait 2\n\n# 1b. Capture, CDP browser (cloud backend or \u002Fbrowser connect)\n#     get the endpoint from \u002Fbrowser connect or BROWSER_CDP_URL\npython3 scripts\u002Fhar_capture_cdp.py \"ws:\u002F\u002FHOST\u002Fdevtools\u002Fbrowser\u002F...\" out.har \\\n  --goto \"https:\u002F\u002FSITE\u002F\" --action \"fill:input[name=search]:my query\" \\\n  --action \"sleep:3\" --wait 2\n\n# 2. Derive — read the endpoints out of the HAR\npython3 scripts\u002Fhar_to_client.py out.har --host SITE --max-body 400\n\n# 3. Replay — write a tiny client from the printed endpoint (see Procedure)\n```\n\n## Quick Reference\n\n```\nhar_capture.py \u003Curl> \u003Cout.har> [--wait S] [--headed] [--action SPEC ...]\n  action SPEC:  fill:SELECTOR:TEXT | press:SELECTOR:KEY | click:SELECTOR\n                goto:URL | sleep:SECONDS      (run in order after page load)\n  use when Hermes LAUNCHED the browser (local browser_navigate default)\n\nhar_capture_cdp.py \u003Ccdp_url> \u003Cout.har> [--goto URL] [--wait S] [--action SPEC ...]\n  same action SPEC; attaches to an existing CDP browser and does NOT close it\n  use for cloud backends (Browserbase\u002FBrowser-Use\u002FFirecrawl) & \u002Fbrowser connect\n\nhar_to_client.py \u003Cin.har> [--host SUBSTR] [--include-static] [--max-body N]\n  default: keeps only XHR\u002Ffetch\u002FJSON; --host narrows to one domain\n  prints per endpoint: query params, non-boring req headers, req body sample,\n                       response status\u002Fcontent-type + body sample\n  prints \"### Replay hints\": the browser User-Agent, cookie\u002Fauth presence\n```\n\n## Procedure\n\n0. **Pick the capturer by pathway** (see How to Run table). Launched-locally → `har_capture.py`; reached over CDP → `har_capture_cdp.py`. On Hermes, `\u002Fbrowser connect` tells you the CDP endpoint when a cloud\u002Fremote backend is active.\n1. **Find the interaction.** Open the site with `browser_navigate` (or `--headed` capture) to see which selector to type into \u002F click, and confirm a JSON XHR fires in devtools\u002Fnetwork.\n2. **Capture the HAR** via the `terminal` tool. Order `--action` to reach the request: `fill` the box, then `sleep` long enough for the debounced XHR, and always leave `--wait` at the end so late responses flush. Both capturers embed response bodies, so the derived client sees real payload shapes.\n3. **Derive** with `har_to_client.py --host \u003Cdomain>`. Read off: the method, the URL\u002Fpath template (numeric\u002FUUID segments collapse to `{id}`), query params, request-body JSON, and the `### Replay hints` block.\n4. **Write the client.** Recreate the request exactly — same method, path, query params, body. Send the headers the site actually needs: at minimum copy the **User-Agent** from the replay hints. If hints report cookies or an auth\u002Ftoken header, resend those too.\n5. **Test browserless.** Run the client with the `terminal` tool and confirm it returns the same data the browser saw. This is the payoff: no browser in the loop.\n6. **(Optional) Wrap as a CLI** — a small `argparse` script over the derived call, e.g. `search.py \"frank herbert\"`.\n\nWorked example (Wikipedia search-title, derived + replayed live):\n\n```python\nimport requests\nr = requests.get(\n    \"https:\u002F\u002Fen.wikipedia.org\u002Fw\u002Frest.php\u002Fv1\u002Fsearch\u002Ftitle\",\n    params={\"q\": \"frank herbert\", \"limit\": 5},\n    headers={\"accept\": \"application\u002Fjson\",\n             \"User-Agent\": \"Mozilla\u002F5.0 ... Chrome\u002F131 Safari\u002F537.36\"},  # from HAR\n    timeout=15,\n)\nfor p in r.json()[\"pages\"]:\n    print(p[\"title\"], \"-\", p.get(\"description\"))\n```\n\n## Pitfalls\n\n- **Default library User-Agent gets 403.** Many sites (Wikipedia, Cloudflare-fronted APIs) reject `python-requests\u002Fx.y`. Always send the browser UA from the replay hints. This is the #1 reason a derived client fails when the browser succeeded.\n- **A failed `--action` aborts before the HAR flushes** — you get no file. If capture errors on a selector, the run produced nothing; fix the selector (use `--headed` to watch) and rerun. Don't debug a missing HAR.\n- **Server-rendered pages have no XHR** to derive — `har_to_client.py` prints \"No API-looking entries\". The data came in the HTML; scrape it or find the interaction that does fetch JSON.\n- **Debounced\u002Ftypeahead XHRs need a real pause.** Add `--action \"sleep:3\"` after `fill`; typing alone won't have fired the request when the HAR closes.\n- **Auth\u002Fsession endpoints** need the captured `Cookie`\u002F`Authorization` header, and those expire. The derived client is only as durable as the credential; re-capture when it 401s. HARs contain live secrets — treat `out.har` as sensitive and delete it after deriving.\n- **`record_har_content=\"embed\"` makes big HARs.** Use `--max-body` to cap what's printed; the file itself can be large for media-heavy pages.\n- **Endpoints shift.** Sites change private APIs without notice. Re-run the capture→derive loop when a client breaks rather than patching URLs by hand.\n- **Wrong capturer = empty\u002Fno HAR.** `har_capture.py` on a cloud\u002FCDP backend records nothing (it launches its own local browser instead of the one you meant). `har_capture_cdp.py` needs the endpoint; on Hermes get it from `\u002Fbrowser connect` or `BROWSER_CDP_URL`. Match the capturer to the pathway (How to Run table).\n- **Headless-Chrome UA is a weak tell.** Local\u002Fagent-browser capture yields a `HeadlessChrome\u002F...` User-Agent; some sites sniff the \"Headless\" token. Cloud backends (Browserbase\u002FBrowser-Use) send a real desktop-Chrome UA, so a client derived from a cloud capture replays more reliably. If a headless-derived client 403s where the browser didn't, swap the \"Headless\" UA for a normal Chrome UA string before assuming the endpoint changed.\n- **CDP capture doesn't close the browser.** `har_capture_cdp.py` attaches to a browser it doesn't own and leaves it running — correct for cloud\u002Fremote sessions Hermes manages. Don't add a close; let the owning backend tear it down.\n\n## Verification\n\nEnd-to-end proof against a live site with no API key:\n\n```bash\npython3 scripts\u002Fhar_capture.py \"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMain_Page\" \u002Ftmp\u002Fwiki.har \\\n  --action \"fill:input[name=search]:dune messiah\" --action \"sleep:3\" --wait 2\npython3 scripts\u002Fhar_to_client.py \u002Ftmp\u002Fwiki.har --host wikipedia.org --max-body 200\n```\n\nExpect the derivation to print `GET https:\u002F\u002Fen.wikipedia.org\u002Fw\u002Frest.php\u002Fv1\u002Fsearch\u002Ftitle`\nwith `q` and `limit` params and a JSON `pages` response — then replay it with the\nProcedure snippet and confirm matching titles come back over plain HTTP.\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":35,"description":7},"Hermes Agent","0.1.0",{"hermes":27},{"tags":28,"category":34},[29,30,31,32,33],"Browser","HAR","API","Reverse-Engineering","Playwright","web-development",[36,37,38],"linux","macos","windows","main","116bb09f1369e85cd8a54fec4135e218dca4a061","skills\u002Fweb-development\u002Fhar-derived-api-client",0,"https:\u002F\u002Fgithub.com\u002Fmerllinsbeard\u002Fmerlin-CTO","https:\u002F\u002Fgithub.com\u002Fmerllinsbeard\u002Fmerlin-CTO\u002Freleases\u002Flatest","https:\u002F\u002Fgithub.com\u002Fmerllinsbeard","ai","2026-08-25 21:36:43",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add merllinsbeard\u002Fmerlin-CTO --skill har-derived-api-client",{"tool":54,"command":55},"bunx","bunx skills add merllinsbeard\u002Fmerlin-CTO --skill har-derived-api-client",{"tool":57,"command":58},"pnpm","pnpm dlx skills add merllinsbeard\u002Fmerlin-CTO --skill har-derived-api-client","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmerllinsbeard\u002Fmerlin-CTO\u002Fblob\u002Fmain\u002Fskills\u002Fweb-development\u002Fhar-derived-api-client\u002FSKILL.md",true,[62,68,72],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"scripts\u002Fhar_capture_cdp.py","SCRIPT","脚本",4728,"https:\u002F\u002Fgithub.com\u002Fmerllinsbeard\u002Fmerlin-CTO\u002Fblob\u002Fmain\u002Fskills\u002Fweb-development\u002Fhar-derived-api-client\u002Fscripts\u002Fhar_capture_cdp.py",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"scripts\u002Fhar_capture.py",2496,"https:\u002F\u002Fgithub.com\u002Fmerllinsbeard\u002Fmerlin-CTO\u002Fblob\u002Fmain\u002Fskills\u002Fweb-development\u002Fhar-derived-api-client\u002Fscripts\u002Fhar_capture.py",{"path":73,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":74,"sourceHtmlUrl":75},"scripts\u002Fhar_to_client.py",5834,"https:\u002F\u002Fgithub.com\u002Fmerllinsbeard\u002Fmerlin-CTO\u002Fblob\u002Fmain\u002Fskills\u002Fweb-development\u002Fhar-derived-api-client\u002Fscripts\u002Fhar_to_client.py",[77,84,91,98,105,112],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7B3SK15WA8JW4G6RBKZR3ME","writing-for-agents","Use for delegate_task, Kanban, and all agent-facing text.","https:\u002F\u002Fgithub.com\u002Fmerllinsbeard\u002Fmerlin-CTO\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7B3SD78DTTXFVXGDPRK7249","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Fmerllinsbeard\u002Fmerlin-CTO\u002Fblob\u002Fmain\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7B3S8ENS1XQ7YV3N5GV1PCF","vue-best-practices","Use for Vue 3, .vue files, Vue Router, or Pinia. Skip when the repo has no Vue.","https:\u002F\u002Fgithub.com\u002Fmerllinsbeard\u002Fmerlin-CTO\u002Fblob\u002Fmain\u002Fskills\u002Fweb-development\u002Fvue-best-practices\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7B3S2DPXMQN0EFFE8FTF03R","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Fmerllinsbeard\u002Fmerlin-CTO\u002Fblob\u002Fmain\u002Fskills\u002Fweb-development\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7B3S06K4AGG5X59TCX900R6","tailwind-v4","Use when writing or reviewing Tailwind CSS v4 classes or migrating v3 syntax.","https:\u002F\u002Fgithub.com\u002Fmerllinsbeard\u002Fmerlin-CTO\u002Fblob\u002Fmain\u002Fskills\u002Fweb-development\u002Ftailwind-v4\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M7B3RXNDDCPJ7K5303BXXDTV","react-best-practices","Mastra React subset only. Generic React or Next uses vercel-react-best-practices.","https:\u002F\u002Fgithub.com\u002Fmerllinsbeard\u002Fmerlin-CTO\u002Fblob\u002Fmain\u002Fskills\u002Fweb-development\u002Freact-best-practices\u002FSKILL.md",[],[]]