[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75MHETBJPP0FV7ZPZRCTTCX":3,"skill-same:01M75MHETBJPP0FV7ZPZRCTTCX":92},{"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},"01M75MHETBJPP0FV7ZPZRCTTCX","matlab-testing",null,"Generate and run MATLAB unit tests using matlab.unittest and matlab.uitest. Parameterized tests, fixtures, mocking, coverage analysis, CI\u002FCD with buildtool, app testing with gestures. Use when creating tests, writing test classes, running test suites, checking coverage, testing apps, or validating MATLAB code.","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-testing\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-testing\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: matlab-testing\ndescription: Generate and run MATLAB unit tests using matlab.unittest and matlab.uitest. Parameterized tests, fixtures, mocking, coverage analysis, CI\u002FCD with buildtool, app testing with gestures. Use when creating tests, writing test classes, running test suites, checking coverage, testing apps, or validating MATLAB code.\nlicense: MathWorks BSD-3-Clause\nmetadata:\n  author: MathWorks\n  version: \"1.1\"\n---\n\n# Testing\n\nGenerate, structure, and run MATLAB unit tests using the `matlab.unittest` framework. Covers class-based tests, parameterized testing, fixtures, mocking, coverage analysis, CI\u002FCD integration, and app testing via MCP.\n\n## When to Use\n\n- User asks to write tests for a MATLAB function or class\n- User wants to run an existing test suite\n- User needs coverage analysis or CI\u002FCD configuration\n- Test-driven development — writing tests before implementation\n- Testing App Designer apps with programmatic gestures (see [reference\u002Fapp-testing-guidance.md](reference\u002Fapp-testing-guidance.md))\n\n## When NOT to Use\n\n- Testing Simulink models — use Simulink test skills\n- Performance benchmarking — use profiling workflows\n\n## Must-Follow Rules\n\n- **Present a test plan first** — For non-trivial test suites, propose test methods and edge cases for user approval before writing code\n- **Always use class-based tests** — Every test file must inherit from `matlab.unittest.TestCase`. Never use script-based tests\n- **No logic in test methods** — No `if`, `switch`, `for`, or `try\u002Fcatch`. Follow **Arrange-Act-Assert**. If a test needs conditionals, split into separate methods\n- **Test public interfaces, not implementation** — Never test private methods directly\n- **Execute via MCP** — Use `run_matlab_test_file` or `evaluate_matlab_code` to run tests\n\n## Workflow\n\n### Simple tests (clear behavior, limited scope)\n1. Briefly state what you'll test (methods + key edge cases)\n2. Write the test file after user confirms\n\n### Standard tests (large codebase, multiple files)\n1. **Gather requirements** — Code to test, expected behaviors, error conditions, scope, dependencies\n2. **Present test plan** — List test methods, edge cases, parameterization strategy for approval\n3. **Implement** — Write tests following the patterns below\n4. **Run** — Execute via `run_matlab_test_file` MCP tool\n5. **Check coverage** — Identify untested paths, add tests\n\n## Key Functions\n\n| Category | Functions | Purpose |\n|----------|-----------|---------|\n| Equality | `verifyEqual`, `verifyNotEqual` | Compare values (use `AbsTol` for floats) |\n| Boolean | `verifyTrue`, `verifyFalse` | Check logical conditions |\n| Size\u002Ftype | `verifySize`, `verifyClass`, `verifyEmpty` | Structural checks |\n| Errors | `verifyError` | Confirm error is thrown with correct ID |\n| Warnings | `verifyWarning`, `verifyWarningFree` | Check warning behavior |\n| Infra | `runtests`, `TestSuite`, `TestRunner` | Run and organize tests |\n| Coverage | `CodeCoveragePlugin`, `CoverageResult` | Measure test coverage |\n\n### Qualification Levels\n\n| Level | On failure | When to use |\n|-------|-----------|-------------|\n| `verify` | Continues test | Default — most assertions |\n| `assert` | Stops current test | Setup validation |\n| `fatalAssert` | Stops entire suite | Environment preconditions |\n| `assume` | Skips test | Conditional execution (e.g., toolbox check) |\n\n## Patterns\n\n### Basic Test Class\n\n```matlab\nclassdef computeAreaTest \u003C matlab.unittest.TestCase\n    %computeAreaTest Tests for the computeArea function.\n\n    methods (Test)\n        function testSquare(testCase)\n            result = computeArea(5, 5);\n            testCase.verifyEqual(result, 25);\n        end\n\n        function testFloatingPoint(testCase)\n            result = computeArea(1\u002F3, 3);\n            testCase.verifyEqual(result, 1, AbsTol=1e-12);\n        end\n\n        function testNegativeInputErrors(testCase)\n            testCase.verifyError( ...\n                @() computeArea(-1, 5), 'computeArea:negativeInput');\n        end\n    end\nend\n```\n\n### Parameterized Tests\n\nParameterize only when assertion logic is identical across all cases — only the data varies. Use struct for readable test names:\n\n```matlab\nclassdef unitConverterTest \u003C matlab.unittest.TestCase\n\n    properties (TestParameter)\n        conversionCase = struct( ...\n            'freezing', struct('input', 0, 'expected', 32), ...\n            'boiling',  struct('input', 100, 'expected', 212), ...\n            'bodyTemp', struct('input', 37, 'expected', 98.6));\n    end\n\n    methods (Test)\n        function testCelsiusToFahrenheit(testCase, conversionCase)\n            result = celsiusToFahrenheit(conversionCase.input);\n            testCase.verifyEqual(result, conversionCase.expected, AbsTol=1e-10);\n        end\n    end\nend\n```\n\nFor advanced parameterization (combinations, dynamic parameters, `ClassSetupParameter`), see [reference\u002Fparameterized-tests-guidance.md](reference\u002Fparameterized-tests-guidance.md).\n\n### Setup, Teardown, and Fixtures\n\nPrefer `addTeardown` over `TestMethodTeardown` blocks. Use `PathFixture` to add source folders:\n\n```matlab\nclassdef fileProcessorTest \u003C matlab.unittest.TestCase\n\n    methods (TestClassSetup)\n        function addSourceToPath(testCase)\n            srcFolder = fullfile(fileparts(fileparts(mfilename('fullpath'))), 'src');\n            testCase.applyFixture(matlab.unittest.fixtures.PathFixture(srcFolder, ...\n                IncludingSubfolders=true));\n        end\n    end\n\n    methods (Test)\n        function testProcessFile(testCase)\n            tmpDir = string(tempname);\n            mkdir(tmpDir);\n            testCase.addTeardown(@() rmdir(tmpDir, 's'));\n\n            testFile = fullfile(tmpDir, \"data.csv\");\n            writematrix(rand(10, 3), testFile);\n\n            result = processFile(testFile);\n            testCase.verifySize(result, [10 3]);\n        end\n    end\nend\n```\n\nFor built-in fixtures, custom fixtures, and shared fixtures, see [reference\u002Ffixtures-guidance.md](reference\u002Ffixtures-guidance.md).\n\n### Determinism\n\nSeed the RNG and restore it in teardown for reproducible tests:\n\n```matlab\nmethods (TestMethodSetup)\n    function resetRandomSeed(testCase)\n        originalRng = rng;\n        testCase.addTeardown(@() rng(originalRng));\n        rng(42, \"twister\");\n    end\nend\n```\n\n### Test Tags\n\nUse `TestTags` for selective execution:\n\n```matlab\nmethods (Test, TestTags = {'Unit'})\n    function testFastCalculation(testCase)\n        % ...\n    end\nend\n\nmethods (Test, TestTags = {'Integration', 'Slow'})\n    function testFullPipeline(testCase)\n        % ...\n    end\nend\n```\n\nRun by tag: `runtests('tests', Tag='Unit')` or `runtests('tests', ExcludeTag='Slow')`.\n\n## Running Tests\n\n### Via MCP\n\nUse the `run_matlab_test_file` MCP tool for test files. For inline runs with filtering:\n\n```matlab\nresults = runtests('tests');                            % all tests in folder\nresults = runtests('tests', Tag='Unit');                % by tag\nresults = runtests('tests', Name='*Calculator*');       % by name pattern\nresults = runtests('tests', UseParallel=true);          % parallel execution\nresults = runtests('tests', Strict=true);               % warnings = failures\n```\n\n### Analyzing Results\n\n```matlab\ndisp(results);\n\nfor r = results([results.Failed])\n    fprintf('\\nFAILED: %s\\n', r.Name);\n    disp(r.Details.DiagnosticRecord.Report);\nend\n```\n\n## Coverage Analysis\n\n```matlab\nimport matlab.unittest.TestRunner\nimport matlab.unittest.plugins.CodeCoveragePlugin\nimport matlab.unittest.plugins.codecoverage.CoverageResult\nimport matlab.unittest.plugins.codecoverage.CoverageReport\n\nrunner = TestRunner.withTextOutput;\ncovFormat = CoverageResult;\nrunner.addPlugin(CodeCoveragePlugin.forFolder('src', ...\n    Producing=[covFormat, CoverageReport('coverage-report')]));\nresults = runner.run(testsuite('tests'));\n\ncovResults = covFormat.Result;\ndisp(covResults);\n```\n\nFor coverage gap analysis, use the `printCoverageGaps` script in [reference\u002Ftest-execution-guidance.md](reference\u002Ftest-execution-guidance.md).\n\n## CI\u002FCD Integration\n\nUse `buildtool` with a `buildfile.m` for CI pipelines. See [reference\u002Ftest-execution-guidance.md](reference\u002Ftest-execution-guidance.md) for `buildfile.m` templates and CI configs (GitHub Actions, Azure DevOps, GitLab CI).\n\n## App Designer Testing\n\nFor testing apps with programmatic UI gestures (`press`, `choose`, `type`, `drag`), see [reference\u002Fapp-testing-guidance.md](reference\u002Fapp-testing-guidance.md).\n\nKey points:\n- Inherit from `matlab.uitest.TestCase` (not `matlab.unittest.TestCase`)\n- Call `drawnow` after app creation, before first gesture\n- Compare `uilabel.Text` with char (`'text'`), not string (`\"text\"`)\n- Compare `.Enable` with `matlab.lang.OnOffSwitchState.on`\u002F`.off`\n\n## References\n\nLoad these on demand — most tests only need what's in this file.\n\n| Load when... | Reference |\n|---|---|\n| Tests need setup\u002Fteardown, temp dirs, path management, shared state | [reference\u002Ffixtures-guidance.md](reference\u002Ffixtures-guidance.md) |\n| Floating-point tolerance selection, constraint objects, custom constraints | [reference\u002Fconstraints-guidance.md](reference\u002Fconstraints-guidance.md) |\n| Multiple parameters, dynamic parameters, combination strategies | [reference\u002Fparameterized-tests-guidance.md](reference\u002Fparameterized-tests-guidance.md) |\n| Code depends on external services, needs mock objects or dependency injection | [reference\u002Fmocking-guidance.md](reference\u002Fmocking-guidance.md) |\n| Running tests in CI, buildtool config, coverage gap analysis | [reference\u002Ftest-execution-guidance.md](reference\u002Ftest-execution-guidance.md) |\n| Testing App Designer apps with gestures, dialogs, async callbacks | [reference\u002Fapp-testing-guidance.md](reference\u002Fapp-testing-guidance.md) |\n\n## Conventions\n\n- Always use class-based tests inheriting from `matlab.unittest.TestCase`\n- Name test files `\u003CfunctionName>Test.m` and place in `tests\u002F` directory\n- Use `verify` qualifications by default — they let all tests run even if one fails\n- Use `AbsTol` for every floating-point comparison — never rely on exact equality\n- No logic in test methods — follow Arrange-Act-Assert\n- Use `addTeardown` for cleanup — it runs even if the test fails\n- Use struct-based `TestParameter` for readable parameterized test names\n- Keep test methods focused — test one behavior per method\n- Tests must be independent and compatible with parallel execution\n- Run tests via the `run_matlab_test_file` MCP tool for automatic result capture\n\n----\n\nCopyright 2026 The MathWorks, Inc.\n\n----\n\n","# Testing\n\nGenerate, structure, and run MATLAB unit tests using the `matlab.unittest` framework. Covers class-based tests, parameterized testing, fixtures, mocking, coverage analysis, CI\u002FCD integration, and app testing via MCP.\n\n## When to Use\n\n- User asks to write tests for a MATLAB function or class\n- User wants to run an existing test suite\n- User needs coverage analysis or CI\u002FCD configuration\n- Test-driven development — writing tests before implementation\n- Testing App Designer apps with programmatic gestures (see [reference\u002Fapp-testing-guidance.md](reference\u002Fapp-testing-guidance.md))\n\n## When NOT to Use\n\n- Testing Simulink models — use Simulink test skills\n- Performance benchmarking — use profiling workflows\n\n## Must-Follow Rules\n\n- **Present a test plan first** — For non-trivial test suites, propose test methods and edge cases for user approval before writing code\n- **Always use class-based tests** — Every test file must inherit from `matlab.unittest.TestCase`. Never use script-based tests\n- **No logic in test methods** — No `if`, `switch`, `for`, or `try\u002Fcatch`. Follow **Arrange-Act-Assert**. If a test needs conditionals, split into separate methods\n- **Test public interfaces, not implementation** — Never test private methods directly\n- **Execute via MCP** — Use `run_matlab_test_file` or `evaluate_matlab_code` to run tests\n\n## Workflow\n\n### Simple tests (clear behavior, limited scope)\n1. Briefly state what you'll test (methods + key edge cases)\n2. Write the test file after user confirms\n\n### Standard tests (large codebase, multiple files)\n1. **Gather requirements** — Code to test, expected behaviors, error conditions, scope, dependencies\n2. **Present test plan** — List test methods, edge cases, parameterization strategy for approval\n3. **Implement** — Write tests following the patterns below\n4. **Run** — Execute via `run_matlab_test_file` MCP tool\n5. **Check coverage** — Identify untested paths, add tests\n\n## Key Functions\n\n| Category | Functions | Purpose |\n|----------|-----------|---------|\n| Equality | `verifyEqual`, `verifyNotEqual` | Compare values (use `AbsTol` for floats) |\n| Boolean | `verifyTrue`, `verifyFalse` | Check logical conditions |\n| Size\u002Ftype | `verifySize`, `verifyClass`, `verifyEmpty` | Structural checks |\n| Errors | `verifyError` | Confirm error is thrown with correct ID |\n| Warnings | `verifyWarning`, `verifyWarningFree` | Check warning behavior |\n| Infra | `runtests`, `TestSuite`, `TestRunner` | Run and organize tests |\n| Coverage | `CodeCoveragePlugin`, `CoverageResult` | Measure test coverage |\n\n### Qualification Levels\n\n| Level | On failure | When to use |\n|-------|-----------|-------------|\n| `verify` | Continues test | Default — most assertions |\n| `assert` | Stops current test | Setup validation |\n| `fatalAssert` | Stops entire suite | Environment preconditions |\n| `assume` | Skips test | Conditional execution (e.g., toolbox check) |\n\n## Patterns\n\n### Basic Test Class\n\n```matlab\nclassdef computeAreaTest \u003C matlab.unittest.TestCase\n    %computeAreaTest Tests for the computeArea function.\n\n    methods (Test)\n        function testSquare(testCase)\n            result = computeArea(5, 5);\n            testCase.verifyEqual(result, 25);\n        end\n\n        function testFloatingPoint(testCase)\n            result = computeArea(1\u002F3, 3);\n            testCase.verifyEqual(result, 1, AbsTol=1e-12);\n        end\n\n        function testNegativeInputErrors(testCase)\n            testCase.verifyError( ...\n                @() computeArea(-1, 5), 'computeArea:negativeInput');\n        end\n    end\nend\n```\n\n### Parameterized Tests\n\nParameterize only when assertion logic is identical across all cases — only the data varies. Use struct for readable test names:\n\n```matlab\nclassdef unitConverterTest \u003C matlab.unittest.TestCase\n\n    properties (TestParameter)\n        conversionCase = struct( ...\n            'freezing', struct('input', 0, 'expected', 32), ...\n            'boiling',  struct('input', 100, 'expected', 212), ...\n            'bodyTemp', struct('input', 37, 'expected', 98.6));\n    end\n\n    methods (Test)\n        function testCelsiusToFahrenheit(testCase, conversionCase)\n            result = celsiusToFahrenheit(conversionCase.input);\n            testCase.verifyEqual(result, conversionCase.expected, AbsTol=1e-10);\n        end\n    end\nend\n```\n\nFor advanced parameterization (combinations, dynamic parameters, `ClassSetupParameter`), see [reference\u002Fparameterized-tests-guidance.md](reference\u002Fparameterized-tests-guidance.md).\n\n### Setup, Teardown, and Fixtures\n\nPrefer `addTeardown` over `TestMethodTeardown` blocks. Use `PathFixture` to add source folders:\n\n```matlab\nclassdef fileProcessorTest \u003C matlab.unittest.TestCase\n\n    methods (TestClassSetup)\n        function addSourceToPath(testCase)\n            srcFolder = fullfile(fileparts(fileparts(mfilename('fullpath'))), 'src');\n            testCase.applyFixture(matlab.unittest.fixtures.PathFixture(srcFolder, ...\n                IncludingSubfolders=true));\n        end\n    end\n\n    methods (Test)\n        function testProcessFile(testCase)\n            tmpDir = string(tempname);\n            mkdir(tmpDir);\n            testCase.addTeardown(@() rmdir(tmpDir, 's'));\n\n            testFile = fullfile(tmpDir, \"data.csv\");\n            writematrix(rand(10, 3), testFile);\n\n            result = processFile(testFile);\n            testCase.verifySize(result, [10 3]);\n        end\n    end\nend\n```\n\nFor built-in fixtures, custom fixtures, and shared fixtures, see [reference\u002Ffixtures-guidance.md](reference\u002Ffixtures-guidance.md).\n\n### Determinism\n\nSeed the RNG and restore it in teardown for reproducible tests:\n\n```matlab\nmethods (TestMethodSetup)\n    function resetRandomSeed(testCase)\n        originalRng = rng;\n        testCase.addTeardown(@() rng(originalRng));\n        rng(42, \"twister\");\n    end\nend\n```\n\n### Test Tags\n\nUse `TestTags` for selective execution:\n\n```matlab\nmethods (Test, TestTags = {'Unit'})\n    function testFastCalculation(testCase)\n        % ...\n    end\nend\n\nmethods (Test, TestTags = {'Integration', 'Slow'})\n    function testFullPipeline(testCase)\n        % ...\n    end\nend\n```\n\nRun by tag: `runtests('tests', Tag='Unit')` or `runtests('tests', ExcludeTag='Slow')`.\n\n## Running Tests\n\n### Via MCP\n\nUse the `run_matlab_test_file` MCP tool for test files. For inline runs with filtering:\n\n```matlab\nresults = runtests('tests');                            % all tests in folder\nresults = runtests('tests', Tag='Unit');                % by tag\nresults = runtests('tests', Name='*Calculator*');       % by name pattern\nresults = runtests('tests', UseParallel=true);          % parallel execution\nresults = runtests('tests', Strict=true);               % warnings = failures\n```\n\n### Analyzing Results\n\n```matlab\ndisp(results);\n\nfor r = results([results.Failed])\n    fprintf('\\nFAILED: %s\\n', r.Name);\n    disp(r.Details.DiagnosticRecord.Report);\nend\n```\n\n## Coverage Analysis\n\n```matlab\nimport matlab.unittest.TestRunner\nimport matlab.unittest.plugins.CodeCoveragePlugin\nimport matlab.unittest.plugins.codecoverage.CoverageResult\nimport matlab.unittest.plugins.codecoverage.CoverageReport\n\nrunner = TestRunner.withTextOutput;\ncovFormat = CoverageResult;\nrunner.addPlugin(CodeCoveragePlugin.forFolder('src', ...\n    Producing=[covFormat, CoverageReport('coverage-report')]));\nresults = runner.run(testsuite('tests'));\n\ncovResults = covFormat.Result;\ndisp(covResults);\n```\n\nFor coverage gap analysis, use the `printCoverageGaps` script in [reference\u002Ftest-execution-guidance.md](reference\u002Ftest-execution-guidance.md).\n\n## CI\u002FCD Integration\n\nUse `buildtool` with a `buildfile.m` for CI pipelines. See [reference\u002Ftest-execution-guidance.md](reference\u002Ftest-execution-guidance.md) for `buildfile.m` templates and CI configs (GitHub Actions, Azure DevOps, GitLab CI).\n\n## App Designer Testing\n\nFor testing apps with programmatic UI gestures (`press`, `choose`, `type`, `drag`), see [reference\u002Fapp-testing-guidance.md](reference\u002Fapp-testing-guidance.md).\n\nKey points:\n- Inherit from `matlab.uitest.TestCase` (not `matlab.unittest.TestCase`)\n- Call `drawnow` after app creation, before first gesture\n- Compare `uilabel.Text` with char (`'text'`), not string (`\"text\"`)\n- Compare `.Enable` with `matlab.lang.OnOffSwitchState.on`\u002F`.off`\n\n## References\n\nLoad these on demand — most tests only need what's in this file.\n\n| Load when... | Reference |\n|---|---|\n| Tests need setup\u002Fteardown, temp dirs, path management, shared state | [reference\u002Ffixtures-guidance.md](reference\u002Ffixtures-guidance.md) |\n| Floating-point tolerance selection, constraint objects, custom constraints | [reference\u002Fconstraints-guidance.md](reference\u002Fconstraints-guidance.md) |\n| Multiple parameters, dynamic parameters, combination strategies | [reference\u002Fparameterized-tests-guidance.md](reference\u002Fparameterized-tests-guidance.md) |\n| Code depends on external services, needs mock objects or dependency injection | [reference\u002Fmocking-guidance.md](reference\u002Fmocking-guidance.md) |\n| Running tests in CI, buildtool config, coverage gap analysis | [reference\u002Ftest-execution-guidance.md](reference\u002Ftest-execution-guidance.md) |\n| Testing App Designer apps with gestures, dialogs, async callbacks | [reference\u002Fapp-testing-guidance.md](reference\u002Fapp-testing-guidance.md) |\n\n## Conventions\n\n- Always use class-based tests inheriting from `matlab.unittest.TestCase`\n- Name test files `\u003CfunctionName>Test.m` and place in `tests\u002F` directory\n- Use `verify` qualifications by default — they let all tests run even if one fails\n- Use `AbsTol` for every floating-point comparison — never rely on exact equality\n- No logic in test methods — follow Arrange-Act-Assert\n- Use `addTeardown` for cleanup — it runs even if the test fails\n- Use struct-based `TestParameter` for readable parameterized test names\n- Keep test methods focused — test one behavior per method\n- Tests must be independent and compatible with parallel execution\n- Run tests via the `run_matlab_test_file` MCP tool for automatic result capture\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.1","master","49e49abf2f670d429e0b7e2c0349739c3fdd5cbe","skills\u002Fmatlab-testing",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-testing",{"tool":43,"command":44},"bunx","bunx skills add stanfish06\u002Fskillquarium --skill matlab-testing",{"tool":46,"command":47},"pnpm","pnpm dlx skills add stanfish06\u002Fskillquarium --skill matlab-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-testing\u002FSKILL.md",true,[51,56,62,66,70,74,78,82,86],{"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","参考文档",452,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-testing\u002Fmanifest.yaml",{"path":63,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":64,"sourceHtmlUrl":65},"reference\u002Fapp-testing-guidance.md",9705,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-testing\u002Freference\u002Fapp-testing-guidance.md",{"path":67,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":68,"sourceHtmlUrl":69},"reference\u002Fconstraints-guidance.md",2166,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-testing\u002Freference\u002Fconstraints-guidance.md",{"path":71,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":72,"sourceHtmlUrl":73},"reference\u002Ffixtures-guidance.md",2546,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-testing\u002Freference\u002Ffixtures-guidance.md",{"path":75,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":76,"sourceHtmlUrl":77},"reference\u002Fmocking-guidance.md",3233,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-testing\u002Freference\u002Fmocking-guidance.md",{"path":79,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":80,"sourceHtmlUrl":81},"reference\u002Fparameterized-tests-guidance.md",3647,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-testing\u002Freference\u002Fparameterized-tests-guidance.md",{"path":83,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":84,"sourceHtmlUrl":85},"reference\u002Ftest-execution-guidance.md",4110,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-testing\u002Freference\u002Ftest-execution-guidance.md",{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002FprintCoverageGaps.m","SCRIPT","脚本",2628,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-testing\u002Fscripts\u002FprintCoverageGaps.m",[93,101,110,117,124,131],{"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":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":105,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"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":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"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":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"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":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":105,"licenseFileUrl":135,"sourceHtmlUrl":136,"categories":137,"keywords":138,"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",[],[]]