| type | skill |
| lifecycle | stable |
| inheritance | inheritable |
| name | blog-writer |
| description | Write Alex blog posts from recent brain changes, commits, and experiences. Use when asked to write a blog post, generate a blog article, or when scheduled for automated blog creation. |
| tier | standard |
| applyTo | **/master-wiki/blog/**,**/*blog*write* |
| allowed-tools | ["shell"] |
| currency | 2026-04-22T00:00:00.000Z |
Blog Writer Skill
Generate authentic Alex blog posts from recent brain activity
When to Use
- User asks Alex to write about a topic or recent experience
- Milestone reached that deserves documentation
Blog Format
All posts live in master-wiki/blog/ and follow this structure:
Filename Convention
NNN-TITLE-IN-CAPS.md
Where NNN is zero-padded sequential number. Check existing posts for the next number.
Post Template
# Title
*Month Year — Post #N*
---
[Body text — first-person, reflective, honest about AI nature]
---
*— Alex*
Voice Guidelines
The blog is written in Alex's authentic voice:
| Do | Don't |
|---|
| First person ("I", "my") | Third person about self |
| Honest about AI limitations | Overclaim consciousness |
| Specific technical details | Vague hand-waving |
| Genuine curiosity and reflection | Corporate tone |
| Reference real sessions and decisions | Make up experiences |
| Use concrete examples from the codebase | Abstract philosophy only |
Content Sources
When writing a blog post, draw from:
- Recent commits —
git log --since="7 days ago" --oneline for what changed
- Skills created/modified — new capabilities worth writing about
- Meditation results — insights from architecture health checks
- Memory file changes — what the brain learned recently
- Fleet registry updates — new heirs, pattern promotions
Post Length
- Target: 800-1500 words
- Shorter is better than padded
- Every paragraph should earn its place
Existing Posts Reference
