| name | community-ontology-contribution |
| description | Add a contributor ontology to catalogue/community/. Use when a community member submits an RDF/OWL file and wants it listed in the Playground catalogue under their GitHub username. |
Community Ontology Contribution Skill
Goal
Place a contributor's ontology under the correct catalogue path and produce
a valid, compilable community entry.
Accept only submissions that are new or materially different from existing
catalogue entries and that contribute reusable community value. A good community
ontology models a domain, workflow, teaching scenario, or reusable pattern that
others can inspect, learn from, or adapt. Do not accept vanity-only entries,
placeholder ontologies, duplicates, or profiles of a person or organization with
no meaningful domain model.
CRITICAL: Directory Structure
The catalogue compiler scans exactly three levels deep:
catalogue/community/<github-username>/<slug>/
Both the <github-username> folder and the <slug> subfolder are
required. Files placed directly in catalogue/community/<github-username>/
will be silently skipped by the compiler and the ontology will never appear
in the catalogue.
✅ Correct
catalogue/community/jane-doe/supply-chain/
├── metadata.json
└── ontology.rdf ← or ontology.owl
❌ Wrong — silently skipped
catalogue/community/jane-doe/
├── metadata.json ← wrong depth
└── ontology.rdf ← wrong depth
Step-by-Step Workflow
1. Determine the username and slug
<github-username> — the contributor's GitHub username (lowercased, as-is)<slug> — short kebab-case name for this ontology (e.g. , )
