[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72VRMSH5V16N8BMQWD3QW8K":3,"skill-same:01M72VRMSH5V16N8BMQWD3QW8K":82},{"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":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":42,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M72VRMSH5V16N8BMQWD3QW8K","meteor-cli-installation",null,"Use when installing, locating, repairing, resetting, or uninstalling the Meteor CLI for Meteor 3 development. Triggers on \"meteor: command not found\", npx meteor, installer failures, PATH problems, specific Meteor versions, clean reinstall requests, meteor reset, or corrupted dev bundles. Use this skill when the user asks about fresh workstation setup or making a local Meteor command available. For application failures after the CLI starts, use meteor-debugging; for application code upgrades, use migrate-to-meteor-3.","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-cli-installation\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: meteor-cli-installation\ndescription: >\n  Use when installing, locating, repairing, resetting, or uninstalling the\n  Meteor CLI for Meteor 3 development. Triggers on \"meteor: command not\n  found\", npx meteor, installer failures, PATH problems, specific Meteor\n  versions, clean reinstall requests, meteor reset, or corrupted dev bundles.\n  Use this skill when the user asks about fresh workstation setup or making a\n  local Meteor command available. For application failures after the CLI\n  starts, use meteor-debugging; for application code upgrades, use\n  migrate-to-meteor-3.\nmetadata:\n  author: meteor\n  kind: workflow\n  meteor: \">=3.0\"\n  area: ops\n  tagline: \"Install, locate, repair, reset, or cleanly reinstall the Meteor 3 CLI with correct version and PATH handling.\"\n  bundle: [\"essentials\", \"migration\", \"fullstack\", \"ops\", \"blaze\", \"react\"]\n  docs_synced_at: \"2026-11-13\"\nlicense: MIT\n---\n\n# Install and repair the Meteor CLI\n\nMake the Meteor CLI available without changing an application or deleting\nstate that the user did not place in scope. `npx meteor` runs the official npm\ninstaller and creates a user-wide Meteor installation; it does not add the\ninstaller permanently to global npm packages.\n\n## Decision flow\n\n1. Classify the request before changing the machine.\n   - Install a missing CLI when the user asks to set up Meteor or requests a\n     local create, run, test, build, or deploy operation that requires it.\n   - For explanation, review, or planning only, report the missing prerequisite\n     and the install command without running it.\n   - Require explicit confirmation before any recovery operation that removes\n     state: `meteor reset`, `meteor reset --db`, npm cache clearing, targeted\n     global metadata cleanup, uninstall, or full reinstall.\n   - When evidence makes a cleanup or reinstall plausible, suggest the least\n     destructive option with its reason, scope, and expected state loss. Do\n     not execute it until the user explicitly confirms that operation.\n2. Inspect the host and intended project. Check the operating system,\n   architecture, `node --version`, `npm --version`, CLI lookup result, and\n   `meteor --version` when available. In an application, read\n   `.meteor\u002Frelease` before selecting a release.\n3. Distinguish the requested version:\n   - The npm selector in `npx meteor@\u003Cversion>` chooses an installer package.\n   - A Meteor application is pinned to a framework release in\n     `.meteor\u002Frelease`.\n   Do not reinstall the user-wide CLI merely because a project uses another\n   release.\n   Before selecting Meteor 3.6 for existing local data, read\n   [local database preparation](references\u002Flocal-database-upgrade.md).\n   Its bundled MongoDB 8 requires host checks and MongoDB 7 FCV preparation\n   under the previous release before the new release starts.\n4. For a missing CLI, PATH failure, npm installer failure, or host\n   prerequisite, follow [Installation and PATH](references\u002Finstallation-and-path.md).\n5. For a project release, cache reset, corrupted dev bundle, uninstall, or\n   clean reinstall, follow [Releases, reset, and reinstall](references\u002Freleases-reset-reinstall.md).\n   Use [Reinstall decision guide](references\u002Freinstall-decision.md) before\n   recommending a user-wide reinstall for an observed failure.\n6. Verify the result with `meteor --version`. For project work, run the\n   narrowest requested Meteor command and confirm that it resolves the release\n   in `.meteor\u002Frelease`. Report commands run, selected versions, state removed,\n   and anything the user must do in a new shell.\n\n## Installation rules\n\n| Situation | Action |\n|---|---|\n| Latest supported CLI | Run `npx meteor`. |\n| Pinned installer package | Run `npx meteor@\u003Cversion> install`, then verify the reported Meteor release. |\n| Linux or macOS alternative | `curl https:\u002F\u002Finstall.meteor.com\u002F \\| sh` remains documented. Keep `npx meteor` as the primary cross-platform command. |\n| npm fallback | Run `npm install -g meteor --foreground-script` only after the documented `npx` recovery steps fail. |\n| Existing project needs another release | Use the project's pin or a Meteor `--release` command. Do not replace the user-wide installation first. |\n\nNever run `npx install meteor`. Never add the npm `meteor` installer to an\napplication's `package.json`; it is an installer, not the framework runtime.\n\n## State boundaries\n\n| State | Scope | Safe operation |\n|---|---|---|\n| User Meteor directory | Downloaded tools, releases, dev bundles, and CLI state for the user | `npx meteor uninstall` removes the whole installation. Use only for an authorized uninstall or clean reinstall. |\n| User package catalog metadata | Shared release and package metadata inside the user Meteor directory | Prefer an ordinary online catalog refresh. Treat targeted metadata rebuilding as an advanced, confirmation-required recovery. |\n| `.meteor\u002Frelease` | Project framework release | Change through `meteor update --release \u003Crelease>`, not a global reinstall. |\n| `.meteor\u002Flocal` | Project build cache, generated state, and local development database | Suggest `meteor reset` for project-cache evidence; it preserves the database. `meteor reset --db` deletes it. Run either only after confirmation. |\n| npm `npx` cache | Temporary installer package cache | Suggest clearing only after an `npx`-specific failure, not for an ordinary Meteor build problem. Run only after confirmation. |\n\nDo not delete internal tool or dev-bundle directories selectively without a\ndocumented command and evidence that identifies that layer. Use `meteor reset`\nfor project cache corruption. Use a complete, authorized reinstall only when\nthe user-wide installation itself is corrupt. Never recommend hidden Meteor\nadministration commands as user-facing cache cleaners.\n\n## Handoffs\n\n- The CLI starts but the application fails: `meteor-debugging`.\n- The application must move from Meteor 2 to Meteor 3: `migrate-to-meteor-3`.\n- A build cache or bundler failure remains after the CLI and project state are\n  classified: `meteor-modern-build-stack` or `migrate-to-rspack`.\n- Deployment credentials, Galaxy, containers, or runtime configuration:\n  `meteor-deployment`.\n\n## References\n\n- [Installation and PATH](references\u002Finstallation-and-path.md)\n- [Releases, reset, and reinstall](references\u002Freleases-reset-reinstall.md)\n- [Reinstall decision guide](references\u002Freinstall-decision.md)\n- [Evaluation cases](references\u002Feval-cases.md)\n","# Install and repair the Meteor CLI\n\nMake the Meteor CLI available without changing an application or deleting\nstate that the user did not place in scope. `npx meteor` runs the official npm\ninstaller and creates a user-wide Meteor installation; it does not add the\ninstaller permanently to global npm packages.\n\n## Decision flow\n\n1. Classify the request before changing the machine.\n   - Install a missing CLI when the user asks to set up Meteor or requests a\n     local create, run, test, build, or deploy operation that requires it.\n   - For explanation, review, or planning only, report the missing prerequisite\n     and the install command without running it.\n   - Require explicit confirmation before any recovery operation that removes\n     state: `meteor reset`, `meteor reset --db`, npm cache clearing, targeted\n     global metadata cleanup, uninstall, or full reinstall.\n   - When evidence makes a cleanup or reinstall plausible, suggest the least\n     destructive option with its reason, scope, and expected state loss. Do\n     not execute it until the user explicitly confirms that operation.\n2. Inspect the host and intended project. Check the operating system,\n   architecture, `node --version`, `npm --version`, CLI lookup result, and\n   `meteor --version` when available. In an application, read\n   `.meteor\u002Frelease` before selecting a release.\n3. Distinguish the requested version:\n   - The npm selector in `npx meteor@\u003Cversion>` chooses an installer package.\n   - A Meteor application is pinned to a framework release in\n     `.meteor\u002Frelease`.\n   Do not reinstall the user-wide CLI merely because a project uses another\n   release.\n   Before selecting Meteor 3.6 for existing local data, read\n   [local database preparation](references\u002Flocal-database-upgrade.md).\n   Its bundled MongoDB 8 requires host checks and MongoDB 7 FCV preparation\n   under the previous release before the new release starts.\n4. For a missing CLI, PATH failure, npm installer failure, or host\n   prerequisite, follow [Installation and PATH](references\u002Finstallation-and-path.md).\n5. For a project release, cache reset, corrupted dev bundle, uninstall, or\n   clean reinstall, follow [Releases, reset, and reinstall](references\u002Freleases-reset-reinstall.md).\n   Use [Reinstall decision guide](references\u002Freinstall-decision.md) before\n   recommending a user-wide reinstall for an observed failure.\n6. Verify the result with `meteor --version`. For project work, run the\n   narrowest requested Meteor command and confirm that it resolves the release\n   in `.meteor\u002Frelease`. Report commands run, selected versions, state removed,\n   and anything the user must do in a new shell.\n\n## Installation rules\n\n| Situation | Action |\n|---|---|\n| Latest supported CLI | Run `npx meteor`. |\n| Pinned installer package | Run `npx meteor@\u003Cversion> install`, then verify the reported Meteor release. |\n| Linux or macOS alternative | `curl https:\u002F\u002Finstall.meteor.com\u002F \\| sh` remains documented. Keep `npx meteor` as the primary cross-platform command. |\n| npm fallback | Run `npm install -g meteor --foreground-script` only after the documented `npx` recovery steps fail. |\n| Existing project needs another release | Use the project's pin or a Meteor `--release` command. Do not replace the user-wide installation first. |\n\nNever run `npx install meteor`. Never add the npm `meteor` installer to an\napplication's `package.json`; it is an installer, not the framework runtime.\n\n## State boundaries\n\n| State | Scope | Safe operation |\n|---|---|---|\n| User Meteor directory | Downloaded tools, releases, dev bundles, and CLI state for the user | `npx meteor uninstall` removes the whole installation. Use only for an authorized uninstall or clean reinstall. |\n| User package catalog metadata | Shared release and package metadata inside the user Meteor directory | Prefer an ordinary online catalog refresh. Treat targeted metadata rebuilding as an advanced, confirmation-required recovery. |\n| `.meteor\u002Frelease` | Project framework release | Change through `meteor update --release \u003Crelease>`, not a global reinstall. |\n| `.meteor\u002Flocal` | Project build cache, generated state, and local development database | Suggest `meteor reset` for project-cache evidence; it preserves the database. `meteor reset --db` deletes it. Run either only after confirmation. |\n| npm `npx` cache | Temporary installer package cache | Suggest clearing only after an `npx`-specific failure, not for an ordinary Meteor build problem. Run only after confirmation. |\n\nDo not delete internal tool or dev-bundle directories selectively without a\ndocumented command and evidence that identifies that layer. Use `meteor reset`\nfor project cache corruption. Use a complete, authorized reinstall only when\nthe user-wide installation itself is corrupt. Never recommend hidden Meteor\nadministration commands as user-facing cache cleaners.\n\n## Handoffs\n\n- The CLI starts but the application fails: `meteor-debugging`.\n- The application must move from Meteor 2 to Meteor 3: `migrate-to-meteor-3`.\n- A build cache or bundler failure remains after the CLI and project state are\n  classified: `meteor-modern-build-stack` or `migrate-to-rspack`.\n- Deployment credentials, Galaxy, containers, or runtime configuration:\n  `meteor-deployment`.\n\n## References\n\n- [Installation and PATH](references\u002Finstallation-and-path.md)\n- [Releases, reset, and reinstall](references\u002Freleases-reset-reinstall.md)\n- [Reinstall decision guide](references\u002Freinstall-decision.md)\n- [Evaluation cases](references\u002Feval-cases.md)\n",{"name":5,"license":15,"metadata":24,"description":36},{"area":25,"kind":26,"author":9,"bundle":27,"meteor":33,"tagline":34,"docs_synced_at":35},"ops","workflow",[28,29,30,25,31,32],"essentials","migration","fullstack","blaze","react",">=3.0","Install, locate, repair, reset, or cleanly reinstall the Meteor 3 CLI with correct version and PATH handling.","2026-11-13","Use when installing, locating, repairing, resetting, or uninstalling the Meteor CLI for Meteor 3 development. Triggers on \"meteor: command not found\", npx meteor, installer failures, PATH problems, specific Meteor versions, clean reinstall requests, meteor reset, or corrupted dev bundles. Use this skill when the user asks about fresh workstation setup or making a local Meteor command available. For application failures after the CLI starts, use meteor-debugging; for application code upgrades, use migrate-to-meteor-3.\n","main","0162f7828beea805972d4db9a5e3e08aea3e0d17","skills\u002Fmeteor-cli-installation",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":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add meteor\u002Fagent-skills --skill meteor-cli-installation",{"tool":52,"command":53},"bunx","bunx skills add meteor\u002Fagent-skills --skill meteor-cli-installation",{"tool":55,"command":56},"pnpm","pnpm dlx skills add meteor\u002Fagent-skills --skill meteor-cli-installation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-cli-installation\u002FSKILL.md",true,[60,66,70,74,78],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Feval-cases.md","REFERENCE","参考文档",13968,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-cli-installation\u002Freferences\u002Feval-cases.md",{"path":67,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Finstallation-and-path.md",4489,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-cli-installation\u002Freferences\u002Finstallation-and-path.md",{"path":71,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Flocal-database-upgrade.md",3374,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-cli-installation\u002Freferences\u002Flocal-database-upgrade.md",{"path":75,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Freinstall-decision.md",9925,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-cli-installation\u002Freferences\u002Freinstall-decision.md",{"path":79,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Freleases-reset-reinstall.md",5779,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-cli-installation\u002Freferences\u002Freleases-reset-reinstall.md",[83,90,97,104,111,118],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M72VSP00GY1HPN58HNR966DJ","meteor-native","Use when building or maintaining Meteor 3 Android\u002FiOS apps through Cordova. Triggers on meteor add-platform, android-device, ios-device, mobile-config.js, Cordova plugins, native signing or store artifacts, and mobile hot code push compatibility. Use this skill when the task already concerns Meteor's Cordova app workflow; use meteor-debugging for an unexplained cross-layer failure and meteor-deployment for the backend. React Native\u002FExpo, Capacitor, and native Node.js addons are separate workflows.","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-native\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M72VTT678CAVGTRHSCCZMNSN","migrate-to-rspack","Use when migrating an existing Meteor app to Rspack (Meteor 3.4+), or upgrading Rspack 1 to 2 on Meteor 3.6. Triggers on nested imports, mainModule entry points, server-only apps, replacing fourseven:scss \u002F meteor\u002Fless \u002F coffeescript \u002F jorgenvatle:vite \u002F zodern:melte with loaders, Svelte\u002FTypeScript preprocessing or Lingui SWC plugin failures after upgrade, CommonJS default-import interop, module.exports in client graphs, Node built-ins in browser code, _build \u002F build-assets \u002F build-chunks, .meteorignore hiding handoff files, dynamic chunks under ROOT_URL, meteor.modules for CSS\u002FHTML, resolve.symlinks or resolve.alias migration, automatic dependency updates and immutable CI\u002FDocker builds. Use this skill when the user asks about migration compatibility or a build plugin's Rspack replacement. For new-app setup and rspack.config.js helpers, use meteor-modern-build-stack instead.","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigrate-to-rspack\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M72VTMKP4FEEE8KPTBW0TS0Y","migrate-to-meteor-3","Use when migrating a Meteor 2.x application to Meteor 3.x. Triggers on callAsync, *Async Mongo, removed Fibers, implicit-global ReferenceError, lost Blaze reactivity, a publish function returning a Promise, a scheduler dropping a Promise, a read API receiving update modifiers, async allow\u002Fdeny, an Iron Router controller not running, \"Method stub took too long\", Atmosphere resolution, Express 5 WebApp handlers, lost async context, rawCollection callbacks, TypeScript declaration failures during upgrades, useTracker, and useSubscribe. Use this skill when the user asks about upgrading Meteor, async caller propagation, iterators with await, or replacing and forking packages. Standalone declarations and type-checking belong to meteor-typescript.","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigrate-to-meteor-3\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M72VTEG9AB229C97SRKZ2FFG","meteor-typescript","Use when setting up or repairing Meteor application declarations, TypeScript configuration, JavaScript IntelliSense, or local and CI type-checking. Triggers on meteor types, meteor\u002F* imports resolving to any, missing declarations, duplicate Meteor identifiers, zodern:types, @types\u002Fmeteor, .meteor\u002Ftypes, tsconfig.json, jsconfig.json, and tsc --noEmit in a Meteor app. Use this skill when choosing or migrating declaration providers without changing the app's runtime or bundler. For a Meteor 2-to-3 runtime migration use migrate-to-meteor-3 first; for SWC\u002FRspack compilation use meteor-modern-build-stack or migrate-to-rspack. General TypeScript language questions and Atmosphere declaration publishing are outside this app scope.","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-typescript\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M72VT9PART27QBM306JC3PGN","meteor-testing","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.","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-testing\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":19},"01M72VT4X6FMW8YDG4GNR8FKNJ","meteor-security","Use when auditing or hardening a Meteor 3 application. Triggers on missing check() on method arguments, missing this.userId guards on publications, browser-policy CSP, DDPRateLimiter rules, oauth-encryption via Accounts.config oauthSecretKey, audit-argument-checks, allow\u002Fdeny legacy patterns, BrowserPolicy.content.disallowInlineScripts, BrowserPolicy.framing.disallow. Use this skill when the user asks about hardening, asks about a security review, or asks about CSP for a third-party script (Stripe, Google Maps, fonts).","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-security\u002FSKILL.md",[],[]]