[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72VT9PART27QBM306JC3PGN":3,"skill-same:01M72VT9PART27QBM306JC3PGN":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":6,"updatedAt":41,"install":42,"resources":55},"01M72VT9PART27QBM306JC3PGN","meteor-testing",null,"Use when setting up, designing, writing, or repairing tests and test harnesses in a Meteor 3 app. Triggers on meteortesting:mocha, --driver-package, TEST_WATCH, TEST_BROWSER_DRIVER, MOCHA_GREP, meteor.testModule, focused tests, .only, Meteor.server.method_handlers, Meteor.server.publish_handlers, DDP.connect, --full-app integration mode, sinon, async test signatures, Playwright\u002FCypress E2E. Use this skill when the user asks about test runners, asks about testing publications, or asks about Jest vs Mocha in Meteor. For a failing, hanging, or flaky test whose failing layer or root cause is unknown, use meteor-debugging before changing the test or app.","meteor\u002Fagent-skills","meteor","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F789528?v=4","01M72VQVFCJ72XHP7ZKS3774NA","Meteor","01M72VQVG5VZ0X5VCQYM0MCK1Q",11,"MIT","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-testing\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: meteor-testing\ndescription: >\n  Use when setting up, designing, writing, or repairing tests and test\n  harnesses in a Meteor 3 app. Triggers on\n  meteortesting:mocha, --driver-package, TEST_WATCH, TEST_BROWSER_DRIVER,\n  MOCHA_GREP, meteor.testModule, focused tests, .only,\n  Meteor.server.method_handlers, Meteor.server.publish_handlers,\n  DDP.connect, --full-app integration mode, sinon, async test signatures,\n  Playwright\u002FCypress E2E. Use this skill when the user asks about test\n  runners, asks about testing publications, or asks about Jest vs Mocha\n  in Meteor. For a failing, hanging, or flaky test whose failing layer or root\n  cause is unknown, use meteor-debugging before changing the test or app.\nmetadata:\n  author: meteor\n  kind: knowledge\n  meteor: \">=3.0\"\n  area: testing\n  tagline: \"Set up and write Meteor 3 tests (`meteortesting:mocha`, async signatures, methods\u002Fpublications, Playwright\u002FCypress E2E).\"\n  bundle: [\"fullstack\"]\n  docs_synced_at: \"2026-11-13\"\nlicense: MIT\n---\n\n# Testing Meteor 3 apps\n\n`meteortesting:mocha` is the canonical Meteor test driver. It boots the\napp in test mode (no app code runs except the test files) and reports\nresults in the server console.\n\nIf an existing test fails, hangs, or flakes and the failing layer is unknown,\nuse `meteor-debugging` to isolate the cause. Return here when evidence points to\ntest setup, design, driver behavior, fixtures, or regression coverage.\n\n## Decision flow\n\n1. Unknown failure in an existing test? Use `meteor-debugging` to classify\n   application, data, harness, browser, environment, or shared-state causes.\n2. Pure logic, no Meteor APIs? Plain Mocha or any test runner; nothing\n   Meteor-specific.\n3. Method or publication? Integration test it with `meteortesting:mocha`\n   using `Meteor.server.method_handlers[name].apply(ctx, args)` or\n   `publish_handlers`.\n4. Need to drive a real DDP client (cross-process or end-to-end DDP\n   semantics)? Use `--full-app` mode and `DDP.connect`.\n5. UI flow \u002F browser interaction? Start the normal app with deterministic\n   test settings and run Playwright or Cypress against it. Use\n   `meteor test --full-app` only when the browser flow must load app-test\n   modules.\n\n## Setup\n\n```bash\nmeteor add meteortesting:mocha\nmeteor npm install --save-dev @types\u002Fmocha\n```\n\n```json\n\u002F\u002F package.json\n{\n  \"scripts\": {\n    \"test\": \"TEST_WATCH=1 meteor test --driver-package meteortesting:mocha\",\n    \"test:ci\": \"meteor test --once --driver-package meteortesting:mocha\",\n    \"test:full\": \"meteor test --full-app --driver-package meteortesting:mocha\"\n  }\n}\n```\n\nTest-mode conventions:\n\n- Normal test mode eagerly loads `*.test[s].*` and `*.spec[s].*` files, while\n  ordinary application code loads only when imported by a test.\n- Filename discovery ignores `tests\u002F` directories. A configured\n  `meteor.testModule` instead loads its explicit entry module and imports.\n- `--full-app` eagerly loads the normal app plus `*.app-test[s].*` and\n  `*.app-spec[s].*` files, and sets `Meteor.isAppTest`.\n\nFor Meteor 3.5.2 Rspack full-app\u002FTLA behavior, parent-`private` discovery\nfailures, and the jQuery harness regression fixed in Meteor 3.6, read\n[release-specific test setup](references\u002Fmeteor-3.5.2-testing.md). Check\nresolved packages and suite counts before applying a version-specific fix.\n\nTo focus an existing test, prefer a supported driver filter such as\n`MOCHA_GREP` after checking the installed driver in `.meteor\u002Fversions`; use\n`.only` only temporarily. These select registered tests but do not prevent\nother test modules from evaluating. If loading itself causes interference,\ninspect `meteor.testModule` and read `references\u002Ffocused-runs.md` before\nnarrowing entrypoint imports. Restore every temporary focus or import change,\nthen run the normal affected suite. Read the configured entrypoint paths from\nthe project; do not invent paths, scripts, ports, or helpers.\n\nFor Meteor 3.6 Rspack ignore exceptions or separate legacy test entries, use\nthe [architecture and ignore boundaries](references\u002Ffocused-runs.md#rspack-architecture-and-ignore-boundaries).\nCheck expected suites on each selected program; a modern zero-exit run is\nnot proof of legacy coverage.\n\n## Method test (server-side)\n\nShared test entries also reach the browser. Use `assert` with strict methods;\nserver guards cannot hide static imports. See\n[assertion imports](references\u002Fmocha-setup.md#assertion-imports).\n\n```javascript\nimport assert from \"assert\";\nimport { Meteor } from \"meteor\u002Fmeteor\";\nimport { Items } from \"\u002Fimports\u002Fapi\u002Fitems\";\n\nif (Meteor.isServer) {\n  describe(\"items.add\", function () {\n    beforeEach(async function () {\n      await Items.removeAsync({});\n    });\n\n    it(\"inserts when authed\", async function () {\n      const _id = await Meteor.server.method_handlers[\"items.add\"].apply(\n        { userId: \"u1\" },\n        [{ title: \"x\", qty: 1 }],\n      );\n      const doc = await Items.findOneAsync(_id);\n      assert.strictEqual(doc.title, \"x\");\n    });\n\n    it(\"rejects when unauthed\", async function () {\n      await assert.rejects(() =>\n        Meteor.server.method_handlers[\"items.add\"].apply({ userId: null }, [{}]),\n      );\n    });\n  });\n}\n```\n\n`.apply(context, argsArray)` is the documented form;\n`Meteor.server.method_handlers[name]` is the registered method\nimplementation. Pass a stub `this` with `userId` (and `unblock`,\n`connection`, etc. when needed).\n\n## Publication test (server-side)\n\n```javascript\nif (Meteor.isServer) {\n  describe(\"items.mine publication\", function () {\n    it(\"only ships the subscribing user's items\", async function () {\n      await Items.removeAsync({});\n      await Items.insertAsync({ _id: \"a\", ownerId: \"u1\" });\n      await Items.insertAsync({ _id: \"b\", ownerId: \"u2\" });\n\n      const cursor = await Meteor.server.publish_handlers[\"items.mine\"]\n        .apply({ userId: \"u1\" }, []);\n      const docs = await cursor.fetchAsync();\n      assert.deepStrictEqual(docs.map((d) => d._id), [\"a\"]);\n    });\n  });\n}\n```\n\nFor publications using the low-level `this.added` \u002F `this.changed` API,\ntest with a real DDP client via `--full-app` mode (next section).\n\nAlways await the direct publish handler. Conventional handlers return the\ncursor immediately; async handlers return a Promise of the cursor.\n\n## End-to-end DDP test (`--full-app` mode)\n\n```javascript\nimport { DDP } from \"meteor\u002Fddp-client\";\nimport { Mongo } from \"meteor\u002Fmongo\";\nimport { Tracker } from \"meteor\u002Ftracker\";\n\nconst conn = DDP.connect(Meteor.absoluteUrl());\nconst RemoteItems = new Mongo.Collection(\"items\", { connection: conn });\n\nfunction ready(sub) {\n  return new Promise((resolve) => {\n    const computation = Tracker.autorun((c) => {\n      if (sub.ready()) {\n        c.stop();\n        resolve();\n      }\n    });\n  });\n}\n\nconst sub = conn.subscribe(\"items.mine\");\nawait ready(sub);\nconst docs = RemoteItems.find().fetch();\n```\n\nRun with `meteor test --full-app --driver-package meteortesting:mocha`.\n\n## Client unit test (Minimongo)\n\n```javascript\nif (Meteor.isClient) {\n  describe(\"Items minimongo\", function () {\n    beforeEach(function () { Items.remove({}); });\n\n    it(\"filters by ownerId\", function () {\n      Items.insert({ _id: \"a\", ownerId: \"u1\" });\n      Items.insert({ _id: \"b\", ownerId: \"u2\" });\n      assert.strictEqual(Items.find({ ownerId: \"u1\" }).count(), 1);\n    });\n  });\n}\n```\n\nClient tests run in the browser the driver spawns. With\n`TEST_BROWSER_DRIVER=puppeteer`, the browser is headless Chromium and\nresults flow back to the server console.\n\nDo not treat a server-only green run as complete client coverage. The driver\nprints a message when no browser is connected; configure\n`TEST_BROWSER_DRIVER` in CI and confirm client test counts are present.\n\n## Browser E2E\n\nRun Playwright or Cypress against the normal application unless the test\nneeds Meteor's app-test modules. The server command must work from a clean\nclone with a tracked, nonsecret settings fixture or fully documented test\nenvironment variables. Do not point it at an ignored developer settings file.\n\nCover at least one complete mutation flow and one rejected server action.\nBasic page-title checks do not exercise async method stubs, authorization, or\npublication readiness.\n\n## Anti-patterns\n\n- Reach for Jest. Jest does not understand Meteor's build system. Use\n  `meteortesting:mocha`.\n- Mock Mongo. Run the real driver against a clean DB.\n- Forget `if (Meteor.isServer) { ... }` guards. Server tests crash if\n  they run in the browser harness.\n- Skip `beforeEach` cleanup. Tests leak state across runs.\n- Catch and log a `beforeEach` failure without rethrowing. The test then runs\n  against unknown state and can report a misleading assertion.\n- Assert only the database postcondition for a rejected method. Also require\n  the Promise to reject with the expected `Meteor.Error`.\n- Replace `Meteor.userId` or another global without restoring it in\n  `afterEach`.\n- Use `Meteor.call` with callbacks in async test code. Use\n  `Meteor.callAsync` or unwrap `method_handlers` directly.\n\n## See also\n\n- `references\u002Fmocha-setup.md`\n- `references\u002Ffocused-runs.md`\n- `references\u002Fddp-test-helpers.md`\n- `references\u002Feval-cases.md`\n","# Testing Meteor 3 apps\n\n`meteortesting:mocha` is the canonical Meteor test driver. It boots the\napp in test mode (no app code runs except the test files) and reports\nresults in the server console.\n\nIf an existing test fails, hangs, or flakes and the failing layer is unknown,\nuse `meteor-debugging` to isolate the cause. Return here when evidence points to\ntest setup, design, driver behavior, fixtures, or regression coverage.\n\n## Decision flow\n\n1. Unknown failure in an existing test? Use `meteor-debugging` to classify\n   application, data, harness, browser, environment, or shared-state causes.\n2. Pure logic, no Meteor APIs? Plain Mocha or any test runner; nothing\n   Meteor-specific.\n3. Method or publication? Integration test it with `meteortesting:mocha`\n   using `Meteor.server.method_handlers[name].apply(ctx, args)` or\n   `publish_handlers`.\n4. Need to drive a real DDP client (cross-process or end-to-end DDP\n   semantics)? Use `--full-app` mode and `DDP.connect`.\n5. UI flow \u002F browser interaction? Start the normal app with deterministic\n   test settings and run Playwright or Cypress against it. Use\n   `meteor test --full-app` only when the browser flow must load app-test\n   modules.\n\n## Setup\n\n```bash\nmeteor add meteortesting:mocha\nmeteor npm install --save-dev @types\u002Fmocha\n```\n\n```json\n\u002F\u002F package.json\n{\n  \"scripts\": {\n    \"test\": \"TEST_WATCH=1 meteor test --driver-package meteortesting:mocha\",\n    \"test:ci\": \"meteor test --once --driver-package meteortesting:mocha\",\n    \"test:full\": \"meteor test --full-app --driver-package meteortesting:mocha\"\n  }\n}\n```\n\nTest-mode conventions:\n\n- Normal test mode eagerly loads `*.test[s].*` and `*.spec[s].*` files, while\n  ordinary application code loads only when imported by a test.\n- Filename discovery ignores `tests\u002F` directories. A configured\n  `meteor.testModule` instead loads its explicit entry module and imports.\n- `--full-app` eagerly loads the normal app plus `*.app-test[s].*` and\n  `*.app-spec[s].*` files, and sets `Meteor.isAppTest`.\n\nFor Meteor 3.5.2 Rspack full-app\u002FTLA behavior, parent-`private` discovery\nfailures, and the jQuery harness regression fixed in Meteor 3.6, read\n[release-specific test setup](references\u002Fmeteor-3.5.2-testing.md). Check\nresolved packages and suite counts before applying a version-specific fix.\n\nTo focus an existing test, prefer a supported driver filter such as\n`MOCHA_GREP` after checking the installed driver in `.meteor\u002Fversions`; use\n`.only` only temporarily. These select registered tests but do not prevent\nother test modules from evaluating. If loading itself causes interference,\ninspect `meteor.testModule` and read `references\u002Ffocused-runs.md` before\nnarrowing entrypoint imports. Restore every temporary focus or import change,\nthen run the normal affected suite. Read the configured entrypoint paths from\nthe project; do not invent paths, scripts, ports, or helpers.\n\nFor Meteor 3.6 Rspack ignore exceptions or separate legacy test entries, use\nthe [architecture and ignore boundaries](references\u002Ffocused-runs.md#rspack-architecture-and-ignore-boundaries).\nCheck expected suites on each selected program; a modern zero-exit run is\nnot proof of legacy coverage.\n\n## Method test (server-side)\n\nShared test entries also reach the browser. Use `assert` with strict methods;\nserver guards cannot hide static imports. See\n[assertion imports](references\u002Fmocha-setup.md#assertion-imports).\n\n```javascript\nimport assert from \"assert\";\nimport { Meteor } from \"meteor\u002Fmeteor\";\nimport { Items } from \"\u002Fimports\u002Fapi\u002Fitems\";\n\nif (Meteor.isServer) {\n  describe(\"items.add\", function () {\n    beforeEach(async function () {\n      await Items.removeAsync({});\n    });\n\n    it(\"inserts when authed\", async function () {\n      const _id = await Meteor.server.method_handlers[\"items.add\"].apply(\n        { userId: \"u1\" },\n        [{ title: \"x\", qty: 1 }],\n      );\n      const doc = await Items.findOneAsync(_id);\n      assert.strictEqual(doc.title, \"x\");\n    });\n\n    it(\"rejects when unauthed\", async function () {\n      await assert.rejects(() =>\n        Meteor.server.method_handlers[\"items.add\"].apply({ userId: null }, [{}]),\n      );\n    });\n  });\n}\n```\n\n`.apply(context, argsArray)` is the documented form;\n`Meteor.server.method_handlers[name]` is the registered method\nimplementation. Pass a stub `this` with `userId` (and `unblock`,\n`connection`, etc. when needed).\n\n## Publication test (server-side)\n\n```javascript\nif (Meteor.isServer) {\n  describe(\"items.mine publication\", function () {\n    it(\"only ships the subscribing user's items\", async function () {\n      await Items.removeAsync({});\n      await Items.insertAsync({ _id: \"a\", ownerId: \"u1\" });\n      await Items.insertAsync({ _id: \"b\", ownerId: \"u2\" });\n\n      const cursor = await Meteor.server.publish_handlers[\"items.mine\"]\n        .apply({ userId: \"u1\" }, []);\n      const docs = await cursor.fetchAsync();\n      assert.deepStrictEqual(docs.map((d) => d._id), [\"a\"]);\n    });\n  });\n}\n```\n\nFor publications using the low-level `this.added` \u002F `this.changed` API,\ntest with a real DDP client via `--full-app` mode (next section).\n\nAlways await the direct publish handler. Conventional handlers return the\ncursor immediately; async handlers return a Promise of the cursor.\n\n## End-to-end DDP test (`--full-app` mode)\n\n```javascript\nimport { DDP } from \"meteor\u002Fddp-client\";\nimport { Mongo } from \"meteor\u002Fmongo\";\nimport { Tracker } from \"meteor\u002Ftracker\";\n\nconst conn = DDP.connect(Meteor.absoluteUrl());\nconst RemoteItems = new Mongo.Collection(\"items\", { connection: conn });\n\nfunction ready(sub) {\n  return new Promise((resolve) => {\n    const computation = Tracker.autorun((c) => {\n      if (sub.ready()) {\n        c.stop();\n        resolve();\n      }\n    });\n  });\n}\n\nconst sub = conn.subscribe(\"items.mine\");\nawait ready(sub);\nconst docs = RemoteItems.find().fetch();\n```\n\nRun with `meteor test --full-app --driver-package meteortesting:mocha`.\n\n## Client unit test (Minimongo)\n\n```javascript\nif (Meteor.isClient) {\n  describe(\"Items minimongo\", function () {\n    beforeEach(function () { Items.remove({}); });\n\n    it(\"filters by ownerId\", function () {\n      Items.insert({ _id: \"a\", ownerId: \"u1\" });\n      Items.insert({ _id: \"b\", ownerId: \"u2\" });\n      assert.strictEqual(Items.find({ ownerId: \"u1\" }).count(), 1);\n    });\n  });\n}\n```\n\nClient tests run in the browser the driver spawns. With\n`TEST_BROWSER_DRIVER=puppeteer`, the browser is headless Chromium and\nresults flow back to the server console.\n\nDo not treat a server-only green run as complete client coverage. The driver\nprints a message when no browser is connected; configure\n`TEST_BROWSER_DRIVER` in CI and confirm client test counts are present.\n\n## Browser E2E\n\nRun Playwright or Cypress against the normal application unless the test\nneeds Meteor's app-test modules. The server command must work from a clean\nclone with a tracked, nonsecret settings fixture or fully documented test\nenvironment variables. Do not point it at an ignored developer settings file.\n\nCover at least one complete mutation flow and one rejected server action.\nBasic page-title checks do not exercise async method stubs, authorization, or\npublication readiness.\n\n## Anti-patterns\n\n- Reach for Jest. Jest does not understand Meteor's build system. Use\n  `meteortesting:mocha`.\n- Mock Mongo. Run the real driver against a clean DB.\n- Forget `if (Meteor.isServer) { ... }` guards. Server tests crash if\n  they run in the browser harness.\n- Skip `beforeEach` cleanup. Tests leak state across runs.\n- Catch and log a `beforeEach` failure without rethrowing. The test then runs\n  against unknown state and can report a misleading assertion.\n- Assert only the database postcondition for a rejected method. Also require\n  the Promise to reject with the expected `Meteor.Error`.\n- Replace `Meteor.userId` or another global without restoring it in\n  `afterEach`.\n- Use `Meteor.call` with callbacks in async test code. Use\n  `Meteor.callAsync` or unwrap `method_handlers` directly.\n\n## See also\n\n- `references\u002Fmocha-setup.md`\n- `references\u002Ffocused-runs.md`\n- `references\u002Fddp-test-helpers.md`\n- `references\u002Feval-cases.md`\n",{"name":5,"license":15,"metadata":24,"description":32},{"area":25,"kind":26,"author":9,"bundle":27,"meteor":29,"tagline":30,"docs_synced_at":31},"testing","knowledge",[28],"fullstack",">=3.0","Set up and write Meteor 3 tests (`meteortesting:mocha`, async signatures, methods\u002Fpublications, Playwright\u002FCypress E2E).","2026-11-13","Use when setting up, designing, writing, or repairing tests and test harnesses in a Meteor 3 app. Triggers on meteortesting:mocha, --driver-package, TEST_WATCH, TEST_BROWSER_DRIVER, MOCHA_GREP, meteor.testModule, focused tests, .only, Meteor.server.method_handlers, Meteor.server.publish_handlers, DDP.connect, --full-app integration mode, sinon, async test signatures, Playwright\u002FCypress E2E. Use this skill when the user asks about test runners, asks about testing publications, or asks about Jest vs Mocha in Meteor. For a failing, hanging, or flaky test whose failing layer or root cause is unknown, use meteor-debugging before changing the test or app.\n","main","0162f7828beea805972d4db9a5e3e08aea3e0d17","skills\u002Fmeteor-testing",3,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills","https:\u002F\u002Fdocs.meteor.com\u002F","https:\u002F\u002Fgithub.com\u002Fmeteor","https:\u002F\u002Fmeteor.com\u002F","2026-11-13 22:00:21",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add meteor\u002Fagent-skills --skill meteor-testing",{"tool":48,"command":49},"bunx","bunx skills add meteor\u002Fagent-skills --skill meteor-testing",{"tool":51,"command":52},"pnpm","pnpm dlx skills add meteor\u002Fagent-skills --skill meteor-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-testing\u002FSKILL.md",true,[56,62,66,70,74],{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fddp-test-helpers.md","REFERENCE","参考文档",2720,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-testing\u002Freferences\u002Fddp-test-helpers.md",{"path":63,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Feval-cases.md",11774,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-testing\u002Freferences\u002Feval-cases.md",{"path":67,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Ffocused-runs.md",4349,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-testing\u002Freferences\u002Ffocused-runs.md",{"path":71,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fmeteor-3.5.2-testing.md",3648,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-testing\u002Freferences\u002Fmeteor-3.5.2-testing.md",{"path":75,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fmocha-setup.md",5158,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-testing\u002Freferences\u002Fmocha-setup.md",[79,86,93,100,107,114],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M72VVSHP4F20VMPYR6BG38EW","good-skill","Use when authoring a fixture skill for the validator. Triggers on validator unit tests. Use this skill when asserting the happy path through frontmatter validation.","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fvalid\u002Fgood-skill\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":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M72VVQ4ZS36ASMYGDP7TARR2","meteor-foo","Use when testing the zip builder. Triggers on build-zips unit tests. Ask about archive layout.","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fskills-for-zip\u002Fmeteor-foo\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":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M72VVMYGBZHDJZRGD1H99RDB","_internal","Use when testing internal artifact exclusions. Triggers on ZIP builder tests.","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fskills-for-zip\u002F_internal\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":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M72VVKD7N2TBZWYMD8MV47YN","internal-review","Use when testing that maintainer skills stay outside published ZIP artifacts.","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fskills-for-zip\u002F.github\u002Fskills\u002Finternal-review\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":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M72VVGX8NSSZ2CZK5PW1K56V","oversize-body","Use when the body exceeds 8 KB. Triggers on validator size-limit testing.","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Finvalid\u002Foversize-body\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M72VVF6G3G6GB86GSMASE4T4","one-trigger","Use when a description has only one trigger phrase and nothing else useful enough to push past the heuristic.","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Finvalid\u002Fone-trigger\u002FSKILL.md",[],[]]