Update to Abilitya Assistant

{
  "description": "Bundled Abilitya Assistant capability for configuring, converting, refreshing, or auditing a network with recurring paid access and subscription bundles. Use when a user asks for Subscribable access, recurring membership plans, billing cycles, trials, bundle visibility/status/order, `/subscribe` verification, or subscription catalog management. Do not use for a one-time Purchasable paywall.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 253
    },
    {
      "relative_path": "references/contract-and-lifecycle.md",
      "size_in_bytes": 4586
    }
  ],
  "name": "subscription-access",
  "skill_md_contents": "---\nname: subscription-access\ndescription: Bundled Abilitya Assistant capability for configuring, converting, refreshing, or auditing a network with recurring paid access and subscription bundles. Use when a user asks for Subscribable access, recurring membership plans, billing cycles, trials, bundle visibility/status/order, `/subscribe` verification, or subscription catalog management. Do not use for a one-time Purchasable paywall.\n---\n\n# Abilitya Subscription Access Capability\n\nConfigure recurring access, create a coherent sellable bundle catalog, and verify the deployed subscription landing page. Keep the user-facing conversation under Abilitya Assistant.\n\nContinue applying the parent skill's live-tool discovery, authentication, privacy, confirmation, and cached-read rules. Read the sibling [Introduction Page capability](../introduction-page/SKILL.md) when the required intro is missing or incomplete. Use the Browser capability for deployed visual QA.\n\nRead [contract-and-lifecycle.md](references/contract-and-lifecycle.md) before changing access, creating or editing bundles, or auditing `/subscribe`.\n\n## Workflow\n\n1. Resolve the network, authenticate the manager, and read the current customization and manageable bundle catalog.\n2. Discover and describe the live resolver, login, network PATCH, and every subscription endpoint needed for the task. Treat current schemas as authoritative.\n3. Confirm that the Introduction Page is active and complete. Build or repair it before enabling paid recurring access.\n4. Determine currency and catalog design. Reuse explicit choices. If unspecified, choose a small coherent set such as monthly plus discounted annual, explain the assumption afterward, and avoid trials unless requested. If currency is not specified by the user, default to EUR.\n5. Inspect existing manageable bundles before writing. Never create duplicates from a cached or partial catalog.\n6. Convert displayed prices to integer minor units exactly once. Validate titles, interval limits, visibility, status, and trial shape.\n7. Create processor-backed bundles deliberately. Prefer public and active for normal discovery; set explicit order. Verify each response because retries can create processor state.\n8. PATCH the network with Subscribable access and the chosen currency. Expect the backend to normalize access flags so only Subscribable remains true.\n9. Treat write responses as authoritative. Later list the public catalog without manager-only filters to confirm checkout discovery.\n10. Visit `<canonical-community-url>/subscribe` while unauthorized. Allow for bounded cache delay without repeating mutations.\n11. Inspect desktop above 768 px and mobile at or below 768 px. Verify branded intro media/copy, intended plans, price/cycle formatting, trial or Subscribe labels, savings copy, CTA colors, benefits, regulation, carousel behavior, and document-level overflow.\n12. Keep the deployed `/subscribe` tab available. Return the link, catalog summary, access state, desktop/mobile result, assumptions, and defects.\n\n## Boundaries\n\n- Operate only on Abilitya.\n- Never collect card details, create a setup intent, start a member subscription, or complete billing unless separately authorized.\n- Treat bundle deletion as destructive: it soft-deletes offers and queues asynchronous period-end cancellation for active subscriptions. Require explicit confirmation.\n- Treat price, interval, trial, status, privacy, and deletion changes as commercial changes. Do not broaden them beyond the request.\n- Do not assume editing a bundle migrates existing processor subscriptions; it changes future catalog behavior.\n- Do not expose bundle ids, processor ids, payment-method ids, request ids, client secrets, tokens, credentials, or raw API responses.\n- Do not claim readiness from the access PATCH alone; a Subscribable network needs a discoverable active bundle and visual verification.\n"
}