[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BV3YD64GDBY6RZ2HX8CANJ":3,"skill-same:01M7BV3YD64GDBY6RZ2HX8CANJ":61},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M7BV3YD64GDBY6RZ2HX8CANJ","datapackage",null,"Explore and query any dataset annotated with a Frictionless Data Package descriptor (datapackage.json). Use this skill whenever a user wants to discover what tables or resources a dataset contains, look up column names and descriptions, surface usage warnings embedded in metadata, or understand how to load data from Parquet files, DuckDB or SQLite databases, or CSV files described by a datapackage.json. Also use when the user has a datapackage.json and wants to know what's in it, how to query it efficiently, or how to connect its metadata to actual data files. Pairs well with dataset-specific skills (like `pudl`) that layer domain knowledge on top.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"CC-BY-4.0","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fcatalyst-cooperative-agent-skills\u002Fdatapackage\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: datapackage\ndescription: >\n  Explore and query any dataset annotated with a Frictionless Data Package descriptor\n  (datapackage.json). Use this skill whenever a user wants to discover what tables or\n  resources a dataset contains, look up column names and descriptions, surface usage\n  warnings embedded in metadata, or understand how to load data from Parquet files,\n  DuckDB or SQLite databases, or CSV files described by a datapackage.json. Also use\n  when the user has a datapackage.json and wants to know what's in it, how to query it\n  efficiently, or how to connect its metadata to actual data files. Pairs well with\n  dataset-specific skills (like `pudl`) that layer domain knowledge on top.\nlicense: CC-BY-4.0\ncompatibility: |\n  Required CLI tools: jq >= 1.7\n  Optional CLI tools: frictionless >= 5.18 (with fastparquet for Parquet support)\n  Required skills: duckdb-skills (install-duckdb, attach-db, query)\n  Optional Python packages: marimo, pandas, polars, duckdb (for DataFrame work)\nmetadata:\n  - author: Catalyst Cooperative\n  - email: hello@catalyst.coop\n  - last-updated: 2026-04-03\n---\n\n# Frictionless Data Package Guide\n\nThis skill covers any dataset described by a\n[Frictionless Data Package](https:\u002F\u002Fdatapackage.org\u002F) descriptor file\n(`datapackage.json`). It is intentionally generic — it works for any conforming\ndatapackage, regardless of who published it or what the data contains.\n\nFor PUDL-specific knowledge (S3 bucket paths, table tier conventions, data source\ncontext, usage warnings), also use the `pudl` skill on top of this one.\n\n## What is a datapackage.json?\n\nA `datapackage.json` is a JSON file that describes a collection of tabular data\nresources. Each resource represents one table (or file) and includes:\n\n- `name`: machine-readable identifier\n- `description`: human-readable description, often including processing notes, primary\n    keys, and usage warnings\n- `path`: filename or URL of the actual data file\n- `schema.fields`: list of columns, each with a `name` and `description`\n\nThe file can be large (hundreds of resources, megabytes of JSON). Always query it\nselectively — never load it whole into context.\n\n## Dependency check\n\nBefore querying metadata, verify `jq` is available:\n\n```bash\ncommand -v jq\n```\n\nIf not found, tell the user how to install it:\n\n- macOS: `brew install jq`\n- Linux (apt): `sudo apt install jq`\n- Linux (conda): `conda install jq`\n- Windows: `winget install jqlang.jq`\n\nFor data loading and SQL queries, the `attach-db`, and `query` skills from\n`duckdb-skills` must be installed. Install them from `duckdb\u002Fduckdb-skills`.\n\n## Workflow overview\n\n1. **Locate the descriptor** — find or download `datapackage.json` (see below).\n1. **Query metadata selectively** — use jq or DuckDB to extract only what you need.\n    See [Metadata Querying](.\u002Freferences\u002Fmetadata-querying.md).\n1. **Surface warnings** — always check for usage warnings before presenting a resource.\n1. **Validate** *(optional)* — if the user wants to know whether the data actually\n    matches the descriptor, or if you're diagnosing a suspicious package, use\n    `frictionless validate`. See [Frictionless Validate](.\u002Freferences\u002Ffrictionless-validate.md).\n1. **Load the data** *(optional)* — only if the user explicitly wants to query or\n    explore the actual data. Data files can be large and remote access can be slow or\n    costly. Don't initiate data loading as a follow-on to a metadata lookup without\n    confirming the user wants it. See [Storage Backends](.\u002Freferences\u002Fstorage-backends.md).\n\n## Reference index\n\n- [Metadata Querying](.\u002Freferences\u002Fmetadata-querying.md) — locate the descriptor,\n    query it selectively with jq or DuckDB, surface usage warnings\n- [Storage Backends](.\u002Freferences\u002Fstorage-backends.md) — load data from Parquet,\n    DuckDB, SQLite, or CSV files referenced by the descriptor\n- [Frictionless Validate](.\u002Freferences\u002Ffrictionless-validate.md) — use the `frictionless`\n    CLI to validate packages, check data quality, infer schemas, and diagnose unfamiliar\n    descriptors; read when the user wants to validate a descriptor, check if data matches\n    its schema, or understand what the `frictionless` tool can tell them about a package\n\n## Community patterns and recipes\n\nThe datapackage standard is permissive: publishers frequently add non-standard fields.\nTwo conventions are worth knowing immediately:\n\n- **Custom fields** — non-standard keys added by publishers are common and valid.\n    The `_` prefix convention marks system-generated or platform-specific keys (e.g.\n    `_cache`, `_platformVersion`). Some publishers add custom keys without the prefix\n    (e.g. PUDL adds `duckdb_table`, `sqlite_table` on database-backed resources). Treat\n    unknown fields as informational metadata, not errors.\n- **Compressed resources** — a resource with a `.gz` or `.zip` path may have an\n    explicit `\"compression\": \"gz\"` field. The `bytes` and `hash` fields apply to the\n    compressed file, not the uncompressed original.\n\nFor other patterns (catalogs, versioning, external foreign keys, translation support,\nfield relationships, etc.), fetch the relevant page on demand:\n\n- v1 patterns: \u003Chttps:\u002F\u002Fspecs.frictionlessdata.io\u002Fpatterns\u002F>\n- v2 recipes: \u003Chttps:\u002F\u002Fdatapackage.org\u002Frecipes\u002Fcaching-of-resources\u002F> (navigate via\n    sidebar or next\u002Fprevious links — no index page exists)\n\nBoth pages cover largely the same set of community conventions; consult whichever\nmatches the descriptor version you're working with.\n\n## Companion skills\n\nThis skill delegates actual data querying to:\n\n- **`\u002Fduckdb-skills:attach-db`** — attach a `.duckdb` or `.sqlite` database file and\n    set up a persistent session for querying\n- **`\u002Fduckdb-skills:query`** — run SQL or natural language queries against attached\n    databases, ad-hoc files (Parquet, CSV, remote HTTPS\u002FS3), and JSON files including\n    `datapackage.json` itself (via DuckDB's `read_json`)\n\nThese skills must be installed. See `skills-lock.json` in the project root.\n\n## Key constraints\n\n- **Golden rule: never load the full datapackage.json into context.** It may be\n    megabytes with hundreds of resources. Always query selectively.\n- **Read the full description before presenting a resource.** Descriptions often\n    contain important context: processing notes, primary key conventions, data\n    provenance, or caveats about known limitations. Don't skip them.\n- **Use `uv` to install Python packages** — prefer `uv add \u003Cpackage>` over\n    `pip install \u003Cpackage>`. `uv` is faster and installs into a virtual environment\n    rather than globally. Fall back to `pip` only if `uv` is not available\n    (`command -v uv` returns nothing).\n- **Do not use Python to query descriptor metadata.** Python is not the right tool here\n    — it loads the full JSON into memory (violating the golden rule above), adds\n    unnecessary dependencies, and can't easily handle remote descriptors. Use jq for\n    metadata-only tasks; use DuckDB when you need to combine metadata queries with data\n    queries. Python is only appropriate for loading data (via pandas or polars) after you\n    already know which table and columns you need.\n\n## Schema reference and version detection\n\nTwo versions of the Frictionless Data Package standard are in common use. Identify the\nversion from the top-level descriptor before parsing:\n\n| Field present | Version                          | Example value                                             |\n| ------------- | -------------------------------- | --------------------------------------------------------- |\n| `\"$schema\"`   | v2.0                             | `\"https:\u002F\u002Fdatapackage.org\u002Fprofiles\u002F2.0\u002Fdatapackage.json\"` |\n| `\"profile\"`   | v1.0                             | `\"tabular-data-package\"` or `\"data-package\"`              |\n| neither       | ambiguous (treat as v1 baseline) | —                                                         |\n\nKey differences between versions that affect parsing:\n\n- **Contributors** — v1 has `\"role\": \"author\"` (singular string); v2 has\n    `\"roles\": [\"author\"]` (array). Both may appear in the wild.\n- **Name pattern** — v1 enforces strictly lowercase `[-a-z0-9._\u002F]`; v2 is unrestricted.\n- **`version` field** — present in v2, absent in v1.\n\nBundled schemas:\n\n- [`assets\u002Fdatapackage-v1.schema.json`](.\u002Fassets\u002Fdatapackage-v1.schema.json) — v1.0\n    (JSON Schema draft-04). Used by FERC XBRL packages and many older datasets.\n- [`assets\u002Fdatapackage-v2.schema.json`](.\u002Fassets\u002Fdatapackage-v2.schema.json) — v2.0\n    (JSON Schema draft-07). The current standard. Canonical version always at:\n    \u003Chttps:\u002F\u002Fdatapackage.org\u002Fprofiles\u002F2.0\u002Fdatapackage.json>\n\nRead the appropriate schema when you need to understand which fields are valid in a\ndescriptor or validate one programmatically.\n","# Frictionless Data Package Guide\n\nThis skill covers any dataset described by a\n[Frictionless Data Package](https:\u002F\u002Fdatapackage.org\u002F) descriptor file\n(`datapackage.json`). It is intentionally generic — it works for any conforming\ndatapackage, regardless of who published it or what the data contains.\n\nFor PUDL-specific knowledge (S3 bucket paths, table tier conventions, data source\ncontext, usage warnings), also use the `pudl` skill on top of this one.\n\n## What is a datapackage.json?\n\nA `datapackage.json` is a JSON file that describes a collection of tabular data\nresources. Each resource represents one table (or file) and includes:\n\n- `name`: machine-readable identifier\n- `description`: human-readable description, often including processing notes, primary\n    keys, and usage warnings\n- `path`: filename or URL of the actual data file\n- `schema.fields`: list of columns, each with a `name` and `description`\n\nThe file can be large (hundreds of resources, megabytes of JSON). Always query it\nselectively — never load it whole into context.\n\n## Dependency check\n\nBefore querying metadata, verify `jq` is available:\n\n```bash\ncommand -v jq\n```\n\nIf not found, tell the user how to install it:\n\n- macOS: `brew install jq`\n- Linux (apt): `sudo apt install jq`\n- Linux (conda): `conda install jq`\n- Windows: `winget install jqlang.jq`\n\nFor data loading and SQL queries, the `attach-db`, and `query` skills from\n`duckdb-skills` must be installed. Install them from `duckdb\u002Fduckdb-skills`.\n\n## Workflow overview\n\n1. **Locate the descriptor** — find or download `datapackage.json` (see below).\n1. **Query metadata selectively** — use jq or DuckDB to extract only what you need.\n    See [Metadata Querying](.\u002Freferences\u002Fmetadata-querying.md).\n1. **Surface warnings** — always check for usage warnings before presenting a resource.\n1. **Validate** *(optional)* — if the user wants to know whether the data actually\n    matches the descriptor, or if you're diagnosing a suspicious package, use\n    `frictionless validate`. See [Frictionless Validate](.\u002Freferences\u002Ffrictionless-validate.md).\n1. **Load the data** *(optional)* — only if the user explicitly wants to query or\n    explore the actual data. Data files can be large and remote access can be slow or\n    costly. Don't initiate data loading as a follow-on to a metadata lookup without\n    confirming the user wants it. See [Storage Backends](.\u002Freferences\u002Fstorage-backends.md).\n\n## Reference index\n\n- [Metadata Querying](.\u002Freferences\u002Fmetadata-querying.md) — locate the descriptor,\n    query it selectively with jq or DuckDB, surface usage warnings\n- [Storage Backends](.\u002Freferences\u002Fstorage-backends.md) — load data from Parquet,\n    DuckDB, SQLite, or CSV files referenced by the descriptor\n- [Frictionless Validate](.\u002Freferences\u002Ffrictionless-validate.md) — use the `frictionless`\n    CLI to validate packages, check data quality, infer schemas, and diagnose unfamiliar\n    descriptors; read when the user wants to validate a descriptor, check if data matches\n    its schema, or understand what the `frictionless` tool can tell them about a package\n\n## Community patterns and recipes\n\nThe datapackage standard is permissive: publishers frequently add non-standard fields.\nTwo conventions are worth knowing immediately:\n\n- **Custom fields** — non-standard keys added by publishers are common and valid.\n    The `_` prefix convention marks system-generated or platform-specific keys (e.g.\n    `_cache`, `_platformVersion`). Some publishers add custom keys without the prefix\n    (e.g. PUDL adds `duckdb_table`, `sqlite_table` on database-backed resources). Treat\n    unknown fields as informational metadata, not errors.\n- **Compressed resources** — a resource with a `.gz` or `.zip` path may have an\n    explicit `\"compression\": \"gz\"` field. The `bytes` and `hash` fields apply to the\n    compressed file, not the uncompressed original.\n\nFor other patterns (catalogs, versioning, external foreign keys, translation support,\nfield relationships, etc.), fetch the relevant page on demand:\n\n- v1 patterns: \u003Chttps:\u002F\u002Fspecs.frictionlessdata.io\u002Fpatterns\u002F>\n- v2 recipes: \u003Chttps:\u002F\u002Fdatapackage.org\u002Frecipes\u002Fcaching-of-resources\u002F> (navigate via\n    sidebar or next\u002Fprevious links — no index page exists)\n\nBoth pages cover largely the same set of community conventions; consult whichever\nmatches the descriptor version you're working with.\n\n## Companion skills\n\nThis skill delegates actual data querying to:\n\n- **`\u002Fduckdb-skills:attach-db`** — attach a `.duckdb` or `.sqlite` database file and\n    set up a persistent session for querying\n- **`\u002Fduckdb-skills:query`** — run SQL or natural language queries against attached\n    databases, ad-hoc files (Parquet, CSV, remote HTTPS\u002FS3), and JSON files including\n    `datapackage.json` itself (via DuckDB's `read_json`)\n\nThese skills must be installed. See `skills-lock.json` in the project root.\n\n## Key constraints\n\n- **Golden rule: never load the full datapackage.json into context.** It may be\n    megabytes with hundreds of resources. Always query selectively.\n- **Read the full description before presenting a resource.** Descriptions often\n    contain important context: processing notes, primary key conventions, data\n    provenance, or caveats about known limitations. Don't skip them.\n- **Use `uv` to install Python packages** — prefer `uv add \u003Cpackage>` over\n    `pip install \u003Cpackage>`. `uv` is faster and installs into a virtual environment\n    rather than globally. Fall back to `pip` only if `uv` is not available\n    (`command -v uv` returns nothing).\n- **Do not use Python to query descriptor metadata.** Python is not the right tool here\n    — it loads the full JSON into memory (violating the golden rule above), adds\n    unnecessary dependencies, and can't easily handle remote descriptors. Use jq for\n    metadata-only tasks; use DuckDB when you need to combine metadata queries with data\n    queries. Python is only appropriate for loading data (via pandas or polars) after you\n    already know which table and columns you need.\n\n## Schema reference and version detection\n\nTwo versions of the Frictionless Data Package standard are in common use. Identify the\nversion from the top-level descriptor before parsing:\n\n| Field present | Version                          | Example value                                             |\n| ------------- | -------------------------------- | --------------------------------------------------------- |\n| `\"$schema\"`   | v2.0                             | `\"https:\u002F\u002Fdatapackage.org\u002Fprofiles\u002F2.0\u002Fdatapackage.json\"` |\n| `\"profile\"`   | v1.0                             | `\"tabular-data-package\"` or `\"data-package\"`              |\n| neither       | ambiguous (treat as v1 baseline) | —                                                         |\n\nKey differences between versions that affect parsing:\n\n- **Contributors** — v1 has `\"role\": \"author\"` (singular string); v2 has\n    `\"roles\": [\"author\"]` (array). Both may appear in the wild.\n- **Name pattern** — v1 enforces strictly lowercase `[-a-z0-9._\u002F]`; v2 is unrestricted.\n- **`version` field** — present in v2, absent in v1.\n\nBundled schemas:\n\n- [`assets\u002Fdatapackage-v1.schema.json`](.\u002Fassets\u002Fdatapackage-v1.schema.json) — v1.0\n    (JSON Schema draft-04). Used by FERC XBRL packages and many older datasets.\n- [`assets\u002Fdatapackage-v2.schema.json`](.\u002Fassets\u002Fdatapackage-v2.schema.json) — v2.0\n    (JSON Schema draft-07). The current standard. Canonical version always at:\n    \u003Chttps:\u002F\u002Fdatapackage.org\u002Fprofiles\u002F2.0\u002Fdatapackage.json>\n\nRead the appropriate schema when you need to understand which fields are valid in a\ndescriptor or validate one programmatically.\n",{"name":5,"license":15,"metadata":24,"description":31,"compatibility":32},[25,27,29],{"author":26},"Catalyst Cooperative",{"email":28},"hello@catalyst.coop",{"last-updated":30},1775174400000,"Explore and query any dataset annotated with a Frictionless Data Package descriptor (datapackage.json). Use this skill whenever a user wants to discover what tables or resources a dataset contains, look up column names and descriptions, surface usage warnings embedded in metadata, or understand how to load data from Parquet files, DuckDB or SQLite databases, or CSV files described by a datapackage.json. Also use when the user has a datapackage.json and wants to know what's in it, how to query it efficiently, or how to connect its metadata to actual data files. Pairs well with dataset-specific skills (like `pudl`) that layer domain knowledge on top.\n","Required CLI tools: jq >= 1.7\nOptional CLI tools: frictionless >= 5.18 (with fastparquet for Parquet support)\nRequired skills: duckdb-skills (install-duckdb, attach-db, query)\nOptional Python packages: marimo, pandas, polars, duckdb (for DataFrame work)\n","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fcatalyst-cooperative-agent-skills\u002Fdatapackage",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":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill datapackage",{"tool":47,"command":48},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill datapackage",{"tool":50,"command":51},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill datapackage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fcatalyst-cooperative-agent-skills\u002Fdatapackage\u002FSkill.md",true,[55],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"metadata.json","REFERENCE","参考文档",493,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fcatalyst-cooperative-agent-skills\u002Fdatapackage\u002Fmetadata.json",[62,70,75,82,87,94],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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":95,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]