[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75MDAZSC33QP831D4VRGGQP":3,"skill-same:01M75MDAZSC33QP831D4VRGGQP":84},{"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},"01M75MDAZSC33QP831D4VRGGQP","matlab-analyze-dependencies",null,"Analyze the effective toolbox file set to produce a Dependency Manifest — classify all transitive dependencies as included, product, add-on, or external-unresolved, then present resolution options with tradeoffs. Use after matlab-define-toolbox-api when the spec is approved.","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-analyze-dependencies\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-analyze-dependencies\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: matlab-analyze-dependencies\ndescription: \"Analyze the effective toolbox file set to produce a Dependency Manifest — classify all transitive dependencies as included, product, add-on, or external-unresolved, then present resolution options with tradeoffs. Use after matlab-define-toolbox-api when the spec is approved.\"\nlicense: MathWorks BSD-3-Clause\nmetadata:\n  author: MathWorks\n  version: \"1.0\"\n---\n\n# matlab-analyze-dependencies — Dependency Analyzer\n\nYou produce the **Dependency Manifest**: a complete picture of what the toolbox needs at runtime, what ships inside the .mltbx, and what doesn't. For anything that doesn't ship, you explain why and present resolution options.\n\n## When to Use\n\n- After `matlab-define-toolbox-api` spec is approved, or user asks \"what does this code depend on?\"\n- Re-running after code changes to update the manifest\n\n## When NOT to Use\n\n- Writing code or fixing bugs — this skill only analyzes, it does not modify source\n- Building the .mltbx — use `matlab-build-toolbox` after dependencies are resolved\n- Initial project setup — use `matlab-define-toolbox-api` first to define the toolbox spec\n\n## Key Functions\n\n| Function | Purpose |\n|----------|---------|\n| `matlab.addons.toolbox.ToolboxOptions` | Determine effective file set (what ships) |\n| `matlab.codetools.requiredFilesAndProducts` | Trace transitive file and product dependencies |\n| `which` | Resolve namespace-qualified function names |\n| `exist` | Check if bare function names resolve |\n| `matlab.addons.installedAddons` | Correlate add-on file paths with metadata |\n\n## Critical Pitfalls\n\nThese three issues cause **silent failures** — no error is raised, but classification results are wrong. Always apply these fixes.\n\n### Pitfall 1: Path Separator Mismatch (Windows)\n\nOn Windows, `fList` returns backslashes regardless of input. If `toolboxRoot` has forward slashes, `startsWith(fList, toolboxRoot)` silently returns false for every file. **Normalize both before any comparison:**\n\n```matlab\ntoolboxRoot = replace(toolboxRoot, '\u002F', filesep);\nfList = replace(fList, '\u002F', filesep);\n```\n\n### Pitfall 2: matlabroot File Leak\n\nFiles under `matlabroot` (e.g., `toolbox\u002Flocal\u002Fuserpath.m`) occasionally appear in `fList` because they live in non-product folder structures. **Filter them out:**\n\n```matlab\nmroot = matlabroot;\nfList = fList(~startsWith(fList, mroot));\n```\n\n### Pitfall 3: Namespace Resolution Requires which()\n\n`exist('pkg.subpkg.func', 'file')` returns **0** even when the function is valid and on the path. For any dotted\u002Fnamespace-qualified name, use `which()` instead:\n\n```matlab\n% exist() FAILS for namespace calls:\nexist('statskit.internal.computeRange', 'file')  % returns 0 (wrong!)\n\n% which() WORKS:\nwhich('statskit.internal.computeRange')  % returns full path\n```\n\n**Resolution strategy:**\n- Bare names (no dots): `exist(name, 'file') > 0 || exist(name, 'builtin') > 0`\n- Dotted names: `~isempty(which(name))`\n\n## Core Concepts\n\n**The Packaging Constraint:** An .mltbx can only contain files inside the toolbox root folder. External files cannot be pulled in at install time. The only options are: copy in, declare add-on dependency, Additional Software (URL zip), or refactor.\n\n**The Effective File Set:** All files in toolbox root minus those excluded by the ignore file and default exclusions. Use `ToolboxOptions` to determine this authoritatively. The ignore file may be named `toolbox.ignore` (R2026a and earlier) or `package.ignore` (R2026b+). Check for both — `ToolboxOptions` handles whichever is present.\n\n## Workflow\n\n### Phase 1 — Determine the Effective File Set\n\n```matlab\nidentifier = matlab.lang.internal.uuid();\nopts = matlab.addons.toolbox.ToolboxOptions(toolboxRoot, identifier);\neffectiveFiles = opts.ToolboxFiles;\n```\n\nDo not reimplement ignore-file logic manually. `ToolboxOptions` handles both file names, default exclusions, and edge cases.\n\n### Phase 2 — Trace Dependencies\n\n```matlab\nmFiles = effectiveFiles(endsWith(effectiveFiles, \".m\") | endsWith(effectiveFiles, \".mlx\"));\n[fList, pList] = matlab.codetools.requiredFilesAndProducts(mFiles);\nfList = string(fList(:));\n```\n\nApply Pitfall 1 (normalize paths) and Pitfall 2 (filter matlabroot) **immediately after** getting fList, before any classification.\n\n**Classify files in fList:**\n- **Included**: starts with `toolboxRoot` and in effective set\n- **Add-on**: under `fullfile(getenv('APPDATA'), 'MathWorks', 'MATLAB Add-Ons')`\n- **External unresolved**: everything else — requires user decision\n\n**Classify products from pList:**\n- `Certain == 1`: confirmed product dependency — declare in metadata\n- `Certain == 0`: heuristic guess — flag for user confirmation\n\n**Check ignore conflicts:** Files inside toolbox root that are in `fList` but NOT in `effectiveFiles` — code needs them but they won't ship.\n\n**Check runtime file references:** `fList` never contains data files (.mat, .csv, images, etc.). Scan `.m` files for I\u002FO functions with string-literal path arguments to detect files that code needs at runtime but won't ship. See `references\u002Fruntime-file-references.md` for the full function list, regex patterns, and classification logic.\n\n### Phase 2b — Detect Unresolved Symbols\n\n`requiredFilesAndProducts` silently skips unresolvable symbols. A separate detection step is needed.\n\n**Do NOT rely on `checkcode`\u002F`codeIssues`** — MATLAB's static analyzer is intentionally lenient about unresolved functions.\n\nFor each file, extract candidate function names (via `mtree` or regex `(?\u003C![%.\\w])([a-zA-Z]\\w*)\\s*\\(`). Filter out:\n- MATLAB keywords (`if`, `for`, `while`, `switch`, `function`, `arguments`, `end`, `return`)\n- The function's own name\n- Local functions defined in the same file\n- Variables in `arguments` blocks (validation syntax looks like function calls to regex)\n- Functions from `localfunctions` pattern (test files)\n\nFor dotted identifiers (regex: `([a-zA-Z]\\w*(?:\\.[a-zA-Z]\\w*)*)(?=\\s*\\()`), apply Pitfall 3 — use `which()`.\n\nClassify unresolved symbols and present with resolution suggestions. See `references\u002Funresolved-symbol-classification.md` for the full classification table and presentation format.\n\n### Phase 3 — Transitive Closure of External Files\n\nFor each external file, trace its dependency subtree. At each level classify children. Build the tree showing pull-in cost.\n\n**Early termination:** If subtree exceeds ~15 files across multiple directories, mark as \"sprawling\" — needs architectural resolution, not file-by-file copying.\n\n**Deduplication:** Use `'toponly'` on each toolbox file to find which externals are directly called. Externals only reached transitively through another external are nested under their parent, not shown as top-level decisions.\n\n**Detect patterns:** Multiple externals from same directory → group them. Parent folder has `.prj` or `resources\u002Fproject\u002F` → belongs to a MATLAB Project.\n\n### Phase 4 — Present Results\n\nProduce a tree view showing directly-called externals with call chains and transitive cost, plus a summary table. See `references\u002Ftree-view-format.md` for formatting guidance.\n\n### Phase 5 — Recommend Resolution Options\n\nPresent options with tradeoffs for each unresolved external or group. See `references\u002Fresolution-options.md` for the option matrix and outward-refactor handoff template.\n\nThis skill **does not perform resolutions**. It presents options so the user (or a downstream skill that handles toolbox structure) can act. Do not copy files, edit ignore files, or refactor code.\n\n### Phase 6 — Persist the Manifest\n\nAfter the user acknowledges the analysis, save as `buildUtilities\u002FtbxManifest.m`. The manifest records the current state — what ships, what's external, what's unresolved — not the resolution decisions. See `scripts\u002FtbxManifest-template.m` for the template structure.\n\n## Output\n\n- **Primary artifact**: `buildUtilities\u002FtbxManifest.m`\n- **Display**: Tree view + summary table + recommendations in conversation\n\n## Scope Boundary\n\nThis skill only **analyzes and recommends**. It does not:\n- Copy or move files into the toolbox\n- Edit ignore files\n- Refactor code or fix typos\n- Modify the MATLAB path\n\nThese actions are the user's responsibility or belong to a downstream skill that understands how the toolbox should be structured. After resolutions are applied externally, re-run this skill to confirm progress.\n\n## Key Rules\n\n- Show the full transitive cost of pulling in any external\n- Surface same-folder groups as one architectural decision, not N individual ones\n- Present resolution options with tradeoffs — do not execute them\n- After resolution (done externally), re-running should show progress (externals become included or add-on)\n- Flag ignore conflicts — a needed-but-excluded file is a silent packaging bug\n\n## Next Steps\n\n- `\u002Fmatlab-create-project` — organize files into a MATLAB project with the resolved dependency structure\n\n----\n\nCopyright 2026 The MathWorks, Inc.\n\n----\n","# matlab-analyze-dependencies — Dependency Analyzer\n\nYou produce the **Dependency Manifest**: a complete picture of what the toolbox needs at runtime, what ships inside the .mltbx, and what doesn't. For anything that doesn't ship, you explain why and present resolution options.\n\n## When to Use\n\n- After `matlab-define-toolbox-api` spec is approved, or user asks \"what does this code depend on?\"\n- Re-running after code changes to update the manifest\n\n## When NOT to Use\n\n- Writing code or fixing bugs — this skill only analyzes, it does not modify source\n- Building the .mltbx — use `matlab-build-toolbox` after dependencies are resolved\n- Initial project setup — use `matlab-define-toolbox-api` first to define the toolbox spec\n\n## Key Functions\n\n| Function | Purpose |\n|----------|---------|\n| `matlab.addons.toolbox.ToolboxOptions` | Determine effective file set (what ships) |\n| `matlab.codetools.requiredFilesAndProducts` | Trace transitive file and product dependencies |\n| `which` | Resolve namespace-qualified function names |\n| `exist` | Check if bare function names resolve |\n| `matlab.addons.installedAddons` | Correlate add-on file paths with metadata |\n\n## Critical Pitfalls\n\nThese three issues cause **silent failures** — no error is raised, but classification results are wrong. Always apply these fixes.\n\n### Pitfall 1: Path Separator Mismatch (Windows)\n\nOn Windows, `fList` returns backslashes regardless of input. If `toolboxRoot` has forward slashes, `startsWith(fList, toolboxRoot)` silently returns false for every file. **Normalize both before any comparison:**\n\n```matlab\ntoolboxRoot = replace(toolboxRoot, '\u002F', filesep);\nfList = replace(fList, '\u002F', filesep);\n```\n\n### Pitfall 2: matlabroot File Leak\n\nFiles under `matlabroot` (e.g., `toolbox\u002Flocal\u002Fuserpath.m`) occasionally appear in `fList` because they live in non-product folder structures. **Filter them out:**\n\n```matlab\nmroot = matlabroot;\nfList = fList(~startsWith(fList, mroot));\n```\n\n### Pitfall 3: Namespace Resolution Requires which()\n\n`exist('pkg.subpkg.func', 'file')` returns **0** even when the function is valid and on the path. For any dotted\u002Fnamespace-qualified name, use `which()` instead:\n\n```matlab\n% exist() FAILS for namespace calls:\nexist('statskit.internal.computeRange', 'file')  % returns 0 (wrong!)\n\n% which() WORKS:\nwhich('statskit.internal.computeRange')  % returns full path\n```\n\n**Resolution strategy:**\n- Bare names (no dots): `exist(name, 'file') > 0 || exist(name, 'builtin') > 0`\n- Dotted names: `~isempty(which(name))`\n\n## Core Concepts\n\n**The Packaging Constraint:** An .mltbx can only contain files inside the toolbox root folder. External files cannot be pulled in at install time. The only options are: copy in, declare add-on dependency, Additional Software (URL zip), or refactor.\n\n**The Effective File Set:** All files in toolbox root minus those excluded by the ignore file and default exclusions. Use `ToolboxOptions` to determine this authoritatively. The ignore file may be named `toolbox.ignore` (R2026a and earlier) or `package.ignore` (R2026b+). Check for both — `ToolboxOptions` handles whichever is present.\n\n## Workflow\n\n### Phase 1 — Determine the Effective File Set\n\n```matlab\nidentifier = matlab.lang.internal.uuid();\nopts = matlab.addons.toolbox.ToolboxOptions(toolboxRoot, identifier);\neffectiveFiles = opts.ToolboxFiles;\n```\n\nDo not reimplement ignore-file logic manually. `ToolboxOptions` handles both file names, default exclusions, and edge cases.\n\n### Phase 2 — Trace Dependencies\n\n```matlab\nmFiles = effectiveFiles(endsWith(effectiveFiles, \".m\") | endsWith(effectiveFiles, \".mlx\"));\n[fList, pList] = matlab.codetools.requiredFilesAndProducts(mFiles);\nfList = string(fList(:));\n```\n\nApply Pitfall 1 (normalize paths) and Pitfall 2 (filter matlabroot) **immediately after** getting fList, before any classification.\n\n**Classify files in fList:**\n- **Included**: starts with `toolboxRoot` and in effective set\n- **Add-on**: under `fullfile(getenv('APPDATA'), 'MathWorks', 'MATLAB Add-Ons')`\n- **External unresolved**: everything else — requires user decision\n\n**Classify products from pList:**\n- `Certain == 1`: confirmed product dependency — declare in metadata\n- `Certain == 0`: heuristic guess — flag for user confirmation\n\n**Check ignore conflicts:** Files inside toolbox root that are in `fList` but NOT in `effectiveFiles` — code needs them but they won't ship.\n\n**Check runtime file references:** `fList` never contains data files (.mat, .csv, images, etc.). Scan `.m` files for I\u002FO functions with string-literal path arguments to detect files that code needs at runtime but won't ship. See `references\u002Fruntime-file-references.md` for the full function list, regex patterns, and classification logic.\n\n### Phase 2b — Detect Unresolved Symbols\n\n`requiredFilesAndProducts` silently skips unresolvable symbols. A separate detection step is needed.\n\n**Do NOT rely on `checkcode`\u002F`codeIssues`** — MATLAB's static analyzer is intentionally lenient about unresolved functions.\n\nFor each file, extract candidate function names (via `mtree` or regex `(?\u003C![%.\\w])([a-zA-Z]\\w*)\\s*\\(`). Filter out:\n- MATLAB keywords (`if`, `for`, `while`, `switch`, `function`, `arguments`, `end`, `return`)\n- The function's own name\n- Local functions defined in the same file\n- Variables in `arguments` blocks (validation syntax looks like function calls to regex)\n- Functions from `localfunctions` pattern (test files)\n\nFor dotted identifiers (regex: `([a-zA-Z]\\w*(?:\\.[a-zA-Z]\\w*)*)(?=\\s*\\()`), apply Pitfall 3 — use `which()`.\n\nClassify unresolved symbols and present with resolution suggestions. See `references\u002Funresolved-symbol-classification.md` for the full classification table and presentation format.\n\n### Phase 3 — Transitive Closure of External Files\n\nFor each external file, trace its dependency subtree. At each level classify children. Build the tree showing pull-in cost.\n\n**Early termination:** If subtree exceeds ~15 files across multiple directories, mark as \"sprawling\" — needs architectural resolution, not file-by-file copying.\n\n**Deduplication:** Use `'toponly'` on each toolbox file to find which externals are directly called. Externals only reached transitively through another external are nested under their parent, not shown as top-level decisions.\n\n**Detect patterns:** Multiple externals from same directory → group them. Parent folder has `.prj` or `resources\u002Fproject\u002F` → belongs to a MATLAB Project.\n\n### Phase 4 — Present Results\n\nProduce a tree view showing directly-called externals with call chains and transitive cost, plus a summary table. See `references\u002Ftree-view-format.md` for formatting guidance.\n\n### Phase 5 — Recommend Resolution Options\n\nPresent options with tradeoffs for each unresolved external or group. See `references\u002Fresolution-options.md` for the option matrix and outward-refactor handoff template.\n\nThis skill **does not perform resolutions**. It presents options so the user (or a downstream skill that handles toolbox structure) can act. Do not copy files, edit ignore files, or refactor code.\n\n### Phase 6 — Persist the Manifest\n\nAfter the user acknowledges the analysis, save as `buildUtilities\u002FtbxManifest.m`. The manifest records the current state — what ships, what's external, what's unresolved — not the resolution decisions. See `scripts\u002FtbxManifest-template.m` for the template structure.\n\n## Output\n\n- **Primary artifact**: `buildUtilities\u002FtbxManifest.m`\n- **Display**: Tree view + summary table + recommendations in conversation\n\n## Scope Boundary\n\nThis skill only **analyzes and recommends**. It does not:\n- Copy or move files into the toolbox\n- Edit ignore files\n- Refactor code or fix typos\n- Modify the MATLAB path\n\nThese actions are the user's responsibility or belong to a downstream skill that understands how the toolbox should be structured. After resolutions are applied externally, re-run this skill to confirm progress.\n\n## Key Rules\n\n- Show the full transitive cost of pulling in any external\n- Surface same-folder groups as one architectural decision, not N individual ones\n- Present resolution options with tradeoffs — do not execute them\n- After resolution (done externally), re-running should show progress (externals become included or add-on)\n- Flag ignore conflicts — a needed-but-excluded file is a silent packaging bug\n\n## Next Steps\n\n- `\u002Fmatlab-create-project` — organize files into a MATLAB project with the resolved dependency structure\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-analyze-dependencies",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-analyze-dependencies",{"tool":43,"command":44},"bunx","bunx skills add stanfish06\u002Fskillquarium --skill matlab-analyze-dependencies",{"tool":46,"command":47},"pnpm","pnpm dlx skills add stanfish06\u002Fskillquarium --skill matlab-analyze-dependencies","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-analyze-dependencies\u002FSKILL.md",true,[51,56,62,66,70,74,78],{"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","参考文档",363,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-analyze-dependencies\u002Fmanifest.yaml",{"path":63,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fresolution-options.md",3245,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-analyze-dependencies\u002Freferences\u002Fresolution-options.md",{"path":67,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fruntime-file-references.md",2997,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-analyze-dependencies\u002Freferences\u002Fruntime-file-references.md",{"path":71,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Ftree-view-format.md",1811,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-analyze-dependencies\u002Freferences\u002Ftree-view-format.md",{"path":75,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Funresolved-symbol-classification.md",2910,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-analyze-dependencies\u002Freferences\u002Funresolved-symbol-classification.md",{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"scripts\u002FtbxManifest-template.m","SCRIPT","脚本",1376,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-analyze-dependencies\u002Fscripts\u002FtbxManifest-template.m",[85,93,102,109,116,123],{"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":89,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"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":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":130,"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",[],[]]