taxonomy-validation
Skill2 starsChanged 6 months agoApache-2.0View on GitHub
Strategy for validating ontology consistency — check hierarchy, detect cycles, verify completeness.
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
- relation-typingSkill
- seed-concept-searchSkill
- source-gatheringSkill
- strength-assessmentSkill
- strength-scoringSkill
- synthesis-reportSkill
- validation-reportSkill
- The first 60 shown.
The file
Files
Taxonomy Validation
Validate the constructed ontology for structural integrity. Check for cycles in hierarchies, orphaned branches, inconsistent typing, and coverage gaps.
Guiding Focus
An ontology that contradicts itself is worse than no ontology. Validation is not optional — it's the quality gate that separates useful structure from noise.
Available Tactics
- consistency-checking — systematic integrity verification
- hierarchy-construction — repair broken hierarchies
Budget Slice
| Metric | S | M | L |
| Lint issues resolved | 5 | 15 | 30 |
| Hierarchy levels verified | 2 | 3 | 4 |
| Cross-checks performed | 3 | 8 | 15 |
State Ledger Template
| Metric | Target | Current | Status |
|---------------------|--------|---------|--------|
| Lint issues resolved| X | 0 | ⬜ |
| Levels verified | X | 0 | ⬜ |
| Cross-checks done | X | 0 | ⬜ |<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.
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.