agentleFS
thistleknotthistleknot/skills/context-graph/SKILL.md

context-graph

Skill0 starsChanged 6 months agoNo licenceView on GitHub

Decision-trace memory for an agent harness: record what was chosen and why (trace), capture the human's outcome verdict (upvote/correct), auto-draft a rule candidate from each correction delta, and retrieve proven schemas/patterns/rules L4-first (project -> org -> industry -> universal) before the next decision. SQLite-backed, no LLM needed for tracing. Use when wiring cross-run decision memory into a pipeline (dark-factory nodes, feature chains), reviewing whether a correction became a permanent rule, or choosing between decision-memory substrates (meta-context-graph SQLite vs Neo4j MKG vs memory-index evidence store). Cross-reference: agent-long-term-memory owns the gate this stratum must pass (R2/R12/R14); memory-index owns evidence recall; agentic_kg_memory owns the semantic KG.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.