[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASKC832DH762EEJAVVNRY0":3,"skill-same:01M7ASKC832DH762EEJAVVNRY0":77},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7ASKC832DH762EEJAVVNRY0","ontology-term-resolution",null,"Resolve free-text scientific labels to ontology term IDs and validate existing CURIEs against the EBI Ontology Lookup Service (OLS4). Use whenever an ontology identifier must be produced or checked - annotating tissue, cell type, disease, phenotype, assay, chemical, organism, sex, or developmental stage fields; preparing metadata for GEO, ENA, BioSamples, CELLxGENE, HCA, or ISA-Tab submission; auditing a metadata table of term IDs; checking whether a term is obsolete and what replaced it; or mapping between ontologies. Triggers include \"ontology term\", \"ontology ID\", \"CURIE\", \"controlled vocabulary\", \"UBERON\", \"CL:\", \"MONDO\", \"HPO\", \"EFO\", \"ChEBI\", \"NCBITaxon\", \"GO term\", \"PATO\", \"annotate this tissue\u002Fcell type\u002Fdisease\", and any request to emit or verify an identifier shaped like PREFIX:0001234.","nikhilesh-s\u002Fclaude-toolkit","nikhilesh-s","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F123913414?v=4","01M7ARX6NXB6DFY1CCP91599KE","Nikhilesh Suravarjjala","01M7ARX6PFTQKR6ME1K2S4AZ9K",0,"MIT","https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fontology-term-resolution\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ontology-term-resolution\ndescription: Resolve free-text scientific labels to ontology term IDs and validate existing CURIEs against the EBI Ontology Lookup Service (OLS4). Use whenever an ontology identifier must be produced or checked - annotating tissue, cell type, disease, phenotype, assay, chemical, organism, sex, or developmental stage fields; preparing metadata for GEO, ENA, BioSamples, CELLxGENE, HCA, or ISA-Tab submission; auditing a metadata table of term IDs; checking whether a term is obsolete and what replaced it; or mapping between ontologies. Triggers include \"ontology term\", \"ontology ID\", \"CURIE\", \"controlled vocabulary\", \"UBERON\", \"CL:\", \"MONDO\", \"HPO\", \"EFO\", \"ChEBI\", \"NCBITaxon\", \"GO term\", \"PATO\", \"annotate this tissue\u002Fcell type\u002Fdisease\", and any request to emit or verify an identifier shaped like PREFIX:0001234.\nlicense: MIT\ncompatibility: Requires Python 3.11+. Scripts use only the standard library - no third-party packages. Needs network access to https:\u002F\u002Fwww.ebi.ac.uk\u002Fols4 (public, no API key).\nallowed-tools: Read Write Edit Bash\nmetadata:\n  version: \"1.0\"\n  skill-author: K-Dense Inc.\n---\n\n# Ontology Term Resolution\n\n## When to use\n\nAny time an ontology identifier is about to be written down or trusted: annotating a metadata\ncolumn, filling a submission template, auditing a table someone else produced, or checking whether\nan ID in an old file is still current.\n\n## The rule\n\n**Never write an ontology ID from memory, and never accept one without checking it.**\n\nOntology IDs are memorable in form and arbitrary in detail. A plausible-looking `UBERON:0002108`\nis a real term (small intestine) that is not the liver, and nothing downstream will catch the\nsubstitution — the ID is well-formed, the ontology is right, and the metadata is silently wrong.\nReviewers cannot spot it either, which is why these errors persist into published datasets.\n\nEvery ID this skill emits comes from a live OLS lookup. Every ID it is handed gets verified.\n\n## Two directions\n\n| Direction | Script | Question answered |\n| --- | --- | --- |\n| text → ID | `scripts\u002Fresolve_terms.py` | What is the term for \"left ventricle\"? |\n| ID → verdict | `scripts\u002Fvalidate_terms.py` | Is `EFO:0001067` real, current, and labelled what this file claims? |\n\nBoth take single values or files, emit TSV or JSON, and need no packages beyond the standard\nlibrary.\n\n## Resolve text to terms\n\n```bash\ncd skills\u002Fontology-term-resolution\u002Fscripts\n\n# one string, constrained to the ontology that should define it\npython3 resolve_terms.py \"liver\" --ontology uberon\n```\n\n```\nquery   rank  curie           label  ontology  match_type   strategy  defining_ontology\nliver   1     UBERON:0002107  liver  uberon    exact_label  exact     true\n```\n\n```bash\n# a column of tissue names; anything not an exact hit is reported, not guessed\npython3 resolve_terms.py --input tissues.txt --ontology uberon \\\n    --exact-only --format tsv -o resolved.tsv\n\n# accept fuzzy fallbacks, then review the partial hits by hand\npython3 resolve_terms.py \"left ventrical of heart\" --ontology uberon --top 3\n```\n\nThe search escalates `exact` (label and synonym) → `token` → `fulltext` and stops at the first\nstrategy that returns anything, reporting which one fired. `--exact-only` disables the ladder.\n`--branch UBERON:0000465` restricts candidates to descendants of a term.\n\n**Read `match_type` before using a result.** `exact_label` and `exact_synonym` are safe;\n`partial` means OLS returned its best guess for a string that does not exist as written, and\nneeds a human decision. `unresolved` is a legitimate output — see `references\u002Fcuration-rules.md`\nfor the normalisations worth retrying first.\n\n## Validate existing IDs\n\n```bash\npython3 validate_terms.py UBERON:0002107 EFO:0001067 UBERON:9999999\n```\n\n```\nid              status     actual_label                  ontology  replacement     detail\nUBERON:0002107  ok         liver                         uberon\nEFO:0001067     obsolete   obsolete_parasitic infection  efo       MONDO:0005135   obsolete; replaced by MONDO:0005135\nUBERON:9999999  not_found                                                          no such term in the ontology this prefix names\n```\n\nExit code is 1 if anything failed, 0 otherwise, 2 on usage or network trouble — so it works as a\nCI gate on a metadata file:\n\n```bash\n# id + label columns; catches IDs that exist but are labelled as something else\npython3 validate_terms.py --input metadata.tsv --strict\n\n# a tissue column must hold UBERON anatomical entities and nothing else\npython3 validate_terms.py --input tissue_ids.tsv \\\n    --branch UBERON:0000465 --expect-ontology uberon\n```\n\n| Status | Meaning | Verdict |\n| --- | --- | --- |\n| `ok` | Exists, current, consistent with everything asserted | pass |\n| `matched_synonym` | Claimed label is a synonym; primary label differs | warn |\n| `imported_only` | Home ontology no longer asserts this ID | warn |\n| `not_a_class` | Term is a property or individual | warn |\n| `not_found` | No such term | fail |\n| `obsolete` | Obsoleted; `replacement` gives the successor when one exists | fail |\n| `label_mismatch` | ID and claimed label describe different things | fail |\n| `wrong_ontology` | Right kind of ID, wrong ontology for this column | fail |\n| `wrong_branch` | Not a descendant of the required root | fail |\n| `malformed_curie` | Not of the form `PREFIX:local` | fail |\n\n`--strict` promotes warnings to failures.\n\n## API behaviour that will mislead you\n\nThese are verified against the live service and are the reason this skill ships scripts rather\nthan a recipe. Full detail in `references\u002Fols4-api.md`.\n\n| Trap | Consequence |\n| --- | --- |\n| `exact=true` is exact **token** matching | `liver` returns 161 hits in UBERON; adding `queryFields=label` returns 1 |\n| `\u002Fsearch` never returns `is_obsolete` or `term_replaced_by` | Named in `fieldList` they are dropped silently; only term detail can answer \"is this ID still current\" |\n| `ontology=efo` returns MONDO and CL hits | Ontologies import each other; filter on the CURIE prefix yourself |\n| The same term appears once per importing ontology | Deduplicate on `obo_id`, keep `is_defining_ontology: true` |\n| The `obo_id` index has holes | `MONDO:0000001` is live but unindexed by `obo_id`; an IRI fallback is required to avoid a false `not_found` |\n| IRIs are not all OBO PURLs | EFO and Orphanet use their own namespaces — resolve IRIs, do not template them |\n| OxO is retired | Returns HTML with HTTP 200; use term cross-references or SSSOM instead |\n| A branch check does not exclude cell types from anatomy | CARO puts `cell` under `anatomical structure`; constrain the prefix too |\n\n## Choosing the ontology\n\nMONDO for disease, HP for phenotype, UBERON for tissue, CL for cell type, EFO for assay, ChEBI for\ncompounds, NCBITaxon for organism, PATO for sex and for `normal`. Prefix-to-OLS-id mappings (`HP`\nis served as `hp`, `Orphanet` as `ordo`), branch roots for `--branch`, and the overlapping-ontology\njudgement calls are in `references\u002Fontology-registry.md`.\n\n## Reporting results\n\nGive the ID **and** the label, and say how each was matched. A table of bare IDs cannot be\nreviewed. State unresolved terms explicitly rather than filling them with the nearest hit.\n\n## References\n\n- `references\u002Fols4-api.md` — endpoints, parameters, response fields, and every verified trap.\n- `references\u002Fontology-registry.md` — prefix\u002Fontology-id table, branch roots, which ontology owns\n  which concept.\n- `references\u002Fcuration-rules.md` — candidate-selection procedure, normalisations to retry,\n  auditing an existing table, obsolete terms, cross-ontology mapping.\n","# Ontology Term Resolution\n\n## When to use\n\nAny time an ontology identifier is about to be written down or trusted: annotating a metadata\ncolumn, filling a submission template, auditing a table someone else produced, or checking whether\nan ID in an old file is still current.\n\n## The rule\n\n**Never write an ontology ID from memory, and never accept one without checking it.**\n\nOntology IDs are memorable in form and arbitrary in detail. A plausible-looking `UBERON:0002108`\nis a real term (small intestine) that is not the liver, and nothing downstream will catch the\nsubstitution — the ID is well-formed, the ontology is right, and the metadata is silently wrong.\nReviewers cannot spot it either, which is why these errors persist into published datasets.\n\nEvery ID this skill emits comes from a live OLS lookup. Every ID it is handed gets verified.\n\n## Two directions\n\n| Direction | Script | Question answered |\n| --- | --- | --- |\n| text → ID | `scripts\u002Fresolve_terms.py` | What is the term for \"left ventricle\"? |\n| ID → verdict | `scripts\u002Fvalidate_terms.py` | Is `EFO:0001067` real, current, and labelled what this file claims? |\n\nBoth take single values or files, emit TSV or JSON, and need no packages beyond the standard\nlibrary.\n\n## Resolve text to terms\n\n```bash\ncd skills\u002Fontology-term-resolution\u002Fscripts\n\n# one string, constrained to the ontology that should define it\npython3 resolve_terms.py \"liver\" --ontology uberon\n```\n\n```\nquery   rank  curie           label  ontology  match_type   strategy  defining_ontology\nliver   1     UBERON:0002107  liver  uberon    exact_label  exact     true\n```\n\n```bash\n# a column of tissue names; anything not an exact hit is reported, not guessed\npython3 resolve_terms.py --input tissues.txt --ontology uberon \\\n    --exact-only --format tsv -o resolved.tsv\n\n# accept fuzzy fallbacks, then review the partial hits by hand\npython3 resolve_terms.py \"left ventrical of heart\" --ontology uberon --top 3\n```\n\nThe search escalates `exact` (label and synonym) → `token` → `fulltext` and stops at the first\nstrategy that returns anything, reporting which one fired. `--exact-only` disables the ladder.\n`--branch UBERON:0000465` restricts candidates to descendants of a term.\n\n**Read `match_type` before using a result.** `exact_label` and `exact_synonym` are safe;\n`partial` means OLS returned its best guess for a string that does not exist as written, and\nneeds a human decision. `unresolved` is a legitimate output — see `references\u002Fcuration-rules.md`\nfor the normalisations worth retrying first.\n\n## Validate existing IDs\n\n```bash\npython3 validate_terms.py UBERON:0002107 EFO:0001067 UBERON:9999999\n```\n\n```\nid              status     actual_label                  ontology  replacement     detail\nUBERON:0002107  ok         liver                         uberon\nEFO:0001067     obsolete   obsolete_parasitic infection  efo       MONDO:0005135   obsolete; replaced by MONDO:0005135\nUBERON:9999999  not_found                                                          no such term in the ontology this prefix names\n```\n\nExit code is 1 if anything failed, 0 otherwise, 2 on usage or network trouble — so it works as a\nCI gate on a metadata file:\n\n```bash\n# id + label columns; catches IDs that exist but are labelled as something else\npython3 validate_terms.py --input metadata.tsv --strict\n\n# a tissue column must hold UBERON anatomical entities and nothing else\npython3 validate_terms.py --input tissue_ids.tsv \\\n    --branch UBERON:0000465 --expect-ontology uberon\n```\n\n| Status | Meaning | Verdict |\n| --- | --- | --- |\n| `ok` | Exists, current, consistent with everything asserted | pass |\n| `matched_synonym` | Claimed label is a synonym; primary label differs | warn |\n| `imported_only` | Home ontology no longer asserts this ID | warn |\n| `not_a_class` | Term is a property or individual | warn |\n| `not_found` | No such term | fail |\n| `obsolete` | Obsoleted; `replacement` gives the successor when one exists | fail |\n| `label_mismatch` | ID and claimed label describe different things | fail |\n| `wrong_ontology` | Right kind of ID, wrong ontology for this column | fail |\n| `wrong_branch` | Not a descendant of the required root | fail |\n| `malformed_curie` | Not of the form `PREFIX:local` | fail |\n\n`--strict` promotes warnings to failures.\n\n## API behaviour that will mislead you\n\nThese are verified against the live service and are the reason this skill ships scripts rather\nthan a recipe. Full detail in `references\u002Fols4-api.md`.\n\n| Trap | Consequence |\n| --- | --- |\n| `exact=true` is exact **token** matching | `liver` returns 161 hits in UBERON; adding `queryFields=label` returns 1 |\n| `\u002Fsearch` never returns `is_obsolete` or `term_replaced_by` | Named in `fieldList` they are dropped silently; only term detail can answer \"is this ID still current\" |\n| `ontology=efo` returns MONDO and CL hits | Ontologies import each other; filter on the CURIE prefix yourself |\n| The same term appears once per importing ontology | Deduplicate on `obo_id`, keep `is_defining_ontology: true` |\n| The `obo_id` index has holes | `MONDO:0000001` is live but unindexed by `obo_id`; an IRI fallback is required to avoid a false `not_found` |\n| IRIs are not all OBO PURLs | EFO and Orphanet use their own namespaces — resolve IRIs, do not template them |\n| OxO is retired | Returns HTML with HTTP 200; use term cross-references or SSSOM instead |\n| A branch check does not exclude cell types from anatomy | CARO puts `cell` under `anatomical structure`; constrain the prefix too |\n\n## Choosing the ontology\n\nMONDO for disease, HP for phenotype, UBERON for tissue, CL for cell type, EFO for assay, ChEBI for\ncompounds, NCBITaxon for organism, PATO for sex and for `normal`. Prefix-to-OLS-id mappings (`HP`\nis served as `hp`, `Orphanet` as `ordo`), branch roots for `--branch`, and the overlapping-ontology\njudgement calls are in `references\u002Fontology-registry.md`.\n\n## Reporting results\n\nGive the ID **and** the label, and say how each was matched. A table of bare IDs cannot be\nreviewed. State unresolved terms explicitly rather than filling them with the nearest hit.\n\n## References\n\n- `references\u002Fols4-api.md` — endpoints, parameters, response fields, and every verified trap.\n- `references\u002Fontology-registry.md` — prefix\u002Fontology-id table, branch roots, which ontology owns\n  which concept.\n- `references\u002Fcuration-rules.md` — candidate-selection procedure, normalisations to retry,\n  auditing an existing table, obsolete terms, cross-ontology mapping.\n",{"name":5,"license":15,"metadata":24,"description":7,"allowed-tools":27,"compatibility":28},{"version":25,"skill-author":26},"1.0","K-Dense Inc.","Read Write Edit Bash","Requires Python 3.11+. Scripts use only the standard library - no third-party packages. Needs network access to https:\u002F\u002Fwww.ebi.ac.uk\u002Fols4 (public, no API key).","nik-claude-toolkit","4feaa2876384b593d9e30d9190bc56985eeeeb8e","skills\u002Fontology-term-resolution","https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit","https:\u002F\u002Fgithub.com\u002Fnikhilesh-s","2026-10-22 14:30:58",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add nikhilesh-s\u002Fclaude-toolkit --skill ontology-term-resolution",{"tool":41,"command":42},"bunx","bunx skills add nikhilesh-s\u002Fclaude-toolkit --skill ontology-term-resolution",{"tool":44,"command":45},"pnpm","pnpm dlx skills add nikhilesh-s\u002Fclaude-toolkit --skill ontology-term-resolution","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fontology-term-resolution\u002FSKILL.md",true,[49,55,59,63,69,73],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fcuration-rules.md","REFERENCE","参考文档",5403,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fontology-term-resolution\u002Freferences\u002Fcuration-rules.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fols4-api.md",6406,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fontology-term-resolution\u002Freferences\u002Fols4-api.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fontology-registry.md",5550,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fontology-term-resolution\u002Freferences\u002Fontology-registry.md",{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"scripts\u002Fols_client.py","SCRIPT","脚本",12458,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fontology-term-resolution\u002Fscripts\u002Fols_client.py",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"scripts\u002Fresolve_terms.py",8160,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fontology-term-resolution\u002Fscripts\u002Fresolve_terms.py",{"path":74,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":75,"sourceHtmlUrl":76},"scripts\u002Fvalidate_terms.py",9746,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fontology-term-resolution\u002Fscripts\u002Fvalidate_terms.py",[78,85,93,100,107,114],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7AT8339CZMCRMRZP6G1R329","zarr-python","Chunked N-D arrays for cloud storage (Zarr-Python 3). Compressed arrays, parallel I\u002FO, S3\u002FGCS via fsspec, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7AT77E7JPH96ETQBNDVVYDM","video-use","Edit any video by conversation. Transcribe, cut, color grade, generate overlay animations, burn subtitles — for talking heads, montages, tutorials, travel, interviews. No presets, no menus. Ask questions, confirm the plan, execute, iterate, persist. Production-correctness rules are hard; everything else is artistic freedom.","https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fvideo-use\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fvideo-use\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7AT6YVX000D73Q40SBPZYKP","venue-templates","Prepare journal manuscripts, conference papers, research posters, and grant documents using venue-specific formatting guidance and bundled LaTeX scaffolds. Use when selecting an official template, checking current page or anonymity rules, adapting academic writing to a venue, or inspecting a submission PDF.","https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fvenue-templates\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7AT6SGGBENKX1G6V8V9G2MJ","vaex","Use this skill for processing and analyzing large tabular datasets (billions of rows) that exceed available RAM. Vaex excels at out-of-core DataFrame operations, lazy evaluation, fast aggregations, efficient visualization of big data, and machine learning on large datasets. Apply when users need to work with large CSV\u002FHDF5\u002FArrow\u002FParquet files, perform fast statistics on massive datasets, create visualizations of big data, or build ML pipelines that do not fit in memory.","https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fvaex\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7AT6HHDJ54MR4HDPFHJYR7G","usfiscaldata","Query the U.S. Treasury Fiscal Data REST API for federal financial data. No API key required. Use for national debt (Debt to the Penny), Daily Treasury Statements, Monthly Treasury Statements, Treasury securities auctions, interest rates, foreign exchange rates, savings bonds, or U.S. government revenue and spending statistics.","https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fusfiscaldata\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M7AT662JFE4THBVAZBB3ANJD","uncertainty-and-units","Track physical units and propagate measurement uncertainty in scientific calculations using pint and uncertainties. Use for unit conversion and dimensional checking, GUM uncertainty budgets, Type A and Type B evaluation, coverage factors and expanded uncertainty, Monte Carlo propagation, significant-figure and plus-minus reporting, error propagation through curve fits, CODATA constants, auditing Python code for stripped units or broken uncertainty propagation, and order-of-magnitude plausibility checks using dimensionless groups (Reynolds, Peclet, Damkohler, Knudsen, Biot, Womersley), characteristic scales such as diffusion time or Debye length, and observed magnitude ranges. Trigger on \"is this number physically reasonable\", \"sanity check these units\", \"what regime is this flow in\", or a result that looks off by orders of magnitude.","https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Funcertainty-and-units\u002FSKILL.md",[],[]]