rtg-schema-design
Skill9 starsChanged 4 months agoApache-2.0View on GitHub
Design or evolve language-neutral RTG graph schemas from user and system needs. Use when choosing anchors, associated data, links, required properties, type keys, migration boundaries, or compatibility rules; when reviewing an RTG schema for clarity and extensibility; or before making consequential schema changes to a live RTG graph.
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Read schema-design.md before authoring or approving a schema.
- Distinctive: line 40
Stop when the schema is sufficient for correct storage, linking, querying, extension, and black-box validation.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
RTG Schema Design
Turn domain meaning into the smallest precise RTG schema that supports identity, typed facts, relationships, queries, and safe evolution. Preserve partial knowledge and implementation freedom.
Read schema-design.md before authoring or approving a schema.
Workflow
- Elicit the questions, decisions, and ordinary requests the graph must support.
- Inspect the existing schema and representative live data when evolving a graph.
- Identify independently addressable things as anchors, coherent typed facts as associated data, and meaningful navigable relationships as links.
- Define stable type keys, property kinds, required fields, deliberate field refinements, and allowed link endpoints.
- Walk through incomplete, duplicate, evolving, and query scenarios. Remove requirements that would force agents to invent facts.
- Explain the proposed semantics and compatibility impact. Obtain human approval before a consequential live-schema change.
- Stage and validate the migration, inspect findings, cut over atomically, then validate live data and representative queries.
Output Standard
Produce a reviewable schema proposal containing:
- the user outcomes and queries it supports;
- anchor, associated-data, and link definitions with rationale;
- exact property kinds, optionality, justified refinements, and link endpoint sets;
- identity, naming, and duplicate-handling rules;
- compatibility and migration effects on existing data;
- validation and acceptance scenarios;
- intentional freedoms and deferred specializations.
Stop when the schema is sufficient for correct storage, linking, querying, extension, and black-box validation. Do not model agent prompts, private implementation structure, or speculative domain detail as schema.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- component-authoringSkill
- documentation-syncSkill
- model-hygiene-reviewSkill
- python-component-implementationSkill
- rtg-knowledge-graph-mcpSkill
- sysml-referenceSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.