Hello, community!
We have published v1.0.0-beta.2, the public beta of a new catalog of Agent Skills for developers building, debugging, migrating, and operating Meteor 3 applications.
This is a public beta. The catalog is installable from GitHub, and we have verified the exact tagged installation in Codex, Claude Code, and through the open
skillsCLI. It has not yet been submitted to curated public plugin directories, and its behavior still needs testing across real Meteor applications, agents, and models.
The repository is public at meteor/agent-skills. This beta contains 14 skills covering the parts of Meteor development where framework context, version awareness, and practical decision-making matter most.
AI assistants have become part of daily development. This beta gives them focused Meteor guidance for real tasks, with version boundaries, concrete commands, code patterns, and handoffs between framework areas.
What is included in the beta
This beta covers 14 skills:
| Scope | Skills | What they help with |
|---|---|---|
| Meteor 3 migration | migrate-to-meteor-3, migrate-to-rspack |
Fibers removal, async API migrations, application-wide Promise changes, package triage, and moving existing applications to Rspack |
| Modern build stack | meteor-modern-build-stack |
SWC, file watching, bundler optimization, Rspack configuration, version pairing, and build diagnostics |
| Data and application APIs | meteor-methods, meteor-pubsub, meteor-mongo-minimongo |
Methods, validation, latency compensation, publications, subscriptions, queries, indexes, Minimongo, oplog, and Change Streams |
| User interfaces | meteor-react, meteor-blaze |
Reactive data, Suspense, Fast Refresh, Spacebars, Tracker, async rendering, lifecycle behavior, and bundler-specific refresh behavior |
| Application foundations | meteor-accounts, meteor-security, meteor-testing |
Authentication, OAuth, password flows, authorization, rate limiting, CSP, unit and integration tests, and browser E2E testing |
| Community packages | meteor-community-packages |
Selecting and integrating documented community packages while checking versions, ownership, behavior, support boundaries, and original repositories |
| Debugging and operations | meteor-debugging, meteor-deployment |
Evidence-first diagnosis across build, runtime, data, tests, browsers, mobile, and production, plus Galaxy, Docker, Kubernetes, settings, and Node version matching |
You can install the complete catalog, select one skill, or use one of the curated bundles for migration, full-stack development, operations, Blaze, or React. The skills remain separate so an agent can load the smallest relevant context instead of treating every Meteor question as the same task.
This initial scope is intentionally practical. It focuses on work developers are doing now and on areas where generic advice commonly loses important Meteor details. The full catalog and bundle list describes every skill and its installation command.
Try the beta
The commands below install the latest public beta from the repository.
Codex
Install all 14 skills as the Meteor plugin:
codex plugin marketplace add meteor/agent-skills
codex plugin add meteor@meteor
Claude Code
Install the same catalog as a Claude Code plugin:
claude plugin marketplace add meteor/agent-skills
claude plugin install meteor@meteor
Individual skills and other agents
The open skills CLI supports installing the catalog into Claude Code, Cursor, Codex, Copilot, Gemini CLI, OpenCode, and other compatible agents.
List the skills in this beta:
npx skills add meteor/agent-skills --list
Install one skill:
npx skills add meteor/agent-skills --skill migrate-to-meteor-3
Or run the command without --skill to select skills interactively:
npx skills add meteor/agent-skills
Start a fresh conversation after installation and use the catalog on one real Meteor task in a separate branch or test project. Ask naturally, without naming a skill. This lets us test whether the agent selects the right skill and whether its guidance works in a real application.
Not sure where to start? Try one of these:
- Migrate a Meteor 2 application or one complete synchronous call chain to Meteor 3
- Move a Meteor 3.4+ application to Rspack, including its build plugins and production bundle checks
- Debug a method, publication, Mongo query, React component, or Blaze template from an active application
- Review accounts, authorization, rate limiting, or browser security decisions
- Validate a Galaxy deployment or a containerized Meteor production setup
The feedback we need
After trying a task, please reply in this thread or open an issue with:
- The prompt or task, with sensitive application details removed
- The skill the agent selected, or the skill you expected it to select
- The agent client and model
- Your Meteor release and relevant Atmosphere or npm package versions
- The observed result and what you expected instead
- A small reproduction, logs, or relevant file structure when available
We especially want to hear about incorrect or missed skill selections, wrong commands or APIs, inaccurate version boundaries, missing decisions, references that do not load, and installation failures. Successful results are useful too because they show which workflows already hold up across different clients, models, Meteor releases, and application types.
How the skills will stay current
Meteor keeps evolving, so we will review the catalog alongside new Meteor releases and documentation changes. We will verify behavior and version boundaries, update the relevant skills, add regression cases for confirmed gaps, and publish tagged releases so reports remain reproducible.
Community feedback is part of this process. When a skill misses an important decision or a new Meteor workflow needs dedicated guidance, we can turn that report into a focused update and evaluation case.
The repository includes the contribution workflow and maintenance verification guide for anyone interested in the complete process.
Part of Meteor’s modernization
Meteor 3 moved from Fibers to Promises and async APIs. It modernized builds through SWC and Rspack, and introduced Change Streams.
The next work continues that direction with built-in TypeScript, CapacitorJS for modern native development, and Rstest for Meteor-aware testing. CapacitorJS remains pre-beta work with open timing, while Rstest is implemented but not yet published for public testing.
AI-assisted development belongs in this evolution. Agent Skills keep assistants aligned with current Meteor APIs, version boundaries, framework decisions, and the support boundaries of promoted community packages without replacing documentation or human judgment. The new debugging workflow also helps agents locate the failing layer before changing modern build, data, test, browser, native, or deployment code. As new integrations become published workflows, the catalog will follow with confirmed guidance.
Thank you to our sponsors
Meteor’s continued modernization depends on sponsors who make long-term investment in the framework possible. Thank you to our current sponsors: Galaxy, Input Logic, and CodeRabbit.
If Meteor has helped you build and grow, consider supporting what comes next through the Meteor Sponsorship Program.
Try the beta on one real Meteor task and tell us what happened. Your feedback will decide whether we refine another beta, expand a missing area, or move the catalog toward its first stable release.
Thank you for helping us build the long-term AI tooling Meteor developers need.