agentsclimarketplace

Ontology domain intake

Skill Mokee04/ontology_research/ontology-domain-intake

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-domain-intake

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

Clarify the target domain for ontology work by defining scope, users, constraints, out-of-scope areas, and approval points before modeling starts.

SKILL.md

1.5 KB, 304 tokens by cl100k_base, as published. Nobody here has run it

Ontology Domain Intake

Read:

  • ../refs/Total Guide.md
  • ../shared/references/templates.md

Use this worker skill to produce a clean scope and constraint statement.

Tasks

  1. Begin with discovery questions if the user has not yet specified intended use, users, available data, and constraints.
  2. Ask the domain intake question set below before drafting scope.
  3. Name the domain and intended use.
  4. Separate in-scope from out-of-scope.
  5. Identify intended users, downstream systems, and data sensitivity.
  6. Note required standards, regulations, or internal constraints.
  7. Mark where human approval is required.

Domain Intake Question Set

Ask explicitly about:

  1. The operational use case or service to support
  2. The core entities or axes that define the domain
  3. The data currently collected for each core entity
  4. The most important decisions or workflows to improve
  5. The boundaries of the first version
  6. Sensitive or regulated data elements
  7. Any required internal terminology or external standards

Output

Write or refine:

  • ../exe/<run-id>/planning/scope.md
  • ../exe/<run-id>/planning/risks.md

Guardrails

  • do not let scope remain open-ended
  • do not draft scope from the domain label alone when the intended use is still unclear
  • do not hide unresolved ambiguity
  • do not treat approval-sensitive constraints as optional

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.