skills sourced live from GitHub · all skills listed are free · each skill is provided under its author's license.
home / Writing / Blog Writing Guide Skill by @sickn33
The skill is the skills/blog-writing-guide folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.
This skill enforces Sentry's blog writing standards across every post — whether you're helping an engineer write your first blog post or a marketer draft a product…
Applies Sentry's blog writing standards, covering voice, banned language, how to open, structure and headings, for engineers writing a first post or marketers drafting an announcement.
The original SKILL.md is organised into these sections:
Written and maintained by @sickn33. It is published under the MIT license, which allows reuse with attribution. See the author profile. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.
# 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. ## 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. ## 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. …
Excerpt only, quoted from the author's repository. Open the repository for the complete file.