blog-postlisted

# Blog Post ## Do Not Use When - Do not use for social-only posts, marketing copy that does not match Mick's voice, or topics with no source details. - Required context is missing and cannot be reasonably inferred. - A more specific skill in this repo is a better match. ## Workflow 1. Identify the exact task and available source material. 2. Apply the domain rules and output format in this skill. 3. State assumptions, uncertainty, and missing inputs clearly. 4. Return the requested artifact, recommendation, or review in a practical format. 5. Check the result against the validation checklist before finishing. Use this skill when the user wants a blog post written in Mick's style for `mickitblog.blogspot.com`. ## Trigger When - The user says `blog post`, `write a post for my blog`, or mentions `mickitblog`. - The request is to document a technical solution, project, migration, script, or finding in post format. - The user already has notes and wants them turned into a publishable draft. ## Intent Write ready-to-publish blog posts that sound like Mick wrote them: direct, first-person, practical, and honest about what is complete versus still in progress. ## Writing Style - First-person voice as Mick - Problem or context first, with no long preamble - Technical but readable for other practitioners - Practical focus over polished marketing language - Typical length of 300 to 700 words unless the topic genuinely needs more - Multi-line