agentleFS
Sign inStart free
yogsoth-aiyogsoth-ai/knowledge-structuring/skills/domain-scoping/SKILL.md

domain-scoping

Skill2 starsChanged 6 months agoApache-2.0View on GitHub

Strategy for defining ontology boundaries — identify seed concepts, classify topic size, establish scope constraints.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After budget gate passes, ask:

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Domain Scoping

Define the boundaries of the ontology. What's in scope, what's out, what are the seed concepts that anchor the domain.

Guiding Focus

Establish clear boundaries before extraction begins. An unbounded ontology grows without purpose. Seed concepts define the center of gravity; scope constraints define the edges.

Available Tactics

  • concept-decomposition — break broad domains into tractable sub-areas
  • hierarchy-construction — establish initial top-level categories

Budget Slice

MetricSML
Seed concepts identified51020
Scope boundaries defined358
Source pages surveyed51530

State Ledger Template

| Metric              | Target | Current | Status |
|---------------------|--------|---------|--------|
| Seed concepts       | X      | 0       | ⬜     |
| Scope boundaries    | X      | 0       | ⬜     |
| Sources surveyed    | X      | 0       | ⬜     |
<HARD-GATE> Cannot exit until 80% of budget met. Print state ledger before each iteration decision. </HARD-GATE>

Adversarial Completeness Probe

After budget gate passes, ask:

  • Are there obvious sub-domains I haven't considered?
  • Would an expert in this field agree with my scope boundaries?
  • Are my seed concepts truly central, or peripheral?

Max 2 extra iterations if gaps found.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free