30
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill lyndonkl/claude --skill communication-storytelling- SKILL.md12.0 KB
Overview
This skill transforms complex analysis, data, or technical information into clear, persuasive narratives tailored to specific stakeholders. It produces a one-sentence headline, 3–5 logical key points, concrete evidence for each point, and a concise call-to-action to drive understanding and decisions. Use it whenever information must become a story that informs, persuades, or prompts action.
How this skill works
I inspect the input material (data, analysis, findings, or feature lists) and the target audience (expertise, concerns, time constraints, and decision power). Then I choose an appropriate narrative structure (e.g., Problem-Solution-Benefit, Before-After-Bridge, Situation-Complication-Resolution), craft a headline, arrange 3–5 key points with supporting proof, and finish with a clear call-to-action. I validate clarity against audience needs and flag gaps, assumptions, or missing evidence.
When to use it
- Present technical analysis to non-technical stakeholders or executives who need quick decisions
- Write customer-facing emails, product announcements, or investor updates from internal data
- Announce organizational changes, crisis responses, or high-stakes recommendations
- Turn research, A/B test results, or postmortems into actionable insights
- Whenever the user says: “write this for…”, “explain to…”, “present findings”, or “make this compelling”
Best practices
- Start with the lede: a one-sentence headline that captures the core message
- Limit one key number or idea per point; humanize data with examples or anecdotes
- Match tone and jargon to the audience and front-load conclusions for executives
- Show sources and assumptions for major claims and acknowledge limitations
- Use a clear, time-bound call-to-action that states what the audience should do next
Example use cases
- Convert Q2 metrics and qualitative feedback into a 3-slide executive summary with recommendation
- Explain a technical architecture change to a product marketing team in plain language
- Draft an investor update that highlights traction, risks, and the funding ask
- Write a customer-facing product launch announcement that contrasts before/after value
- Turn a postmortem into a lessons-learned narrative with concrete remediation steps
FAQ
Choose based on goal: Decision = Problem-Solution-Benefit, Change or launch = Before-After-Bridge, Executive summary = Situation-Complication-Resolution, Major transformation = Hero’s Journey.
How much data should I include?
Include only data that directly supports your key points. One clear number per point is ideal; link to appendices for full datasets.