Generate React BYOS screens and routers from Descope flow JSON exports.
npx skills add https://github.com/descope/skills --skill descope-byos-builder
Please help me install this Agent Skill. Skill: descope-byos-builder Source: https://github.com/descope/skills/tree/main/skills/descope-byos-builder Command: npx skills add https://github.com/descope/skills --skill descope-byos-builder
BYOS builder automates the generation of Descope BYOS screens and flow wiring by analyzing Descope flow exports and producing a map of screen components and routers ready for integration.
Export the main flow and all subflows, then wire the generated BYOS components into your app using the FlowEntry and ScreenRouter pattern.
High-intent search queries and answers about installing and using this skill.
Generate React components from Descope flow JSON exports by parsing the flow data to extract screen names, interaction IDs, and input names, then scaffolding a unique BYOS screen component for each entry. This automates the UI wiring process.
BYOS handles screen name collisions across multiple Descope subflows by implementing a screen router. This router directs users to the correct component when duplicate screen names exist across the main flow and invoked post-auth promotion subflows.
Yes, you can use BYOS to automate WebAuthn handling and ctxKey prefill by mirroring flow-specific rules. The generator guides proper payloads and BYOS screen behavior to satisfy componentsConditions and context key requirements.
The best way to wire post-auth promotion subflows is to export the main flow and all subflows, then use the generated BYOS components. The builder exports and wires these screens automatically using the FlowEntry and ScreenRouter pattern.
No, you do not need to manually define input names and contextKeys. The generator uses parse-flow.mjs to automatically extract screen names, interaction IDs, input names, contextKeys, and subflow loaders for accurate component scaffolding.
Your Descope BYOS screen requires a router for duplicate screen names because the builder generates a React component per unique screen name across all flows. A router resolves collisions when the same screen name appears in different subflows.
m16khbGenerate command, skill, and agent files from parsed user inputs.
MOODMNKY-LLCAutomate macOS UI capture, inspection, and interaction via the Peekaboo CLI.
DITEKmaxRender After Effects animations as interactive web assets with lottie-web and dotLottie.
mkgs-databricks-demosDesign user interfaces for custom Databricks Apps using AppKit/React components.
