From myvault-content
This skill should be used before creating content to clarify WHAT to write, for WHOM, and WHY. It guides exploring content goals, audiences, angles, and messaging decisions before drafting. Triggers on "let's brainstorm content", "help me think through", "what should we write about", "explore angles", vague content requests, or when multiple valid approaches need clarification.
How this skill is triggered — by the user, by Claude, or both
Slash command
/myvault-content:content-brainstormingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides detailed process knowledge for effective content brainstorming sessions that clarify **WHAT** to create before diving into **HOW** to write it.
This skill provides detailed process knowledge for effective content brainstorming sessions that clarify WHAT to create before diving into HOW to write it.
Content brainstorming is valuable when:
Content brainstorming can be skipped when:
Before diving into questions, assess whether brainstorming is needed.
Signals that requirements are clear:
Signals that brainstorming is needed:
If requirements are clear, suggest: "Your brief seems clear. Consider proceeding directly to /myvault:write with this guidance."
Ask questions one at a time to understand the user's content goals. Avoid overwhelming with multiple questions.
Question Techniques:
Prefer multiple choice when natural options exist
Start broad, then narrow
Validate assumptions explicitly
Ask about success criteria early
Key Topics to Explore:
| Topic | Example Questions |
|---|---|
| Goal | What's the purpose? Why create this now? |
| Audience | Who's this for? What's their current state? |
| Content Type | Blog post, newsletter, social, website copy, help docs? |
| Message | What's the ONE thing they should remember? |
| Transformation | What changes for them? (Before → After) |
| Action | What should they do after reading? |
| Constraints | Any brand rules? Products to mention/avoid? |
| Existing Assets | Can we build on existing research or content? |
Exit Condition: Continue until the intent is clear OR user says "proceed" or "let's move on"
After understanding the intent, propose 2-3 concrete content angles. Present them creatively—the goal is to help the user see different approaches, not to force a template.
What to Explore:
How to Present Angles:
Brand Voice Guardrails:
Create a brief that captures the key decisions without prescribing exact structure. The brief should be clear, concise, and useful for writing—not a rigid template.
What to Capture:
How to Capture It:
Output Location: docs/content-briefs/YYYY-MM-DD-<topic>-brief.md
Example frontmatter (flexible, not required):
---
date: YYYY-MM-DD
topic: password-security-families
content-type: blog
audience: families
---
Present clear options for what to do next:
/myvault:research [topic]/myvault:write [based on this brief]During brainstorming, actively enforce MyVault standards:
MyVault is a tool, not a personality.
| Never | Always |
|---|---|
| "I found 12 duplicates" | "MyVault found 12 duplicates" |
| "I'm here to help!" | Cut entirely |
| "I organized your photos" | "Your photos are organized" |
Build confidence, not fear.
| Fear-Based (Never) | Confidence-Based (Always) |
|---|---|
| "Protect yourself from hackers" | "Your photos stay private" |
| "Don't let big tech spy on you" | "We can't see your photos" |
| "Before it's too late" | "Always secure" |
Keep sections short—200-300 words maximum. After each section of output, pause to validate understanding:
This prevents wasted effort on misaligned content direction.
| Anti-Pattern | Better Approach |
|---|---|
| Asking 5 questions at once | Ask one at a time |
| Jumping to writing | Stay focused on WHAT to say, not HOW to say it |
| Proposing fear-based angles | Always confidence-based messaging |
| Ignoring existing brand voice | Load brand-kit skill for voice guardrails |
| Making assumptions about audience | State assumptions explicitly and confirm |
| Creating lengthy briefs | Keep it concise—details go in the draft |
| Using banned words in examples | Follow style guide strictly |
Brainstorming answers WHAT to create:
Writing answers HOW to create it:
When content brief exists, /myvault:write should detect it and use it as input, skipping its own planning phase.
When research is needed, enforce source quality:
| Tier | Description | Use For |
|---|---|---|
| A | Peer-reviewed, large sample, recent | Key claims |
| B | Reputable organization, good methodology | Key claims |
| C | Industry report, smaller sample | Supporting details |
| D | Single source, unverified, old | Flag clearly |
Rule: Tier A/B for key claims. Never single-source without flagging.
Private by design. Intelligent by nature.
npx claudepluginhub markiianb/myvault-content-plugin --plugin myvault-contentCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.