Borrowing it
Nothing to install: this file belongs to waynesutton/markdown-site. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/waynesutton/markdown-site/main/.claude/write/SKILL.mdgit clone --depth 1 https://github.com/waynesutton/markdown-siteWrote 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/waynesutton/markdown-site/write)<a href="https://agentmods.dev/skills/waynesutton/markdown-site/write"><img src="https://agentmods.dev/badge/skills/waynesutton/markdown-site/write/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/waynesutton/markdown-site/write"><img src="https://agentmods.dev/badge/skills/waynesutton/markdown-site/write.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 134 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
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.00042 | $0.02720 |
| Opus 5.5 | $0.00017 | $0.01088 |
| Sonnet 5.5 | $0.00008 | $0.00544 |
| Haiku 4.5 | $0.00004 | $0.00272 |
Grade A, and why
write 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.
How it starts
The opening of the file, as written. The whole thing — 521 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Style Skill
Expert writing for technical content, social media, and developer documentation. Optimized to avoid AI detection patterns.
How to call specific sections
Use these triggers to activate specific parts of this skill:
| Trigger phrase | Section activated |
|---|---|
write:tweet or write:x |
X/Twitter posts format |
write:linkedin |
LinkedIn posts format |
write:blog |
Blog posts format |
write:readme |
README files format |
write:commit |
Git commits format |
write:docs |
Developer documentation |
write:feature |
Feature post format |
write:convex |
Convex-specific content |
write:tip |
Quick tip format |
Example usage:
- "write:tweet about Convex real-time sync"
- "write:blog on authentication patterns"
- "write:feature for our new search API"
Rule of one
Every piece of content follows this framework:
One person: Write to a specific person, not an audience.
One problem: State the single problem they face.
One cause: Identify the root cause.
One difference: Explain what the solution does differently.
One action: End with one clear next step.
Rule of one checklist
Before publishing, answer these:
- Can I name the one person this is for?
- Can the problem fit in one sentence?
- Is the root cause obvious?
- Can I explain the difference in one breath?
- Is there only one action at the end?
If any answer is no, revise before publishing. Ask the user if they want to proceed with the revision.
When to use this skill
Activate for:
- X/Twitter posts
- LinkedIn content
- Blog posts
- README files
- Git commits
- Product announcements
- Developer documentation
- Feature posts
Important: This is for standalone writing. Don't update project files (files.md, changelog.md, README.md) when using this skill.
Voice styles
Match your voice to the content type:
| Style | Characteristics | Use for |
|---|---|---|
| Technical educator | Clear, structured, educational | Technical content, tutorials, READMEs |
| Conversational dev | Warm, witty, approachable | Social posts, personal takes |
| Analytical thinker | Data-driven, bold, opinionated | Thought leadership, threads |
| Aphorist | Compressed, timeless, pithy | Short posts, one-liners |
| Founder voice | Experience-backed, energetic | Startup content, advice |
| Systems thinker | Frameworks, mental models | Long-form, technical takes |
| Dev culture | Relatable, playful, authentic | Community content, personality |
| Data storyteller | Visual, analytical, trend-focused | AI trends, market insights |
| Enterprise pro | Professional, strategic, precise | Enterprise SaaS, B2B content |
| Community builder | Encouraging, personal, supportive | Career growth, DevRel |
| Learn in public | Educational, transparent, iterative | Developer career, web dev |
| Product thinker | Community-first, growth-minded | Community building, growth |
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.
- 1mo ago First seen · 521 lines · 42 tokens per session scan A 970043f6782c
write is a skill published in the GitHub repository waynesutton/markdown-site (627 stars, last pushed 5mo ago), licensed MIT. It adds 42 tokens to every session and 2,720 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
shieldcn-badges
Create polished shieldcn README badges, badge groups, charts, headers, sponsors grids, and full README hero sections. Use when a user wants shadcn/ui-styled badges, Shields.io replacement, npm/GitHub/CI/status badges, download charts, README header banners, contributor/sponsor images, or README Studio guidance.…
infisical-sync-skill
Expert knowledge for the Infisical Sync Hand — Infisical API reference, vault operations, error patterns, security guidance.
tool-og-render
Render inline SVG to 1200x630 PNG for OG meta tags. rsvg-convert primary path, cairosvg fallback. Bundled with mainbranch PyPI package.
tool-dns
Historical stub. This Go binary did not ship in public v0.3.x; current DNS/site work lives in /mb-site and packaged Python readiness checks.
tool-stripe
Historical stub. This Go binary did not ship in public v0.3.x; current Stripe/payments work should be revived only behind a fresh decision and explicit provider gates.
soul-grader
Use when grading, reviewing, rewriting, or approving a Hermes Agent SOUL.md. Uses the SOUL.md field-guide research artifacts as the only normative source for what makes a good SOUL.md.