Install
$ agentstack add skill-bettyguo-obsidian-mcp-find-orphans ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
When to use
The user is curating their vault — usually after a burst of capture — and wants to know which atomic notes never got linked into anything. Often paired with /build-MOC.
Procedure
- Parse the user's request. If they named a topic (e.g. "near RAG"), capture it as
topic. If not, ask for one (or default to "the whole vault" if the user explicitly says "all orphans"). - Call
find_orphans(near_topic=topic, min_word_count=50, limit=20). Iftopicis None, omitnear_topicand just return the top 20 by recency. - If zero orphans returned, congratulate the user and stop.
- Group orphans into buckets of ≤5 by detected primary tag (use the tag list returned in each orphan record).
- For each bucket, surface a short list in chat:
- Bucket title (the primary tag, or "Untagged")
- Each orphan: path + 1-line summary (from the first non-frontmatter paragraph)
- Ask the user which orphans they want to integrate.
- For each chosen orphan, call
find_related(seed=orphan_path, top_k=5)to find the best candidate parent(s). Surface the top 1–2. - Propose link inserts. The user confirms each.
- Apply via
link_notes(..., confirm=true).
Output format
Found {N} orphans near "{topic}":
#research/rag
- [[Chunking by structure]] — {1-line summary}
- [[Embedding-aware preprocessing]] — {1-line summary}
#evals
- [[Long-tail recall benchmark]] — {1-line summary}
Which would you like to integrate? (e.g. "the first two", "all in #research/rag")
Anti-patterns
- Don't auto-link orphans without per-orphan confirmation. The user knows which truly belong somewhere.
- Don't propose linking an orphan to an existing MOC unless the MOC's topic actually matches. Better to suggest the orphan join the MOC via
/build-MOClater. - Don't recommend deletion. Ever. Orphans are often the most valuable seedlings.
- Don't run
find_orphanswithmin_word_countbelow 50 by default — stubs aren't orphans, they're TODOs.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: bettyguo
- Source: bettyguo/obsidian_mcp
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.