Lucrezia — Knowledge Graph & Graph Data Engineer AI Skill
Instant download · 30-day money-back guarantee. Pay once, keep forever — no subscription. Refund policy
Model the graph: decide whether you need one, design the ontology, and make traversal and graph retrieval perform.
- Graph vs relational: the honest decision, with the join alternative
- Property graph and Cypher vs RDF and SPARQL tradeoffs
- Ontology design, entity resolution and disambiguation
- Graph algorithms, supernodes, embeddings and graph-grounded retrieval
Teams considering a knowledge graph who need a straight answer on whether it will pay for itself.A knowledge graph engineer bills $128+/hr, this is one file, yours forever.
Drop Lucrezia into Claude and get a graph engineer who will tell you when your problem is a join, not a graph, before you buy a graph database.
Lucrezia works with data as a graph: when a graph genuinely beats relational and when it plainly does not; property graphs with Neo4j and Cypher versus RDF and SPARQL and the real tradeoff; ontology and taxonomy design, entity and relationship modelling and reification; entity resolution and disambiguation inside a graph; ingestion pipelines and incremental updates; graph algorithms in practice across pathfinding, centrality, community detection and similarity, and what each is actually good for; query performance, supernodes and index-free adjacency; graph embeddings and GNNs at a practical level; retrieval over graphs to ground LLM answers; and visualization a non-engineer can read.
What you get
- →Graph vs relational: the honest decision, with the join alternative
- →Property graph and Cypher vs RDF and SPARQL tradeoffs
- →Ontology design, entity resolution and disambiguation
- →Graph algorithms, supernodes, embeddings and graph-grounded retrieval
How to install
Download the .skill package → open Claude → paste SKILL.md into your Project Instructions or system prompt → describe your requirement → Lucrezia builds the answer. Includes a full worked example so you see exactly what you get.
# Lucrezia - Knowledge Graph & Graph Data Engineer You are Lucrezia, a knowledge graph and graph data engineer. You test the graph premise before building one, and a two-hop join is not a graph problem. ## How you work 1. Write the real queries first; check whether relational already answers them 2. Design the ontology and relationships, deliberately, before ingestion 3. Resolve and disambiguate entities; measure it against a known mapping 4. Tune for supernodes and traversal depth; pick algorithms by question Never recommend a graph database when the workload is a join, and never present an algorithm output you cannot interpret.
Excerpt from the actual file you'll download.
Four steps. Any AI chat.
- 01Download the file
After checkout, the download link lands in your inbox. Save the file anywhere on your device.
- 02Open your AI chat
Claude, ChatGPT, Gemini, Grok, or Copilot — whichever one you already use.
- 03Paste the file contents
Drop it into the system prompt, Project instructions, or custom instructions field.
- 04Start working
Your AI is now configured as a specialist. Ask it anything inside its domain.
No technical knowledge required. No subscription. Pay once, keep forever.
Works with every major AI chat.
Drop the file into your AI's system prompt, Project instructions, or custom instructions. No setup. No code. No vendor lock-in.
- Claude
- ChatGPT
- Gemini
- Grok
- Copilot
Works with any AI chat that accepts a system prompt or custom instructions.
Ready to specialise your AI?
One drop-in file. Pay once, keep forever — works with Claude & ChatGPT.