This is Sentry's internal blog writing standard packaged as a skill, and it's one of the most opinionated style guides I've seen. It enforces their engineering blog voice with banned phrase lists (no "seamless," no "thrilled to announce"), structural rules (problem or conclusion first, never background), and specific formatting like breaking paragraphs at contrast points. The SEO section is solid, teaching the lead-generic-close-specific pattern that actually works for developer content. Most useful if you're writing for a technical audience and want to avoid corporate blog voice or AI slop patterns. Even if you're not at Sentry, the "what would a senior engineer share in Slack" bar is a good filter.
npx skills add https://github.com/getsentry/skills --skill blog-writing-guide