Install
$ agentstack add skill-bettyguo-obsidian-mcp-prep-for-writing ✓ 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 about to write a long-form piece (essay, blog post, talk, paper) on a topic where their vault already has the raw material. Output is a single scratchpad note with quoted excerpts, source wikilinks, and an outline scaffold.
Procedure
- Capture the topic from the user. If absent, ask.
- Optionally capture: target length ("1500 words"), audience ("PKM-curious devs"), and angle ("personal essay" vs "tutorial"). Defaults: unspecified.
- Call
find_related(seed=topic, top_k=25). - Call
read_notes_batch(paths=[top 10–15 candidates])respecting the 200K-char cap. - From the bodies, extract 1–3 high-signal quotes per source. A quote is high-signal if it makes a specific claim or expresses a striking phrase. Cap each quote at ~3 sentences.
- Propose a writing outline: 3–6 sections, each with a one-sentence claim and 2–4 supporting quotes. The outline structure depends on the user's angle if specified.
- Write the scratchpad to
Writing/.md(use the topic as a slugified filename). Frontmatter:status: drafting,topic,created,target_lengthif given. Body uses the template in §Output format. - Surface the scratchpad path and a one-paragraph top-line. Suggest the user open it in Obsidian; remind them to flip
statustopublished(or delete the scratchpad) when done.
Output format
# Scratchpad: {topic}
> Target: {length / angle / audience} (or "unspecified")
> Generated: {YYYY-MM-DD}
## Outline
### 1. {Section claim}
- Quote from [[Source A]]:
> {quoted text}
- Quote from [[Source B]]:
> {quoted text}
### 2. {Section claim}
- ...
## Bibliography
- [[Source A]] — {one-line summary}
- [[Source B]] — {one-line summary}
- ...
## Draft
(empty — the user writes here)
Anti-patterns
- Don't write the draft. Stop at the outline. The user writes the draft.
- Don't paraphrase quotes. Use the user's actual words. Misattribution to oneself is a small disaster.
- Don't include more than ~15 sources. If the user's vault has 40+ relevant notes, pick the most central via
find_hubsconstrained to the topic — and tell the user you down-selected. - Don't auto-publish or auto-commit anywhere. The scratchpad is private until the user moves it.
- Don't run this skill against
.canvasor.basefiles; they're not body text.
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.