Skip to content

v1.0.0-beta.2

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 27 Aug 07:39
· 3 commits to main since this release
8360d85

Meteor Agent Skills v1.0.0-beta.2

This second public beta expands the catalog from 12 to 14 Meteor-maintained skills. It adds focused guidance for documented community packages and evidence-first debugging, while improving Meteor test focus and build-stack routing.

Highlights

  • Add meteor-community-packages for selecting and integrating packages from Meteor's documented community catalog while preserving ownership, version, support, security, and upstream-repository boundaries.
  • Add meteor-debugging for diagnosing the first failing boundary across builds, server and client runtime, DDP, Mongo and Minimongo, tests, browsers, mobile, and production.
  • Extend meteor-testing with focused-run guidance that separates test execution filters from meteor.testModule loading.
  • Add neighboring routing cases for testing and the modern build stack.
  • Refine package adoption, Wormhole exposure, jam:method testing, Playwright CLI evidence, driver-version checks, and test entrypoint guidance from manual evaluation results.

Verification

  • All 35 new or affected manual acceptance cases passed in fresh Claude Code sessions.
  • Repository validation, links, catalog generation, dependency audit, and 33 automated tests passed.
  • The release contains 14 ZIP assets with published SHA-256 digests.
  • Exact tagged installation passed with:
    • Codex CLI 0.149.1
    • Claude Code 2.1.221 using Claude Sonnet 5
    • skills CLI 1.5.23
  • Codex and Claude Code loaded both new skills from 1.0.0-beta.2.
  • Tagged skills discovery and full installation exposed exactly the 14 public skills.
  • A downloaded release ZIP matched its published digest and loaded its linked reference.

Known limitations

  • This remains a public beta and has not been submitted to curated plugin directories.
  • Skill selection and application can vary across clients and models. Feedback from real Meteor applications remains necessary.
  • Community package APIs follow their independently released package versions. Agents must verify the current upstream release and resolved application version before adoption.

Changes