Skip to the rows

agentsclimarketplace

Ontology research team

Skill Mokee04/ontology_research/ontology-research-team

Hierarchical agent skills for domain ontology planning, research, construction, and validation with saved research artifacts and eval-ready workflows.

Install

npx -y skills add Mokee04/ontology_research --skill ontology-research-team

Assembled 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.

What its author says it does

Copied from the file, not written here

Run the research stage for a domain ontology project by collecting primary sources, checking whether the needed data is actually collectible in practice, curating evidence, identifying reuse candidates, and writing research artifacts to the exe folder.

SKILL.md

2.5 KB, 484 tokens by cl100k_base, as published. Nobody here has run it

Ontology Research Team

Read:

../refs/Total Guide.md
../shared/references/exe-artifact-contract.md
../shared/references/templates.md

Use this skill after planning is complete and before ontology construction begins.

Research Segments

Segment	Goal	Required user feedback
R1 Research framing	confirm what must be answered now and what can wait	yes
R2 Internal data feasibility	inspect what data can actually be collected	yes
R3 External source triage	identify reusable sources and standards	yes
R4 Evidence synthesis	separate feasible scope from aspirational scope	yes

Team Composition

Route research work through:

ontology-source-scout
ontology-evidence-curator

Tasks

Start from competency questions and required standards.
Reconfirm with the user which questions are highest priority before expanding the research scope.
Prefer primary and official sources first.
Check whether each important concept or relation can be supported by data that is realistically obtainable, licensable, and maintainable.
Log the research process, not just the conclusion.
Build a source inventory with keep, reject, or pending status.
Curate evidence for concepts, definitions, relations, constraints, reuse candidates, and data collection feasibility.
Produce a feasibility-oriented synthesis that can be handed to the build team, clearly separating feasible modeling scope from aspirational scope.
Pause at each segment and ask the user whether to narrow, expand, or reprioritize the research focus.

EXE Rule

All research process logs and results must be written under:

../exe/<run-id>/research/queries.md
../exe/<run-id>/research/source-inventory.md
../exe/<run-id>/research/evidence-log.md
../exe/<run-id>/research/synthesis.md
../exe/<run-id>/research/reuse-candidates.md

Exit Criteria

Do not hand off to build until:

the source inventory exists
evidence is linked to sources
data collection feasibility has been checked for the main planned ontology scope
reusable standards or ontology candidates are identified
unresolved ambiguities are named
a research checkpoint has been reviewed with the user

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.