meteormeteor/agent-skills/skills/meteor-cli-installation/SKILL.md

meteor-cli-installation

Skill10 starsChanged 3 months agoMITView on GitHub

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.

Pipes a download into a shell
Installs packages

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

wekan/wekanedited, first seen Oct 8, 2026

Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
wekan/wekan★ 21k98% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- release-publishingSkill
- skill-gap-auditSkill
- skill-maintenanceSkill
- meteor-accountsSkill
- meteor-blazeSkill
- meteor-community-packagesSkill
- meteor-debuggingSkill
- meteor-deploymentSkill
- meteor-methodsSkill
- meteor-modern-build-stackSkill
- meteor-mongo-minimongoSkill
- meteor-nativeSkill
- meteor-pubsubSkill
- meteor-reactSkill
- meteor-securitySkill
- meteor-testingSkill
- meteor-typescriptSkill
- migrate-to-meteor-3Skill
- migrate-to-rspackSkill

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
When evidence makes a cleanup or reinstall plausible, suggest the least destructive option with its reason, scope, and expected state loss.
line 40
Distinctive:
Do not reinstall the user-wide CLI merely because a project uses another release.
line 51
Distinctive:
Before selecting Meteor 3.6-beta.3 or 3.6-rc.0 for existing local data, read local database preparation.
line 53
Distinctive:
Use Reinstall decision guide before recommending a user-wide reinstall for an observed failure.
line 61
Very specific:
Verify the result with meteor --version.
line 63
Very specific:
Never run npx install meteor.
line 78
Very specific:
Do not delete internal tool or dev-bundle directories selectively without a documented command and evidence that identifies that layer.
line 91

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Install and repair the Meteor CLI

Make the Meteor CLI available without changing an application or deleting state that the user did not place in scope. npx meteor runs the official npm installer and creates a user-wide Meteor installation; it does not add the installer permanently to global npm packages.

Decision flow

Classify the request before changing the machine.
- Install a missing CLI when the user asks to set up Meteor or requests a local create, run, test, build, or deploy operation that requires it.
- For explanation, review, or planning only, report the missing prerequisite and the install command without running it.
- Require explicit confirmation before any recovery operation that removes state: meteor reset, meteor reset --db, npm cache clearing, targeted global metadata cleanup, uninstall, or full reinstall.
- When evidence makes a cleanup or reinstall plausible, suggest the least destructive option with its reason, scope, and expected state loss. Do not execute it until the user explicitly confirms that operation.
Inspect the host and intended project. Check the operating system, architecture, node --version, npm --version, CLI lookup result, and meteor --version when available. In an application, read .meteor/release before selecting a release.
Distinguish the requested version:
- The npm selector in npx meteor@<version> chooses an installer package.
- A Meteor application is pinned to a framework release in .meteor/release. Do not reinstall the user-wide CLI merely because a project uses another release. Before selecting Meteor 3.6-beta.3 or 3.6-rc.0 for existing local data, read local database preparation. Its bundled MongoDB 8 requires host checks and MongoDB 7 FCV preparation under the previous release before the new release starts.
For a missing CLI, PATH failure, npm installer failure, or host prerequisite, follow Installation and PATH.
For a project release, cache reset, corrupted dev bundle, uninstall, or clean reinstall, follow Releases, reset, and reinstall. Use Reinstall decision guide before recommending a user-wide reinstall for an observed failure.
Verify the result with meteor --version. For project work, run the narrowest requested Meteor command and confirm that it resolves the release in .meteor/release. Report commands run, selected versions, state removed, and anything the user must do in a new shell.

Installation rules

Situation	Action
Latest supported CLI	Run `npx meteor`.
Pinned installer package	Run `npx meteor@<version> install`, then verify the reported Meteor release.
Linux or macOS alternative	`curl https://install.meteor.com/ \| sh` remains documented. Keep `npx meteor` as the primary cross-platform command.
npm fallback	Run `npm install -g meteor --foreground-script` only after the documented `npx` recovery steps fail.
Existing project needs another release	Use the project's pin or a Meteor `--release` command. Do not replace the user-wide installation first.

Never run npx install meteor. Never add the npm meteor installer to an application's package.json; it is an installer, not the framework runtime.

State boundaries

State	Scope	Safe operation
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.
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.
`.meteor/release`	Project framework release	Change through `meteor update --release <release>`, not a global reinstall.
`.meteor/local`	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.
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.

Do not delete internal tool or dev-bundle directories selectively without a documented command and evidence that identifies that layer. Use meteor reset for project cache corruption. Use a complete, authorized reinstall only when the user-wide installation itself is corrupt. Never recommend hidden Meteor administration commands as user-facing cache cleaners.

Handoffs

The CLI starts but the application fails: meteor-debugging.
The application must move from Meteor 2 to Meteor 3: migrate-to-meteor-3.
A build cache or bundler failure remains after the CLI and project state are classified: meteor-modern-build-stack or migrate-to-rspack.
Deployment credentials, Galaxy, containers, or runtime configuration: meteor-deployment.

References

Installation and PATH
Releases, reset, and reinstall
Reinstall decision guide
Evaluation cases

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free