written-communication

written-communication is a skill for Claude Code, Codex from liqiongyu/lenny_skills_plus. It costs 21 tokens per session (1,926 once invoked), scanned A, original, Apache-2.0.

A method for turning rough notes into clear written communication, such as an email, memo, project update, or shared reference document. It makes the next actions, owners, and deadlines explicit.

In plain words
What is it for?
Use it to draft stakeholder emails, write concise memos, clarify project updates, or maintain a central project document.
Why use it?
It removes ambiguity from internal communication and helps teams find one reliable version of important information. It also makes long or messy documents easier to scan.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to draft stakeholder emails, write concise memos, clarify project updates, or maintain a central project document.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/liqiongyu/lenny_skills_plus/written-communication
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add liqiongyu/lenny_skills_plus --skill written-communication
Clone the repo
git clone --depth 1 https://github.com/liqiongyu/lenny_skills_plus

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for written-communication

README.md
[![agentmods](https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/written-communication/github.svg)](https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/written-communication)
Your own site
<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/written-communication"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/written-communication/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for written-communication

Your own site · 80×15
<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/written-communication"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/written-communication.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,926 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.01926
Opus 5 $0.00010 $0.00963
Sonnet 5 $0.00004 $0.00385
Haiku 4.5 $0.00002 $0.00193

Measured 9d ago against content hash c6a181f5f641, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

written-communication scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/written-communication/SKILL.md · 132 lines

How it starts

The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Written Communication

Scope

Covers

  • Turning messy notes into a clear email, memo, doc, or async update
  • Making the “how” explicit (what happens next, by whom, by when)
  • Editing for clarity at scale (scanability, definitions, single source of truth)
  • Creating/maintaining a canonical doc for an ongoing project

When to use

  • “Draft an email to stakeholders explaining a change and what I need from them.”
  • “Turn these bullets into a 1-page memo with a recommendation and next steps.”
  • “Rewrite this doc to be clearer, shorter, and more actionable.”
  • “Create a canonical doc as the source of truth for this project.”

When NOT to use

  • You need marketing/brand copy (landing pages, ads) more than internal/executive clarity.
  • You need a full product spec/PRD from scratch (use writing-prds or writing-specs-designs).
  • You need a presentation deck, slide outline, or talk track (use giving-presentations; this skill produces written documents, not spoken-word deliverables).
  • You need a stakeholder alignment campaign with pre-briefs and decision meetings (use stakeholder-alignment; a memo may be one artifact within that campaign).
  • You need to craft communications specifically to manage your relationship with your manager (use managing-up; different framing and tactics apply).
  • You’re writing legal/HR/regulated communications without expert review.
  • The real issue is alignment via facilitation (you may need a meeting/offsite plan, not a rewrite).

Inputs

Minimum required

  • Artifact type + channel (email / memo / doc / status update; where it will live)
  • Audience (roles/seniority) + what they care about
  • Goal + ask (inform/align/decide; what you want the reader to do, by when)
  • Key context (facts, constraints, timeline, links) + what must be avoided (sensitivities)
  • Source material (notes, existing draft, Slack threads, etc.)

Missing-info strategy

  • Ask up to 5 questions from references/INTAKE.md (3–5 at a time), then proceed.
  • If critical info remains missing, make explicit assumptions and offer 2–3 options (structure/tone/ask).

Read the full file on GitHub · 132 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 132 lines · 21 tokens per session scan A c6a181f5f641

Subscribe to this mod's changes

written-communication is a skill published in the GitHub repository liqiongyu/lenny_skills_plus (52 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 1,926 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.