Agent skill

Knowledge Graph Builder

by FerroxLabs in FerroxLabs/wayland

Knowledge graph engineering covering ontology design, graph database selection (Neo4j, Amazon Neptune, ArangoDB), entity and relation extraction from text, graph-based RAG (GraphRAG), knowledge…

Apache-2.0Auto-check passedKnowledge Management

Install Knowledge Graph Builder

skills CLI
$ npx skills add FerroxLabs/wayland --skill knowledge-graph-builder -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FerroxLabs/wayland knowledge-graph-builder --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/ai-machine-learning/knowledge-graph-builder .claude/skills/knowledge-graph-builder && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
knowledge-graph-builder
GitHub stars
608
Token cost
~3.4k tokens
SKILL.md length
523 words
Files
1
Skills in repo
1,194
Repo updated
First seen
Licence
Apache-2.0

At a glance

Knowledge graph engineering covering ontology design, graph database selection (Neo4j, Amazon Neptune, ArangoDB), entity and relation extraction from text, graph-based RAG (GraphRAG), knowledge…

  • The user asks about knowledge graph builder
  • SKILL.md covers Overview, Knowledge Graph Architecture, Graph Database Selection and Ontology Design, plus 9 more sections
  • Calls aws
  • Knowledge graph builder best practices

What it does

Knowledge Graph Builder is an agent skill from FerroxLabs/wayland. Knowledge graph engineering covering ontology design, graph database selection (Neo4j, Amazon Neptune, ArangoDB), entity and relation extraction from text, graph-based RAG (GraphRAG), knowledge graph embeddings, graph query optimization, and integration patterns with LLM systems. Use when the user asks about knowledge graph builder, knowledge graph builder best practices, or needs guidance on knowledge graph builder implementation. Do NOT use when the user needs a different specialized skill or is asking about an…

Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Knowledge Management, covering Knowledge graphs. It works with Neo4j. The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.

When your agent uses it

  • The user asks about knowledge graph builder
  • Knowledge graph builder best practices
  • Needs guidance on knowledge graph builder implementation
  • The user needs a different specialized skill

Example prompts

  • “/knowledge-graph-builder”

Requirements

  • Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • aws

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use aws, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Knowledge Graph Builder loads about 3.4k tokens when it runs. Until then it costs about 143 tokens; SKILL.md has 523 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~143
When it runs · the whole SKILL.md, loaded when a task matches
~3.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 523 words, ~3,378 tokens.

Download SKILL.mdSave it as .claude/skills/knowledge-graph-builder/SKILL.md (or your agent's skills folder).
name
knowledge-graph-builder
description
Knowledge graph engineering covering ontology design, graph database selection (Neo4j, Amazon Neptune, ArangoDB), entity and relation extraction from text, graph-based RAG (GraphRAG), knowledge graph embeddings, graph query optimization, and integration patterns with LLM systems. Use when the user asks about knowledge graph builder, knowledge graph builder best practices, or needs guidance on knowledge graph builder implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.
license
Apache-2.0
metadata.author
foundry-skills
metadata.version
1.0.0
metadata.tags
ai-ml guide best-practices
metadata.category
ai-machine-learning
metadata.subcategory
applied-ai
metadata.disclaimer
none
metadata.difficulty
advanced

Knowledge Graph Builder

Overview

Knowledge graphs represent structured relationships between entities, enabling powerful reasoning, contextual retrieval, and explainable AI. Building production knowledge graphs requires ontology design, entity extraction, graph database selection, query optimization, and integration with LLM systems via GraphRAG patterns.

Knowledge Graph Architecture

+------------------+     +-------------------+     +------------------+
| Data Sources     | --> | Extraction        | --> | Graph Database   |
| - Documents      |     | - NER             |     | (Person)-[:WORKS_AT]->(Company)
| - APIs           |     | - Relation extract|     | (Paper)-[:CITES]->(Paper)
| - Databases      |     | - Entity linking  |     | (Product)-[:HAS]->(Feature)
+------------------+     +-------------------+     +------------------+
                                                          |
+------------------+     +-------------------+     +------v-----------+
| Applications     | <-- | Query & Reasoning | <-- | Indexing &       |
| - GraphRAG       |     | - Cypher / SPARQL |     | Enrichment       |
| - Recommendations|     | - Path finding    |     | - Embeddings     |
| - Analytics      |     | - Subgraph match  |     | - Community det. |
+------------------+     +-------------------+     +------------------+

Graph Database Selection

FeatureNeo4jAmazon NeptuneArangoDBTigerGraphDgraph
Query LangCypherGremlin/SPARQLAQLGSQLGraphQL+-
HostingBothManaged (AWS)BothBothBoth
Vector SupportSince 5.13NoNoNoNo
RDF SupportLimitedNativeNoNoNo
CommunityVery LargeAWS ecosystemMediumMediumMedium
Learning CurveLowMediumMediumHighMedium
Selection guide:
  AWS native? -> Amazon Neptune
  Need RDF/SPARQL? -> Neptune or Apache Jena
  Graph + document hybrid? -> ArangoDB (multi-model)
  SQL-like preferred? -> Neo4j (Cypher is most approachable)
  GraphQL preferred? -> Dgraph
  Enterprise trillions of edges? -> TigerGraph
  Default -> Neo4j (largest community, vector search, mature)

Ontology Design

Design Process
1. Start with competency questions
   "Who authored papers about topic X?"
   "What products share features?"

2. Identify entity types (nouns in questions)

3. Define relationship types (verbs connecting nouns)
   Always directional: (Subject)-[:VERB]->(Object)

4. Add properties (attributes of nodes and edges)
   Include temporal properties (created_at, valid_from)

5. Define constraints (uniqueness, required props, cardinality)
Schema in Neo4j
cypher
CREATE CONSTRAINT person_id IF NOT EXISTS
FOR (p:Person) REQUIRE p.id IS UNIQUE;

CREATE CONSTRAINT company_id IF NOT EXISTS
FOR (c:Company) REQUIRE c.id IS UNIQUE;

CREATE FULLTEXT INDEX entity_search IF NOT EXISTS
FOR (n:Person|Company|Paper) ON EACH [n.name, n.title, n.description];

CREATE VECTOR INDEX entity_embeddings IF NOT EXISTS
FOR (n:Entity) ON (n.embedding)
OPTIONS {indexConfig: {
  `vector.dimensions`: 1536,
  `vector.similarity_function`: 'cosine'
}};
Common Ontology Patterns
Temporal:     (Person)-[:WORKS_AT {from: date, to: date}]->(Company)
Hierarchical: (Category)-[:SUBCATEGORY_OF]->(Category)
Provenance:   (Fact)-[:EXTRACTED_FROM {confidence: 0.95}]->(Document)
Events:       (Person)-[:PARTICIPATED_IN]->(Event)-[:OCCURRED_AT]->(Location)
Multi-hop:    (Drug)-[:TREATS]->(Disease)-[:HAS_SYMPTOM]->(Symptom)

Entity and Relation Extraction

LLM-Based Extraction
python
from openai import OpenAI
import json

class KnowledgeExtractor:
    def __init__(self, model: str = "gpt-4o-mini"):
        self.client = OpenAI()
        self.model = model

    def extract(self, text: str, schema: dict = None) -> dict:
        schema_inst = ""
        if schema:
            schema_inst = (f"\nEntity types: {schema.get('entity_types', [])}\n"
                          f"Relation types: {schema.get('relation_types', [])}\n")

        response = self.client.chat.completions.create(
            model=self.model,
            messages=[
                {"role": "system", "content": "Extract precise entities and relationships. "
                 "Only extract what is explicitly stated or strongly implied."},
                {"role": "user", "content": f"Extract entities and relationships:{schema_inst}\n"
                 f"Return JSON: {{\"entities\": [{{\"id\", \"type\", \"name\", \"properties\"}}], "
                 f"\"relationships\": [{{\"source\", \"target\", \"type\", \"properties\"}}]}}\n\n"
                 f"Text: {text}"},
            ],
            response_format={"type": "json_object"}, temperature=0,
        )
        return json.loads(response.choices[0].message.content)

    def extract_batch(self, documents: list[str], schema: dict = None) -> dict:
        all_entities = {}
        all_rels = []
        for doc in documents:
            result = self.extract(doc, schema)
            for e in result.get("entities", []):
                key = (e["type"], e["name"].lower())
                if key not in all_entities:
                    all_entities[key] = e
                else:
                    all_entities[key]["properties"].update(e.get("properties", {}))
            all_rels.extend(result.get("relationships", []))
        return {"entities": list(all_entities.values()), "relationships": all_rels}
Extraction Method Comparison
MethodSpeedQualityCostBest For
SpaCy NERVery FastGoodFreeStandard entities, high volume
LLM extractionSlowExcellentAPI costComplex relations, custom schema
Fine-tuned BERTFastVery GoodFree (GPU)Domain-specific entities
Hybrid (SpaCy + LLM)MediumExcellentModerateBest quality/cost balance

GraphRAG

GraphRAG vs. Vector RAG
DimensionVector RAGGraphRAGHybrid
RetrievalSemantic similarityStructural traversalBoth
ReasoningLimitedMulti-hop relationshipsStrong
ExplainabilityLowHigh (explicit paths)High
Setup complexityLowHighHigh
Best forUnstructured Q&ARelational questionsComplex domains
Implementation
python
from neo4j import GraphDatabase

class GraphRAGPipeline:
    def __init__(self, neo4j_uri: str, neo4j_auth: tuple, llm_model: str = "gpt-4o"):
        self.driver = GraphDatabase.driver(neo4j_uri, auth=neo4j_auth)
        self.client = OpenAI()
        self.llm_model = llm_model

    def query(self, question: str) -> dict:
        entities = self._extract_query_entities(question)
        subgraph = self._retrieve_subgraph(entities)
        answer = self._generate_answer(question, subgraph)
        return {"answer": answer, "entities_found": entities,
                "subgraph_nodes": len(subgraph["nodes"])}

    def _extract_query_entities(self, question: str) -> list[str]:
        resp = self.client.chat.completions.create(
            model="gpt-4o-mini",
            messages=[{"role": "user", "content":
                f"Extract entity names. JSON: {{\"entities\": [...]}}\nQuestion: {question}"}],
            response_format={"type": "json_object"}, temperature=0,
        )
        return json.loads(resp.choices[0].message.content).get("entities", [])

    def _retrieve_subgraph(self, entities: list[str], hops: int = 2) -> dict:
        nodes, edges = [], []
        with self.driver.session() as session:
            for entity in entities:
                result = session.run("""
                    CALL db.index.fulltext.queryNodes('entity_search', $name)
                    YIELD node, score WHERE score > 0.5
                    WITH node LIMIT 5
                    CALL apoc.path.subgraphAll(node, {maxLevel: $hops, limit: 50})
                    YIELD nodes, relationships
                    RETURN nodes, relationships
                """, name=entity, hops=hops)
                for record in result:
                    nodes.extend([{"labels": list(n.labels), "props": dict(n)} for n in record["nodes"]])
                    edges.extend([{"type": r.type} for r in record["relationships"]])
        return {"nodes": nodes, "edges": edges}

    def _generate_answer(self, question: str, subgraph: dict) -> str:
        context = "\n".join(
            f"[{'/'.join(n['labels'])}] {n['props']}" for n in subgraph["nodes"][:30]
        )
        resp = self.client.chat.completions.create(
            model=self.llm_model,
            messages=[
                {"role": "system", "content": "Answer using the knowledge graph context. Cite entities."},
                {"role": "user", "content": f"Context:\n{context}\n\nQuestion: {question}"},
            ], temperature=0,
        )
        return resp.choices[0].message.content

Knowledge Graph Embeddings

ModelApproachBest For
TransETranslational (h + r = t)Hierarchical relations
DistMultBilinear diagonalSymmetric relations
ComplExComplex-valued bilinearAsymmetric relations
RotatERotationalInferring new relations

Query Optimization

cypher
-- Bound traversal depth (never use unbounded [*])
MATCH (a:Person {name: "Alice"})-[*1..3]->(b:Company)
RETURN b.name;

-- Use full-text index instead of CONTAINS
CALL db.index.fulltext.queryNodes('entity_search', 'Alice') YIELD node;

-- Profile to find bottlenecks
PROFILE MATCH (a:Person)-[:WORKS_AT]->(c:Company)-[:LOCATED_IN]->(city:City)
WHERE city.name = "San Francisco"
RETURN a.name, c.name;

-- Use parameters (enables query plan caching)
MATCH (p:Person {name: $name}) RETURN p;

Checklist

  • Define competency questions the graph must answer
  • Design ontology with entity types, relationships, and constraints
  • Select graph database based on deployment, scale, and team expertise
  • Build entity extraction pipeline (SpaCy for speed, LLM for quality)
  • Implement relation extraction with confidence scoring
  • Set up entity linking and deduplication across documents
  • Create graph indexes (full-text, vector, composite)
  • Implement GraphRAG pipeline for LLM-powered Q&A
  • Optimize queries with bounded traversals and index usage
  • Plan incremental update strategy for evolving knowledge bases
  • Monitor graph quality (completeness, consistency, freshness)
Show full SKILL.md (206 more words)Show less

When to Use

Use this skill when:

  • Designing or implementing knowledge graph builder solutions
  • Reviewing or improving existing knowledge graph builder approaches
  • Making architectural or implementation decisions about knowledge graph builder
  • Learning knowledge graph builder patterns and best practices
  • Troubleshooting knowledge graph builder-related issues

Do NOT use this skill when:

  • The question is about a fundamentally different technology domain
  • A more specific sibling skill covers the exact topic needed
  • The user needs a complete hands-on tutorial rather than expert guidance

Output Format

markdown
# Knowledge Graph Builder Analysis

## Context Assessment
[Situation summary and constraints]

## Recommended Approach
[Primary recommendation with rationale]

## Implementation Steps
1. [Step with specific details]
2. [Step with specific details]
3. [Step with specific details]

## Trade-offs and Considerations
- [Key trade-off 1]
- [Key trade-off 2]

## Next Steps
- [Immediate action item]
- [Follow-up action item]

Example

Input: "Help me implement knowledge graph builder for a medium-scale production application"

Output: A structured analysis covering current state assessment, recommended knowledge graph builder approach with specific patterns, implementation roadmap with milestones, and risk mitigation strategies tailored to the application scale and constraints.

Edge Cases

  • Legacy system integration: When knowledge graph builder must coexist with legacy approaches, provide a gradual migration path rather than a complete rewrite
  • Scale mismatch: When the solution complexity exceeds the project scale, recommend a simpler approach and note when to revisit
  • Team skill gaps: When the team lacks experience with the recommended approach, include learning resources and simpler alternatives
  • Conflicting requirements: When constraints conflict (e.g., performance vs. maintainability), explicitly state the trade-off and recommend based on stated priorities

© FerroxLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src/process/resources/skills-library/bodies/skills/ai-machine-learning/knowledge-graph-builder of FerroxLabs/wayland.

Open the folder on GitHubat commit 4c030c7

Compare with similar skills

Knowledge Graph Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Knowledge Graph Builder compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Knowledge Graph Builder this skillFerroxLabs/wayland608—~3.4kAutomated safety check: PassApache-2.0
Amazon Neptuneaws/agent-toolkit-for-aws2.8k—~4.7kAutomated safety check: PassApache-2.0
Neo4j Document Import Skillneo4j-contrib/neo4j-skills114—~5.4kAutomated safety check: NotesMIT
Graphiti Guidewentorai/research-plugins2981 repos~2.1kAutomated safety check: PassMIT
Neo4j Driver Python Skillneo4j-contrib/neo4j-skills114—~4.1kAutomated safety check: NotesMIT
Neo4j Graphrag Skillneo4j-contrib/neo4j-skills114—~4.2kAutomated safety check: NotesMIT

Similar skills

  • Amazon Neptune

    aws/agent-toolkit-for-aws

    Official

    Provides authoritative guidance on Amazon Neptune Database and Neptune Analytics for graph, knowledge-graph, and relationship-heavy workloads — fraud detection / fraud rings, agentic memory /…

    2.8k GitHub stars~4.7k tokensUpdated today
    Knowledge ManagementAuto-check passed
  • Neo4j Document Import Skill

    neo4j-contrib/neo4j-skills

    Ingests unstructured and semi-structured documents into Neo4j as a knowledge graph.

    114 GitHub stars~5.4k tokensUpdated today
    Knowledge ManagementAuto-check: notes
  • Graphiti Guide

    wentorai/research-plugins

    Build real-time knowledge graphs for AI agents using Graphiti by Zep

    298 GitHub starsUsed in 1 repo~2.1k tokens
    Knowledge ManagementAuto-check passed
  • Neo4j Driver Python Skill

    neo4j-contrib/neo4j-skills

    Neo4j Python Driver v6 — driver lifecycle, executequery, managed and explicit transactions, async (AsyncGraphDatabase), result handling, data type mapping, error handling, UNWIND batching…

    114 GitHub stars~4.1k tokensUpdated today
    Knowledge ManagementAuto-check: notes
  • Neo4j Graphrag Skill

    neo4j-contrib/neo4j-skills

    Build GraphRAG retrieval pipelines on Neo4j using the neo4j-graphrag Python package (v1.22.0+).

    114 GitHub stars~4.2k tokensUpdated today
    Knowledge ManagementAuto-check: notes
  • Graphify Dotnet

    managedcode/dotnet-skills

    Use graphify-dotnet to generate codebase knowledge graphs, architecture snapshots, and exportable repository maps from .NET or polyglot source trees, with optional AI-enriched semantic relationships.

    486 GitHub stars~1.9k tokensUpdated today
    Knowledge ManagementAuto-check passed

More from FerroxLabs/wayland

All 1,194 skills in this repo
  • Star Office Helper

    FerroxLabs/wayland

    Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.

    608 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check: notes
  • Openclaw Setup

    FerroxLabs/wayland

    OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.

    608 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Tvcontrol Setup

    FerroxLabs/wayland

    Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.

    608 GitHub stars~5.7k tokensUpdated yesterday
    Auto-check passed
  • Ab Testing Specialist

    FerroxLabs/wayland

    End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.

    608 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed
  • Academic Writer

    FerroxLabs/wayland

    Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…

    608 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed
  • Accessibility Auditor

    FerroxLabs/wayland

    Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…

    608 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Knowledge Graph Builder

What does Knowledge Graph Builder do?

Knowledge graph engineering covering ontology design, graph database selection (Neo4j, Amazon Neptune, ArangoDB), entity and relation extraction from text, graph-based RAG (GraphRAG), knowledge…. Knowledge Graph Builder is an agent skill from FerroxLabs/wayland. Knowledge graph engineering covering ontology design, graph database selection (Neo4j, Amazon Neptune, ArangoDB), entity and relation extraction from text, graph-based RAG (GraphRAG), knowledge graph embeddings, graph query optimization, and integration patterns with LLM systems.

When should I use Knowledge Graph Builder?

Knowledge Graph Builder fits situations like: the user asks about knowledge graph builder; knowledge graph builder best practices; needs guidance on knowledge graph builder implementation; the user needs a different specialized skill.

How do I install Knowledge Graph Builder in Claude Code?

Run `npx skills add FerroxLabs/wayland --skill knowledge-graph-builder -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/ai-machine-learning/knowledge-graph-builder in FerroxLabs/wayland) into .claude/skills/knowledge-graph-builder in your project. Claude Code loads it when a task matches its description.

How do I install Knowledge Graph Builder in Codex?

Run `npx skills add FerroxLabs/wayland --skill knowledge-graph-builder -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/ai-machine-learning/knowledge-graph-builder in FerroxLabs/wayland) into .agents/skills/knowledge-graph-builder in your project. Codex loads it when a task matches its description.

Can I use Knowledge Graph Builder in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill knowledge-graph-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/knowledge-graph-builder, .gemini/skills/knowledge-graph-builder, .github/skills/knowledge-graph-builder and .opencode/skills/knowledge-graph-builder in your project.

What does Knowledge Graph Builder need to run?

Going by SKILL.md and its folder, Knowledge Graph Builder needs the command-line tools its instructions call (aws). Our summary lists: Python 3.

Does Knowledge Graph Builder access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Knowledge Graph Builder safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Knowledge Graph Builder use?

Knowledge Graph Builder is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Knowledge Graph Builder use?

About 3.4k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Knowledge Graph Builder?

Skills that share tags, products or a category with Knowledge Graph Builder: Amazon Neptune (aws/agent-toolkit-for-aws, 2.8k stars), Neo4j Document Import Skill (neo4j-contrib/neo4j-skills, 114 stars), Graphiti Guide (wentorai/research-plugins, 298 stars) and Neo4j Driver Python Skill (neo4j-contrib/neo4j-skills, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Knowledge Graph Builder?

FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.

Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.