Agent skill · Documentation

vaultr-writing

Write an article beat-by-beat, drawing from the vault's knowledge base. The user states what to write, who it's for, and what stance to take — the skill discovers relevant knowledge units and leads a choose-your-own-adventure writing journey. Use when the user wants to write something grounded in their accumulated understanding, not assemble raw notes.

skoowoogithub.com/skoowooGitHub ↗
claude-codeApache-2.0
Install
npx skills add skoowoo/vaultr-notes --skill vaultr-writing --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Path: skills/vaultr-writing/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 74
Language: Go

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

<what-to-do> ## Phase 0 — Topic alignment Ask the user for three things (can be in one message): 1. **What** — the topic or question the article addresses 2. **Who** — the intended reader (their background, what they already know) 3. **Stance** — the position or argument the article will take If the user didn't say where to save the article, ask now. Remember the path. Once you have those three, scan the knowledge base: ```bash vaultr knowledge --help vaultr knowledge list-indexes ``` Select 1–3 domain indexes most relevant to the topic. Read those index files to find matching units. If no indexes exist, scan `_knowledge/` directly. **Present the palette for confirmation.** Do not proceed to Phase 1 until the user signs off. Format it like this: --- **Sources found** | # | Knowledge unit | What it contributes | | --- | -------------- | ---------------------------------------------------- | | 1 | `unit-name` | one sentence on what this unit brings to the article | | 2 | … | … | **Possible gaps:** list anything you think the article needs that the knowledge base doesn't cover (if any). > That's everything I found. Does this palette cover what you need, or should we add more? If somet

What's inside
Steps it walks through
  1. Phase 0 — Topic alignment
  2. Phase 1 — Starting beats
  3. Phase 2 — Beat-by-beat writing
  4. Phase 3 — Close
  5. What is a beat
  6. Writing one beat
  7. Handling knowledge gaps
  8. Ending the journey
  9. Writing rhythm
  10. The knowledge-writing loop
Ships with 1 file
  • references/extract.md
Commands it runs
vaultr knowledge --help
vaultr knowledge list-indexes
More from vaultr-notes
All skills →
About this skill
What does the vaultr-writing skill do?

Write an article beat-by-beat, drawing from the vault's knowledge base. The user states what to write, who it's for, and what stance to take — the skill discovers relevant knowledge units and leads a choose-your-own-adventure writing journey. Use when the user wants to write something grounded in their accumulated understanding, not assemble raw notes.

How do I install it?

Run `npx skills add skoowoo/vaultr-notes --skill vaultr-writing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From skoowoo/vaultr-notes, a repository with 74 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going