beckn

Understands Beckn 2.0.0 LTS core schema and generates complete, valid sample payloads for all API actions given a use case description. Detects when domain-specific custom schemas are needed and maps them correctly. Covers retail, food & beverage, grocery, EV charging, energy (P2P trading, demand flex), and data marketplace (DDM) domains.

"Guides developers through designing and publishing Beckn 2.0 schemas — from deciding whether a new schema is needed, through authoring, to registry contribution. Covers the four core mental models: check-before-create, abstraction level, inheritance vs composition, and AI-first authoring."

Understands Beckn 2.0.0 LTS core schema and generates complete, valid sample payloads for all API actions given a use case description. Detects when domain-specific custom schemas are needed and maps them correctly. Covers retail, food & beverage, grocery, EV charging, energy (P2P trading, demand flex), and data marketplace (DDM) domains.

Guides developers through designing and publishing Beckn 2.0 schemas — from deciding whether a new schema is needed, through authoring, to registry contribution. Covers the four core mental models: check-before-create, abstraction level, inheritance vs composition, and AI-first authoring.

"Helps developers configure Beckn-ONIX adapter YAML files — covering modules (BAP/BPP), handler steps, plugin wiring (registry, key manager, cache, schema validator, signer, router, publisher, middleware), routing rules, deployment scenarios, and observability setup."

Helps developers configure Beckn-ONIX adapter YAML files — covering modules (BAP/BPP), handler steps, plugin wiring (registry, key manager, cache, schema validator, signer, router, publisher, middleware), routing rules, deployment scenarios, and observability setup.

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.