Knowledge Graph Registry Curator

This skill helps you work with the Knowledge Graph Registry, a collection of resources and tools for managing and sharing metadata about knowledge graphs and their relationships.

Purpose

Guide contributions to the Knowledge Graph Registry by ensuring all Resource and Product entries follow the schema defined in `src/kg_registry/kg_registry_schema/schema/kg_registry_schema.yaml`.

Core Rules

Schema Compliance

1. **Follow the schema strictly** - all fields, types, and enums must match `kg_registry_schema.yaml`

2. **Use existing enum values only** - never create new values for enum fields

3. **Use existing categories** - do not create new classes beyond what's defined in the schema

4. **No ToolResource category** - this is not a valid category

5. **Use "Product" as fallback** - if no specific category fits, use "Product" (not "DataProduct")

File Organization

1. **Never modify `registry/` directory** - these files are auto-generated from Makefile targets

2. **Never create Product files manually** - Products are auto-generated from their corresponding Resource entries

3. **Use `resource/` directory** - consult existing files as examples for Resource entries

Resource Entry Requirements

1. **Include at least one Product** - every Resource must have Products listed

2. **Link Products to Resources** - if a Product references another Resource (e.g., "A mapping file to WikiPathways"), include that Resource's ID in the Product's `original_source` field

3. **Set creation_date to metadata page creation** - not the Resource's actual creation date

4. **Set last_modified_date to today** - update whenever you modify the page

5. **Leave curators field empty** - this is managed by the KG-Registry team

Validation

1. **Validate before committing** - use `poetry run make validate-file` on any modified Resource page

2. **Fix all validity issues** - do not proceed until validation passes

Quick Curation Workflow

When performing batch curation of stub Resource pages:

Step 1: Find Stub Pages

Locate all Resource pages with `stub` in their `domains` list.

Step 2: Select a Resource

Choose a stub page at random. Check `reports/curation_problems.tsv` - if already listed, skip and select another.

Step 3: Research the Resource

Step 4: Expand the Resource Page

Step 5: Validate

Run `poetry run make validate-file` on the updated Resource page. Fix any errors before continuing.

Step 6: Repeat

Return to Step 2 and continue until you've curated at least 5 Resources.

Common Pitfalls

Validation Commands

```bash

Validate a specific Resource file

poetry run make validate-file FILE=path/to/resource.yaml

Use Poetry environment for any make command

poetry run make <target>

```

Example Product Linking

If a Product description says "A mapping file to WikiPathways":

```yaml

original_source:

- wikipathways

```

Always find the Resource ID and include it in `original_source`.