What problem does it solve? PingOne Authorize has no API for authoring policy logic, so policies must be built by importing a snapshot file through the admin console. This Skill converts plain-language authorization rules (e.g. "deny if amount over 2000", "require step-up MFA over 500") into a valid snapshot JSON file matching PingOne's export/import schema, avoiding malformed imports and INDETERMINATE decisions. ## Core Features & Use Cases - Rule-to-Snapshot Generation: Turns natural-language rules into a complete snapshot file with attributes, conditions, statements, rules, a policy, and a policy set in the correct assembly order. - Fail-Safe Defaults: Enforces attribute default values and a catch-all permit rule so decisions resolve to PERMIT/DENY instead of INDETERMINATE. - Outcome Modeling: Distinguishes hard DENY rules from PERMIT-with-obligation rules (step-up MFA, HITL/consent) with machine-readable statement codes for the calling application. - Use Case: A developer needs a transaction authorization policy in PingOne Authorize that denies amounts over 2000, requires step-up MFA over 500, and permits otherwise — the Skill produces the ready-to-import JSON file. ## Quick Start Ask the assistant to generate a PingOne Authorize import file from your rules, for example: "Create a P1AZ policy that denies transactions over 2000, requires step-up MFA over 500, and permits everything else."
