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.
npx skills add hardiktiwari/PM-operating-OS --skill writing-clearlygit clone --depth 1 https://github.com/hardiktiwari/PM-operating-OSWrote 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.
[](https://agentmods.dev/skills/hardiktiwari/pm-operating-os/writing-clearly)<a href="https://agentmods.dev/skills/hardiktiwari/pm-operating-os/writing-clearly"><img src="https://agentmods.dev/badge/skills/hardiktiwari/pm-operating-os/writing-clearly/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.
<a href="https://agentmods.dev/skills/hardiktiwari/pm-operating-os/writing-clearly"><img src="https://agentmods.dev/badge/skills/hardiktiwari/pm-operating-os/writing-clearly.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00032 | $0.00600 |
| Opus 5 | $0.00016 | $0.00300 |
| Sonnet 5 | $0.00006 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
writing-clearly 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Clearly
Help PMs write clear, concise prose for PM artifacts. Applies principles of plain language, structure, and scannability to make communications effective and easy to act on.
When to Use
- Writing or editing a PRD
- Drafting status updates or stakeholder comms
- Composing Slack posts or emails
- Creating documentation or runbooks
- When asked "help me make this clearer" or "tighten this up"
Process / Template
1. Identify the Artifact and Audience
- What are you writing? (PRD, update, post, doc)
- Who will read it? (engineers, leadership, customers)
- What do they need to do? (decide, build, understand, act)
2. Apply Clear Writing Principles
Lead with the main point
- Put the conclusion or ask first
- Don't bury the lead in the last paragraph
Use plain language
- Prefer short words over long (use vs. utilize, help vs. facilitate)
- Prefer active voice (we will ship vs. it will be shipped)
- Cut jargon unless the audience expects it
Be specific
- Use numbers, dates, names instead of "soon," "many," "several"
- Replace vague terms with concrete ones
Structure for scannability
- Use headers, bullets, and short paragraphs
- One idea per paragraph
- Front-load key info in each sentence
Cut ruthlessly
- Remove filler (e.g., "in order to" → "to")
- Remove redundancy
- If a sentence doesn't add value, cut it
3. Use the Right Format
| Artifact | Key Moves |
|---|---|
| PRD | Clear problem statement, explicit requirements, scannable sections |
| Status update | TL;DR first, bullets, metrics, explicit asks |
| Slack/email | Short paragraphs, one ask per message |
| Doc/runbook | Step-by-step, headers, examples |
4. Edit in Passes
- Pass 1 — Structure: does the order make sense?
- Pass 2 — Clarity: can a reader understand it in one pass?
- Pass 3 — Brevity: what can be cut?
5. Validate
- Can the reader answer: What? Why? What do I do?
- Would a busy executive get it in 2 minutes?
- Are there ambiguous pronouns or missing context?
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.
- 12d ago First seen · 79 lines · 32 tokens per session scan A 7d0cc31aa2ca
writing-clearly is a skill published in the GitHub repository hardiktiwari/PM-operating-OS (5 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 600 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
bcc-throughline
BCC global progress cockpit (plans.md/progress.md/findings.md). Slash: /bcc-throughline · chat: bcc:throughline · "where are we" · reprioritize · resume after /clear. Not for coding or full PLAN grill.
handoff
Guides the Claude Code agent through completing a task, selecting a handoff tier, building a valid completion-card, and performing a clean task handoff.
req-create
Create structured requirement documents from user ideas. Use when capturing new features, tasks, or user stories.
execute-plan
Implement a written plan (from write-plan or interview-plan) when the user says execute or implement it. Loads the plan, executes ready tasks in waves in the ticket venue, runs the plan's review gate itself. Do not use while still interviewing or writing the plan.
generate-stories
Translate a single Epic into clear, actionable User Stories with explicit acceptance criteria. Activate when an Epic is defined and work needs to be prepared for Delivery execution.
review-input
Adversarial review of any input (human idea, agent analysis, research report, feedback, observation) BEFORE it mutates persistent project state. Universal interceptor with domain auto-detection, 2-phase classification + evaluation, and triple-verdict output (veracity / fit / actionability). Anti-girouette guardrail…