[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75ME40RAMF0FYWD6ZSN1R5W":3,"skill-same:01M75ME40RAMF0FYWD6ZSN1R5W":62},{"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},"01M75ME40RAMF0FYWD6ZSN1R5W","matlab-build-toolbox",null,"Execute the build plan — introspect buildfile.m, run its dependency chain, and produce the .mltbx toolbox package. Mechanical execution with no human checkpoint. Works with any buildplan shape.","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-build-toolbox\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-build-toolbox\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: matlab-build-toolbox\ndescription: \"Execute the build plan — introspect buildfile.m, run its dependency chain, and produce the .mltbx toolbox package. Mechanical execution with no human checkpoint. Works with any buildplan shape.\"\nlicense: MathWorks BSD-3-Clause\nmetadata:\n  author: MathWorks\n  version: \"1.0\"\n---\n\n# matlab-build-toolbox — Build Executor\n\nYou execute the build pipeline. You are an operator — you introspect the plan to find the right task to invoke, run it, report results at each stage, and stop on failure. This is the only skill in the pipeline with no human checkpoint.\n\n## When to Use\n\n- After `matlab-assess-toolbox` reports READY (no blockers)\n- User says \"build it\", \"run the build\", or \"build package\"\n- User has their own `buildfile.m` and wants to execute it\n- As part of the full pipeline after readiness gate passes\n\n## When NOT to Use\n\n- No `buildfile.m` exists — use `matlab-create-buildfile` first\n- User wants to create or modify build tasks — use `matlab-create-buildfile`\n- User wants to publish\u002Frelease — use `matlab-publish-toolbox` after a successful build\n- User wants a readiness check — use `matlab-assess-toolbox`\n\n## Key Functions\n\n| Function | Purpose |\n|----------|---------|\n| `matlab.buildtool.Plan.load` | Introspect the build plan to discover tasks and dependencies |\n| `buildtool` | Execute the build pipeline (runs task dependency chain) |\n| `dir` | Locate and verify the `.mltbx` artifact after packaging |\n\n## Inputs\n\n- **project_root**: Path to the project (default: current directory)\n- **target** (optional): The buildtool task to execute. If omitted, auto-detected from the plan (see Step 2).\n\n## Workflow\n\n### Step 1 — Verify Preconditions\n\nBefore executing:\n1. Confirm `buildfile.m` exists at the project root\n2. Determine pipeline context:\n   - **Full pipeline** (`buildUtilities\u002FtoolboxSpecification.m` and `buildUtilities\u002FtbxManifest.m` exist): readiness was run, proceed with full context\n   - **Standalone buildplan** (only `buildfile.m` exists): user has their own plan not generated by `matlab-create-buildfile`. Skip spec\u002Fmanifest checks, proceed with introspection.\n3. If full pipeline context exists, confirm no blockers from last readiness check\n\nIf `buildfile.m` does not exist, stop and direct the user to `matlab-create-buildfile` or ask them to provide one.\n\n### Step 2 — Introspect the Build Plan\n\nLoad the plan and discover its structure:\n\n```matlab\nplan = matlab.buildtool.Plan.load(\"buildfile.m\");\ndisp({plan.Tasks.Name})\n```\n\nIdentify the **target task** (in priority order):\n1. Use the `target` input if provided\n2. Look for a task named `package`\n3. Find the terminal task — one with no downstream dependents that produces the `.mltbx`\n4. If ambiguous (multiple candidates), ask the user which to run\n\nIdentify the **dependency chain** leading to the target:\n\n```matlab\n% The chain executes in topological order when you run the target\n% e.g., buildtool package → runs check, test, package\n```\n\nReport what will execute:\n```\nBuild target: \"package\"\nDependency chain: check → test → package\n```\n\n### Step 3 — Execute Build Pipeline\n\nRun via MATLAB, stopping on first failure:\n\n```matlab\nbuildtool \u003Ctarget>\n```\n\nMonitor each stage dynamically based on what's in the chain:\n\n| Task Type | Success Condition | On Failure |\n|-----------|-------------------|------------|\n| `CodeIssuesTask` or \"check\" | 0 error-severity findings | Report findings, stop |\n| `TestTask` or \"test\" | All tests pass | Report failures, stop |\n| Coverage (if present) | Reports coverage | Log warning if below threshold (does not stop) |\n| `MexTask` | MEX file produced | Report error, stop |\n| `PcodeTask` | P-code files produced | Report error, stop |\n| Packaging task | `.mltbx` file produced | Report error, stop |\n\nNot all chains have all stages. Report only what exists in this plan.\n\n### Step 4 — Verify Artifact\n\nAfter successful packaging, locate and verify the `.mltbx`. First check the task's declared `Outputs` (authoritative), then fall back to scanning `release\u002F` and the project root:\n\n```matlab\nmltbxFile = dir(fullfile(\"release\", \"*.mltbx\"));\nassert(~isempty(mltbxFile), \"No .mltbx file found in release\u002F\");\nassert(mltbxFile(1).bytes > 0, \"Package file is empty\");\nfprintf(\"Package: %s (%.1f KB)\\n\", fullfile(mltbxFile(1).folder, mltbxFile(1).name), mltbxFile(1).bytes \u002F 1024);\n```\n\nIf no `.mltbx` in `release\u002F`, check the task's declared `Outputs` or scan the project root. A zero-byte file counts as a failure.\n\n### Step 5 — Report Results\n\n```\n## Build Complete\n\n- Package: release\u002FMyToolbox.mltbx (142.3 KB)\n- Target: \"package\"\n- Chain: check → test → package\n- Static analysis: 0 errors, 2 warnings\n- Tests: 25\u002F25 passed\n- Coverage: 85%\n- Duration: 12.3s\n\n### Next Steps\n- Run `matlab-publish-toolbox` to version-tag and release\n- Test installation: matlab.addons.toolbox.installToolbox(\"release\u002FMyToolbox.mltbx\")\n```\n\nAdapt the report to what actually ran — omit sections for stages not in this plan (e.g., if no coverage task, don't report coverage).\n\nOn failure:\n\n```\n## Build Failed — [Stage]\n\n### What happened\n[error details]\n\n### Suggested fix\n[actionable suggestion]\n\n### To retry\nRun `matlab-build-toolbox` after fixing the issue.\n```\n\n## Output\n\n- `.mltbx` toolbox package\n- Build report (pass or fail with details)\n\n## Checkpoint\n\n**No** — this skill is mechanical. It executes an already-approved plan. If it fails, it reports why and stops.\n\n## Key Rules\n\n- **Introspect first.** Read the buildplan before executing. Never assume the task name or dependency chain — discover it.\n- **Stop on first failure.** Never continue past a failing stage. A package from broken code is worse than no package.\n- **Report everything.** Show counts, percentages, durations. The user should be able to verify the build quality.\n- **Verify the artifact.** Check `.mltbx` exists and has non-zero size. A zero-byte package is a silent failure.\n- **No decisions.** You execute the plan. You do not modify code, skip tests, or lower thresholds. If something fails, report it and stop.\n- **Idempotent.** Running this skill again after fixing an issue should work cleanly.\n\n## Next Steps\n\n- `\u002Fmatlab-publish-toolbox` — version-stamp and distribute the release\n\n----\n\nCopyright 2026 The MathWorks, Inc.\n\n----\n\n","# matlab-build-toolbox — Build Executor\n\nYou execute the build pipeline. You are an operator — you introspect the plan to find the right task to invoke, run it, report results at each stage, and stop on failure. This is the only skill in the pipeline with no human checkpoint.\n\n## When to Use\n\n- After `matlab-assess-toolbox` reports READY (no blockers)\n- User says \"build it\", \"run the build\", or \"build package\"\n- User has their own `buildfile.m` and wants to execute it\n- As part of the full pipeline after readiness gate passes\n\n## When NOT to Use\n\n- No `buildfile.m` exists — use `matlab-create-buildfile` first\n- User wants to create or modify build tasks — use `matlab-create-buildfile`\n- User wants to publish\u002Frelease — use `matlab-publish-toolbox` after a successful build\n- User wants a readiness check — use `matlab-assess-toolbox`\n\n## Key Functions\n\n| Function | Purpose |\n|----------|---------|\n| `matlab.buildtool.Plan.load` | Introspect the build plan to discover tasks and dependencies |\n| `buildtool` | Execute the build pipeline (runs task dependency chain) |\n| `dir` | Locate and verify the `.mltbx` artifact after packaging |\n\n## Inputs\n\n- **project_root**: Path to the project (default: current directory)\n- **target** (optional): The buildtool task to execute. If omitted, auto-detected from the plan (see Step 2).\n\n## Workflow\n\n### Step 1 — Verify Preconditions\n\nBefore executing:\n1. Confirm `buildfile.m` exists at the project root\n2. Determine pipeline context:\n   - **Full pipeline** (`buildUtilities\u002FtoolboxSpecification.m` and `buildUtilities\u002FtbxManifest.m` exist): readiness was run, proceed with full context\n   - **Standalone buildplan** (only `buildfile.m` exists): user has their own plan not generated by `matlab-create-buildfile`. Skip spec\u002Fmanifest checks, proceed with introspection.\n3. If full pipeline context exists, confirm no blockers from last readiness check\n\nIf `buildfile.m` does not exist, stop and direct the user to `matlab-create-buildfile` or ask them to provide one.\n\n### Step 2 — Introspect the Build Plan\n\nLoad the plan and discover its structure:\n\n```matlab\nplan = matlab.buildtool.Plan.load(\"buildfile.m\");\ndisp({plan.Tasks.Name})\n```\n\nIdentify the **target task** (in priority order):\n1. Use the `target` input if provided\n2. Look for a task named `package`\n3. Find the terminal task — one with no downstream dependents that produces the `.mltbx`\n4. If ambiguous (multiple candidates), ask the user which to run\n\nIdentify the **dependency chain** leading to the target:\n\n```matlab\n% The chain executes in topological order when you run the target\n% e.g., buildtool package → runs check, test, package\n```\n\nReport what will execute:\n```\nBuild target: \"package\"\nDependency chain: check → test → package\n```\n\n### Step 3 — Execute Build Pipeline\n\nRun via MATLAB, stopping on first failure:\n\n```matlab\nbuildtool \u003Ctarget>\n```\n\nMonitor each stage dynamically based on what's in the chain:\n\n| Task Type | Success Condition | On Failure |\n|-----------|-------------------|------------|\n| `CodeIssuesTask` or \"check\" | 0 error-severity findings | Report findings, stop |\n| `TestTask` or \"test\" | All tests pass | Report failures, stop |\n| Coverage (if present) | Reports coverage | Log warning if below threshold (does not stop) |\n| `MexTask` | MEX file produced | Report error, stop |\n| `PcodeTask` | P-code files produced | Report error, stop |\n| Packaging task | `.mltbx` file produced | Report error, stop |\n\nNot all chains have all stages. Report only what exists in this plan.\n\n### Step 4 — Verify Artifact\n\nAfter successful packaging, locate and verify the `.mltbx`. First check the task's declared `Outputs` (authoritative), then fall back to scanning `release\u002F` and the project root:\n\n```matlab\nmltbxFile = dir(fullfile(\"release\", \"*.mltbx\"));\nassert(~isempty(mltbxFile), \"No .mltbx file found in release\u002F\");\nassert(mltbxFile(1).bytes > 0, \"Package file is empty\");\nfprintf(\"Package: %s (%.1f KB)\\n\", fullfile(mltbxFile(1).folder, mltbxFile(1).name), mltbxFile(1).bytes \u002F 1024);\n```\n\nIf no `.mltbx` in `release\u002F`, check the task's declared `Outputs` or scan the project root. A zero-byte file counts as a failure.\n\n### Step 5 — Report Results\n\n```\n## Build Complete\n\n- Package: release\u002FMyToolbox.mltbx (142.3 KB)\n- Target: \"package\"\n- Chain: check → test → package\n- Static analysis: 0 errors, 2 warnings\n- Tests: 25\u002F25 passed\n- Coverage: 85%\n- Duration: 12.3s\n\n### Next Steps\n- Run `matlab-publish-toolbox` to version-tag and release\n- Test installation: matlab.addons.toolbox.installToolbox(\"release\u002FMyToolbox.mltbx\")\n```\n\nAdapt the report to what actually ran — omit sections for stages not in this plan (e.g., if no coverage task, don't report coverage).\n\nOn failure:\n\n```\n## Build Failed — [Stage]\n\n### What happened\n[error details]\n\n### Suggested fix\n[actionable suggestion]\n\n### To retry\nRun `matlab-build-toolbox` after fixing the issue.\n```\n\n## Output\n\n- `.mltbx` toolbox package\n- Build report (pass or fail with details)\n\n## Checkpoint\n\n**No** — this skill is mechanical. It executes an already-approved plan. If it fails, it reports why and stops.\n\n## Key Rules\n\n- **Introspect first.** Read the buildplan before executing. Never assume the task name or dependency chain — discover it.\n- **Stop on first failure.** Never continue past a failing stage. A package from broken code is worse than no package.\n- **Report everything.** Show counts, percentages, durations. The user should be able to verify the build quality.\n- **Verify the artifact.** Check `.mltbx` exists and has non-zero size. A zero-byte package is a silent failure.\n- **No decisions.** You execute the plan. You do not modify code, skip tests, or lower thresholds. If something fails, report it and stop.\n- **Idempotent.** Running this skill again after fixing an issue should work cleanly.\n\n## Next Steps\n\n- `\u002Fmatlab-publish-toolbox` — version-stamp and distribute the release\n\n----\n\nCopyright 2026 The MathWorks, Inc.\n\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-build-toolbox",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-build-toolbox",{"tool":43,"command":44},"bunx","bunx skills add stanfish06\u002Fskillquarium --skill matlab-build-toolbox",{"tool":46,"command":47},"pnpm","pnpm dlx skills add stanfish06\u002Fskillquarium --skill matlab-build-toolbox","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-build-toolbox\u002FSKILL.md",true,[51,56],{"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","参考文档",357,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-build-toolbox\u002Fmanifest.yaml",[63,71,80,87,94,101],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"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",[],[]]