Learned

Skill slogsdon/skills-vault-knowledge/skills/learned

Turn a vault insight or pattern into polished written content — blog draft, LinkedIn post, newsletter section. Use when /learned is invoked, when the user says "write this up", "turn this into a post", "I want to publish about X", or when a /weekly-learnings session surfaces a publishable thread. Do NOT use for raw note-taking (use /log) or for ghost-writing in someone else's voice (use /ghost).From its SKILL.md

Install

npx -y skills add slogsdon/skills-vault-knowledge --skill learned

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 371 tokens by cl100k_base, as published. Nobody here has run it

Skill: /learned [argument]

Transform vault insights into a polished written piece — blog post, essay, or reflection — in Shane's voice, grounded in specific vault material, not a bullet dump.

Don't: produce a bullet list of insights — write narrative prose. Don't start with the most recent note — lead with the most surprising or hard-won insight.

Steps

Parse the argument/topic from Shane's request.
Follow Qwen Protocol with:
- task: "Vault access (bash only, no MCP tools): obsidian search query='TERM' limit=10, obsidian read file='Note Name' (no .md). Transform Shane's vault insights about '[argument]' into a polished written piece — a blog post, essay, or reflection. Use his authentic voice."
- skill: "learned"
Review Qwen's result, synthesize if needed, and present to Shane.

Fallback

If Qwen is unavailable:

Run obsidian search query='[argument]' limit=10 via bash to find notes related to the topic
Read the top 5–10 most relevant notes by running obsidian read file='[note name]' via bash for each
Extract key insights, observations, and recurring ideas from those notes
Transform them into a polished written piece in Shane's voice:
- Use first-person, direct prose (not listicles unless the content demands it)
- Lead with the most surprising or hard-won insight
- Build a narrative arc: what changed, what was learned, why it matters
- End with an open question or implication
Present the piece to Shane

What ships with it

Read from the repository