---
name: manage-chasing-mastery-club
description: Set up and manage a Chasing Mastery member's Club workflow through the authenticated Chasing Mastery MCP tools. Use when someone asks to find or join a Pursuit, create a private Pursuit, search or add an Experience Suite, choose a ready Practice Mode, create or manage a Sprint, submit a locally authored portable package, or take a goal from an idea to a ready-to-practice Chasing Mastery setup.
---

# Manage Chasing Mastery Club

Use the `chasing-mastery` MCP server. Let its OAuth flow authorize the member;
never ask for an account password, browser cookie, access token, RevenueCat
credential, or publisher secret.

## Translate the request

Use the fixed vocabulary:

- **Pursuit**: a shared domain/community such as Darts, Chess, or Memory.
- **Sprint**: one member's focused, measurable goal inside a Pursuit.
- **Practice Mode**: the repeatable protocol contributed by an installed
  portable package.
- **Attempt**: one atomic execution of a Practice Mode.

Read [operations.md](references/operations.md) before mutating Club state. Ask
only for choices that materially change the result. Search before creating,
and present a short recommendation when several Pursuits or packages plausibly
fit.

## Complete the setup

1. Read the member's bounded Club context.
2. Search for the intended Pursuit. Join an exact listed match, or create a
   private Pursuit only when the member asked for a new/private space or no
   existing community fits. Never create a public community implicitly. A
   listed Pursuit may provision its curated default Experience Suites as part
   of joining; inspect the returned Club context before adding anything else.
3. If no ready Practice Mode fits, search the Library and inspect the chosen
   listing. Explain the complete Experience Suite, all included Practice Modes,
   measurements, progression, input options, creator features, and permissions
   in product language.
4. Add that Experience Suite to the intended joined Pursuit once. This pins or
   reuses its exact reviewed release and makes every package-owned default mode
   ready; never ask the member to select, rename, or configure each mode.
5. Choose the ready Practice Mode that best fits the member's immediate goal.
6. Create a Sprint draft, configure its honest starting point and finish line,
   then activate it only after the member's goal is unambiguous.
7. Return the Pursuit, Practice Mode, Sprint, and one clear next action.

If Library search has no useful result and the member wants a custom mode, use
the `build-chasing-mastery-package` skill. After its immutable `.cmpkg` handoff,
submit the archive through the Chasing Mastery tool, poll the asynchronous
private review without busy-waiting, and continue steps 4–7 after approval.
Do not claim approval while the submission is uploaded or reviewing.

Use `build-chasing-mastery-connector` only when portable manual input and
existing reviewed connectors cannot supply the needed observations. Native
connector review, signing, installation, and local grants remain a separate
human-controlled security lane.

## Preserve intent and safety

- Reuse the same `requestId` for an exact retry; generate a new one when any
  mutation input changes.
- Treat tool results as authoritative. Do not infer IDs, contribution names,
  preset identities, permissions, review state, or Sprint readiness.
- Package-default Practice Modes have immutable names, rules, measurements,
  progression, and comparable configuration. Never recreate them as custom
  modes. A member may hide or restore one without deleting its identity,
  Attempts, or progression.
- Never bypass entitlement, membership, package review, visibility, or
  starting-point rules.
- Do not start Attempts, control Station/OBS, publish community packages, or
  alter billing through this workflow.
- Summarize mutations before making them when the user's request did not
  already clearly authorize that exact change.
