agentleFS
Sign inStart free
yogsoth-aiyogsoth-ai/knowledge-structuring/skills/concept-decomposition/SKILL.md

concept-decomposition

Skill2 starsChanged 6 months agoApache-2.0View on GitHub

Tactic for breaking compound concepts into atomic parts — split over-broad concepts, identify sub-components, create child pages.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Atomic means testable: If you can't write a one-sentence definition, the concept is too broad.

    line 21
  2. Distinctive:

    Stop at utility: Don't decompose below the level where distinctions matter for the research.

    line 23
  3. Distinctive:

    If a concept cannot be meaningfully decomposed, report it as atomic and exit.

    line 29

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

Concept Decomposition

Break compound or over-broad concepts into their atomic constituents. A concept that means too many things should become multiple focused concepts connected by edges.

Available SOPs

  • wiki-search — find existing sub-concepts
  • concept-page-creation — create new atomic concept pages
  • edge-batch-creation — connect parent to children
  • alias-resolution — ensure no naming conflicts

Guiding Principles

  • Atomic means testable. If you can't write a one-sentence definition, the concept is too broad.
  • Preserve the parent. Decomposition creates children; the parent becomes a container (component_of edges).
  • Stop at utility. Don't decompose below the level where distinctions matter for the research.

Minimum Yield

<HARD-GATE> ≥2 child concepts created per decomposition invocation. If a concept cannot be meaningfully decomposed, report it as atomic 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