write-tech-blog-post
Writes or revises a technical blog post or article for a defined reader, using a focused claim, verified examples, and an intentional authorial voice.
Synopsis
User-invoked. Name this skill when you want the agent to apply it. disable-model-invocation is true.
Source file: skills/write-tech-blog-post/SKILL.md.
Front matter
- name
write-tech-blog-post- description
- Writes or revises a technical blog post or article for a defined reader, using a focused claim, verified examples, and an intentional authorial voice.
- disable-model-invocation
true
Full contents
---
name: write-tech-blog-post
description: Writes or revises a technical blog post or article for a defined reader, using a focused claim, verified examples, and an intentional authorial voice.
disable-model-invocation: true
---
# Write a technical blog post
Read [write-tech-core](../write-tech-core/SKILL.md) first.
An article earns attention by giving one reader a useful way to think, not by
covering a topic.
## Find the article
State these privately before drafting:
- Reader and what they know.
- The gap in their understanding.
- One claim the article will support.
- Evidence for that claim.
- Related material to leave out.
If the material contains a struggle, bug, surprising result, or changed
opinion, use it. Do not turn a narrow discovery into a comprehensive survey.
Explain only the background this reader needs.
Every factual paragraph must use the evidence ledger. "Comprehensive" changes
the requested scope, not the available facts. Derive the lesson from the given
causal chain without imagining components, mechanisms, or recommendations.
## Accuracy gate
Before returning, check each concrete noun. Remove any component, event, user,
metric, mechanism, or scenario absent from the evidence ledger. Direct
deductions may connect facts but may not add how the system works.
Red flags include "typically," "usually," "most teams," and invented examples.
Each signals a claim that needs evidence.
### Closed-facts mode
For a short fact set with no sources, produce only:
1. a title;
2. an opening that states the supplied event and result;
3. a short causal reading of those same facts;
4. a conclusion that lands the supplied claim.
Reuse supplied nouns. Do not add background, examples, components, code,
advice, or hypothetical cases.
## Shape
Use this sequence without mandatory headings:
1. Open on the concrete problem, result, or tension.
2. Give only the context needed to understand the claim.
3. Walk through the evidence and causal chain. Use a real, minimal example.
4. State what the finding changes: a decision, mental model, or practice.
5. End when the claim lands.
Each section must move the argument. Cut a paragraph if removing it changes
nothing.
## Voice and truth
Use first person for firsthand experience and judgment. State uncertainty
where it matters. Do not invent motives, scale, failure modes, implementation,
or general advice. Keep code executable and small.
## Example
Weak opening:
```text
Caching is an important technique used throughout modern software systems.
This article explores negative caching and best practices.
```
Focused opening:
```text
We cached "customer not found" for five minutes. When that customer was
created during the window, reads still returned 404. The cache had made
absence into stale state.
```
Return the article only. Do not add SEO metadata, promotion copy, or a generic
"key takeaways" section unless requested.