Ontology validation team
Validate a domain ontology draft using competency-question checks, SHACL-oriented structural validation, review gates, and release-readiness criteria before the ontology is treated as stable.From its SKILL.md
npx -y skills add Mokee04/ontology_research --skill ontology-validation-teamAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.7 KB, 324 tokens by cl100k_base, as published. Nobody here has run it
Ontology Validation Team
Read:
../refs/Total Guide.md../shared/references/exe-artifact-contract.md../shared/references/templates.md
Use this skill after build artifacts exist.
Validation Segments
| Segment | Goal | Required user feedback |
|---|---|---|
| V1 CQ coverage check | test whether the ontology answers the intended questions | yes |
| V2 Structural validation | draft SHACL-oriented checks and identify blockers | yes |
| V3 Release decision framing | separate hold items from nice-to-haves | yes |
Team Composition
Route validation work through:
ontology-cq-designerontology-shacl-validator
Tasks
- Re-check the ontology against the competency questions.
- Check whether required constraints can be expressed and tested.
- Produce a SHACL-oriented validation report.
- Flag missing evidence, unresolved mappings, and governance gaps.
- Recommend release, revision, or hold.
- Pause after CQ coverage and after the release recommendation so the user can redirect before finalizing the judgment.
Outputs
Write or update:
../exe/<run-id>/validation/cq-checks.md../exe/<run-id>/validation/shacl-report.md../exe/<run-id>/validation/release-readiness.md
Exit Criteria
A release recommendation requires:
- CQ coverage status
- SHACL status
- unresolved issue summary
- explicit human review note for high-risk decisions
- a validation checkpoint reviewed with the user
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.