[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74YPN5RCBTPFQ3FMFDXH6DS":3,"skill-same:01M74YPN5RCBTPFQ3FMFDXH6DS":95},{"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":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":36,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M74YPN5RCBTPFQ3FMFDXH6DS","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\".","KalarisLabs\u002Fresearch-agent-skills","KalarisLabs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F300878568?v=4","01M74Y7MT23GXXC56VM6TVSXZY","Kalarislabs","01M74Y7MTQM9REXZX4SNXWX95C",132,"MIT","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenomic-coordinates\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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.1'\n  category: scientific-databases\n  maintainer: Kalaris Labs\n  tags: genomic coordinates, liftover, variant normalization, genome assemblies, bioinformatics\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\n## Agent operating procedure\n\n1. **Check the environment.** Confirm network access, API keys (if required) and the database's current API documentation and rate limits.\n2. **Pin down the inputs.** Confirm formats, identifiers and parameters from the data or the user. Ask rather than guess any value that changes the result.\n3. **Run a small version first.** Fetch a single known record and check the response format before bulk queries.\n4. **Execute the full task** using the instructions and references above.\n5. **Validate the result.** Identifiers resolve, record counts are reported, and the database version or access date is recorded.\n6. **Report.** State what was run (versions, commands, parameters), what was checked, and what is still uncertain.\n\n| If this happens | Do this |\n|---|---|\n| HTTP 429 or 5xx errors | Respect rate limits with backoff, batch requests, and report partial results honestly. |\n| A function, flag or endpoint in these instructions is missing in the installed version | Check the installed version's own documentation (`help()`, `--help`, official docs), adapt, and tell the user. Never invent an API. |\n| A required input, identifier or parameter is ambiguous | Ask the user, or state the assumption explicitly before running. |\n\n**Integrity rules**\n\n- Never fabricate results, parameters, identifiers, citations or statistics. If something cannot be run or verified, say so plainly.\n- Never invent accession numbers, IDs or records; report 'not found' instead.\n- Treat version-specific details here as possibly outdated: confirm them against the official documentation for the installed version.\n- Ask before actions that cost money, consume shared GPUs or cloud quota, touch personal or patient data, or cannot be undone.\n\n## Related skills\n\n- `polars-bio`: Python library polars-bio for genomic interval operations and bioinformatics file I\u002FO on Polars DataFrames, built on Arrow and DataFusion.\n- `gtars`: Inspects and plans work with Gtars, the Rust\u002FPython\u002FCLI toolkit for genomic intervals: BED RegionSet set algebra (reduce, setdiff, intersec…\n- `geniml`: Plans and audits local genomic-interval machine learning workflows with Geniml (0.8.4) and Gtars: validates BED files against chromosome si…\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\n## Agent operating procedure\n\n1. **Check the environment.** Confirm network access, API keys (if required) and the database's current API documentation and rate limits.\n2. **Pin down the inputs.** Confirm formats, identifiers and parameters from the data or the user. Ask rather than guess any value that changes the result.\n3. **Run a small version first.** Fetch a single known record and check the response format before bulk queries.\n4. **Execute the full task** using the instructions and references above.\n5. **Validate the result.** Identifiers resolve, record counts are reported, and the database version or access date is recorded.\n6. **Report.** State what was run (versions, commands, parameters), what was checked, and what is still uncertain.\n\n| If this happens | Do this |\n|---|---|\n| HTTP 429 or 5xx errors | Respect rate limits with backoff, batch requests, and report partial results honestly. |\n| A function, flag or endpoint in these instructions is missing in the installed version | Check the installed version's own documentation (`help()`, `--help`, official docs), adapt, and tell the user. Never invent an API. |\n| A required input, identifier or parameter is ambiguous | Ask the user, or state the assumption explicitly before running. |\n\n**Integrity rules**\n\n- Never fabricate results, parameters, identifiers, citations or statistics. If something cannot be run or verified, say so plainly.\n- Never invent accession numbers, IDs or records; report 'not found' instead.\n- Treat version-specific details here as possibly outdated: confirm them against the official documentation for the installed version.\n- Ask before actions that cost money, consume shared GPUs or cloud quota, touch personal or patient data, or cannot be undone.\n\n## Related skills\n\n- `polars-bio`: Python library polars-bio for genomic interval operations and bioinformatics file I\u002FO on Polars DataFrames, built on Arrow and DataFusion.\n- `gtars`: Inspects and plans work with Gtars, the Rust\u002FPython\u002FCLI toolkit for genomic intervals: BED RegionSet set algebra (reduce, setdiff, intersec…\n- `geniml`: Plans and audits local genomic-interval machine learning workflows with Geniml (0.8.4) and Gtars: validates BED files against chromosome si…\n",{"name":5,"license":15,"metadata":24,"description":7,"allowed-tools":29,"compatibility":30},{"tags":25,"version":26,"category":27,"maintainer":28},"genomic coordinates, liftover, variant normalization, genome assemblies, bioinformatics","1.1","scientific-databases","Kalaris Labs","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.","main","29fe36d26127205057d5e0ed8425f6b0e9a8c13a","skills\u002Fgenomic-coordinates",16,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills","https:\u002F\u002Fdocs.kalarislabs.com\u002Fresearch-agent-skills","https:\u002F\u002Fgithub.com\u002FKalarisLabs","kalarislabs.com","Applied AI lab building the infrastructure for the agentic era","2026-11-14 17:49:08",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add KalarisLabs\u002Fresearch-agent-skills --skill genomic-coordinates",{"tool":47,"command":48},"bunx","bunx skills add KalarisLabs\u002Fresearch-agent-skills --skill genomic-coordinates",{"tool":50,"command":51},"pnpm","pnpm dlx skills add KalarisLabs\u002Fresearch-agent-skills --skill genomic-coordinates","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenomic-coordinates\u002FSKILL.md",true,[55,61,65,69,73,79,83,87,91],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fformat-conventions.md","REFERENCE","参考文档",9511,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenomic-coordinates\u002Freferences\u002Fformat-conventions.md",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Freference-builds.md",7150,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenomic-coordinates\u002Freferences\u002Freference-builds.md",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Ftranscript-coordinates.md",6334,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenomic-coordinates\u002Freferences\u002Ftranscript-coordinates.md",{"path":70,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fvariant-representation.md",6274,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenomic-coordinates\u002Freferences\u002Fvariant-representation.md",{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002F_common.py","SCRIPT","脚本",13801,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenomic-coordinates\u002Fscripts\u002F_common.py",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"scripts\u002Faudit_intervals.py",19424,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenomic-coordinates\u002Fscripts\u002Faudit_intervals.py",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"scripts\u002Fcheck_contigs.py",17068,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenomic-coordinates\u002Fscripts\u002Fcheck_contigs.py",{"path":88,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":89,"sourceHtmlUrl":90},"scripts\u002Fconvert_coords.py",6706,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenomic-coordinates\u002Fscripts\u002Fconvert_coords.py",{"path":92,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Fnormalize_variant.py",10070,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenomic-coordinates\u002Fscripts\u002Fnormalize_variant.py",[96,103,110,117,124,131],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M74Z8MGT305R11SNY5G28QH5","plos","Prepare manuscripts for PLOS journals (PLOS ONE, PLOS Biology, PLOS Computational Biology, PLOS Genetics, PLOS Medicine, PLOS Pathogens, PLOS Neglected Tropical Diseases, PLOS Global Public Health and others), covering structure, abstract and author summary, Vancouver-style references, the mandatory data availability policy, ethics and financial disclosure statements, figure requirements (PACE), the PLOS LaTeX template, reporting guidelines and PLOS ONE's publication criteria. Use when targeting any PLOS journal or checking compliance with PLOS policies.","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fplos\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M74Z8CCN9APXYHNQ95V1EBGT","pkpd-modeling","Pharmacokinetic and pharmacodynamic modelling and simulation - non-compartmental analysis, compartmental and population PK, PK\u002FPD and exposure-response, TMDD, PBPK orientation, bioequivalence, allometric scaling and first-in-human dose, drug interaction prediction, and Bayesian therapeutic drug monitoring. Use when analysing concentration-time data, deriving exposure metrics, fitting PK or PD models, or evaluating dosing regimens. Triggers include \"pharmacokinetics\", \"pharmacodynamics\", \"PK\u002FPD\", \"NCA\", \"non-compartmental\", \"AUC\", \"Cmax\", \"lambda z\", \"half-life\", \"clearance\", \"volume of distribution\", \"compartmental model\", \"population PK\", \"popPK\", \"NONMEM\", \"nlmixr2\", \"Pharmpy\", \"Monolix\", \"exposure-response\", \"Emax\", \"EC50\", \"indirect response\", \"effect compartment\", \"TMDD\", \"PBPK\", \"bioequivalence\", \"RSABE\", \"ABEL\", \"allometric scaling\", \"first-in-human\", \"MABEL\", \"drug-drug interaction\", \"DDI\", \"ICH M12\", \"concentration-QTc\", \"therapeutic drug monitoring\", \"MIPD\", and \"dosing regimen\".","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fpkpd-modeling\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M74Z86YHJJ1FM3X87BHN76KZ","pinecone","Guides use of Pinecone, a managed serverless vector database, through its Python client and the LangChain and LlamaIndex integrations. Covers creating indexes, upserting and querying vectors, metadata filtering, namespaces, hybrid dense and sparse search, index management, and deleting vectors. Use when building a production RAG system on a hosted vector store, adding semantic search or recommendations without running infrastructure, isolating per-user or per-tenant data with namespaces, combining dense and sparse vectors in one query, or filtering results by metadata. Do not use for self-hosted or local stores (Chroma, Weaviate) or offline similarity search (FAISS).","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fpinecone\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":19},"01M74Z80T6E89SAJ8MYDD0767Q","pi-agent","Build with and use Pi, the minimal terminal coding harness. Use for installing Pi, configuring providers\u002Fmodels\u002Fsettings\u002Fenvironment variables, creating Pi skills\u002Fextensions\u002Fpackages\u002Fthemes\u002Fprompt templates, embedding Pi through the SDK, integrating over RPC or JSON event streams, parsing sessions, running local models through the llama.cpp router, developing custom Pi providers and TUI components, or using ecosystem packages such as pi-subagents (delegation\u002Forchestration), pi-mcp-adapter (MCP servers), pi-interview (interactive forms), and pi-web-access (web search, fetching, video understanding).","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fpi-agent\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":19},"01M74Z7WF1Y8Q3VFAQPPPRAFMV","phoenix-observability","Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fphoenix-observability\u002FSKILL.md",[],[],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":19},"01M74Z7HNEH1A2AVYR3G1X2QV6","peft-fine-tuning","Fine-tunes LLMs with Hugging Face PEFT, using LoRA, QLoRA, IA3, AdaLoRA, prefix tuning, and prompt tuning so that under 1% of parameters are trained. Covers rank, alpha, and target module selection, loading and merging adapters, multi-adapter serving, and integration with TRL SFTTrainer, Axolotl, and vLLM. Use when fine-tuning 7B-70B models on limited GPU memory, when running QLoRA on a single 24GB GPU, when choosing LoRA rank and alpha, when merging or swapping adapters on one base model, or when debugging CUDA OOM or an adapter that does not apply. Not for full fine-tuning of small models under 1B parameters or cases needing all weights updated.","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fpeft-fine-tuning\u002FSKILL.md",[],[]]