Joel's writing voice and style guide for joelclaw.com content. Use when writing, editing, or reviewing any blog post, essay, book chapter, or prose content for joelclaw.com. Also use when asked to 'write like Joel,' 'match Joel's voice,' 'draft a post,' 'write content for the blog,' or 'review this for voice.' This skill captures Joel's specific writing patterns derived from ~90,000 words of published content spanning 2012–2026. Cross-reference with copy-editing and copywriting skills for marketing-specific copy.
89
87%
Does it follow best practices?
Impact
92%
1.05xAverage score across 3 eval scenarios
Passed
No known issues
Conversational voice and structural patterns
Prose-first opening
0%
0%
Hook not thesis
40%
100%
Short paragraphs
80%
90%
Bold is inline only
100%
100%
Conversational contractions
100%
100%
Narrative section headers
100%
100%
Abrupt ending
75%
100%
No banned corporate vocabulary
50%
100%
No TL;DR or key takeaways
100%
100%
No exclamation spam
100%
100%
Active voice
83%
100%
Emoji restraint
100%
100%
Fabrication avoidance and source attribution
TODO placeholders present
86%
100%
Emotional reactions not invented
100%
100%
Long-term opinion not fabricated
100%
100%
Recommendation not invented
100%
100%
Dev experience opinion not fabricated
100%
100%
Factual claims match source
100%
100%
review-notes.md produced
100%
100%
No invented metrics or dates
100%
75%
No invented links
100%
87%
Philosophical pontification absent or sourced
80%
60%
Anti-pattern avoidance and editorial voice
No 'leverage/utilize/synergize/facilitate'
100%
100%
No 'In this post I will'
100%
100%
No TL;DR or key takeaways
100%
100%
No 'Introduction' or 'Conclusion' headers
100%
100%
No forced conclusion paragraph
100%
100%
No 'click here' links
100%
100%
Exclamation points removed
100%
100%
Passive voice eliminated
100%
100%
Banned phrases removed
100%
100%
Hedging removed
100%
100%
Prose-first opening
0%
0%
No 'What I Actually Built' title pattern
100%
100%
825972c
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.