descope-byos-builder
Use when building React "Bring Your Own Screen" (BYOS) custom UI on top of a Descope flow — takes exported flow JSONs, extracts the real interaction IDs and outputs, generates BYOS components that match hosted parity, and avoids the rediscovery-the-hard-way failure modes (silent form rejection, shared screen-name collisions, anonymous-session stickiness, nested-form hydration errors, wrong form keys, dead-end buttons, missing OAuth provider field).
Install
With your agent
Install OMGSkills skill "descope/skills:skills/descope-byos-builder" into this agent's normal skills directory: use the OMGSkills MCP get_skill tool, install only the pinned_install commit and path, verify SKILL.md against pinned_install.skill_md_sha, and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/descope/skills /tmp/skills && ln -s /tmp/skills/skills/descope-byos-builder ~/.claude/skills/descope-byos-builderFrom README
Descope BYOS Builder Translate Descope flow JSON exports into working React BYOS screens that call state.next(interactionId, form). The failures below are recorded from real BYOS sessions — every one cost 15–60 minutes the first time. When to Use Building custom UI over a Descope flow while keeping Descope's flow engine (no client-side JWT parsing, full flow logic intact) Modifying an existing BYOS implementation after the underlying flow changed in the Descope console Debugging "flow completes but session stays wrong" / "button does nothing" / "session is anonymous" / "passkey ceremony aborts" symptoms Auditing whether an existing BYOS matches hosted-screen parity Adding post-auth promotion subflows (e.g. add-passkeys) that run after logged-in Don't use for: flows that fully work with the hosted widget (BYOS is a tradeoff — you give up flow edits propagating without code changes). The Iron Rule Ground every BYOS component in the exported flow JSON.