Curate and maintain KG-Registry resource pages from a local repository clone: expand stub entries into complete metadata, batch-process uncatalogued stubs, validate schema compliance and provenance, and update stale product URLs.
Use when curating or expanding a KG-Registry resource page. Applies to stub resources and incomplete existing pages stored as Markdown with YAML front matter under resource/.
Use when asked to curate the next N KG-Registry stub resources. Selects uncatalogued stub pages not already listed in reports/curation_problems.tsv and dispatches single-resource curation in parallel.
Use when validating or quality-checking KG-Registry resource pages after curation, especially for schema compliance, provenance slot correctness, and stub-cleanup issues.
Use when updating the URL for a specific KG-Registry product, especially when the original URL is dead, redirected, versioned, or replaced by a newer canonical landing or download page.
A registry for knowledge graphs and their components.
KG-Registry Documentation: Start here to learn about the purpose of KG-Registry and how it works.
Entries in KG-Registry are either Resources or Products. Resources represent top-level entries for knowledge graph and data sources. Products are specific representations or interfaces for a resource (e.g., graph dumps, APIs, or visualizations). This also includes associated software and documentation sets.
For more detail:
For developers working on the KG-Registry website and backend:
.agents/Resource publication metadata is validated against cache files produced by
linkml-reference-validator.
Cached title, year, DOI, and first-author mismatches are validation errors;
missing cache files are warnings during ordinary validation.
uv run make validate-file FILE=resource/<resource>/<resource>.md
uv run make cache-publication-references
uv run make validate-publication-reference-cache
See Reference Validation for the full procedure. The data quality dashboard also reports resources with missing publications or publication citation metadata issues.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub knowledge-graph-hub/kg-registry --plugin kg-registry-discoveryAuthor, maintain, validate, and visualize Open Knowledge Format (OKF) bundles — portable markdown knowledge for humans and agents.
OntoShip — ontology-driven docs that ship: a md+git knowledge base (FTS5 search, HTML graph, ontology linter) plus the spec-driven dev-flow built on it. CLI/plugin: gitmark.
Persistent knowledge graph for AI agents — typed entities, closed edge ontology, hybrid search, GQL queries.
A persistent LLM-maintained wiki for your knowledge base. Ingest sources, query your knowledge, and lint for consistency.
Build and maintain an LLM-curated personal knowledge base in your project — Andrej Karpathy's LLM Wiki pattern, designed to scale to thousands of pages without becoming a context bottleneck. Now with an optional compiled graph layer for typed, provenance-backed relationships.
A Terraforming MCP for Knowledge Graphs: validate, classify, and govern AI-generated ontologies.