What problem does it solve? Technical blog posts lose credibility with skeptical developer readers when they contain unsupported claims, marketing voice, missing methodology, or no stated limitations. This Skill drafts or edits engineering blog posts so every assertion is measured, shown, sourced, or marked as opinion before publication. ## Core Features & Use Cases - Pattern selection: Matches raw material to one of eight post patterns (Bug Hunt, Rewrote It in X, How We Built It, Benchmarks and Test Results, Lessons Learned, Thoughts on Trends, Non-markety Product Perspectives, Explainer) ranked by effort, value, and compliance cost. - Claim ledger and credibility gate: Classifies every assertion into four evidence classes and blocks handoff until six checks pass, including benchmark disclosure, honest limitations, and pinned code snippets. - Draft and edit modes: Drafts new posts from raw material, or returns a three-tier fix list (blocking, strong, optional) for existing drafts without rewriting the author's voice. - Use Case: Turn internal incident notes into a public postmortem: the Skill runs a redaction pass on names and ticket IDs, selects the Bug Hunt pattern, and produces a post with dead ends, root cause, and a generalizable lesson. ## Quick Start Ask the assistant to turn your incident notes, migration numbers, or design doc into an engineering blog post, or to review an existing technical draft for unsupported claims before publishing.
