schemas

Generate production-ready Beckn Protocol v2.1 generalised schema packs for any use case or vertical, in two modes: (1) Greenfield — create new schemas targeting the generalised Resource/Offer/Contract model from domain descriptions; (2) Migration — take existing v2 schema folders and produce v2.1 equivalents with a structural fit review. Use this skill whenever the user wants to create, design, generate, or migrate Beckn v2.1 schemas — phrases like "generalised schema", "resource schema", "contract schema", "v2.1 schema", "migrate my v2 schemas to v2.1", "upgrade schema to generalised", or wants to model any domain (mobility, hiring, energy, healthcare, data, carbon, etc.) using the domain-neutral v2.1 core. For v1→v2.1, instruct the user to run beckn-v2-schema first, then this skill. For commerce-oriented schemas staying on Item/Order/Fulfillment, use beckn-v2-schema. Always use this skill for any v2.1 generalised schema generation or migration task.

Validates Beckn Protocol v2.1 generalised extension schema packs for correctness and consistency across four quality layers: OpenAPI structure, JSON-LD prefix resolution, cross-file consistency, and example payload validation. Use this skill whenever the user asks to test, validate, check, or verify their Beckn v2.1 generalised schemas — phrases like "run tests on my v2.1 schemas", "validate the generalised schema pack", "check if my resource schemas are correct", or "test the v2.1 contract schemas". Also use automatically at the end of any beckn-v21-schema generation workflow to confirm the generated pack is clean before publishing. For v2 schemas using Item/Order/Fulfillment semantics, use the beckn-schema-tester skill instead.