domains / families / marketing / blog-writing-guide

blog-writing-guide

combined

Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions "blog post," "blog draft," "write-up," "announcement post," "engineering post," "deep dive," "postmortem," or asks for help with technical writing for Sentry. Even if the user just says "help me write about [feature/topic]" — if it sounds like it could become a Sentry blog post, use this 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.

When to use

• You need to draft or edit a Sentry blog post.
• The task involves technical storytelling, product announcements, or engineering deep-dives in Sentry's blog voice.
• You want blog content that is opinionated, specific, and technically credible rather than generic marketing copy.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The two copies share the same core Sentry voice, banned language, opening, and structure rules, but each contains material sections the other lacks. The getsentry copy adds detailed formatting-for-skimmability rules (paragraph breaks at contrast points, no em dashes) and an SEO-for-developer-content section (lead generic close specific, keywords in H2s, definitional section, FAQ). The sickn33 copy adds a When-to-Use section, Section Headings Must Convey Information, Technical Quality Standards (numbers over adjectives, code must work, diagrams, honesty over hype), Title Guidelines, The Closing, and a Post Types table. Because crowning one copy would hide real alternative guidance, the correct decision is combine.