Help users master professional writing to bridge gaps between stakeholders, scale their leadership influence, and ensure organizational clarity through structured narratives and async-first norms.
npx skills add https://github.com/RefoundAI/lenny-skills --skill written-communication
Scale your influence and drive alignment through structured, clear, and persuasive writing.
Help the user with written communication for leaders using insights from 12 guests and posts across Lenny's Podcast and Newsletter.
Julian Shapiro: "They're forcing functions for me to hold myself accountable and to be thorough when learning something for my own benefit. That's all they are. Basically if I want to go learn growth or writing well or some other topic, I will go ahead and do a ton of research, read everything I can get my hands on, do a ton of experimentation to try to build a set of novel insights that you couldn't find from other people's research hopefully, and then the next stage is try to make it as concise and actionable as possible so that I can reference it for my own selfish benefit."
Use writing as a selfish tool for your own learning to ensure the resulting work is thorough and high quality.
Kevin Yien: "writing is clarity at scale, and a key component to a PM's job is creating clarity both i"
Effective writing is a primary tool for maintaining clarity and alignment across an entire organization simultaneously.
From "The Minto Pyramid Principle and the SCR Framework": "If you simplify this further, there are three parts to every narrative: Situation, Complication, Resolution. 1. Situation: What is the state of affairs today. Facts, data, and unambiguous background. 2. Complication: What has changed that requires action. What is the problem? 3. Resolution: What we need to do to resolve this complication."
Structure business communications around a Situation, Complication, and Resolution to provide necessary context before proposing solutions.
From "Essential reading for product builders—part 2": "The best executive communication starts with the state of affairs. It’s fact-based, unambiguous. It’s totally not controversial. No matter what side of an issue or a hard choice you’re on, you should be able to read the situation and go, ‘That pretty much sums it up.’"
Achieve executive level clarity by starting with a non-controversial set of facts that everyone can agree on before introducing complications.
See references/artifacts.md for the full list with details.
For all 13 sourced insights from 12 guests, see references/guest-insights.md
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
Take refoundai/written-communication from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.