[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BTE45S7ZG56JFGFBKT23EB":3,"skill-same:01M7BTE45S7ZG56JFGFBKT23EB":54},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7BTE45S7ZG56JFGFBKT23EB","browser-to-api",null,"Turn a website's observable HTTP traffic into a best-effort OpenAPI 3.1 spec by analyzing a `browser-trace` capture. Use when the user wants to discover\u002Fextract API endpoints from a browser session, build an OpenAPI doc from network traffic, or document a third-party site's XHR\u002Ffetch surface for client integration.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fbrowserbase-skills\u002Fbrowser-to-api\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: browser-to-api\ndescription: Turn a website's observable HTTP traffic into a best-effort OpenAPI 3.1 spec by analyzing a `browser-trace` capture. Use when the user wants to discover\u002Fextract API endpoints from a browser session, build an OpenAPI doc from network traffic, or document a third-party site's XHR\u002Ffetch surface for client integration.\ncompatibility: \"Requires Node 18+ and a `browser-trace` run directory (`.o11y\u002F\u003Crun>\u002F`) produced by the sibling `browser-trace` skill. The scripts use only the Node standard library — no `npm install` step. `jq` is referenced in docs for ad-hoc querying but is not required by the scripts.\"\nlicense: MIT\nallowed-tools: Bash, Read, Grep\n---\n\n# Browser to API\n\nReplay-driven API discovery. Consume a `browser-trace` capture, pair its CDP request \u002F response events, templatize observed URLs, infer JSON schemas from samples, and emit an **OpenAPI 3.1** document plus a human-readable coverage report.\n\nThis skill **does not capture traffic**. It is purely offline post-processing on top of `browser-trace`'s `cdp\u002Fnetwork\u002F*.jsonl` buckets. The two skills compose:\n\n```\nbrowser-trace    →  .o11y\u002F\u003Crun>\u002Fcdp\u002Fnetwork\u002F{requests,responses}.jsonl\nbrowser-to-api   →  .o11y\u002F\u003Crun>\u002Fapi-spec\u002Findex.html + openapi.yaml + client.mjs\n```\n\n## When to use\n\n- The user wants an OpenAPI document for a third-party or undocumented website API.\n- The user has a `browser-trace` run and wants endpoints + schemas extracted from it.\n- The user is building a client\u002FSDK against a site that doesn't publish a spec.\n- The user wants a coverage report showing which flows would broaden the spec.\n\nIf the user wants to **capture** traffic, send them to `browser-trace` first.\n\n## Two-step workflow\n\n### 1. Capture with `browser-trace` (and optionally bodies via `browse network on`)\n\n```bash\n# Local example against an existing debuggable Chrome target\nTARGET=9222\n\nnode ..\u002Fbrowser-trace\u002Fscripts\u002Fstart-capture.mjs \"$TARGET\" my-site\nbrowse open about:blank --cdp \"$TARGET\"\nbrowse network on                                    # capture request\u002Fresponse bodies\nbrowse open https:\u002F\u002Fexample.com\n# ...drive whatever flows you want covered...\n\n# Snapshot the bodies dir BEFORE turning capture off (the temp dir is shared\n# per-session, so subsequent `browse network on` runs would mix your bodies\n# with whatever a future capture writes if you skip this step).\ncp -r \"$(browse network path | jq -r .path)\" .o11y\u002Fmy-site\u002Fcdp\u002Fnetwork\u002Fbodies\u002F\nbrowse network off\n\nnode ..\u002Fbrowser-trace\u002Fscripts\u002Fstop-capture.mjs my-site\nnode ..\u002Fbrowser-trace\u002Fscripts\u002Fbisect-cdp.mjs my-site\n```\n\n`browse network on` is **optional but strongly recommended** — without it, the spec has no response-body schemas (the CDP firehose used by `browse cdp` does not embed bodies). With it, both request bodies (already captured by CDP) *and* response bodies are joined into the trace by CDP `requestId`.\n\n### 2. Generate the spec\n\n```bash\nnode scripts\u002Fdiscover.mjs --run .o11y\u002Fmy-site\n# → .o11y\u002Fmy-site\u002Fapi-spec\u002Findex.html          ← open this\n#   .o11y\u002Fmy-site\u002Fapi-spec\u002Fclient.mjs\n#   .o11y\u002Fmy-site\u002Fapi-spec\u002Fopenapi.yaml\n#   .o11y\u002Fmy-site\u002Fapi-spec\u002Fopenapi.json\n#   .o11y\u002Fmy-site\u002Fapi-spec\u002Freport.md\n#   .o11y\u002Fmy-site\u002Fapi-spec\u002Fconfidence.json\n#   .o11y\u002Fmy-site\u002Fapi-spec\u002Fsamples\u002F*.json\n#   .o11y\u002Fmy-site\u002Fapi-spec\u002Fintermediate\u002F*.jsonl\n```\n\n`discover.mjs` auto-detects `\u003Crun>\u002Fcdp\u002Fnetwork\u002Fbodies\u002F`. To use a body capture from elsewhere (e.g. didn't snapshot, want the live `browse network` dir), pass `--bodies \u003Cpath>` explicitly.\n\n### 3. Open the HTML report\n\nAfter `discover.mjs` finishes, **always open the generated HTML report**:\n\n```bash\nopen .o11y\u002Fmy-site\u002Fapi-spec\u002Findex.html\n```\n\nThe report is a self-contained HTML file (no server needed) that shows each discovered operation as an expandable card with variables, client usage, request\u002Fresponse examples, and a generated `client.mjs` snippet at the bottom. This is the primary deliverable — always open it for the user.\n\n## CLI flags\n\n| Flag | Required | Meaning |\n|---|---|---|\n| `--run \u003Cpath>` | yes | Path to a `browser-trace` run directory |\n| `--out \u003Cpath>` | no | Output dir; default `\u003Crun>\u002Fapi-spec\u002F` |\n| `--bodies \u003Cpath>` | no | `browse network` capture dir to join into the trace (auto-detected from `\u003Crun>\u002Fcdp\u002Fnetwork\u002Fbodies\u002F` when present) |\n| `--include \u003Cregex>` | no | Only include URLs matching regex (repeatable) |\n| `--exclude \u003Cregex>` | no | Exclude URLs matching regex (repeatable; in addition to defaults) |\n| `--origins \u003Clist>` | no | Comma-separated origin allow-list (e.g. `api.example.com,example.com`) |\n| `--format \u003Cyaml\\|json\\|both>` | no | Output format. Default `both` |\n| `--title \u003Cstring>` | no | OpenAPI `info.title`. Default derived from primary origin |\n| `--redact \u003Clist>` | no | Extra header names \u002F JSON keys to redact (comma-separated) |\n| `--min-samples \u003Cn>` | no | Minimum samples per endpoint to include. Default `1` |\n| `--stage \u003Cname>` | no | Run only one stage: `load`, `filter`, `normalize`, `infer`, `emit` |\n\n\n## Output layout\n\n```\n\u003Crun>\u002Fapi-spec\u002F\n├── index.html                visual report — open this (self-contained, no server)\n├── client.mjs                zero-dep fetch client with typed functions per operation\n├── openapi.yaml              machine-readable spec\n├── openapi.json              mirror\n├── report.md                 markdown summary + curl examples\n├── confidence.json           per-endpoint confidence + normalization flags\n├── samples\u002F                  redacted request\u002Fresponse examples\n│   └── \u003Cmethod>__\u003Cpath-hash>.json\n└── intermediate\u002F             pipeline byproducts (paired\u002Ffiltered\u002Fendpoints jsonl)\n```\n\n## What you get from `browse cdp` and `browse network`\n\nTwo complementary capture sources:\n\n| Source | Provides | Limitation |\n|---|---|---|\n| `browse cdp` (used by `browser-trace`) | request method\u002FURL\u002Fheaders\u002F`postData`, response status\u002Fheaders\u002FmimeType, full event timing | **Does not embed response bodies.** Bodies must be pulled with `Network.getResponseBody`, which the firehose doesn't do. |\n| `browse network on` (separate command) | request bodies AND response bodies on disk, keyed by CDP `requestId` | Capture dir is shared per `browse` session; snapshot before another `browse network on` overwrites it. |\n\n`discover.mjs` will pull bodies from a `browse network` dir if you pass `--bodies \u003Cpath>` (or stash them under `\u003Crun>\u002Fcdp\u002Fnetwork\u002Fbodies\u002F`, which is auto-detected). The matching is by `requestId` — `browse network` writes that into each `request.json` as `id`, and we join directly.\n\nWhat changes when bodies are present:\n\n- ✅ Path templating, query-param schemas, status codes, content-types — same either way.\n- ✅ Request-body schemas — `postData` from CDP is enough; bodies dir is a nice-to-have for non-`postData` cases.\n- ✅ **Response-body schemas** — fully inferred from real samples. Without bodies you get `{ description, content: \u003CmimeType> }` skeletons.\n\nThe report flags every endpoint that has no response-body sample.\n\n## Automatic noise filtering\n\nThe normalize stage automatically classifies and drops infrastructure noise:\n\n- **Tracking \u002F analytics** — paths containing `\u002Ftrack`, `\u002Fpixel`, `\u002Fbeacon`, `\u002Fimpression`, `\u002Fpageview`, `\u002Fdag\u002Fv*`\n- **Bot defense** — Akamai (`\u002Fakam\u002F`), fingerprint payloads (`sensor_data`), obfuscated multi-segment paths\n- **Session plumbing** — `\u002Fsession`, `\u002Fauthenticate\u002Fstart`, cookie consent, A\u002FB experiment endpoints\n- **HTML page renders** — `GET` requests returning `text\u002Fhtml` (the rendered page, not the API)\n\nThis typically drops 60-80% of captured traffic. The `--include` flag can rescue a false positive.\n\n## GraphQL \u002F multiplexed endpoint decomposition\n\nWhen a single endpoint (like `\u002Fdapi\u002Ffe\u002Fgql`) is called with different `operationName` values, the skill automatically splits it into separate logical operations. Each gets its own:\n- OpenAPI path entry (e.g. `\u002Fdapi\u002Ffe\u002Fgql [Autocomplete]`)\n- Request\u002Fresponse schema inferred from only that operation's samples\n- Curl example and variables table in the report\n\nDetection works on body fields (`operationName`, `method`, `action`) and query params (`opname`, `op`). This covers GraphQL (APQ and inline), JSON-RPC, and similar dispatch patterns.\n\n## Limitations\n\n- **Coverage is bounded by the captured flow.** Endpoints not exercised in the trace will not appear. The skill cannot prove completeness.\n- **Schemas are inductive, not contractual.** A field might be optional on the server even if every sample contained it.\n- **Auth is observed, not specified.** The skill records auth-shaped headers in an `x-observed-auth` extension but won't claim a security scheme.\n- **Path templating is heuristic.** Numeric \u002F UUID \u002F hex \u002F slug patterns are detected per segment. Ambiguous URLs are flagged in `confidence.json`.\n- **Redaction is best-effort.** Default redactions cover common credentials, but app-specific secrets may slip through; use `--redact` for known custom headers\u002Fkeys.\n\n## Best practices\n\n1. **Drive the flows you want documented.** The richer the browser-trace, the richer the spec.\n2. **Use `--origins` for noisy sites.** A marketing page hits dozens of analytics hosts; restrict to the API origin you care about.\n3. **Inspect `report.md` first.** It has curl-ready examples and response samples for every discovered operation.\n4. **Bump `--min-samples` to 2+** when you want only confidently-shaped endpoints in the final doc — drop the long tail.\n5. **Pair with `browse network on`** when response-body schemas matter. The CDP firehose alone has request bodies but not response bodies.\n\nFor pipeline internals and the file format reference, see [REFERENCE.md](REFERENCE.md).\n","# Browser to API\n\nReplay-driven API discovery. Consume a `browser-trace` capture, pair its CDP request \u002F response events, templatize observed URLs, infer JSON schemas from samples, and emit an **OpenAPI 3.1** document plus a human-readable coverage report.\n\nThis skill **does not capture traffic**. It is purely offline post-processing on top of `browser-trace`'s `cdp\u002Fnetwork\u002F*.jsonl` buckets. The two skills compose:\n\n```\nbrowser-trace    →  .o11y\u002F\u003Crun>\u002Fcdp\u002Fnetwork\u002F{requests,responses}.jsonl\nbrowser-to-api   →  .o11y\u002F\u003Crun>\u002Fapi-spec\u002Findex.html + openapi.yaml + client.mjs\n```\n\n## When to use\n\n- The user wants an OpenAPI document for a third-party or undocumented website API.\n- The user has a `browser-trace` run and wants endpoints + schemas extracted from it.\n- The user is building a client\u002FSDK against a site that doesn't publish a spec.\n- The user wants a coverage report showing which flows would broaden the spec.\n\nIf the user wants to **capture** traffic, send them to `browser-trace` first.\n\n## Two-step workflow\n\n### 1. Capture with `browser-trace` (and optionally bodies via `browse network on`)\n\n```bash\n# Local example against an existing debuggable Chrome target\nTARGET=9222\n\nnode ..\u002Fbrowser-trace\u002Fscripts\u002Fstart-capture.mjs \"$TARGET\" my-site\nbrowse open about:blank --cdp \"$TARGET\"\nbrowse network on                                    # capture request\u002Fresponse bodies\nbrowse open https:\u002F\u002Fexample.com\n# ...drive whatever flows you want covered...\n\n# Snapshot the bodies dir BEFORE turning capture off (the temp dir is shared\n# per-session, so subsequent `browse network on` runs would mix your bodies\n# with whatever a future capture writes if you skip this step).\ncp -r \"$(browse network path | jq -r .path)\" .o11y\u002Fmy-site\u002Fcdp\u002Fnetwork\u002Fbodies\u002F\nbrowse network off\n\nnode ..\u002Fbrowser-trace\u002Fscripts\u002Fstop-capture.mjs my-site\nnode ..\u002Fbrowser-trace\u002Fscripts\u002Fbisect-cdp.mjs my-site\n```\n\n`browse network on` is **optional but strongly recommended** — without it, the spec has no response-body schemas (the CDP firehose used by `browse cdp` does not embed bodies). With it, both request bodies (already captured by CDP) *and* response bodies are joined into the trace by CDP `requestId`.\n\n### 2. Generate the spec\n\n```bash\nnode scripts\u002Fdiscover.mjs --run .o11y\u002Fmy-site\n# → .o11y\u002Fmy-site\u002Fapi-spec\u002Findex.html          ← open this\n#   .o11y\u002Fmy-site\u002Fapi-spec\u002Fclient.mjs\n#   .o11y\u002Fmy-site\u002Fapi-spec\u002Fopenapi.yaml\n#   .o11y\u002Fmy-site\u002Fapi-spec\u002Fopenapi.json\n#   .o11y\u002Fmy-site\u002Fapi-spec\u002Freport.md\n#   .o11y\u002Fmy-site\u002Fapi-spec\u002Fconfidence.json\n#   .o11y\u002Fmy-site\u002Fapi-spec\u002Fsamples\u002F*.json\n#   .o11y\u002Fmy-site\u002Fapi-spec\u002Fintermediate\u002F*.jsonl\n```\n\n`discover.mjs` auto-detects `\u003Crun>\u002Fcdp\u002Fnetwork\u002Fbodies\u002F`. To use a body capture from elsewhere (e.g. didn't snapshot, want the live `browse network` dir), pass `--bodies \u003Cpath>` explicitly.\n\n### 3. Open the HTML report\n\nAfter `discover.mjs` finishes, **always open the generated HTML report**:\n\n```bash\nopen .o11y\u002Fmy-site\u002Fapi-spec\u002Findex.html\n```\n\nThe report is a self-contained HTML file (no server needed) that shows each discovered operation as an expandable card with variables, client usage, request\u002Fresponse examples, and a generated `client.mjs` snippet at the bottom. This is the primary deliverable — always open it for the user.\n\n## CLI flags\n\n| Flag | Required | Meaning |\n|---|---|---|\n| `--run \u003Cpath>` | yes | Path to a `browser-trace` run directory |\n| `--out \u003Cpath>` | no | Output dir; default `\u003Crun>\u002Fapi-spec\u002F` |\n| `--bodies \u003Cpath>` | no | `browse network` capture dir to join into the trace (auto-detected from `\u003Crun>\u002Fcdp\u002Fnetwork\u002Fbodies\u002F` when present) |\n| `--include \u003Cregex>` | no | Only include URLs matching regex (repeatable) |\n| `--exclude \u003Cregex>` | no | Exclude URLs matching regex (repeatable; in addition to defaults) |\n| `--origins \u003Clist>` | no | Comma-separated origin allow-list (e.g. `api.example.com,example.com`) |\n| `--format \u003Cyaml\\|json\\|both>` | no | Output format. Default `both` |\n| `--title \u003Cstring>` | no | OpenAPI `info.title`. Default derived from primary origin |\n| `--redact \u003Clist>` | no | Extra header names \u002F JSON keys to redact (comma-separated) |\n| `--min-samples \u003Cn>` | no | Minimum samples per endpoint to include. Default `1` |\n| `--stage \u003Cname>` | no | Run only one stage: `load`, `filter`, `normalize`, `infer`, `emit` |\n\n\n## Output layout\n\n```\n\u003Crun>\u002Fapi-spec\u002F\n├── index.html                visual report — open this (self-contained, no server)\n├── client.mjs                zero-dep fetch client with typed functions per operation\n├── openapi.yaml              machine-readable spec\n├── openapi.json              mirror\n├── report.md                 markdown summary + curl examples\n├── confidence.json           per-endpoint confidence + normalization flags\n├── samples\u002F                  redacted request\u002Fresponse examples\n│   └── \u003Cmethod>__\u003Cpath-hash>.json\n└── intermediate\u002F             pipeline byproducts (paired\u002Ffiltered\u002Fendpoints jsonl)\n```\n\n## What you get from `browse cdp` and `browse network`\n\nTwo complementary capture sources:\n\n| Source | Provides | Limitation |\n|---|---|---|\n| `browse cdp` (used by `browser-trace`) | request method\u002FURL\u002Fheaders\u002F`postData`, response status\u002Fheaders\u002FmimeType, full event timing | **Does not embed response bodies.** Bodies must be pulled with `Network.getResponseBody`, which the firehose doesn't do. |\n| `browse network on` (separate command) | request bodies AND response bodies on disk, keyed by CDP `requestId` | Capture dir is shared per `browse` session; snapshot before another `browse network on` overwrites it. |\n\n`discover.mjs` will pull bodies from a `browse network` dir if you pass `--bodies \u003Cpath>` (or stash them under `\u003Crun>\u002Fcdp\u002Fnetwork\u002Fbodies\u002F`, which is auto-detected). The matching is by `requestId` — `browse network` writes that into each `request.json` as `id`, and we join directly.\n\nWhat changes when bodies are present:\n\n- ✅ Path templating, query-param schemas, status codes, content-types — same either way.\n- ✅ Request-body schemas — `postData` from CDP is enough; bodies dir is a nice-to-have for non-`postData` cases.\n- ✅ **Response-body schemas** — fully inferred from real samples. Without bodies you get `{ description, content: \u003CmimeType> }` skeletons.\n\nThe report flags every endpoint that has no response-body sample.\n\n## Automatic noise filtering\n\nThe normalize stage automatically classifies and drops infrastructure noise:\n\n- **Tracking \u002F analytics** — paths containing `\u002Ftrack`, `\u002Fpixel`, `\u002Fbeacon`, `\u002Fimpression`, `\u002Fpageview`, `\u002Fdag\u002Fv*`\n- **Bot defense** — Akamai (`\u002Fakam\u002F`), fingerprint payloads (`sensor_data`), obfuscated multi-segment paths\n- **Session plumbing** — `\u002Fsession`, `\u002Fauthenticate\u002Fstart`, cookie consent, A\u002FB experiment endpoints\n- **HTML page renders** — `GET` requests returning `text\u002Fhtml` (the rendered page, not the API)\n\nThis typically drops 60-80% of captured traffic. The `--include` flag can rescue a false positive.\n\n## GraphQL \u002F multiplexed endpoint decomposition\n\nWhen a single endpoint (like `\u002Fdapi\u002Ffe\u002Fgql`) is called with different `operationName` values, the skill automatically splits it into separate logical operations. Each gets its own:\n- OpenAPI path entry (e.g. `\u002Fdapi\u002Ffe\u002Fgql [Autocomplete]`)\n- Request\u002Fresponse schema inferred from only that operation's samples\n- Curl example and variables table in the report\n\nDetection works on body fields (`operationName`, `method`, `action`) and query params (`opname`, `op`). This covers GraphQL (APQ and inline), JSON-RPC, and similar dispatch patterns.\n\n## Limitations\n\n- **Coverage is bounded by the captured flow.** Endpoints not exercised in the trace will not appear. The skill cannot prove completeness.\n- **Schemas are inductive, not contractual.** A field might be optional on the server even if every sample contained it.\n- **Auth is observed, not specified.** The skill records auth-shaped headers in an `x-observed-auth` extension but won't claim a security scheme.\n- **Path templating is heuristic.** Numeric \u002F UUID \u002F hex \u002F slug patterns are detected per segment. Ambiguous URLs are flagged in `confidence.json`.\n- **Redaction is best-effort.** Default redactions cover common credentials, but app-specific secrets may slip through; use `--redact` for known custom headers\u002Fkeys.\n\n## Best practices\n\n1. **Drive the flows you want documented.** The richer the browser-trace, the richer the spec.\n2. **Use `--origins` for noisy sites.** A marketing page hits dozens of analytics hosts; restrict to the API origin you care about.\n3. **Inspect `report.md` first.** It has curl-ready examples and response samples for every discovered operation.\n4. **Bump `--min-samples` to 2+** when you want only confidently-shaped endpoints in the final doc — drop the long tail.\n5. **Pair with `browse network on`** when response-body schemas matter. The CDP firehose alone has request bodies but not response bodies.\n\nFor pipeline internals and the file format reference, see [REFERENCE.md](REFERENCE.md).\n",{"name":5,"license":15,"description":7,"allowed-tools":24,"compatibility":25},"Bash, Read, Grep","Requires Node 18+ and a `browser-trace` run directory (`.o11y\u002F\u003Crun>\u002F`) produced by the sibling `browser-trace` skill. The scripts use only the Node standard library — no `npm install` step. `jq` is referenced in docs for ad-hoc querying but is not required by the scripts.","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fbrowserbase-skills\u002Fbrowser-to-api",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill browser-to-api",{"tool":40,"command":41},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill browser-to-api",{"tool":43,"command":44},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill browser-to-api","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fbrowserbase-skills\u002Fbrowser-to-api\u002FSkill.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"metadata.json","REFERENCE","参考文档",431,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fbrowserbase-skills\u002Fbrowser-to-api\u002Fmetadata.json",[55,62,67,74,79,86],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":63,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"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},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":75,"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":76,"categories":77,"keywords":78,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\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},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":87,"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":88,"categories":89,"keywords":90,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]