Update to Abilitya Assistant

{
  "description": "Bundled Abilitya Assistant capability for creating, activating, refreshing, or auditing a branded introduction page. Use when a user asks to configure introductory media, CTA/background imagery, landing copy, benefit lists, regulation text, the intro switch, or desktop/mobile verification at `/:slug/intro`; also use as the introduction-page prerequisite before later purchasable or subscribable access setup.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 241
    },
    {
      "relative_path": "references/contract-and-rendering.md",
      "size_in_bytes": 2555
    }
  ],
  "name": "introduction-page",
  "skill_md_contents": "---\nname: introduction-page\ndescription: Bundled Abilitya Assistant capability for creating, activating, refreshing, or auditing a branded introduction page. Use when a user asks to configure introductory media, CTA/background imagery, landing copy, benefit lists, regulation text, the intro switch, or desktop/mobile verification at `/:slug/intro`; also use as the introduction-page prerequisite before later purchasable or subscribable access setup.\n---\n\n# Abilitya Introduction Page Capability\n\nCreate a complete branded entry page, save it on Abilitya, and verify the deployed experience at desktop and mobile widths. Keep the user-facing conversation under Abilitya Assistant.\n\nContinue applying the parent skill's live-tool discovery, authentication, privacy, upload, confirmation, and cached-read rules. Use the Browser capability for deployed visual QA.\n\nRead [contract-and-rendering.md](references/contract-and-rendering.md) before selecting assets, writing the PATCH, or auditing the deployed page.\n\n## Workflow\n\n1. Resolve the target network, authenticate the manager, and read the current customization.\n2. Discover and describe the live resolver, login, customization read, upload, and network PATCH tools. Treat the live schemas as authoritative.\n3. Select a required 9:16 image or video under 100 MB for primary intro media. Prefer a strong network-owned upload already used by approved Content; otherwise upload authoritative client-owned media. Verify its actual dimensions and crop.\n4. Select optional 16:9 images under 100 MB for the desktop CTA and background. These do not appear on mobile.\n5. Write CTA title, subtitle, and description; button title and subtitle; feature heading/list; and regulation text. Keep the CTA description within the manager UI's 100-character limit.\n6. PATCH only `customization.isIntroLandingActive` and `customization.intro`. Send upload ids, not media URLs. Treat the write response as authoritative.\n7. Verify the saved response contains the active flag, all requested media relationships, and every landing setting.\n8. Visit `<canonical-community-url>/intro` while unauthenticated. Allow for backend and ISR cache delay; use bounded reloads without repeating a successful PATCH.\n9. Inspect one desktop viewport above 768 px and one mobile viewport at or below 768 px. Close the cookie banner if it blocks inspection. Verify assets, crops, copy, CTA color, legibility, benefits, regulation control, and absence of horizontal overflow.\n10. Return the live intro link, asset/copy summary, desktop/mobile result, and any remaining defect. Do not claim completion from the PATCH alone.\n\n## PATCH shape\n\nFollow the described live schema. The expected business shape is:\n\n```ts\n{\n  customization: {\n    isIntroLandingActive: true,\n    intro: {\n      mediaIntroId,\n      imageCallToActionId,\n      imageBackgroundId,\n      landingSettings: {\n        callToActionTitle,\n        callToActionSubtitle,\n        callToActionDescription,\n        buttonTitle,\n        buttonSubtitle,\n        featuresTitle,\n        featuresList,\n        regulation\n      }\n    }\n  }\n}\n```\n\nUse `null` for an intentionally removed optional CTA/background asset only when accepted by the live schema. The backend validates every supplied upload relationship.\n\n## Boundaries\n\n- Operate only on Abilitya.\n- Do not change access type, price, subscription bundles, Content, or notifications unless explicitly requested.\n- Public intro pages gate unauthenticated entry until authentication. Private access optionally uses an intro before its membership-code gate; route that setup through the sibling [Private Access capability](../private-access/SKILL.md). Purchasable and subscribable access require an intro; route them through the Paywall and Subscription capabilities.\n- Prefer authoritative or user-supplied imagery over generated client-branded visuals.\n- Do not repeat a successful write because a cached GET or ISR page is stale.\n"
}