Build with your agent

You should not need to learn Chasing Mastery infrastructure before you can test a good practice idea. Choose the coding agent you already use, describe the member experience in ordinary language, and let the Chasing Mastery Author workflow handle the brief, standalone project, pinned tools, preview, proof, and review handoff.

All three routes use the same Agent Skills, version-3 package brief, public SDK, Workbench, Connector Lab, and immutable release format. The invocation syntax changes; the authored project does not. You can start in one provider and continue in another without migration or regenerated source.

Current channel: Developer Preview 0.2.0. Local package and connector authoring is real and credential-free. Optional Club tools currently use the clearly labeled staging OAuth/MCP resource. The OpenAI universal-directory listing is prepared but cannot be published until production MCP deployment and external review are complete.

Certified hosts

The exact public archive—not a source checkout—has completed both the complete Experience Suite/Workbench journey and the Station connector/Connector Lab journey on:

• Linux x86-64;
• Apple Silicon macOS.

Read the release-bound certification record or follow certification.report from the latest release JSON. Windows remains uncertified preview-only. The package bootstrap contains a PowerShell path, but that is not equivalent to a passing Windows machine journey. Connector authoring does not support Windows or Intel macOS in this release.

Codex

The public preview is a downloaded local marketplace. It works in Codex today without access to the private platform repository.

shasum -a 256 chasing-mastery-author-openai-preview-0.2.0.zip

unzip chasing-mastery-author-openai-preview-0.2.0.zip
codex plugin marketplace add ./chasing-mastery-developers
codex plugin add chasing-mastery-author@chasing-mastery-developers

Use $build-chasing-mastery-package to build a practice experience for the goal
below. Interview me only for choices that materially affect the member
experience, then open the real result in Workbench.

[Describe the pursuit, one Attempt, the result, and the ideal player experience.]

After OpenAI review and publication, the same plugin will be installable from the universal Plugins Directory shared by ChatGPT and Codex. That future route replaces the preview download; it does not introduce a second workflow.

ChatGPT

Eligible ChatGPT plans can upload either local authoring skill now from Plugins → Skills → Create → Upload from your computer:

• Build a package skill
• Build a connector skill

Review the downloaded archive and compare its SHA-256 with the corresponding entry under providers.openai.chatgptPersonalSkills.downloads in the release record before upload. Open ChatGPT Work on an empty local folder, invoke the installed skill, and use the same product prompt shown above.

This early-access route uploads one focused skill at a time. It does not add the scoped Club MCP tools. The reviewed universal plugin is the intended complete ChatGPT experience; until it is published, the docs will not imply that a directory install or authenticated Club handoff already exists.

Claude Code

Claude Code 2.1.224 or newer can install the checksum-pinned archive directly from the Chasing Mastery marketplace:

claude --version
claude plugin marketplace add https://docs.chasingmastery.club/integrations/claude/marketplace.json
claude plugin install chasing-mastery-author@chasing-mastery-developers

Restart Claude Code or run /reload-plugins, then invoke:

/chasing-mastery-author:build-chasing-mastery-package

Natural language also works: “Build a Chasing Mastery Practice Mode for this goal.” The explicit command is useful when you want to make the workflow choice unambiguous.

Claude verifies the archive against the SHA-256 pin in the marketplace. A failed integrity check is terminal; never disable verification or replace the archive with an unpinned copy.

What the agent should do next

The first interaction should feel like product design, not environment setup:

1. recognize whether the idea needs a package, a connector, or both;
2. ask one compact batch of only the unanswered product questions;
3. restate the member promise, Attempt, result, progression, player, creator presentation, correction policy, and edge cases;
4. write the provider-neutral authoring brief;
5. bootstrap the standalone project without sudo, a global CM CLI, or a platform checkout;
6. implement against public SDKs and open the real artifact in Workbench or Connector Lab;
7. iterate visibly until you approve the experience;
8. produce immutable review bytes only after conformance passes and you say it is ready.

The bootstrap uses exact Node 24.18.0. If the host has a different version, it downloads the platform's checksum-pinned portable runtime into the author cache; it never replaces or globally upgrades the developer's Node installation.

Continue with the complete authoring workflow to see the project that remains after the conversation ends.

Sign-in is intentionally late

Designing, running, and packing an experience is local. No Chasing Mastery account is required. Sign-in begins only if you explicitly ask the agent to search your Club, submit exact private package bytes, or set up a Pursuit and Sprint. That action must open first-party OAuth consent with only the necessary club.read, club.manage, or packages.submit scopes.

Never paste a password, cookie, access token, publisher key, Station credential, or billing secret into the conversation. The plugin does not need one.

Updates and rollback

• Codex preview: download the new semantic-version bundle, verify its release record, add or refresh that marketplace, and reinstall the plugin. Start a new thread.
• Claude: run claude plugin marketplace update chasing-mastery-developers, then reinstall when the marketplace advertises a new plugin version.
• Rollback: use a retained versioned archive and release record. Never overwrite old bytes under the same semantic version.

The latest release record is the machine-readable source of version, payload, archive, provider, support, and MCP channel truth.