blog-writing-guide

blog-writing-guide is a skill for Claude Code from getsentry/skills. It costs 163 tokens per session (2,680 once invoked), scanned A, original, Apache-2.0.

A writing and editing guide for Sentry engineering blog posts, including technical articles, announcements, and draft reviews.

In plain words
What is it for?
Use it to draft, review, or improve engineering blog content while following Sentry’s preferred voice, structure, and language rules.
Why use it?
It helps keep posts technically precise and consistent with Sentry’s direct, experienced writing style instead of sounding like generic marketing copy.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the skills plugin — 27 skills, 1 agent shipped together

Good fit Use it to draft, review, or improve engineering blog content while following…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/getsentry/skills/blog-writing-guide
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add getsentry/skills --skill blog-writing-guide
Clone the repo
git clone --depth 1 https://github.com/getsentry/skills

Made for: Claude Code.

Or install skills, the plugin that ships this one along with the rest of its 27 skills, 1 agent.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for blog-writing-guide

README.md
[![agentmods](https://agentmods.dev/badge/skills/getsentry/skills/blog-writing-guide.svg)](https://agentmods.dev/skills/getsentry/skills/blog-writing-guide)
Your own site
<a href="https://agentmods.dev/skills/getsentry/skills/blog-writing-guide"><img src="https://agentmods.dev/badge/skills/getsentry/skills/blog-writing-guide.svg" alt="Measured on agentmods" height="20"></a>
Per session 163 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,680 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00163 $0.02680
Opus 5 $0.00081 $0.01340
Sonnet 5 $0.00033 $0.00536
Haiku 4.5 $0.00016 $0.00268

Measured 7d ago against content hash 8aba654d1af0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

blog-writing-guide scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/blog-writing-guide/SKILL.md · 216 lines

How it starts

The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.

Banned Language

Never use these. They are automatic red flags:

  • "We're excited/thrilled to announce" — just announce it
  • "Best-in-class" / "industry-leading" / "cutting-edge" — show, don't tell
  • "Seamless" / "seamlessly" — nothing is seamless
  • "Empower" / "leverage" / "unlock" — say what you actually mean
  • "Robust" — describe what makes it robust instead
  • "At [Company], we believe..." — just state the belief
  • "Streamline" — everyone is streamlining, stop
  • Filler transitions: "That being said," "It's worth noting that," "At the end of the day," "Without further ado," "As you might know"
  • "In this blog post, we will explore..." — be direct, just start

The Opening (First 2-3 Sentences)

The opening must do one of two things: state the problem or state the conclusion. Never start with background, company history, or hype.

Good: "Two weeks before launch, we killed our entire metrics product. Here's why pre-aggregating time-series metrics breaks down for debugging, and how we rebuilt the system from scratch."

Read the full file on GitHub · 216 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 216 lines · 163 tokens per session scan A 8aba654d1af0

Subscribe to this mod's changes

blog-writing-guide is a skill published in the GitHub repository getsentry/skills (979 stars, last pushed 12d ago), licensed Apache-2.0. It adds 163 tokens to every session and 2,680 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

sentry-nestjs-sdk

Full Sentry SDK setup for NestJS. Use when asked to "add Sentry to NestJS", "install @sentry/nestjs", "setup Sentry in NestJS", or configure error monitoring, tracing, profiling, logging, metrics, crons, or AI monitoring for NestJS applications. Supports Express and Fastify adapters, GraphQL, microservices…

getsentry/sentry-for-ai · 89 tokens

sentry-node-sdk

Full Sentry SDK setup for Node.js, Bun, and Deno. Use when asked to "add Sentry to Node.js", "add Sentry to Bun", "add Sentry to Deno", "install @sentry/node", "@sentry/bun", or "@sentry/deno", or configure error monitoring, tracing, logging, profiling, metrics, crons, or AI monitoring for server-side…

getsentry/sentry-for-ai · 98 tokens

sentry-react-native-sdk

Full Sentry SDK setup for React Native and Expo. Use when asked to "add Sentry to React Native", "install @sentry/react-native", "setup Sentry in Expo", or configure error monitoring, tracing, profiling, session replay, or logging for React Native applications. Supports Expo managed, Expo bare, and vanilla React…

getsentry/sentry-for-ai · 75 tokens

sentry-android-sdk

Full Sentry SDK setup for Android. Use when asked to "add Sentry to Android", "install sentry-android", "setup Sentry in Android", or configure error monitoring, tracing, profiling, session replay, or logging for Android applications. Supports Kotlin and Java codebases.

getsentry/sentry-for-ai · 64 tokens

sentry-browser-sdk

Full Sentry SDK setup for browser JavaScript. Use when asked to "add Sentry to a website", "install @sentry/browser", or configure error monitoring, tracing, session replay, or logging for vanilla JavaScript, jQuery, static sites, or WordPress.

getsentry/sentry-for-ai · 61 tokens

sentry-flutter-sdk

Full Sentry SDK setup for Flutter and Dart. Use when asked to "add Sentry to Flutter", "install sentryflutter", "setup Sentry in Dart", or configure error monitoring, tracing, profiling, session replay, or logging for Flutter applications. Supports Android, iOS, macOS, Linux, Windows, and Web.

getsentry/sentry-for-ai · 74 tokens