ontology-building
Skill2 starsChanged 6 months agoApache-2.0View on GitHub
Campaign for building domain ontologies — systematic concept extraction, relation typing, taxonomy construction, and iterative refinement. Produces a structured concept hierarchy in the wiki vault.
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-exportSkill
- ontology-refinementSkill
- question-generationSkill
- rebuttal-documentationSkill
- relation-typingSkill
- seed-concept-searchSkill
- source-gatheringSkill
- strength-assessmentSkill
- strength-scoringSkill
- synthesis-reportSkill
- taxonomy-validationSkill
- validation-reportSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 52
Call context-init at campaign start
- Very specific: line 53
Call context-checkpoint after each strategy completes
- Very specific: line 54
Call knowledge-compilation (wiki-vault tactic) after each strategy </HARD-GATE>
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Ontology Building
Build a structured ontology for a research domain. Extracts concepts from sources, types their relationships, constructs taxonomies, validates consistency, and iteratively refines until the ontology is coherent and complete.
Manifest
| Level | Count | Skills |
| Strategy | 5 | domain-scoping, concept-extraction, relation-typing, taxonomy-validation, ontology-refinement |
| Tactic | 3 | concept-decomposition, hierarchy-construction, consistency-checking |
| SOP | 10 | seed-concept-search, source-gathering, concept-page-creation, alias-resolution, edge-batch-creation, hierarchy-visualization, gap-detection, merge-candidates, confidence-update, ontology-export |
Budget Table
| Metric | Small | Medium | Large |
| Source pages ingested | 10 | 25 | 50 |
| Concept pages created | 15 | 40 | 80 |
| Edges created | 30 | 100 | 200 |
| Taxonomy depth (levels) | 2 | 3 | 4 |
| Validation passes | 1 | 2 | 3 |
Strategy Sequence (Reference, Not Prescription)
- domain-scoping — define boundaries, identify seed concepts, classify topic size
- concept-extraction — mine sources for concepts, create pages, resolve aliases
- relation-typing — identify and type relationships between concepts
- taxonomy-validation — check hierarchy consistency, detect gaps and conflicts
- ontology-refinement — merge near-duplicates, fill gaps, update confidence scores
CC may reorder, skip, or repeat strategies based on the domain's needs.
MCP Tools Used
vault_search— find existing concepts, detect duplicatesvault_add_edge— create typed relationshipsvault_query_graph— explore concept neighborhoodsvault_graph_stats— assess ontology coverage and connectivityvault_lint— validate structural integrityvault_index— maintain search index
Context-Management
<HARD-GATE>
- Call `context-init` at campaign start
- Call `context-checkpoint` after each strategy completes
- Call `knowledge-compilation` (wiki-vault tactic) after each strategy
</HARD-GATE>Guiding Principles
- Breadth before depth. Map the concept landscape broadly before drilling into any sub-area.
- Edges over pages. A concept without relationships is useless. Prioritize connecting over creating.
- Aliases are enemies. The same concept with different names fragments the ontology. Resolve aggressively.
- Confidence is honest. Mark uncertain classifications explicitly. Low confidence is better than false certainty.
- The ontology is never finished. Each research session may reveal new concepts or invalidate old ones.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.