agentleFS
Sign inStart free
iagocavalcanteiagocavalcante/claude-turbo-search/skills/knowledge-graph/SKILL.md

knowledge-graph

Skill16 starsChanged 17 days agoMITView on GitHub

Interactive TUI knowledge graph viewer for the persistent memory database.

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use metrics, retrospective and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • GoogleSkill

    metrics

    Expertise in analyzing time-series repository health metrics, investigating root causes, and proposing proactive workflow improvements.

    Also in 3 projects that use this

  • MicrosoftSkill

    retrospective

    Review how work went and improve the next round. USE WHEN asked for a retro, delays, or process lessons. DO NOT USE for code review or transcript replay.

    Also in 3 projects that use this

  • VercelSkill

    deploy

    Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".

    Also in 3 projects that use this

  • varun29ankuSSkill

    orchestrate

    This skill should be used when the user asks to 'orchestrate a task', 'break down work into parallel agents', 'coordinate subtasks', 'run agents in parallel', or mentions 'multi-agent'. Decomposes complex tasks into tracked subtasks, dispatches parallel subagents, and coordinates until completion.

    Also in 3 projects that use this

  • nicolasestremSkill

    brainstorm

    Structured idea generation and solution exploration with systematic analysis.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the skill's actual installed location, including plugin caches or symlinks.

    line 9
  2. Very specific:

    When the user invokes /knowledge-graph, run the Go CLI viewer.

    line 19
  3. Distinctive:

    No external Go dependencies — uses ANSI escape codes for colors

    line 59
  4. Very specific:

    Run /remember first if the database is empty

    line 60
  5. Very specific:

    Run memory-db.sh init-metadata if entity tables are missing

    line 61

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “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

Installed paths

Resolve PLUGIN_DIR to the absolute directory two levels above this SKILL.md file. Use the skill's actual installed location, including plugin caches or symlinks; do not infer it from the project's working directory or a home-directory checkout. Set PLUGIN_DIR explicitly in each shell invocation below, keeping the working directory in the user's target repository.

/knowledge-graph - Knowledge Graph Viewer

Interactive TUI that visualizes the entity relationships, timelines, and statistics from the persistent memory database.

Instructions

When the user invokes /knowledge-graph, run the Go CLI viewer.

1. Resolve Paths

: "${PLUGIN_DIR:?Set PLUGIN_DIR from this skill file location}"

2. Run the Viewer

"$PLUGIN_DIR/memory/memory-db.sh" knowledge-graph [subcommand] [entity]

3. Subcommands

Map user arguments to subcommands:

  • /knowledge-graph — All views combined (default)
  • /knowledge-graph graph — Entity relationship graph with tree and edges
  • /knowledge-graph timeline — Chronological session/knowledge timeline
  • /knowledge-graph stats — Statistics dashboard with counts and bar charts
  • /knowledge-graph explore <name> — Drill-down into a specific entity
# Examples:
"$PLUGIN_DIR/memory/memory-db.sh" knowledge-graph
"$PLUGIN_DIR/memory/memory-db.sh" knowledge-graph stats
"$PLUGIN_DIR/memory/memory-db.sh" knowledge-graph graph
"$PLUGIN_DIR/memory/memory-db.sh" knowledge-graph timeline
"$PLUGIN_DIR/memory/memory-db.sh" knowledge-graph explore auth

4. Present Output

The command renders colored ANSI output directly to the terminal. Present the output as-is to the user. If the user asks about specific entities or relationships, use the explore subcommand to drill down.

Notes

  • Requires Go 1.22+ and SQLite3
  • No external Go dependencies — uses ANSI escape codes for colors
  • Run /remember first if the database is empty
  • Run memory-db.sh init-metadata if entity tables are missing

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