Blog Writing Guide

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.

skills.sh installs: 3.4K
GitHub stars: 1.1K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add getsentry/skills --skill blog-writing-guide --agent claude-code

Installs into .claude/skills of the current project.

Files

Sentry Blog Writing Skill

This skill enforces Sentry's blog writing standards across every post — whether you're helping an engineer write their first blog post or a marketer draft a product announcement.

The bar: Every Sentry blog post should be something a senior engineer would share in their team's Slack, or reference in a technical decision.

What follows are the core principles to internalize and apply to every piece of content.

The Sentry Voice

We sound like: A senior developer at a conference afterparty explaining something they're genuinely excited about — smart, specific, a little irreverent, deeply knowledgeable.

We don't sound like: A corporate blog, a press release, a sales deck, or an AI-generated summary.

Be technically precise, opinionated, and direct. Humor is welcome but should serve the content, not replace it. Sarcasm works. One good joke per post is plenty.

Use "we" (Sentry) and "you" (the reader). This is a conversation, not a paper.