agentleFS
c-ibarrac-ibarra/ObsidianKnowledgeCurator/.agents/skills/knowledge-link/SKILL.md

knowledge-link

Skill0 starsChanged 43 days agoMITView on GitHub

Use this skill when the user wants to find connections between notes, add wikilinks, discover orphaned notes, build a Map of Content (MOC), update a Master Plan, or strengthen the vault link graph. Triggers include "link these notes", "find related notes", "find orphan notes", "build an index", "create a MOC", "update Master Plan".

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the target note and its existing links:

    line 22
  2. Very specific:

    If confirmed, append to the note's ## Related section:

    line 41
  3. Very specific:

    Never include results from dswok in the orphan list.

    line 61
  4. Distinctive:

    Never add links without user confirmation when modifying existing notes

    line 106
  5. Distinctive:

    Always justify each proposed connection

    line 107
  6. Distinctive:

    Do not create wikilinks to non-existent notes

    line 108

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

Knowledge Link Skill

Goal

Identify and create meaningful connections between notes — strengthening the link graph and keeping Master Plans up to date. Uses obsidian CLI for all operations.

Prerequisites

pgrep -x Obsidian > /dev/null && echo "open" || echo "CLOSED"
# Read obsidian-cli skill before operating

⚠️ Never touch: dataScienceKnowledgeBase/dswok

Mode A — Link a specific note to others

  1. Read the target note and its existing links:
obsidian read file="<note name>"
obsidian links file="<note name>"
obsidian backlinks file="<note name>" counts
  1. Extract 3–5 core concepts. Search for each:
obsidian search query="<concept>" limit=5
  1. Propose new links (always state the reason):
Suggested links for [[Target Note]]:
- [[Related Note A]] — same concept: X
- [[Related Note B]] — continuation of idea: Y
  1. If confirmed, append to the note's ## Related section:
obsidian append file="<note name>" content="\n## Related\n- [[Related Note A]]\n- [[Related Note B]]"

Mode B — Find orphan notes

obsidian orphans total    # count first
obsidian orphans          # full list
obsidian deadends         # notes with no backlinks
obsidian unresolved       # broken wikilinks

For each orphan, read and propose connections:

obsidian read file="<orphan name>"
obsidian search query="<core concept from orphan>" limit=5

Never include results from dswok in the orphan list.

Mode C — Create or Update Master Plan

Master Plans are index notes for a series or category. They live at: <RootFolder>/<Category>/Master Plan — <Series>.md

Check if one exists first:

obsidian search query="Master Plan <category>" limit=3

If updating, append the new note entry:

obsidian append file="Master Plan — <Series>" \
  content="\n- [[<Note Name>]] · Type · Date"

If creating, use this structure (no YAML):

# Master Plan — <Series or Category>

> **Series/Category Index**
> Type: master-plan
> Tags: #index

## Description
<2-3 lines describing the series or category>

## Notes

### <Subsection if applicable>
- [[Note 01 — Title]] · video · Month Year
- [[Note 02 — Title]] · article · Month Year

## Related
- [[Master Plan — Related Category]]
obsidian create path="<RootFolder>/<Category>/Master Plan — <Series>.md" \
  content="<above structure>" silent

Constraints

  • Never add links without user confirmation when modifying existing notes
  • Always justify each proposed connection
  • Do not create wikilinks to non-existent notes
  • Never touch dswok
  • Bulk operations (>5 notes): confirm scope first

Examples

"Update the Claude Code Master Plan"

obsidian search query="Master Plan Claude Code" limit=3
obsidian files folder="dataScienceKnowledgeBase/AI Engineer/Claude Code" total
# append new entries to Master Plan

"Do I have orphan notes?"

obsidian orphans total
obsidian deadends
obsidian unresolved

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.