Agent Skills

skill-creator

✓★ 753

by sentry

Alias for sentry-skills:skill-writer. Use when users explicitly ask for "skill-creator" or reference the legacy skill name. Redirects to the canonical skill authoring workflow.

🧰 Not standalone — use together with getsentry/sentry-mcp

openspec-propose

✓★ 753

by getsentry

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

🧰 Not standalone — use together with getsentry/sentry-mcp

logging-observability

✓★ 753

by sentry

Review code for correct logging and error handling patterns. Use when reviewing code that handles errors, uses logging functions, or captures exceptions. Enforces the error hierarchy where 4xx errors are never logged to Sentry and 5xx errors always are. Trigger phrases include "review logging", "check error handling", "audit observability", or verify correct use of logIssue vs logError.

🧰 Not standalone — use together with getsentry/sentry-mcp

mcp-audit

✓★ 753

by sentry

Audit MCP servers for protocol compliance, metadata drift, and compatibility regressions. Use when reviewing tool annotations, tool/result schemas, structured output, lifecycle/init handshake, capabilities, prompts/resources support, transports, auth, security, version drift, or Warden/CI MCP compatibility checks. Trigger phrases include "audit MCP", "check MCP spec compliance", "review tool hints", "validate tools/list", "check initialize handshake", "review prompt or resource capabilities", an

🧰 Not standalone — use together with getsentry/sentry-mcp

create-pr

✓★ 753

by sentry

Alias for sentry-skills:pr-writer. Use when users explicitly ask for "create-pr" or reference the legacy skill name. Redirects to the canonical PR writing workflow.

🧰 Not standalone — use together with getsentry/sentry-mcp

create-branch

✓★ 441

by sentry

Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.

🧰 Not standalone — use together with getsentry/sentry-docs

test-skill-b

✓★ 347

by getsentry

Test skill B for integration tests

🧰 Not standalone — use together with getsentry/warden

security-review

✓★ 347

by getsentry

Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.

🧰 Not standalone — use together with getsentry/warden

test-skill

✓★ 347

by getsentry

A test skill for integration tests

🧰 Not standalone — use together with getsentry/warden

test-skill-a

✓★ 347

by getsentry

Test skill A for integration tests

🧰 Not standalone — use together with getsentry/warden

agent-prompt

✓★ 347

by sentry

Reference guide for writing effective agent prompts and skills. Use when creating new skills, reviewing prompt quality, or understanding Warden's prompt architecture.

🧰 Not standalone — use together with getsentry/warden

architecture-review

✓★ 347

by sentry

Staff-level codebase health review. Finds monolithic modules, silent failures, type safety gaps, test coverage holes, and LLM-friendliness issues.

🧰 Not standalone — use together with getsentry/warden

code-review

✓★ 347

by getsentry

Finds real correctness bugs in code changes. Use for adversarial code review, bug hunts, regression review, PR correctness review, logic errors, data loss, race conditions, state bugs, interface contract breaks, error handling bugs, edge cases, broken builds, or broken workflows. Excludes style, readability, architecture, AppSec, and best-practice-only feedback unless the issue causes a demonstrable bug.

🧰 Not standalone — use together with getsentry/warden

testing-guidelines

✓★ 347

by sentry

Guide for writing tests. Use when adding new functionality, fixing bugs, or when tests are needed. Emphasizes integration tests, real-world fixtures, and regression coverage.

🧰 Not standalone — use together with getsentry/warden

example-local

✓★ 276

by getsentry

Provide a compact local example response. Use when users invoke /example-local.

🧰 Not standalone — use together with getsentry/junior

github-code

✓★ 276

by getsentry

Work with GitHub repositories, source code, branches, commits, pushes, pull requests, reviews, diffs, and CI runs. Use for repo implementation tasks, source-code investigation, cloning/fetching, branch and push workflows, PR creation, PR updates, PR review feedback, and GitHub Actions checks. Prefer this skill for repository and code tasks even when the repo concerns Sentry products.

🧰 Not standalone — use together with getsentry/junior

github-issues

✓★ 276

by getsentry

Create, update, comment on, label, and inspect GitHub issues with concise, evidence-backed content. Use when users ask to open, edit, view, close, reopen, or triage GitHub issues — including tracking bugs, features, or tasks. Prefer this skill over generic repository tools for issue operations; do not use for pull requests, branches, pushes, or PR creation order questions.

🧰 Not standalone — use together with getsentry/junior

hex

✓★ 276

by getsentry

Internal data access primitive. Executes a Hex query and returns structured results. Called by core skills — not intended for direct use. Invoke when you need to run a Hex query on behalf of a core skill that has provided a query and pattern. Do not use for Sentry product telemetry, Sentry feature-usage questions, or explicit requests to use Sentry telemetry when the Sentry skill is available.

🧰 Not standalone — use together with getsentry/junior

jr-rpc

✓★ 276

by getsentry

Manage low-level config and plugin introspection flows via jr-rpc bash commands. Use only when the user explicitly asks to read or update provider defaults/config or list installed plugins. Do not use for PR, branch, push, or auth-order questions; load the matching provider skill instead.

🧰 Not standalone — use together with getsentry/junior

notion

✓★ 276

by getsentry

Search Notion pages and data sources and summarize the best match. Use when users ask to look up docs, specs, notes, meeting notes, project context, roadmaps, trackers, or internal references stored in Notion.

🧰 Not standalone — use together with getsentry/junior

self-update

✓★ 276

by getsentry

Update this junior-prod app to the latest published Junior release. Use when asked to self-update Junior, bump @sentry/junior and @sentry/junior-* dependencies, run safety checks, and open a draft PR.

🧰 Not standalone — use together with getsentry/junior

sentry

✓★ 276

by getsentry

Query live Sentry telemetry with the Sentry CLI and generate Sentry deep links. Use when users ask to investigate Sentry issues, events, logs, traces, organizations, projects, replays, product feature usage, Sentry's own product telemetry, or authenticated Sentry API data. Do not use it for repository/source-code/PR tasks, even when the topic concerns Sentry products.

🧰 Not standalone — use together with getsentry/junior

source-handbook

✓★ 276

by getsentry

Check bundled source handbook files for capability, policy, or implementation verification questions. Use when users ask to double-check or verify what the internal/source handbook says.

🧰 Not standalone — use together with getsentry/junior

vercel

✓★ 276

by getsentry

Query Vercel deployments, build logs, runtime logs, and deployment status through the Vercel CLI. Use when users ask to debug Vercel deployments, inspect failed builds, fetch production or preview runtime logs, find a deployment for a project or commit SHA, or investigate Vercel-hosted app errors. Do not use it for deploying, rolling back, changing project settings, domains, env vars, caches, storage, or any other Vercel mutation.

🧰 Not standalone — use together with getsentry/junior

list-working-directory

✓★ 276

by getsentry

Lists files in the sandbox working directory for eval verification. Use when users ask to "list files in the working directory", "show files here", or invoke /list-working-directory in eval scenarios.

🧰 Not standalone — use together with getsentry/junior

linear

✓★ 276

by getsentry

Manage Linear issues through Linear's hosted MCP server. Use when users ask to create a Linear ticket, update a Linear issue, add a Linear comment, move work between states, assign work, or look up Linear issue, team, or project details from Slack context.

🧰 Not standalone — use together with getsentry/junior

junior-qa

✓★ 276

by getsentry

Validate Junior changes through local app-facing paths. Use for local client or agent QA, dashboard mock reporting UI QA, PR readiness, plugin CLI commands, skill/tool/prompt/plugin behavior, and behavior that tests do not cover well but can be exercised with `pnpm cli -- chat ...`, `pnpm cli -- <command> ...`, or `JUNIOR_DASHBOARD_MOCK_CONVERSATIONS=true pnpm dev`.

🧰 Not standalone — use together with getsentry/junior

eval-mcp

✓★ 276

by getsentry

Use for `/eval-mcp` requests that need the eval MCP handbook lookup.

🧰 Not standalone — use together with getsentry/junior

candidate-brief

✓★ 276

by getsentry

Looks up candidate data via a Python script and formats it into a brief. Use when users invoke /candidate-brief with a candidate name.

🧰 Not standalone — use together with getsentry/junior

agent-browser

✓★ 276

by getsentry

Automate websites with the agent-browser CLI for navigation, form flows, screenshots, extraction, and repeatable browser tasks. Use when users ask to interact with web apps, gather evidence from pages, or run browser-based QA steps.

🧰 Not standalone — use together with getsentry/junior