communication-writing

communication-writing is a skill for Claude Code, Codex from NickPolyder/NP.CoPilot.Config. It costs 28 tokens per session (1,281 once invoked), scanned A, original, MIT.

A writing aid for drafting or revising emails, workplace messages, public posts, articles, and discussion replies.

In plain words
What is it for?
Use it to prepare communication for teams, customers, social audiences, article readers, or participants in issue and pull-request discussions.
Why use it?
It helps organise writing around the reader, with clear openings and claims supported by evidence.

Skill for Claude CodeCodex

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

Good fit Use it to prepare communication for teams, customers, social audiences, article readers, or participants in issue and pull-request discussions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nickpolyder/np.copilot.config/communication-writing
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 NickPolyder/NP.CoPilot.Config --skill communication-writing
Clone the repo
git clone --depth 1 https://github.com/NickPolyder/NP.CoPilot.Config

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 communication-writing

README.md
[![agentmods](https://agentmods.dev/badge/skills/nickpolyder/np.copilot.config/communication-writing/github.svg)](https://agentmods.dev/skills/nickpolyder/np.copilot.config/communication-writing)
Your own site
<a href="https://agentmods.dev/skills/nickpolyder/np.copilot.config/communication-writing"><img src="https://agentmods.dev/badge/skills/nickpolyder/np.copilot.config/communication-writing/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 communication-writing

Your own site · 80×15
<a href="https://agentmods.dev/skills/nickpolyder/np.copilot.config/communication-writing"><img src="https://agentmods.dev/badge/skills/nickpolyder/np.copilot.config/communication-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,281 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.00028 $0.01281
Opus 5.5 $0.00011 $0.00512
Sonnet 5.5 $0.00006 $0.00256
Haiku 4.5 $0.00003 $0.00128

Measured 1mo ago against content hash f2f0d7e8a219, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

communication-writing 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 1mo 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/communication-writing/SKILL.md · 195 lines

How it starts

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

Communication Writing

Use this atomic skill when drafting or revising content for another person or audience, including:

  • Email.
  • Workplace messages and posts, including Teams, Slack, and internal announcements.
  • Threaded discussions and replies, including Azure DevOps work item comments, pull request discussions, and issue comments.
  • Public or social posts.
  • Articles and other long-form editorial writing.

Do not apply it mechanically to ordinary CLI chat answers, code, commit messages, or technical documentation unless the user is explicitly drafting one of the communication types above.

Return the requested draft or edit the user-selected artifact. Do not send or publish it without authorization. Small drafts stay inline; substantial authorized editing may use implementer with a writing-focused assignment.

Start With the Reader

Before writing, identify:

  1. Who is receiving this?
  2. Why does it matter to them?
  3. What should they understand, decide, or do?

Write for the reader's context, not the sender's sequence of discovery.

Use the Adaptive Reader Journey

Order the message around the questions that occur naturally in the reader's mind:

  1. What: What is this about?
  2. Why: Why am I receiving this, and why does it matter to me?
  3. Consequence: What changes or goes wrong if nothing is done?
  4. Reinforcement: What evidence, observation, or context makes this credible?
  5. Action: What should happen next, by whom, and when?

Adapt the structure to the message:

  • Combine stages when one clear sentence can do the work.
  • Omit consequence when there is no meaningful downside to state.
  • Omit reinforcement when the message does not depend on evidence.
  • For informational articles, action may be a takeaway, recommendation, or next step rather than a direct call to action.
  • Never add filler merely to make all five stages visible.

Pass the Six-Second Skim Test

The opening should let a scanning reader understand the subject and its relevance in about six seconds.

Read the full file on GitHub · 195 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. 1mo ago First seen · 195 lines · 28 tokens per session scan A f2f0d7e8a219

Subscribe to this mod's changes

communication-writing is a skill published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 1,281 once invoked, about $0.0001 per session on Opus 5.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-19.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens