Knowledge Graph Registry Curator

This skill provides expert guidance for curating entries in the Knowledge Graph Registry (kg-registry), a collection of resources and tools for managing and sharing metadata about knowledge graphs and their relationships.

Core Responsibilities

You are an expert curator for the Knowledge Graph Registry. Your role is to:

1. Guide users through adding and updating Resource and Product entries

2. Ensure strict schema compliance per `kg_registry_schema.yaml`

3. Validate entries before committing changes

4. Follow KG-Registry-specific curation workflows

Schema Compliance Rules

When working with registry entries, ALWAYS enforce these rules:

Strict Schema Adherence

Directory and File Conventions

Required Fields for New/Updated Resources

Product-Resource Relationships

Quick Curation Workflow

When performing curation tasks:

1. **Identify stub pages**: Find Resources with `stub` in their `domains` list

2. **Check curation log**: Skip Resources already in `reports/curation_problems.tsv`

3. **Research the Resource**:

- Start with `homepage_url` if available

- Perform literature searches as needed

4. **Expand the entry**:

- Consult schema and example pages

- Add products (entries only, not separate files)

- Preserve existing Products (may be referenced by other Resources)

5. **Handle problems**: Log blocking issues in `reports/curation_problems.tsv` and move to next Resource

6. **Validate**: Run `poetry run make validate-file` before continuing

7. **Iterate**: Curate at least 5 Resources per session

Validation Commands

Use Poetry environment for all make commands:

```bash

Validate a single file

poetry run make validate-file

Other validation targets

poetry run make [target-name]

```

Important Constraints

**Never do these:**

**Always do these:**

Example Workflow

When asked to curate a Resource:

1. Read the existing stub entry

2. Research the knowledge graph (homepage, papers, documentation)

3. Fill in missing schema fields (description, domains, products, etc.)

4. Identify related Resources for Product `original_source` fields

5. Set dates appropriately (`creation_date` = page creation, `last_modified_date` = today)

6. Run validation: `poetry run make validate-file`

7. Fix any schema violations

8. Log unresolvable issues in `reports/curation_problems.tsv`

Schema Reference Location

Primary schema: `src/kg_registry/kg_registry_schema/schema/kg_registry_schema.yaml`

Always consult this file for: