relation-typing
Skill2 starsChanged 6 months agoApache-2.0View on GitHub
Strategy for identifying and typing relationships between concepts — create edges with appropriate types and weights.
In this repository70 other files it gives its agents.
- alias-resolutionSkill
- argument-mappingSkill
- argument-synthesisSkill
- argument-visualizationSkill
- axis-extractionSkill
- axis-validationSkill
- causal-chain-querySkill
- causal-modelingSkill
- claim-decompositionSkill
- claim-extractionSkill
- claim-page-creationSkill
- combination-enumerationSkill
- combination-mappingSkill
- concept-decompositionSkill
- concept-extractionSkill
- concept-page-creationSkill
- confidence-scoringSkill
- confidence-updateSkill
- consistency-checkingSkill
- contradiction-flaggingSkill
- counterfactual-reasoningSkill
- dimensional-analysisSkill
- dimension-discoverySkill
- dimension-page-creationSkill
- domain-scopingSkill
- edge-batch-creationSkill
- evidence-attachmentSkill
- evidence-collectionSkill
- evidence-linking-argSkill
- evidence-linkingSkill
- evidence-weighingSkill
- feedback-loop-detectionSkill
- gap-detectionSkill
- gap-prioritizationSkill
- hierarchy-constructionSkill
- hierarchy-visualizationSkill
- intervention-analysisSkill
- intervention-page-creationSkill
- knowledge-compilationSkill
- loop-documentationSkill
- matrix-exportSkill
- matrix-generationSkill
- mechanism-edge-creationSkill
- mechanism-mappingSkill
- merge-candidatesSkill
- model-gap-detectionSkill
- model-validationSkill
- novelty-scoringSkill
- ontology-buildingSkill
- ontology-exportSkill
- ontology-refinementSkill
- question-generationSkill
- rebuttal-documentationSkill
- seed-concept-searchSkill
- source-gatheringSkill
- strength-assessmentSkill
- strength-scoringSkill
- synthesis-reportSkill
- taxonomy-validationSkill
- validation-reportSkill
- The first 60 shown.
The file
Files
Relation Typing
Identify relationships between extracted concepts and type them using the edge type vocabulary. Every concept should connect to at least 2 others.
Guiding Focus
Relationships are more important than concepts in an ontology. Focus on making the graph dense and meaningful. Choose edge types carefully — a wrong type is worse than a missing edge.
Available Tactics
- hierarchy-construction — build is-a and part-of hierarchies
- consistency-checking — verify no contradictory edges
Budget Slice
| Metric | S | M | L |
| Edges created | 20 | 60 | 150 |
| Edge types used | 4 | 6 | 8 |
| Orphans remaining | <3 | <5 | <8 |
State Ledger Template
| Metric | Target | Current | Status |
|---------------------|--------|---------|--------|
| Edges created | X | 0 | ⬜ |
| Edge types used | X | 0 | ⬜ |
| Orphans remaining | <X | ? | ⬜ |<HARD-GATE>
Cannot exit until 80% of budget met. Print state ledger before each iteration decision.
</HARD-GATE>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.