agentleFS
Sign inStart free
yogsoth-aiyogsoth-ai/knowledge-structuring/skills/mechanism-edge-creation/SKILL.md

mechanism-edge-creation

Skill2 starsChanged 6 months agoApache-2.0View on GitHub

SOP for creating a causal mechanism edge — documents how one variable causes changes in another.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Create an edge representing a causal mechanism between two variables.

    line 10
  2. Distinctive:

    Verify both variable pages exist

    line 18
  3. Distinctive:

    Call vault_add_edge with appropriate weight (strength of mechanism)

    line 20
  4. Distinctive:

    Document mechanism description in the source variable's page body

    line 21
  5. Very specific:

    Inline wikilink: Ensure the source page contains [[dir/slug]] pointing to the target (dir/slug = target path minus .md).

    line 22
  6. Distinctive:

    Every causal edge must have a stated mechanism (HOW does X cause Y).

    line 27

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

Mechanism Edge Creation

Create an edge representing a causal mechanism between two variables.

Tool

vault_add_edge

Protocol

  1. Verify both variable pages exist
  2. Determine edge type: derived_from (direct causation), component_of (mediating variable)
  3. Call vault_add_edge with appropriate weight (strength of mechanism)
  4. Document mechanism description in the source variable's page body
  5. Inline wikilink: Ensure the source page contains [[dir/slug]] pointing to the target (dir/slug = target path minus .md). Place inline where the mechanism is documented. If already present, skip.

HARD-GATE

<HARD-GATE> Every causal edge must have a stated mechanism (HOW does X cause Y). Weight must reflect mechanism strength: 1.0=strong, 0.5=moderate, 0.2=weak. </HARD-GATE>

Yield

Returns: { success: boolean, mechanism: string, weight: number }

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