Name: Buildcores Opendb Agent
Author: buildcores

name	buildcores-opendb-agent
description	Verifies and enriches BuildCores OpenDB part JSON files, including schema-safe edits, variant hygiene, duplicate checks, and required post-edit validation. Use when editing files under open-db/, updating specs/SKUs/manufacturer URLs, adding new parts, or maintaining data quality.

BuildCores OpenDB Agent

When to Use

Use this skill when working on BuildCores OpenDB data tasks:

Updating existing component JSON files in open-db/
Adding new parts or variants
Filling missing specs, SKUs, or manufacturer_url
Cleaning schema violations and data consistency issues

Core Rules

Do not guess specs. Use authoritative sources or leave fields blank/null.
Treat opendb_id as canonical. Filename (without .json) must match it.
Do not add fields not defined in the category schema.
Check for duplicates before adding a new part.
After every JSON edit, run validation and require pass.

Required Workflow

Identify category and open the relevant schema:
- schemas/{Category}.schema.json
Make targeted edits only for fields supported by schema.
Run validation on edited files:
- ./scripts/validate.sh <path-to-file.json>
If validation fails, fix errors immediately and re-run.
Do not mark work complete until validation passes.

Duplicate and Variant Hygiene

Before creating a part:

Search by name keywords
Search by manufacturer part number(s)
Search by retailer SKU(s)
Verify variant-level differences (OC/non-OC, color, capacity, revision)

Do not create duplicates. Similar siblings can still be valid distinct variants.

Verification Priority

Manufacturer source (primary authority)
Retailer listings (secondary confirmation)
Cross-source agreement for disputed/missing values

Data Quality Targets

Accurate, schema-compliant specs
Correct variant grouping (metadata.manufacturer, metadata.series, metadata.variant)
Valid general_product_information values
Clean formatting and no unknown keys

Repo Instructions Source

Follow the complete repository guidance in agents.md at repo root for:

End-to-end quality checklists
Variant grouping standards
Source verification process
Save vs verify expectations

BuildCores OpenDB Agent

When to Use

Use this skill when working on BuildCores OpenDB data tasks:

Updating existing component JSON files in open-db/

Adding new parts or variants

Filling missing specs, SKUs, or manufacturer_url

Cleaning schema violations and data consistency issues

Core Rules

Do not guess specs. Use authoritative sources or leave fields blank/null.

Treat opendb_id as canonical. Filename (without .json) must match it.

Do not add fields not defined in the category schema.

Check for duplicates before adding a new part.

After every JSON edit, run validation and require pass.

Required Workflow

Identify category and open the relevant schema:

schemas/{Category}.schema.json

Make targeted edits only for fields supported by schema.

Run validation on edited files:

./scripts/validate.sh <path-to-file.json>

If validation fails, fix errors immediately and re-run.

Do not mark work complete until validation passes.

Duplicate and Variant Hygiene

Before creating a part:

Search by name keywords

Search by manufacturer part number(s)

Search by retailer SKU(s)

Verify variant-level differences (OC/non-OC, color, capacity, revision)

Do not create duplicates. Similar siblings can still be valid distinct variants.

Verification Priority

Manufacturer source (primary authority)

Retailer listings (secondary confirmation)

Cross-source agreement for disputed/missing values

Data Quality Targets

Accurate, schema-compliant specs

Correct variant grouping (metadata.manufacturer, metadata.series, metadata.variant)

Valid general_product_information values

Clean formatting and no unknown keys

Repo Instructions Source

Follow the complete repository guidance in agents.md at repo root for:

End-to-end quality checklists

Variant grouping standards

Source verification process

Save vs verify expectations

buildcores-opendb-agent