agentleFS
Sign inStart free
yogsoth-aiyogsoth-ai/knowledge-structuring/skills/hierarchy-construction/SKILL.md

hierarchy-construction

Skill2 starsChanged 6 months agoApache-2.0View on GitHub

Tactic for building is-a and part-of hierarchies — establish parent-child relationships, verify transitivity, detect cycles.

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:

    If the hierarchy is already complete for the current scope, report and exit.

    line 30

≈ “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

Hierarchy Construction

Build taxonomic hierarchies using component_of and instance_of edges. Ensure hierarchies are acyclic, transitive, and complete.

Available SOPs

  • edge-batch-creation — create hierarchy edges in bulk
  • hierarchy-visualization — inspect current hierarchy structure
  • gap-detection — find missing intermediate levels
  • consistency-checking (tactic, peer) — verify no cycles

Guiding Principles

  • Acyclic always. A cycle in a hierarchy is a logical error. Detect and break immediately.
  • Intermediate levels matter. Jumping from "machine learning" directly to "Adam optimizer" skips useful structure.
  • Multiple inheritance is fine. A concept can belong to multiple parents (component_of multiple things).
  • Depth ≤ 5. Hierarchies deeper than 5 levels are usually over-specified.

Minimum Yield

<HARD-GATE> ≥3 hierarchy edges created per invocation. If the hierarchy is already complete for the current scope, report and exit. </HARD-GATE>

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