beckn-v21-schema-tester

Validate Beckn v2.1 schema packs across four quality layers.

2|3|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/beckn/schemas --skill beckn-v21-schema-tester
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beckn-v21-schema-tester
Source: https://github.com/beckn/schemas/tree/main/tools/beckn-v21-schema-tester
Command: npx skills add https://github.com/beckn/schemas --skill beckn-v21-schema-tester

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Quick Start

Run the tester against your Beckn v2.1 generalised schema pack to verify all four quality layers end-to-end.

Frequently Asked Questions about beckn-v21-schema-tester

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a Beckn v2.1 generalized extension schema pack?

You can validate a Beckn v2.1 generalized extension schema pack by running a four-layer test suite that checks OpenAPI structure, resolves JSON-LD prefixes, verifies cross-file consistency, and validates example payloads across core and domain schemas.

What is the difference between Beckn v2.1 and v2 schema validation?

Beckn v2.1 schema validation targets generalized extension schema packs using flat and versioned layouts, whereas v2 schema validation applies to schemas using Item, Order, and Fulfillment semantics and requires a different tester.

How do I check JSON-LD prefix resolution and OpenAPI structure in Beckn v2.1 schemas?

To check JSON-LD prefix resolution and OpenAPI structure in Beckn v2.1 schemas, use an automated tester that enforces v2.1 rules, resolves external references, and reports actionable fixes for schema authors.

Can I test cross-file consistency across core and domain schemas in Beckn v2.1?

Yes, you can test cross-file consistency across core and domain schemas in Beckn v2.1 by running a validation suite that verifies consistency and resolves external references across flat and versioned layouts.

When should I use a Beckn v2.1 schema tester instead of a general OpenAPI validator?

Use a Beckn v2.1 schema tester instead of a general OpenAPI validator when you need to enforce specific v2.1 rules, resolve JSON-LD prefixes, and validate example payloads across generalized extension schema packs.

Why does my Beckn v2.1 schema validation fail on external references?

Beckn v2.1 schema validation may fail on external references due to unresolved JSON-LD prefixes or cross-file inconsistencies, which the tester identifies by resolving references and reporting actionable fixes.