[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AS9TH998KG77MJASPDR3DD":3,"skill-same:01M7AS9TH998KG77MJASPDR3DD":89},{"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},"01M7AS9TH998KG77MJASPDR3DD","genomic-coordinates",null,"Convert genomic intervals between coordinate conventions, normalise and compare variant representations, and detect assembly or contig-naming mismatches before they corrupt an analysis. Use whenever coordinates cross a format, tool, or assembly boundary - converting between BED, GFF\u002FGTF, VCF, SAM\u002FBAM, WIG, PSL, genePred, Picard interval_list, or region strings; reconciling 0-based half-open with 1-based inclusive; left-aligning or trimming indels; checking whether two variant records describe the same change; mapping genomic to transcript, CDS, or protein positions; auditing a BED\u002FGTF\u002FVCF for convention violations; or diagnosing GRCh37 vs hg19 vs GRCh38 vs T2T, chr-prefix, and liftover problems. Triggers include \"off by one\", \"0-based\", \"1-based\", \"half-open\", \"coordinate system\", \"left-align\", \"normalize variant\", \"bcftools norm\", \"chr prefix\", \"wrong genome build\", \"liftover\", \"REF mismatch\", and \"HGVS\".","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\u002Fgenomic-coordinates\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: genomic-coordinates\ndescription: Convert genomic intervals between coordinate conventions, normalise and compare variant representations, and detect assembly or contig-naming mismatches before they corrupt an analysis. Use whenever coordinates cross a format, tool, or assembly boundary - converting between BED, GFF\u002FGTF, VCF, SAM\u002FBAM, WIG, PSL, genePred, Picard interval_list, or region strings; reconciling 0-based half-open with 1-based inclusive; left-aligning or trimming indels; checking whether two variant records describe the same change; mapping genomic to transcript, CDS, or protein positions; auditing a BED\u002FGTF\u002FVCF for convention violations; or diagnosing GRCh37 vs hg19 vs GRCh38 vs T2T, chr-prefix, and liftover problems. Triggers include \"off by one\", \"0-based\", \"1-based\", \"half-open\", \"coordinate system\", \"left-align\", \"normalize variant\", \"bcftools norm\", \"chr prefix\", \"wrong genome build\", \"liftover\", \"REF mismatch\", and \"HGVS\".\nlicense: MIT\ncompatibility: Requires Python 3.11+. Scripts use only the standard library - no third-party packages and no network access. Variant normalisation needs a reference FASTA, and uses its .fai index when one is present.\nallowed-tools: Read Write Edit Bash\nmetadata:\n  version: \"1.0\"\n  skill-author: K-Dense Inc.\n---\n\n# Genomic Coordinates\n\n## When to use\n\nAny time a coordinate crosses a boundary: between two file formats, between two\ntools, between two assemblies, or between the genome and a transcript.\n\n## The rule\n\n**A coordinate is three facts, not one: the number, the convention it is written\nin, and the assembly it was measured against.** Carry all three or the number is\nnot interpretable.\n\nCoordinate errors are the quietest class of bug in genomics. An off-by-one BED\nfile parses, sorts, and intersects without complaint. A GRCh37 VCF joined against\na GRCh38 annotation returns rows. A right-shifted indel simply fails to match its\nentry in ClinVar, and the result is a variant reported as novel. Nothing raises\nan error; the answer is just wrong, and it is wrong in a direction that looks\nplausible.\n\nSo: convert with the table, not from memory, and verify against the reference\nwhenever a reference is available.\n\n## The two conversions\n\n```\n1-based inclusive  ->  0-based half-open :  start - 1,  end\n0-based half-open  ->  1-based inclusive :  start + 1,  end\n```\n\nThe end coordinate never moves. If a conversion changed both numbers, it is wrong.\n\n## Which format is which\n\n| 0-based, half-open | 1-based, inclusive |\n| --- | --- |\n| BED, bedGraph, bigWig, narrowPeak | GFF3, GTF, VCF |\n| BAM\u002FCRAM (binary POS) | SAM (text POS) |\n| PSL, genePred, refFlat | WIG, Picard interval_list |\n| MAF (UCSC multiple alignment) | MAF (TCGA mutation annotation) |\n| PyRanges, pybedtools | GRanges\u002FIRanges, samtools & UCSC & Ensembl region strings |\n\nBoth \"MAF\" formats exist, they mean different things, and they disagree. UCSC\nserves 0-based files through a 1-based browser box. `references\u002Fformat-conventions.md`\nhas the full table with per-format detail.\n\n```bash\ncd skills\u002Fgenomic-coordinates\u002Fscripts\n\npython3 convert_coords.py --list                          # the table\npython3 convert_coords.py --from bed --to gff chr1 999 1000\npython3 convert_coords.py --from ucsc --to bed \"chr7:5,530,601-5,530,625\"\npython3 convert_coords.py --from granges --to pyranges --input regions.tsv\n```\n\n```\ncontig  input                 output           length  status  detail\nchr7    chr7:5530601-5530625  5530600-5530625  25      ok\n```\n\nZero-length BED features (`chromStart == chromEnd`, a legal insertion point) are\nreported as `unrepresentable` rather than converted to `end = start - 1`. Exit\ncode is 1 when any interval is degenerate or invalid.\n\n## Variants are not intervals\n\nA VCF `POS` for an indel is the **anchor base** — the base *before* the event,\nitself unchanged. And the same change can be written many ways:\n`chr1:7:CAC:C`, `chr1:3:CAC:C` and `chr1:2:GCA:G` are one deletion. Joining,\ndeduplicating, or looking up variants before normalising loses real matches\nsilently, and it loses them preferentially in repeats, where indels concentrate.\n\nNormalise — trim to parsimony, then left-align against the reference — before any\ncomparison:\n\n```bash\npython3 normalize_variant.py --fasta ref.fa chr1 7 CAC C\npython3 normalize_variant.py --fasta ref.fa --split --input cohort.vcf\npython3 normalize_variant.py --fasta ref.fa --compare chr1:7:CAC:C chr1:2:GCA:G\n```\n\n```\ninput         normalized    type      pos_shift  ref_check  changed\nchr1:7:CAC:C  chr1:2:GCA:G  deletion  5          ok         yes\n```\n\nEvery record's `REF` is checked against the FASTA first. A `MISMATCH` means the\nvariants and the reference are different assemblies — stop and run\n`check_contigs.py` rather than adjusting coordinates. Multi-allelic records must\nbe split with `--split` **before** normalising, never after.\n\nHGVS shifts indels the opposite way, 3'-most along the transcript. For a\nminus-strand gene that is the opposite genomic direction from VCF's\nleft-alignment. Details and the full procedure: `references\u002Fvariant-representation.md`.\n\n## Check the assembly before trusting a join\n\n```bash\npython3 check_contigs.py --identify unknown.fa.fai\npython3 check_contigs.py variants.vcf annotation.gtf --genome GRCh38.fa.fai\n```\n\n```\nfile          kind    contigs  naming        assembly  detail\nref.fa.fai    sizes   25       plain         GRCh37    24\u002F24 primary chromosome lengths match;\n                                                       chrM is 16569 bp, i.e. GRCh37\u002F38 (rCRS MT)\n```\n\nThe script reads `.fai`, `.chrom.sizes`, VCF headers, SAM headers, FASTA, BED,\nand GTF\u002FGFF, identifies the assembly from primary-chromosome lengths, and reports\nevery reason a join between two files would go wrong: naming mismatch, length\nconflict, coordinates past a contig end, contigs present in one file only. Exit\ncode 1 on any incompatibility.\n\n**GRCh37 and hg19 differ only in the mitochondrion** — 16,569 bp (rCRS) versus\n16,571 bp. Nuclear coordinates are identical, so a mixed pipeline runs fine and\nonly the mtDNA results are wrong. `check_contigs.py` reports which one it found.\nBuilds, naming schemes, ALT contigs, and liftover pitfalls:\n`references\u002Freference-builds.md`.\n\n## Audit a file against its own format\n\n```bash\npython3 audit_intervals.py peaks.bed\npython3 audit_intervals.py gencode.gtf --genome hg38.chrom.sizes\npython3 audit_intervals.py cohort.vcf --genome GRCh38.fa.fai\n```\n\nLooks for the evidence that a coordinate mistake leaves behind:\n\n| Finding | What it proves |\n| --- | --- |\n| `start_below_one` in GFF\u002FGTF | 0-based data in a 1-based file; everything is one base left |\n| `many_zero_length` in BED | 1-based single-base features written into a 0-based file |\n| `past_contig_end` | wrong assembly, or an off-by-one at the contig edge |\n| `mixed_contig_naming` | any join will silently match one subset |\n| `first_block_offset` | BED12 `blockStarts` written as absolute coordinates |\n| `not_parsimonious` | untrimmed alleles; normalise before joining |\n| `bad_alt_allele` | Ensembl\u002FVEP `-` notation in a VCF, which has no anchor base |\n\nExit code 1 on any fatal finding, so it works as a CI gate on a data directory.\n\n## Transcript, CDS, and protein positions\n\n`c.742` and `chr17:7,674,220` are both \"position\", and neither converts to the\nother by arithmetic. Transcript coordinates count spliced bases in transcription\norder — decreasing genomic coordinate on the minus strand — and `c.1` is the `A`\nof the initiator `ATG`, not the start of the transcript.\n\nThe rules that get mis-remembered: there is no `c.0`; 5' UTR positions are\nnegative and 3' UTR positions take a `*`; GFF phase is the bases to *remove* to\nreach the next codon, not `start % 3`; and a `c.` description is meaningless\nwithout a versioned transcript accession, because the same variant numbers\ndifferently in each transcript. `references\u002Ftranscript-coordinates.md` has the\nconversion procedure and the boundary cases.\n\nDo the conversion with a tool that holds the transcript model — VEP,\n`bcftools csq`, Mutalyzer, the `hgvs` package — not by hand.\n\n## Reporting results\n\nState the assembly next to the coordinates, every time.\n`chr7:5,530,601-5,530,625` is not a location; `chr7:5,530,601-5,530,625 (GRCh38)`\nis. Say which convention a coordinate column is in, in the column header or the\nfile's documentation. When a conversion produced a result, say which direction it\nwent.\n\n## References\n\n- `references\u002Fformat-conventions.md` — every format's convention, with per-format\n  detail, BED12 block rules, region-string syntax, and tool behaviour.\n- `references\u002Fvariant-representation.md` — VCF allele conventions, the\n  normalisation algorithm, equivalence checking, multi-allelic splitting, and how\n  HGVS disagrees with VCF.\n- `references\u002Freference-builds.md` — build signatures, GRCh37 vs hg19, ALT\n  contigs, naming schemes, and liftover failure modes.\n- `references\u002Ftranscript-coordinates.md` — genomic ↔ transcript ↔ CDS ↔ protein,\n  HGVS numbering, phase, and transcript choice.\n","# Genomic Coordinates\n\n## When to use\n\nAny time a coordinate crosses a boundary: between two file formats, between two\ntools, between two assemblies, or between the genome and a transcript.\n\n## The rule\n\n**A coordinate is three facts, not one: the number, the convention it is written\nin, and the assembly it was measured against.** Carry all three or the number is\nnot interpretable.\n\nCoordinate errors are the quietest class of bug in genomics. An off-by-one BED\nfile parses, sorts, and intersects without complaint. A GRCh37 VCF joined against\na GRCh38 annotation returns rows. A right-shifted indel simply fails to match its\nentry in ClinVar, and the result is a variant reported as novel. Nothing raises\nan error; the answer is just wrong, and it is wrong in a direction that looks\nplausible.\n\nSo: convert with the table, not from memory, and verify against the reference\nwhenever a reference is available.\n\n## The two conversions\n\n```\n1-based inclusive  ->  0-based half-open :  start - 1,  end\n0-based half-open  ->  1-based inclusive :  start + 1,  end\n```\n\nThe end coordinate never moves. If a conversion changed both numbers, it is wrong.\n\n## Which format is which\n\n| 0-based, half-open | 1-based, inclusive |\n| --- | --- |\n| BED, bedGraph, bigWig, narrowPeak | GFF3, GTF, VCF |\n| BAM\u002FCRAM (binary POS) | SAM (text POS) |\n| PSL, genePred, refFlat | WIG, Picard interval_list |\n| MAF (UCSC multiple alignment) | MAF (TCGA mutation annotation) |\n| PyRanges, pybedtools | GRanges\u002FIRanges, samtools & UCSC & Ensembl region strings |\n\nBoth \"MAF\" formats exist, they mean different things, and they disagree. UCSC\nserves 0-based files through a 1-based browser box. `references\u002Fformat-conventions.md`\nhas the full table with per-format detail.\n\n```bash\ncd skills\u002Fgenomic-coordinates\u002Fscripts\n\npython3 convert_coords.py --list                          # the table\npython3 convert_coords.py --from bed --to gff chr1 999 1000\npython3 convert_coords.py --from ucsc --to bed \"chr7:5,530,601-5,530,625\"\npython3 convert_coords.py --from granges --to pyranges --input regions.tsv\n```\n\n```\ncontig  input                 output           length  status  detail\nchr7    chr7:5530601-5530625  5530600-5530625  25      ok\n```\n\nZero-length BED features (`chromStart == chromEnd`, a legal insertion point) are\nreported as `unrepresentable` rather than converted to `end = start - 1`. Exit\ncode is 1 when any interval is degenerate or invalid.\n\n## Variants are not intervals\n\nA VCF `POS` for an indel is the **anchor base** — the base *before* the event,\nitself unchanged. And the same change can be written many ways:\n`chr1:7:CAC:C`, `chr1:3:CAC:C` and `chr1:2:GCA:G` are one deletion. Joining,\ndeduplicating, or looking up variants before normalising loses real matches\nsilently, and it loses them preferentially in repeats, where indels concentrate.\n\nNormalise — trim to parsimony, then left-align against the reference — before any\ncomparison:\n\n```bash\npython3 normalize_variant.py --fasta ref.fa chr1 7 CAC C\npython3 normalize_variant.py --fasta ref.fa --split --input cohort.vcf\npython3 normalize_variant.py --fasta ref.fa --compare chr1:7:CAC:C chr1:2:GCA:G\n```\n\n```\ninput         normalized    type      pos_shift  ref_check  changed\nchr1:7:CAC:C  chr1:2:GCA:G  deletion  5          ok         yes\n```\n\nEvery record's `REF` is checked against the FASTA first. A `MISMATCH` means the\nvariants and the reference are different assemblies — stop and run\n`check_contigs.py` rather than adjusting coordinates. Multi-allelic records must\nbe split with `--split` **before** normalising, never after.\n\nHGVS shifts indels the opposite way, 3'-most along the transcript. For a\nminus-strand gene that is the opposite genomic direction from VCF's\nleft-alignment. Details and the full procedure: `references\u002Fvariant-representation.md`.\n\n## Check the assembly before trusting a join\n\n```bash\npython3 check_contigs.py --identify unknown.fa.fai\npython3 check_contigs.py variants.vcf annotation.gtf --genome GRCh38.fa.fai\n```\n\n```\nfile          kind    contigs  naming        assembly  detail\nref.fa.fai    sizes   25       plain         GRCh37    24\u002F24 primary chromosome lengths match;\n                                                       chrM is 16569 bp, i.e. GRCh37\u002F38 (rCRS MT)\n```\n\nThe script reads `.fai`, `.chrom.sizes`, VCF headers, SAM headers, FASTA, BED,\nand GTF\u002FGFF, identifies the assembly from primary-chromosome lengths, and reports\nevery reason a join between two files would go wrong: naming mismatch, length\nconflict, coordinates past a contig end, contigs present in one file only. Exit\ncode 1 on any incompatibility.\n\n**GRCh37 and hg19 differ only in the mitochondrion** — 16,569 bp (rCRS) versus\n16,571 bp. Nuclear coordinates are identical, so a mixed pipeline runs fine and\nonly the mtDNA results are wrong. `check_contigs.py` reports which one it found.\nBuilds, naming schemes, ALT contigs, and liftover pitfalls:\n`references\u002Freference-builds.md`.\n\n## Audit a file against its own format\n\n```bash\npython3 audit_intervals.py peaks.bed\npython3 audit_intervals.py gencode.gtf --genome hg38.chrom.sizes\npython3 audit_intervals.py cohort.vcf --genome GRCh38.fa.fai\n```\n\nLooks for the evidence that a coordinate mistake leaves behind:\n\n| Finding | What it proves |\n| --- | --- |\n| `start_below_one` in GFF\u002FGTF | 0-based data in a 1-based file; everything is one base left |\n| `many_zero_length` in BED | 1-based single-base features written into a 0-based file |\n| `past_contig_end` | wrong assembly, or an off-by-one at the contig edge |\n| `mixed_contig_naming` | any join will silently match one subset |\n| `first_block_offset` | BED12 `blockStarts` written as absolute coordinates |\n| `not_parsimonious` | untrimmed alleles; normalise before joining |\n| `bad_alt_allele` | Ensembl\u002FVEP `-` notation in a VCF, which has no anchor base |\n\nExit code 1 on any fatal finding, so it works as a CI gate on a data directory.\n\n## Transcript, CDS, and protein positions\n\n`c.742` and `chr17:7,674,220` are both \"position\", and neither converts to the\nother by arithmetic. Transcript coordinates count spliced bases in transcription\norder — decreasing genomic coordinate on the minus strand — and `c.1` is the `A`\nof the initiator `ATG`, not the start of the transcript.\n\nThe rules that get mis-remembered: there is no `c.0`; 5' UTR positions are\nnegative and 3' UTR positions take a `*`; GFF phase is the bases to *remove* to\nreach the next codon, not `start % 3`; and a `c.` description is meaningless\nwithout a versioned transcript accession, because the same variant numbers\ndifferently in each transcript. `references\u002Ftranscript-coordinates.md` has the\nconversion procedure and the boundary cases.\n\nDo the conversion with a tool that holds the transcript model — VEP,\n`bcftools csq`, Mutalyzer, the `hgvs` package — not by hand.\n\n## Reporting results\n\nState the assembly next to the coordinates, every time.\n`chr7:5,530,601-5,530,625` is not a location; `chr7:5,530,601-5,530,625 (GRCh38)`\nis. Say which convention a coordinate column is in, in the column header or the\nfile's documentation. When a conversion produced a result, say which direction it\nwent.\n\n## References\n\n- `references\u002Fformat-conventions.md` — every format's convention, with per-format\n  detail, BED12 block rules, region-string syntax, and tool behaviour.\n- `references\u002Fvariant-representation.md` — VCF allele conventions, the\n  normalisation algorithm, equivalence checking, multi-allelic splitting, and how\n  HGVS disagrees with VCF.\n- `references\u002Freference-builds.md` — build signatures, GRCh37 vs hg19, ALT\n  contigs, naming schemes, and liftover failure modes.\n- `references\u002Ftranscript-coordinates.md` — genomic ↔ transcript ↔ CDS ↔ protein,\n  HGVS numbering, phase, and transcript choice.\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 and no network access. Variant normalisation needs a reference FASTA, and uses its .fai index when one is present.","nik-claude-toolkit","4feaa2876384b593d9e30d9190bc56985eeeeb8e","skills\u002Fgenomic-coordinates","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 genomic-coordinates",{"tool":41,"command":42},"bunx","bunx skills add nikhilesh-s\u002Fclaude-toolkit --skill genomic-coordinates",{"tool":44,"command":45},"pnpm","pnpm dlx skills add nikhilesh-s\u002Fclaude-toolkit --skill genomic-coordinates","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgenomic-coordinates\u002FSKILL.md",true,[49,55,59,63,67,73,77,81,85],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fformat-conventions.md","REFERENCE","参考文档",9511,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgenomic-coordinates\u002Freferences\u002Fformat-conventions.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Freference-builds.md",7150,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgenomic-coordinates\u002Freferences\u002Freference-builds.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Ftranscript-coordinates.md",6334,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgenomic-coordinates\u002Freferences\u002Ftranscript-coordinates.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fvariant-representation.md",6274,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgenomic-coordinates\u002Freferences\u002Fvariant-representation.md",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"scripts\u002F_common.py","SCRIPT","脚本",13550,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgenomic-coordinates\u002Fscripts\u002F_common.py",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"scripts\u002Faudit_intervals.py",19077,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgenomic-coordinates\u002Fscripts\u002Faudit_intervals.py",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"scripts\u002Fcheck_contigs.py",16049,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgenomic-coordinates\u002Fscripts\u002Fcheck_contigs.py",{"path":82,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":83,"sourceHtmlUrl":84},"scripts\u002Fconvert_coords.py",6618,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgenomic-coordinates\u002Fscripts\u002Fconvert_coords.py",{"path":86,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fnormalize_variant.py",9962,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgenomic-coordinates\u002Fscripts\u002Fnormalize_variant.py",[90,97,105,112,119,126],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"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":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"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":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"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",[],[]]