Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    battery passport data validator

    1

    Validate battery passport JSON against versioned, hash-pinned schemas with strict evidence discipline and gap reporting.

    $15

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    battery passport data validator

    battery passport data validator

    Example session with this skill installed

    Validate the battery passport data in data/bp-004.json against the schema defined in profiles/eu-2026-v2.schema.json using the hash pinned in the runtime guide.

    • Read your context and instructions
    • Compiled the battery passport data

    I have completed the validation of the battery passport JSON against the hash-pinned schema. The check identified two structural errors and one missing mandatory field for recycled content tracking.

    Battery Passport Validation Report

    MetricValue / Status
    Input Filedata/bp-004.json
    Schema Profileeu-2026-v2.schema.json
    Profile Hash (Verified)sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
    Validation ResultFAIL
    Error: Path $.battery.composition.cobaltType mismatch: expected number, found string.
    Error: Path $.battery.provenance.origin_idMissing required property.
    Evidence TraceabilitySource: Supplier Portal V3. Date: 2024-05-20.

    Analysis of Results
    The validation failed due to a data type error in the cobalt composition field and a missing origin identifier. The scripts/validate.py tool confirmed these discrepancies against the synthetic fixtures. No values were invented to fill the missing origin_id; it remains marked as a gap.

    Next steps

    • Request the missing origin_id from the upstream supplier for file bp-004.json.
    • Correct the data type for the cobalt composition field from string to numeric.
    • Re-run scripts/validate.py once the JSON is updated to confirm conformance.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    Battery passport data is often fragmented and non-compliant with evolving EU regulations. Manually checking JSON files against versioned customer schemas is error-prone and risks exposing sensitive underlying values during the QA process.

    What it does

    • Validates battery passport JSON against hash-pinned customer schemas for strict version control.
    • Identifies field-level errors and missing data points without exposing actual values in logs.
    • Verifies profile provenance and records source versioning for audit trails.
    • Generates gap lists for missing profiles to help define new data requirements.
    • Distinguishes between supplied observations and live verification tests in technical reports.

    Frameworks & tools

    JSON Schema, Python, and synthetic fixtures for QA testing.

    Why this beats prompting it yourself

    General-purpose LLMs tend to "hallucinate" missing recycled-content figures or identifiers when data is absent. This skill enforces strict evidence discipline, ensuring that an execution error or missing control never results in a false PASS.

    Use cases

    • QA testing of battery passport JSON before production deployment.
    • Generating gap analysis reports for unmapped battery data profiles.
    • Auditing provenance and versioning for regulatory supply chain data.
    • Validating synthetic test data against official customer schema definitions.

    Known limitations

    Does not determine legal scope or certify compliance. Requires an approved profile and hash for validation; cannot validate without a defined schema.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for LLM Ops.

    Does not certify legal compliance or determine regulatory scope. Requires pre-defined versioned schemas and hashes to perform validation.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Software
    Python

    Permissions

    No special permissions declared or detected

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill uses hash-pinned schema validation to ensure data matches specific regulatory or customer versions, preventing the 'hallucinations' or false passes common in general-purpose AI checks.

    You will receive the validation logic, a suite of synthetic test fixtures for QA, and documentation on how to map your battery passport profiles to the validator.

    The skill requires a defined JSON schema and its corresponding hash; it cannot perform validation on unstructured data without a pre-approved profile.

    Yes, it is designed to be framework-agnostic and can be integrated into Python-based AI agents or LLM-ops pipelines that handle JSON data processing.

    The skill generates detailed gap reports that identify exactly which fields are missing or non-compliant, helping you define requirements for new data profiles.

    New in LLM Ops