[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CAVQJMDPASVBR7DXB44EQV":3,"skill-same:01M7CAVQJMDPASVBR7DXB44EQV":52},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7CAVQJMDPASVBR7DXB44EQV","insforge-debug",null,"Use when diagnosing problems in an InsForge project — reactive failures (SDK error object, HTTP 4xx\u002F5xx, gateway timeout 502\u002F503\u002F504, edge function failure or timeout, login\u002FOAuth\u002Fauth errors, RLS denial, realtime channel issues, slow query on one endpoint, edge function or Vercel deploy failure), proactive audits (security\u002FRLS review, performance\u002Findex review, system health check, pre-launch readiness), or when the user has an error but doesn't know where to start.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Finsforge-agent-skills\u002Finsforge-debug\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: insforge-debug\ndescription: >-\n  Use when diagnosing problems in an InsForge project — reactive failures (SDK\n  error object, HTTP 4xx\u002F5xx, gateway timeout 502\u002F503\u002F504, edge function failure\n  or timeout, login\u002FOAuth\u002Fauth errors, RLS denial, realtime channel issues,\n  slow query on one endpoint, edge function or Vercel deploy failure), proactive\n  audits (security\u002FRLS review, performance\u002Findex review, system health check,\n  pre-launch readiness), or when the user has an error but doesn't know where\n  to start.\nlicense: Apache-2.0\n---\n\n# InsForge Debug\n\nDiagnose problems in InsForge projects by combining the backend's observability primitives — logs, metrics, db-health, advisor, policies, metadata, error objects, deploy state, and AI assist. This skill provides:\n\n1. A reference per **debug primitive** (one observability surface each — under `references\u002F`)\n2. **Symptom Recipes** (below) that name the primitive sequence for known reactive symptoms and proactive audits\n\n**Always use `npx @insforge\u002Fcli`** — never install the CLI globally.\n\n## Fastest Path: AI-Assisted Triage\n\nWhen the user gives a concrete description (error message, failing URL, HTTP status), hand it to the InsForge debug agent. Unlike the other primitives, this one returns suggestions, not just observations — verify the diagnosis against the primitives it cites before acting on it.\n\n```bash\nnpx @insforge\u002Fcli diagnose --ai \"\u003Cissue description>\"\n```\n\nSee [references\u002Fai-assisted.md](references\u002Fai-assisted.md) for when to use this first vs when to skip, and how to verify the output.\n\n## Debug Primitives\n\nEach primitive is one independently-queryable observability surface backed by a distinct underlying data source. Real diagnoses are compositions of primitives.\n\nAll commands run via `npx @insforge\u002Fcli ...`. The `(command)` shown next to each primitive is the actual CLI command — primitive names are concept labels, **not** CLI subcommand names (e.g., \"DB health\" is `diagnose db`, not `diagnose db-health`; \"Policies\" is `db policies`, not `diagnose policies`).\n\n| Primitive (command) | What you see | Reference |\n|---------------------|-------------|-----------|\n| **Logs** (`logs \u003Csource>`; `diagnose logs` for cross-source aggregate) | Time-stream of events from 5 backend sources (`insforge.logs` \u002F `postgREST.logs` \u002F `postgres.logs` \u002F `function.logs` \u002F `function-deploy.logs`) | [references\u002Flogs.md](references\u002Flogs.md) |\n| **Metrics** (`diagnose metrics`) | EC2 instance time-series (CPU \u002F memory \u002F disk \u002F network) over `1h` \u002F `6h` \u002F `24h` \u002F `7d` | [references\u002Fmetrics.md](references\u002Fmetrics.md) |\n| **DB health** (`diagnose db`) | Current Postgres state via 7 named checks (`connections` \u002F `slow-queries` \u002F `bloat` \u002F `size` \u002F `index-usage` \u002F `locks` \u002F `cache-hit`) | [references\u002Fdb-health.md](references\u002Fdb-health.md) |\n| **Advisor** (`diagnose advisor --json`) | Static-scan issues across 3 categories (`security` \u002F `performance` \u002F `health`) with `ruleId` \u002F `affectedObject` \u002F `recommendation` | [references\u002Fadvisor.md](references\u002Fadvisor.md) |\n| **Policies** (`db policies`) | Active RLS rules from `pg_policies` (USING \u002F WITH CHECK per cmd per role) — returns all policies as a dump | [references\u002Fpolicies.md](references\u002Fpolicies.md) |\n| **Metadata** (`metadata --json`) | Declarative backend state dump (auth config \u002F tables \u002F buckets \u002F functions \u002F AI models \u002F realtime channels) | [references\u002Fmetadata.md](references\u002Fmetadata.md) |\n| **Error objects** (no command — read SDK \u002F HTTP response) | SDK error envelope + HTTP status — the routing table from a client-visible error to the right log source | [references\u002Ferror-objects.md](references\u002Ferror-objects.md) |\n| **Deploy state** (`deployments list` + `deployments status \u003Cid> --json` + `logs function-deploy.logs`) | Frontend (Vercel) deployment history + per-deploy metadata, plus edge function deploy logs | [references\u002Fdeploy-state.md](references\u002Fdeploy-state.md) |\n| **AI assist** (`diagnose --ai \"\u003Cdescription>\"`) | LLM agent that combines the other primitives — returns a diagnosis with suggestions | [references\u002Fai-assisted.md](references\u002Fai-assisted.md) |\n\n## Symptom Recipes\n\nEach recipe is a primitive call sequence with one-line \"look for X\" at each step. Command syntax, flags, and deep interpretation are in the per-primitive references above.\n\n### Recipe: SDK returned `{ data: null, error: { code, message } }`\n\n1. **error-objects** — read code\u002Fmessage\u002Fdetails. If code starts with `PGRST*`, route by prefix using the table in the reference.\n2. **logs** (matching source per error-objects routing) — find the error timestamp, get the full backend-side context.\n3. **db-health** (`connections`, `locks`, `slow-queries`) — only if the error suggests DB issue (PostgREST timeout, lock conflict).\n\n### Recipe: HTTP 4xx\u002F5xx response on a specific request\n\n1. **error-objects** — use the HTTP status routing table to pick the log source (each status has a distinct path; 429 is special).\n2. **logs** (right source for that status) — find the failing request line and error.\n3. **metrics** — only for 5xx patterns spanning multiple endpoints, to confirm system-wide load issue.\n\n### Recipe: RLS access issue (403 on write, or empty result on read)\n\n> Same bug, two surfacings. Writes (INSERT \u002F UPDATE \u002F DELETE) fail loudly with **403**. Reads (SELECT) fail silently with an **empty array** — PostgREST filters denied rows out instead of returning 403, so the request looks successful with zero rows. Diagnosis path is the same except step 1 only applies to the 403 variant.\n\n1. **logs** (`postgREST.logs`) — *403 variant only*: find the policy violation event with table and role context. *Empty-result variant*: skip — no error is logged for silently-filtered rows.\n2. **policies** — list policies for that table; walk USING \u002F WITH CHECK against the actual request and the JWT claim used.\n3. **metadata** — verify auth config (which claim feeds `auth.uid()` \u002F `requesting_user_id()`; for third-party auth like Clerk\u002FAuth0, is the provider registered as a JWT issuer?).\n4. **db query** (`db query \"\u003Csql>\"`) — *empty-result variant only*: confirm rows that *should* be visible actually exist by querying as service role (not as the user): `npx @insforge\u002Fcli db query \"SELECT id, user_id FROM \u003Ctable>\"`. Distinguishes \"RLS filtered everything\" from \"no matching data exists\".\n\n### Recipe: Login fails \u002F OAuth callback errors \u002F token expired\n\n1. **logs** (`insforge.logs`) — find auth errors with timestamp and provider context.\n2. **metadata** — verify the provider is enabled, redirect URLs match the callback URL exactly (protocol + host + path).\n\n### Recipe: Edge function runtime error \u002F timeout\n\n1. **logs** (`function.logs`) — get the error stack and execution context.\n2. **metadata** — confirm the function exists and `status: \"active\"`.\n3. (If needed) `npx @insforge\u002Fcli functions code \u003Cslug>` — inspect the source for obvious issues.\n\n### Recipe: `functions deploy` failed\n\n1. **deploy-state** (`function-deploy.logs`) — find the build\u002Fpush error.\n2. **metadata** — confirm whether the function ended up in the active list (partial-deploy detection).\n\n### Recipe: `deployments deploy` failed (Vercel)\n\n1. **deploy-state** (`deployments list` + `status \u003Cid> --json`) — read `status`, `metadata.webhookEventType`, and `envVarKeys`.\n2. **Local** `npm run build` — reproduce the same error locally for faster iteration.\n\n### Recipe: Single slow query \u002F one endpoint slow\n\n1. **logs** (`postgres.logs`) — find the query text and timestamp.\n2. **db-health** (`slow-queries`, `index-usage`) — confirm it's in `pg_stat_statements`; check for missing index.\n3. **policies** — if it's an RLS-gated table, verify the policy isn't adding hidden joins.\n\n### Recipe: All responses slow \u002F high CPU\u002Fmemory (active incident)\n\n1. **metrics** (`--range 1h`) — confirm system-wide pressure (CPU \u002F memory \u002F disk).\n2. **db-health** — DB is the most common bottleneck; check `connections`, `locks`, `slow-queries`.\n3. **logs** (`diagnose logs` aggregate) — error patterns across sources at the spike timestamp.\n4. **advisor** (`--severity critical`) — pre-existing known issues that may explain the degradation.\n\n### Recipe: Realtime channel won't connect \u002F messages missing\n\n1. **logs** (`insforge.logs`) — WebSocket errors and subscription failures.\n2. **metadata** — verify the channel pattern matches what the client subscribes to, `enabled: true`.\n3. **policies** — RLS on the underlying table (realtime delivers row changes; RLS gates which rows the subscriber sees).\n\n### Recipe: 429 rate limit\n\n1. **error-objects** — confirm 429 status. **No logs are recorded for 429s; no `Retry-After` header is returned.** Don't waste time grepping logs.\n2. **metrics** (`--range 1h`) — overall backend load context.\n3. **Fix is always client-side**: debounce, batch, exponential backoff, eliminate retry loops.\n\n### Recipe: Gateway timeout (502 \u002F 503 \u002F 504) on a specific URL\n\nRoute by URL subsystem before drilling:\n\n| URL pattern | Drill into |\n|-------------|-----------|\n| `\u002Fapi\u002Fdatabase\u002Frecords\u002F...` | **logs** (`postgREST.logs` → `postgres.logs`) + **db-health** (`locks`, `slow-queries`) |\n| `\u002Ffunctions\u002F\u003Cslug>` | **logs** (`function.logs`) — function may be crash-looping |\n| `\u002Fapi\u002Fauth\u002F...` | **logs** (`insforge.logs`) |\n| Any path during system-wide spike | **metrics** (`--range 1h`) |\n\n### Recipe: Pre-launch \u002F proactive audit\n\n> Requires Platform login (`npx @insforge\u002Fcli login`). **Not available when the project is linked via `--api-key`** — fall back to `db-health` + `policies` + `metadata` for a manual audit in that case.\n\n1. **advisor** — full scan, then `--severity critical` first, then warnings.\n2. **advisor** (`--category security`) — focus on security issues; cross-verify with **policies** (RLS coverage) and **metadata** (auth config, public buckets, secret presence).\n3. **advisor** (`--category performance`) — cross-verify with **db-health** (`slow-queries`, `index-usage`, `bloat`).\n4. **advisor** (`--category health`) — cross-verify with **metrics** (resource trends over `7d`).\n5. After fixes, re-run **advisor** and confirm `isResolved: true` for each addressed `ruleId`.\n\n### Recipe: Don't know where to start\n\n1. **ai-assisted** (`diagnose --ai \"\u003Cerror or URL>\"`) — get a starting hypothesis.\n2. **Verify** by re-checking the primitives the diagnosis names. Trust the primitive observations over the suggestion.\n","# InsForge Debug\n\nDiagnose problems in InsForge projects by combining the backend's observability primitives — logs, metrics, db-health, advisor, policies, metadata, error objects, deploy state, and AI assist. This skill provides:\n\n1. A reference per **debug primitive** (one observability surface each — under `references\u002F`)\n2. **Symptom Recipes** (below) that name the primitive sequence for known reactive symptoms and proactive audits\n\n**Always use `npx @insforge\u002Fcli`** — never install the CLI globally.\n\n## Fastest Path: AI-Assisted Triage\n\nWhen the user gives a concrete description (error message, failing URL, HTTP status), hand it to the InsForge debug agent. Unlike the other primitives, this one returns suggestions, not just observations — verify the diagnosis against the primitives it cites before acting on it.\n\n```bash\nnpx @insforge\u002Fcli diagnose --ai \"\u003Cissue description>\"\n```\n\nSee [references\u002Fai-assisted.md](references\u002Fai-assisted.md) for when to use this first vs when to skip, and how to verify the output.\n\n## Debug Primitives\n\nEach primitive is one independently-queryable observability surface backed by a distinct underlying data source. Real diagnoses are compositions of primitives.\n\nAll commands run via `npx @insforge\u002Fcli ...`. The `(command)` shown next to each primitive is the actual CLI command — primitive names are concept labels, **not** CLI subcommand names (e.g., \"DB health\" is `diagnose db`, not `diagnose db-health`; \"Policies\" is `db policies`, not `diagnose policies`).\n\n| Primitive (command) | What you see | Reference |\n|---------------------|-------------|-----------|\n| **Logs** (`logs \u003Csource>`; `diagnose logs` for cross-source aggregate) | Time-stream of events from 5 backend sources (`insforge.logs` \u002F `postgREST.logs` \u002F `postgres.logs` \u002F `function.logs` \u002F `function-deploy.logs`) | [references\u002Flogs.md](references\u002Flogs.md) |\n| **Metrics** (`diagnose metrics`) | EC2 instance time-series (CPU \u002F memory \u002F disk \u002F network) over `1h` \u002F `6h` \u002F `24h` \u002F `7d` | [references\u002Fmetrics.md](references\u002Fmetrics.md) |\n| **DB health** (`diagnose db`) | Current Postgres state via 7 named checks (`connections` \u002F `slow-queries` \u002F `bloat` \u002F `size` \u002F `index-usage` \u002F `locks` \u002F `cache-hit`) | [references\u002Fdb-health.md](references\u002Fdb-health.md) |\n| **Advisor** (`diagnose advisor --json`) | Static-scan issues across 3 categories (`security` \u002F `performance` \u002F `health`) with `ruleId` \u002F `affectedObject` \u002F `recommendation` | [references\u002Fadvisor.md](references\u002Fadvisor.md) |\n| **Policies** (`db policies`) | Active RLS rules from `pg_policies` (USING \u002F WITH CHECK per cmd per role) — returns all policies as a dump | [references\u002Fpolicies.md](references\u002Fpolicies.md) |\n| **Metadata** (`metadata --json`) | Declarative backend state dump (auth config \u002F tables \u002F buckets \u002F functions \u002F AI models \u002F realtime channels) | [references\u002Fmetadata.md](references\u002Fmetadata.md) |\n| **Error objects** (no command — read SDK \u002F HTTP response) | SDK error envelope + HTTP status — the routing table from a client-visible error to the right log source | [references\u002Ferror-objects.md](references\u002Ferror-objects.md) |\n| **Deploy state** (`deployments list` + `deployments status \u003Cid> --json` + `logs function-deploy.logs`) | Frontend (Vercel) deployment history + per-deploy metadata, plus edge function deploy logs | [references\u002Fdeploy-state.md](references\u002Fdeploy-state.md) |\n| **AI assist** (`diagnose --ai \"\u003Cdescription>\"`) | LLM agent that combines the other primitives — returns a diagnosis with suggestions | [references\u002Fai-assisted.md](references\u002Fai-assisted.md) |\n\n## Symptom Recipes\n\nEach recipe is a primitive call sequence with one-line \"look for X\" at each step. Command syntax, flags, and deep interpretation are in the per-primitive references above.\n\n### Recipe: SDK returned `{ data: null, error: { code, message } }`\n\n1. **error-objects** — read code\u002Fmessage\u002Fdetails. If code starts with `PGRST*`, route by prefix using the table in the reference.\n2. **logs** (matching source per error-objects routing) — find the error timestamp, get the full backend-side context.\n3. **db-health** (`connections`, `locks`, `slow-queries`) — only if the error suggests DB issue (PostgREST timeout, lock conflict).\n\n### Recipe: HTTP 4xx\u002F5xx response on a specific request\n\n1. **error-objects** — use the HTTP status routing table to pick the log source (each status has a distinct path; 429 is special).\n2. **logs** (right source for that status) — find the failing request line and error.\n3. **metrics** — only for 5xx patterns spanning multiple endpoints, to confirm system-wide load issue.\n\n### Recipe: RLS access issue (403 on write, or empty result on read)\n\n> Same bug, two surfacings. Writes (INSERT \u002F UPDATE \u002F DELETE) fail loudly with **403**. Reads (SELECT) fail silently with an **empty array** — PostgREST filters denied rows out instead of returning 403, so the request looks successful with zero rows. Diagnosis path is the same except step 1 only applies to the 403 variant.\n\n1. **logs** (`postgREST.logs`) — *403 variant only*: find the policy violation event with table and role context. *Empty-result variant*: skip — no error is logged for silently-filtered rows.\n2. **policies** — list policies for that table; walk USING \u002F WITH CHECK against the actual request and the JWT claim used.\n3. **metadata** — verify auth config (which claim feeds `auth.uid()` \u002F `requesting_user_id()`; for third-party auth like Clerk\u002FAuth0, is the provider registered as a JWT issuer?).\n4. **db query** (`db query \"\u003Csql>\"`) — *empty-result variant only*: confirm rows that *should* be visible actually exist by querying as service role (not as the user): `npx @insforge\u002Fcli db query \"SELECT id, user_id FROM \u003Ctable>\"`. Distinguishes \"RLS filtered everything\" from \"no matching data exists\".\n\n### Recipe: Login fails \u002F OAuth callback errors \u002F token expired\n\n1. **logs** (`insforge.logs`) — find auth errors with timestamp and provider context.\n2. **metadata** — verify the provider is enabled, redirect URLs match the callback URL exactly (protocol + host + path).\n\n### Recipe: Edge function runtime error \u002F timeout\n\n1. **logs** (`function.logs`) — get the error stack and execution context.\n2. **metadata** — confirm the function exists and `status: \"active\"`.\n3. (If needed) `npx @insforge\u002Fcli functions code \u003Cslug>` — inspect the source for obvious issues.\n\n### Recipe: `functions deploy` failed\n\n1. **deploy-state** (`function-deploy.logs`) — find the build\u002Fpush error.\n2. **metadata** — confirm whether the function ended up in the active list (partial-deploy detection).\n\n### Recipe: `deployments deploy` failed (Vercel)\n\n1. **deploy-state** (`deployments list` + `status \u003Cid> --json`) — read `status`, `metadata.webhookEventType`, and `envVarKeys`.\n2. **Local** `npm run build` — reproduce the same error locally for faster iteration.\n\n### Recipe: Single slow query \u002F one endpoint slow\n\n1. **logs** (`postgres.logs`) — find the query text and timestamp.\n2. **db-health** (`slow-queries`, `index-usage`) — confirm it's in `pg_stat_statements`; check for missing index.\n3. **policies** — if it's an RLS-gated table, verify the policy isn't adding hidden joins.\n\n### Recipe: All responses slow \u002F high CPU\u002Fmemory (active incident)\n\n1. **metrics** (`--range 1h`) — confirm system-wide pressure (CPU \u002F memory \u002F disk).\n2. **db-health** — DB is the most common bottleneck; check `connections`, `locks`, `slow-queries`.\n3. **logs** (`diagnose logs` aggregate) — error patterns across sources at the spike timestamp.\n4. **advisor** (`--severity critical`) — pre-existing known issues that may explain the degradation.\n\n### Recipe: Realtime channel won't connect \u002F messages missing\n\n1. **logs** (`insforge.logs`) — WebSocket errors and subscription failures.\n2. **metadata** — verify the channel pattern matches what the client subscribes to, `enabled: true`.\n3. **policies** — RLS on the underlying table (realtime delivers row changes; RLS gates which rows the subscriber sees).\n\n### Recipe: 429 rate limit\n\n1. **error-objects** — confirm 429 status. **No logs are recorded for 429s; no `Retry-After` header is returned.** Don't waste time grepping logs.\n2. **metrics** (`--range 1h`) — overall backend load context.\n3. **Fix is always client-side**: debounce, batch, exponential backoff, eliminate retry loops.\n\n### Recipe: Gateway timeout (502 \u002F 503 \u002F 504) on a specific URL\n\nRoute by URL subsystem before drilling:\n\n| URL pattern | Drill into |\n|-------------|-----------|\n| `\u002Fapi\u002Fdatabase\u002Frecords\u002F...` | **logs** (`postgREST.logs` → `postgres.logs`) + **db-health** (`locks`, `slow-queries`) |\n| `\u002Ffunctions\u002F\u003Cslug>` | **logs** (`function.logs`) — function may be crash-looping |\n| `\u002Fapi\u002Fauth\u002F...` | **logs** (`insforge.logs`) |\n| Any path during system-wide spike | **metrics** (`--range 1h`) |\n\n### Recipe: Pre-launch \u002F proactive audit\n\n> Requires Platform login (`npx @insforge\u002Fcli login`). **Not available when the project is linked via `--api-key`** — fall back to `db-health` + `policies` + `metadata` for a manual audit in that case.\n\n1. **advisor** — full scan, then `--severity critical` first, then warnings.\n2. **advisor** (`--category security`) — focus on security issues; cross-verify with **policies** (RLS coverage) and **metadata** (auth config, public buckets, secret presence).\n3. **advisor** (`--category performance`) — cross-verify with **db-health** (`slow-queries`, `index-usage`, `bloat`).\n4. **advisor** (`--category health`) — cross-verify with **metrics** (resource trends over `7d`).\n5. After fixes, re-run **advisor** and confirm `isResolved: true` for each addressed `ruleId`.\n\n### Recipe: Don't know where to start\n\n1. **ai-assisted** (`diagnose --ai \"\u003Cerror or URL>\"`) — get a starting hypothesis.\n2. **Verify** by re-checking the primitives the diagnosis names. Trust the primitive observations over the suggestion.\n",{"name":5,"license":15,"description":7},"main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Finsforge-agent-skills\u002Finsforge-debug",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":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill insforge-debug",{"tool":38,"command":39},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill insforge-debug",{"tool":41,"command":42},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill insforge-debug","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Finsforge-agent-skills\u002Finsforge-debug\u002FSkill.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"metadata.json","REFERENCE","参考文档",447,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Finsforge-agent-skills\u002Finsforge-debug\u002Fmetadata.json",[53,61,66,73,78,85],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":62,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]