[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75MFCNBCR9EE6R5HCMKFQ4M":3,"skill-same:01M75MFCNBCR9EE6R5HCMKFQ4M":68},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M75MFCNBCR9EE6R5HCMKFQ4M","matlab-define-toolbox-api",null,"Scan a folder, triage files into include\u002Fexclude, identify the public API, and produce a toolboxSpecification.m Interface Spec — all in one pass. Use when turning loose code into a toolbox.","stanfish06\u002Fskillquarium","stanfish06","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F93099613?v=4","01M75F1CK4ZW109ZK3T26VN52F","Zhiyuan","01M75F1CM53VH6F79DZ8GXKKES",12,"BSD-2-Clause","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-define-toolbox-api\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-define-toolbox-api\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: matlab-define-toolbox-api\ndescription: \"Scan a folder, triage files into include\u002Fexclude, identify the public API, and produce a toolboxSpecification.m Interface Spec — all in one pass. Use when turning loose code into a toolbox.\"\nlicense: MathWorks BSD-3-Clause\nmetadata:\n  author: MathWorks\n  version: \"1.0\"\n---\n\n# matlab-define-toolbox-api — Toolbox Scope & Spec Generator\n\nYou take a folder of code, figure out what belongs in the toolbox, identify the public API, and produce the Interface Spec — the contract defining what the toolbox exposes. One skill, one artifact.\n\n## When to Use\n\n- User wants to turn code into a toolbox\n- User points at a folder and says \"make this a toolbox\" or \"package this\"\n- User has a mix of scripts, functions, tests, data, and scratch files\n- Starting the files-to-package pipeline from scratch\n\n## When NOT to Use\n\n- Adding files to an existing spec — edit `buildUtilities\u002FtoolboxSpecification.m` directly\n- Analyzing dependencies — use `matlab-analyze-dependencies` after the spec is approved\n- Building the .mltbx package — use `matlab-build-toolbox`\n- Documenting the toolbox — use `matlab-document-toolbox`\n\n## Key Functions\n\n| Function | Purpose |\n|----------|---------|\n| `dir` | Recursive file listing for inventory |\n| `which` | Resolve function locations on path |\n| `exist` | Check whether a name resolves to a file, folder, or built-in |\n| `matlab.codetools.requiredFilesAndProducts` | Trace caller\u002Fcallee relationships for Support classification |\n\n## Inputs\n\n| Input | Required | Description |\n|-------|----------|-------------|\n| **path** | No | Folder or list of files to analyze. If not provided, prompt the user. |\n| **purpose** | No | What the toolbox does and who uses it. If not provided, prompt the user. |\n\n## Workflow\n\n### Step 1 — Gather Inputs\n\nIf **path** is not provided:\n> What folder or files would you like to package as a toolbox?\n\nIf **purpose** is not provided:\n> In a sentence or two, what does this toolbox do? Who will use it?\n\nDo not proceed until both are provided.\n\n### Step 2 — Inventory the Folder\n\nScan the path recursively. Classify every file:\n\n| Category | Detection Rule |\n|----------|---------------|\n| **Function** | `.m` file with `function` keyword on first non-comment line |\n| **Class** | `.m` file with `classdef` keyword |\n| **Script** | `.m` file with no `function`\u002F`classdef` keyword |\n| **Live Script** | `.mlx` file |\n| **Test** | In `tests\u002F`\u002F`test\u002F` folder, or name matches `*Test.m`, `*_test.m`, `test_*.m` |\n| **Data** | `.mat`, `.csv`, `.xlsx`, `.json`, `.xml` (non-config) |\n| **Config\u002FMeta** | `buildfile.m`, `projectStartup.m`, `Contents.m`, `.prj`, `resources\u002F` |\n| **Scratch\u002FTemp** | In `scratch\u002F`, `tmp\u002F`, or names like `untitled*.m`, `Copy_of_*` |\n| **Other** | READMEs, images, licenses, etc. |\n\n### Step 3 — Classify Relevance\n\nUsing the **purpose** as guide, classify each file:\n\n- **Include** — directly serves the toolbox's stated purpose\n- **Support** — needed by included files (helper\u002Futility called internally)\n- **Exclude** — not relevant (tests, scratch, unrelated code)\n- **Uncertain** — needs user input\n\nHeuristics:\n\n| Signal | Disposition |\n|--------|-------------|\n| Function name aligns with purpose keywords | Include |\n| H1 text mentions concepts from purpose | Include |\n| Called by an included file | Support |\n| In `private\u002F` or `+internal` folder | Support |\n| Test file for an included function | Exclude |\n| Script with no connection to purpose | Exclude |\n| Data file referenced by included code | Include |\n| Scratch\u002Ftemp naming pattern | Exclude |\n\n### Step 4 — Identify Public API\n\nFrom the **Include** set, determine visibility:\n\n| Signal | Classification |\n|--------|---------------|\n| Has H1 help text | Likely public |\n| Has `arguments` block or input validation | Likely public |\n| Descriptive action-oriented name | Likely public |\n| Classdef with public methods | Public |\n| Called by others but not standalone | Internal |\n| In `private\u002F` or generic utility name | Internal |\n| Script | Example\u002Fentry point |\n\n### Step 5 — Present Report & Get Confirmation\n\nDisplay a combined scope + API report:\n\n```\n## Toolbox Scope & API — [Name]\n\n**Purpose:** [user's stated purpose]\n**Source:** [path]\n**Total files:** N\n\n### Public API (N functions)\n| Function | Signature | H1 | Category |\n|----------|-----------|-----|----------|\n\n### Internal Support (N files)\n| File | Type | Reason |\n|------|------|--------|\n\n### Excluded (N files)\n| File | Reason |\n|------|--------|\n\n### Uncertain — Need Your Input\n| File | Why Uncertain |\n|------|--------------|\n```\n\nThen ask:\n> **Please review:**\n> 1. Should any excluded files be included?\n> 2. Should any included files be removed?\n> 3. For uncertain files — include or exclude?\n> 4. Is the public API surface correct?\n> 5. What categories should functions be grouped into? (e.g., \"Analysis\", \"I\u002FO\", \"Visualization\")\n\nIncorporate feedback before proceeding.\n\n### Step 6 — Generate Interface Spec\n\nProduce `toolboxSpecification.m` using `scripts\u002FtoolboxSpecificationTemplate.m` as the structure. `spec.entries` is a **cell array** (not a struct array) because `classdef` entries have extra fields (`methods`, `properties`) that `function` entries lack — MATLAB cannot concatenate structs with mismatched fields. Access entries via `spec.entries{i}`. Each entry has a `\"type\"` field — either `\"function\"` or `\"classdef\"`. See the template for the full field conventions for both types.\n\nSave to `buildUtilities\u002FtoolboxSpecification.m` in the project root (create the folder if needed). This folder is excluded from the toolbox package via `toolbox.ignore` or `package.ignore`.\n\n## Output\n\n- **Single artifact**: `buildUtilities\u002FtoolboxSpecification.m` — executable spec as a MATLAB struct\n- **Display**: Markdown report shown during the session for review\n- **Downstream**: Other skills (`matlab-assess-toolbox`, `matlab-build-toolbox`, `matlab-analyze-dependencies`) consume `toolboxSpecification.m`\n\n## Checkpoint\n\n**This skill always pauses for user approval at Step 5.** The user must confirm scope and public API before the spec is generated. Nothing is written until confirmation.\n\n## Key Rules\n\n- **Always prompt if inputs are missing.** Never guess the path or purpose.\n- **Every file is accounted for.** Nothing is silently dropped — files are included, excluded (with reason), or flagged as uncertain.\n- **Purpose drives classification.** The user's stated intent is the primary filter.\n- **Uncertain is valid.** Surface ambiguity rather than guessing wrong.\n- **Reasons are mandatory.** Every include\u002Fexclude decision has a stated reason.\n- **Tests are excluded but acknowledged.** They're handled by `matlab-assess-toolbox` later.\n- **Scripts become examples.** Files without `function` keyword are examples\u002Fentry points, not public API.\n- **User decides visibility.** Heuristics suggest, user confirms.\n- **One artifact, build utilities.** Only `toolboxSpecification.m` is written, to `buildUtilities\u002F` — keeps source clean and is excluded from the packaged toolbox.\n\n## Next Steps\n\n- `\u002Fmatlab-analyze-dependencies` — resolve external dependencies identified in the Interface Spec\n- `\u002Fmatlab-create-project` — organize files into a MATLAB project using the spec as a guide\n\n----\n\nCopyright 2026 The MathWorks, Inc.\n\n----\n","# matlab-define-toolbox-api — Toolbox Scope & Spec Generator\n\nYou take a folder of code, figure out what belongs in the toolbox, identify the public API, and produce the Interface Spec — the contract defining what the toolbox exposes. One skill, one artifact.\n\n## When to Use\n\n- User wants to turn code into a toolbox\n- User points at a folder and says \"make this a toolbox\" or \"package this\"\n- User has a mix of scripts, functions, tests, data, and scratch files\n- Starting the files-to-package pipeline from scratch\n\n## When NOT to Use\n\n- Adding files to an existing spec — edit `buildUtilities\u002FtoolboxSpecification.m` directly\n- Analyzing dependencies — use `matlab-analyze-dependencies` after the spec is approved\n- Building the .mltbx package — use `matlab-build-toolbox`\n- Documenting the toolbox — use `matlab-document-toolbox`\n\n## Key Functions\n\n| Function | Purpose |\n|----------|---------|\n| `dir` | Recursive file listing for inventory |\n| `which` | Resolve function locations on path |\n| `exist` | Check whether a name resolves to a file, folder, or built-in |\n| `matlab.codetools.requiredFilesAndProducts` | Trace caller\u002Fcallee relationships for Support classification |\n\n## Inputs\n\n| Input | Required | Description |\n|-------|----------|-------------|\n| **path** | No | Folder or list of files to analyze. If not provided, prompt the user. |\n| **purpose** | No | What the toolbox does and who uses it. If not provided, prompt the user. |\n\n## Workflow\n\n### Step 1 — Gather Inputs\n\nIf **path** is not provided:\n> What folder or files would you like to package as a toolbox?\n\nIf **purpose** is not provided:\n> In a sentence or two, what does this toolbox do? Who will use it?\n\nDo not proceed until both are provided.\n\n### Step 2 — Inventory the Folder\n\nScan the path recursively. Classify every file:\n\n| Category | Detection Rule |\n|----------|---------------|\n| **Function** | `.m` file with `function` keyword on first non-comment line |\n| **Class** | `.m` file with `classdef` keyword |\n| **Script** | `.m` file with no `function`\u002F`classdef` keyword |\n| **Live Script** | `.mlx` file |\n| **Test** | In `tests\u002F`\u002F`test\u002F` folder, or name matches `*Test.m`, `*_test.m`, `test_*.m` |\n| **Data** | `.mat`, `.csv`, `.xlsx`, `.json`, `.xml` (non-config) |\n| **Config\u002FMeta** | `buildfile.m`, `projectStartup.m`, `Contents.m`, `.prj`, `resources\u002F` |\n| **Scratch\u002FTemp** | In `scratch\u002F`, `tmp\u002F`, or names like `untitled*.m`, `Copy_of_*` |\n| **Other** | READMEs, images, licenses, etc. |\n\n### Step 3 — Classify Relevance\n\nUsing the **purpose** as guide, classify each file:\n\n- **Include** — directly serves the toolbox's stated purpose\n- **Support** — needed by included files (helper\u002Futility called internally)\n- **Exclude** — not relevant (tests, scratch, unrelated code)\n- **Uncertain** — needs user input\n\nHeuristics:\n\n| Signal | Disposition |\n|--------|-------------|\n| Function name aligns with purpose keywords | Include |\n| H1 text mentions concepts from purpose | Include |\n| Called by an included file | Support |\n| In `private\u002F` or `+internal` folder | Support |\n| Test file for an included function | Exclude |\n| Script with no connection to purpose | Exclude |\n| Data file referenced by included code | Include |\n| Scratch\u002Ftemp naming pattern | Exclude |\n\n### Step 4 — Identify Public API\n\nFrom the **Include** set, determine visibility:\n\n| Signal | Classification |\n|--------|---------------|\n| Has H1 help text | Likely public |\n| Has `arguments` block or input validation | Likely public |\n| Descriptive action-oriented name | Likely public |\n| Classdef with public methods | Public |\n| Called by others but not standalone | Internal |\n| In `private\u002F` or generic utility name | Internal |\n| Script | Example\u002Fentry point |\n\n### Step 5 — Present Report & Get Confirmation\n\nDisplay a combined scope + API report:\n\n```\n## Toolbox Scope & API — [Name]\n\n**Purpose:** [user's stated purpose]\n**Source:** [path]\n**Total files:** N\n\n### Public API (N functions)\n| Function | Signature | H1 | Category |\n|----------|-----------|-----|----------|\n\n### Internal Support (N files)\n| File | Type | Reason |\n|------|------|--------|\n\n### Excluded (N files)\n| File | Reason |\n|------|--------|\n\n### Uncertain — Need Your Input\n| File | Why Uncertain |\n|------|--------------|\n```\n\nThen ask:\n> **Please review:**\n> 1. Should any excluded files be included?\n> 2. Should any included files be removed?\n> 3. For uncertain files — include or exclude?\n> 4. Is the public API surface correct?\n> 5. What categories should functions be grouped into? (e.g., \"Analysis\", \"I\u002FO\", \"Visualization\")\n\nIncorporate feedback before proceeding.\n\n### Step 6 — Generate Interface Spec\n\nProduce `toolboxSpecification.m` using `scripts\u002FtoolboxSpecificationTemplate.m` as the structure. `spec.entries` is a **cell array** (not a struct array) because `classdef` entries have extra fields (`methods`, `properties`) that `function` entries lack — MATLAB cannot concatenate structs with mismatched fields. Access entries via `spec.entries{i}`. Each entry has a `\"type\"` field — either `\"function\"` or `\"classdef\"`. See the template for the full field conventions for both types.\n\nSave to `buildUtilities\u002FtoolboxSpecification.m` in the project root (create the folder if needed). This folder is excluded from the toolbox package via `toolbox.ignore` or `package.ignore`.\n\n## Output\n\n- **Single artifact**: `buildUtilities\u002FtoolboxSpecification.m` — executable spec as a MATLAB struct\n- **Display**: Markdown report shown during the session for review\n- **Downstream**: Other skills (`matlab-assess-toolbox`, `matlab-build-toolbox`, `matlab-analyze-dependencies`) consume `toolboxSpecification.m`\n\n## Checkpoint\n\n**This skill always pauses for user approval at Step 5.** The user must confirm scope and public API before the spec is generated. Nothing is written until confirmation.\n\n## Key Rules\n\n- **Always prompt if inputs are missing.** Never guess the path or purpose.\n- **Every file is accounted for.** Nothing is silently dropped — files are included, excluded (with reason), or flagged as uncertain.\n- **Purpose drives classification.** The user's stated intent is the primary filter.\n- **Uncertain is valid.** Surface ambiguity rather than guessing wrong.\n- **Reasons are mandatory.** Every include\u002Fexclude decision has a stated reason.\n- **Tests are excluded but acknowledged.** They're handled by `matlab-assess-toolbox` later.\n- **Scripts become examples.** Files without `function` keyword are examples\u002Fentry points, not public API.\n- **User decides visibility.** Heuristics suggest, user confirms.\n- **One artifact, build utilities.** Only `toolboxSpecification.m` is written, to `buildUtilities\u002F` — keeps source clean and is excluded from the packaged toolbox.\n\n## Next Steps\n\n- `\u002Fmatlab-analyze-dependencies` — resolve external dependencies identified in the Interface Spec\n- `\u002Fmatlab-create-project` — organize files into a MATLAB project using the spec as a guide\n\n----\n\nCopyright 2026 The MathWorks, Inc.\n\n----\n",{"name":5,"license":25,"metadata":26,"description":7},"MathWorks BSD-3-Clause",{"author":27,"version":28},"MathWorks","1.0","master","49e49abf2f670d429e0b7e2c0349739c3fdd5cbe","skills\u002Fmatlab-define-toolbox-api",5,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium","https:\u002F\u002Fgithub.com\u002Fstanfish06","https:\u002F\u002Fwww.stanfish.dev\u002F","2026-11-14 21:31:37",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add stanfish06\u002Fskillquarium --skill matlab-define-toolbox-api",{"tool":43,"command":44},"bunx","bunx skills add stanfish06\u002Fskillquarium --skill matlab-define-toolbox-api",{"tool":46,"command":47},"pnpm","pnpm dlx skills add stanfish06\u002Fskillquarium --skill matlab-define-toolbox-api","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-define-toolbox-api\u002FSKILL.md",true,[51,56,62],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":16},"LICENSE.md","LICENSE","许可证",1482,{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"manifest.yaml","REFERENCE","参考文档",321,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-define-toolbox-api\u002Fmanifest.yaml",{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"scripts\u002FtoolboxSpecificationTemplate.m","SCRIPT","脚本",2243,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-define-toolbox-api\u002Fscripts\u002FtoolboxSpecificationTemplate.m",[69,77,86,93,100,107],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":20},"01M76ZJTRVA456GD7K8Y3EP82H","zarr-python","Stores and queries chunked N-D scientific arrays with Zarr-Python 3, including codecs, sharding, S3\u002FGCS storage, and NumPy\u002FDask\u002FXarray integration. Use for array layout, bounded I\u002FO, format migration, or scientific metadata preservation.","MIT","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":20},"01M76ZJQZ15Q1HKC5V85NHE325","yeet","Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":20},"01M76ZJ8ASZ4QYQ70Y6SBA4Z4S","xarray","N-dimensional labeled arrays and datasets in Python. Built on top of NumPy and Dask. It introduces labels in the form of dimensions, coordinates, and attributes on top of raw NumPy-like arrays, making data analysis in physical sciences more intuitive and less error-prone. Use for working with multi-dimensional scientific data, NetCDF\u002FGRIB\u002FZarr files, climate\u002Fweather\u002Foceanographic datasets, remote sensing, geospatial imaging, large out-of-memory datasets with Dask, and labeled array operations.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fxarray\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":73,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":20},"01M76ZHFBXD6VXPQ02VCEG202B","writing-mstest-tests","Use when asked to fix, rewrite, update, improve, modernize, show corrected code for, or explain existing MSTest tests or MSTest-specific configuration. Use for \"review\" when corrected code or edits are wanted, even for one pasted assertion or passing tests with bad failure output. Covers expected\u002Factual labels; generic Boolean, collection, string, numeric, null, identity, exception, hard-cast, and object[] checks; TestContext\u002Flifecycle; timeout\u002Fcancellation; OS\u002FCI conditions, retry, cleanup, parallelization, MSTest.Sdk project setup, and MSTESTxxxx. Honor the installed MSTest version. DO NOT USE to design new test cases (code-testing), perform report-only audits, create project files rather than explain MSTest setup, run tests, migrate frameworks, or handle non-MSTest\u002Fnon-.NET code.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwriting-mstest-tests\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":73,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":20},"01M76ZDFDF4N88RH6HSYGS7GP2","wgs-prs","End-to-end WGS to polygenic risk score pipeline. Takes paired-end FASTQ files (or a pre-existing VCF) through nf-core\u002Fsarek for variant calling, applies VCF QC (normalisation, hard filtering, Ti\u002FTv and Het\u002FHom checks), then computes polygenic risk scores via the PGS Catalog. Fills the FASTQ to VCF gap upstream of the gwas-prs skill.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwgs-prs\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":81,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":20},"01M76ZCC1SC68J42QK4MDC8RCG","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[]]