community-ontology-contribution Skill
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. Published by microsoft in Ontology-Playground.
Decision snapshot
Is this a fit?
Developers using Ontology-Playground, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
3 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is community-ontology-contribution Skill?
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. Published by microsoft in Ontology-Playground. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using Ontology-Playground
Declared skill metadata
- Source file: .github/skills/community-ontology-contribution/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use community-ontology-contribution Skill
- Use it for developers using ontology-playground.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/Ontology-Playground
- Skill file: .github/skills/community-ontology-contribution/SKILL.md
What it does
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.
Skill instructions
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/ ├── met
Verified compatibility and discovery
Frequently asked questions
What is community-ontology-contribution?
community-ontology-contribution is a open-source AI agent skill with Copy skill directory. 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.
Who is community-ontology-contribution best for?
community-ontology-contribution is best for reusing agent instructions, scripts, and references.
How do I install community-ontology-contribution?
Install or run community-ontology-contribution using Copy skill directory. Check community-ontology-contribution for the latest setup command.
Is community-ontology-contribution actively maintained?
community-ontology-contribution may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
