agentleFS
JackywineJackywine/jackywine-digital-garden-skills/skills/related-notes/SKILL.md

related-notes

Skill9 starsChanged 10 days agoMITView on GitHub

Use when the user shares today's idea, thought, or note and wants related notes from the vault (相关笔记); or asks what in the library connects to what they just said. Search flomo (if connected) and Obsidian for related notes with reasons and links—do not only restate what they wrote.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    When the owner shares a fresh idea, thought, or note (today or "just now"), surface related notes already in the library—not a rewrite of …

    line 11
  2. Distinctive:

    Do not invent relatedness.

    line 17
  3. Very specific:

    Prefer read-only search. Do not add [[wikilinks]] or rewrite their notes unless they explicitly ask to link.

    line 23
  4. Very specific:

    Prefer notes they wrote over pure Clippings/ unless the clip is clearly on-topic.

    line 38
  5. Distinctive:

    Search flomo (L1): when connected — same themes.

    line 39
  6. Distinctive:

    If zero hits: 「库里没找到靠谱相关笔记;要不要把这条先记进 flomo?」

    line 58
  7. Distinctive:

    Do not dump a long unread list.

    line 62
  8. Distinctive:

    Do not restate their whole note as the "related" item.

    line 63
  9. Distinctive:

    Do not batch-edit the vault under this skill.

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

相关笔记 (related notes)

When the owner shares a fresh idea, thought, or note (today or "just now"), surface related notes already in the library—not a rewrite of what they said.

When to run

  • They dump a thought and ask what connects, or say 「相关笔记」 / related notes.
  • A morning or evening prompt: remind them to share today's idea; after they answer, run this skill.
  • Do not invent relatedness. If nothing solid, say so in one line.

Privacy & gates

  • Skip mood / anxiety / voice-diary privacy memos: never search, cite, or link them.
  • Lived-experience gate: do not pad with made-up personal history.
  • Prefer read-only search. Do not add [[wikilinks]] or rewrite their notes unless they explicitly ask to link.

Inputs

  1. Their plain-language idea (required).
  2. Optional: date window, folder, or tag to narrow.
  3. Vault path + machine from memory / onboarding; flomo via official MCP when available.

Steps

  1. Normalize the seed — extract 3–8 keywords / entities / themes (topics, tools, people, projects). Drop filler.
  2. Search Obsidian (disk) — use vault search / CLI / file search on the owner's machine:
    • title + body match on keywords
    • existing [[wikilinks]] and backlinks around hits
    • tags / properties if present
    • Prefer notes they wrote over pure Clippings/ unless the clip is clearly on-topic.
  3. Search flomo (L1) when connected — same themes; skip privacy-tagged / mood notes.
  4. Rank — pick at most 5 strong hits (fewer is fine). Score by: shared concepts, reciprocal links, recency only as a tie-break.
  5. Reply — short lead line, then one bullet per hit:
    • note title as clickable obsidian://open?vault=VAULT_NAME&file=relative/path (spaces %20), or flomo note link if that is the source
    • one sentence why it relates (specific overlap, not "also about notes")
    • optional: 1–2 existing [[wikilink]] neighbors if they strengthen the cluster
  6. Offer next step (one line, wait): add a wikilink between seed and hit; clip today's idea into flomo with #Grokbot/Import; or deepen one hit. Do nothing until they pick.

Output shape

和「…」可能相关的笔记:

- [Title](obsidian://…) — 理由:…
- …

要我帮你加双链 / 写进 flomo / 展开其中一条吗?

If zero hits: 「库里没找到靠谱相关笔记;要不要把这条先记进 flomo?」

Anti-patterns

  • Do not dump a long unread list.
  • Do not restate their whole note as the "related" item.
  • Do not batch-edit the vault under this skill.

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.