agentleFS
yogsoth-aiyogsoth-ai/knowledge-structuring/skills/ontology-export/SKILL.md

ontology-export

Skill2 starsChanged 6 months agoApache-2.0View on GitHub

SOP for exporting ontology summary — generate a readable overview of the current ontology state.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Call vault_graph_stats for global metrics

    line 18
  2. Very specific:

    Write to topics/ontology-summary.md or return as structured data

    line 26

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

Ontology Export

Generate a readable summary of the current ontology state for review or external consumption.

Tool

vault_graph_stats + vault_query_graph + CC file write

Protocol

  1. Call vault_graph_stats for global metrics
  2. Query top-level concepts (depth 2) to build hierarchy overview
  3. Generate summary document with:
    • Total concepts, edges, coverage metrics
    • Top-level taxonomy tree
    • Edge type distribution
    • Orphan list
    • Confidence distribution
  4. Write to topics/ontology-summary.md or return as structured data

HARD-GATE

<HARD-GATE> Export must include quantitative metrics (counts) and qualitative structure (hierarchy). </HARD-GATE>

Yield

Returns: { total_concepts: number, total_edges: number, hierarchy_depth: number, export_path: string }

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.