Update to Abilitya Assistant

{
  "name": "private-access",
  "description": "Bundled Abilitya Assistant capability for configuring, converting, or auditing invite-only networks. Use when a user asks for a Private network, private access, membership-code or invitation-code registration, the dedicated Private authentication type, optional intro-page behavior for a private network, or verification of the fixed authentication gate.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 221
    }
  ],
  "skill_md_contents": "---\nname: private-access\ndescription: Bundled Abilitya Assistant capability for configuring, converting, or auditing invite-only networks. Use when a user asks for a Private network, private access, membership-code or invitation-code registration, the dedicated Private authentication type, optional intro-page behavior for a private network, or verification of the fixed authentication gate.\n---\n\n# Abilitya Private Access Capability\n\nConfigure invite-only access and verify that unauthenticated visitors cannot enter without a manager-issued membership code. 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. Use the sibling [Introduction Page capability](../introduction-page/SKILL.md) only when the user wants an intro page.\n\n## Workflow\n\n1. Resolve the network, authenticate the manager, and read the current customization.\n2. Discover and describe the live resolver, login, customization read, and network PATCH tools.\n3. PATCH the access model to Private. The expected effective configuration is `accessType: \"private\"`, `public: false`, and `auth.authType: \"private\"`. Send only fields required by the live schema; verify the coupled access/auth result from the write response.\n4. Preserve the Introduction Page state unless the user asks to change it. Private networks can use an intro, but it is optional.\n5. Optionally set `invitationCodeLabel` and `invitationCodeDisclaimer` for client-specific membership-code wording.\n6. Verify from the successful response that only Private access is active and authentication is Private.\n7. After cache convergence, verify unauthenticated behavior. Without an intro, ordinary routes must open the fixed, non-dismissible Private authentication modal. With an intro, `/intro` remains reachable and the fixed modal applies after leaving bypass routes.\n8. Verify that registration asks for email, password, and a membership/invitation code. Do not attempt sign-up without a manager-provided valid code.\n9. Return the network link, intro state, authentication result, and whether membership codes still need to be created or imported.\n\n## Behavior and boundaries\n\n- “Private network” means the Private access type, not private Content, a private chat, or an unlisted subscription bundle.\n- Private access and Private authentication are coupled. The flow uses email/password plus membership code; Private is not a general-purpose auth option.\n- The global gate waits for cache restoration, then opens fixed for unauthenticated users on non-bypass routes. Bypass routes include login, registration, password recovery, legal/privacy pages, notification preferences, cookie policy, `/intro`, and account deletion.\n- Managers issue and manage membership codes separately, including bulk CSV import. Changing access type does not generate codes.\n- Do not create, reveal, redeem, or test membership codes unless explicitly requested.\n- Do not alter intro media, commercial bundles, prices, Content, theme, or unrelated settings.\n- Operate only on Abilitya and never expose credentials, tokens, raw ids, or raw API responses.\n"
}