meteor-community-packageslisted

Use when choosing, evaluating, adopting, configuring, or debugging a package from Meteor's documented community catalog, or moving from a community package to a promoted core package such as roles. Triggers on community package recommendations, Atmosphere vs npm selection, Packosphere maintenance checks, jam:* helpers, Meteor.publish.once, Meteor.publish.stream, meteor-rpc, Wormhole, cluster, and mail-preview. Use this skill when the user asks which maintained package fits or how its documented integration works. Route Meteor 2-to-3 package failures to migrate-to-meteor-3 and underlying core API design to its owning skill.
meteor/agent-skills · ★ 7 · API & Backend · score 74

Install: claude install-skill meteor/agent-skills

# Meteor community packages Use Meteor's community package pages as a curated discovery catalog. A listing does not make a package part of Meteor core, transfer its maintenance to the Meteor organization, or guarantee compatibility with every Meteor 3 release. Select a package only after checking its ownership, current release, supported Meteor range, and changes to application behavior. This skill owns package discovery, comparison, first adoption, and the package-specific integration documented in Meteor core. It does not replace the core skill for methods, publications, Mongo, accounts, security, testing, builds, or deployment. ## Decision flow 1. Define the missing capability and the behavior that must remain unchanged. Distinguish a new adoption from a package that stopped resolving during a Meteor upgrade. Route the latter to `migrate-to-meteor-3`. 2. Inspect `.meteor/release`, `.meteor/packages`, `.meteor/versions`, `package.json`, and the npm lockfile. Package APIs follow the resolved package version, not only the Meteor release. 3. Read [`references/package-catalog.md`](references/package-catalog.md) when the request matches the documented catalog or a promoted package. Open only the selected package's local guide and read its baseline, selection rules, and required checks before responding. Then consult its linked upstream repository for APIs or versions beyond Meteor's maintained guidance. 4. Classify the candidate correctly: - A docs