Agent Skills

cell-architecture

✓★ 44,236

by sentry

Reference and active migration guide for Sentry's cell architecture. Explains what cells and localities are and why they're different, how requests reach cells via Synapse API routing, ingestion routing, and the control silo gateway, and how to safely query cross-cell data without silently missing results. The migration section covers how to do migration work: draining the URL_NAME_TO_ACTION registry in test_urls.py to zero (with a recipe for each action type), rolling deploy safety and the two-

🧰 Not standalone — use together with getsentry/sentry

dotagents

✓★ 8,701

by sentry

Manage agent skill dependencies with dotagents. Use when asked to "add a skill", "install skills", "remove a skill", "update skills", "dotagents init", "agents.toml", "agents.lock", "sync skills", "list skills", "set up dotagents", "configure trust", "add MCP server", "add hook", "wildcard skills", "user scope", or any dotagents-related task.

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

skill-scanner

✓★ 8,701

by sentry

Scan agent skills for security issues. Use when asked to "scan a skill",

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

fix-security-vulnerability

✓★ 8,701

by sentry

Analyze and propose fixes for Dependabot security alerts

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

write-tests

✓★ 8,701

by sentry

Write high-quality unit tests (Vitest) and E2E tests (Playwright) following senior test-engineering practices. Use this skill whenever asked to write tests, add test coverage, create test cases, fix failing tests, add missing assertions, test a new feature, write specs, or cover edge cases. Also trigger when the user says "write tests for", "add tests", "test this", "cover this", "needs tests", "add E2E test", "add unit test", "test coverage", or when reviewing code and noticing missing test cov

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

triage-issue

✓★ 8,701

by sentry

Triage GitHub issues with codebase research and actionable recommendations

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

skill-creator

✓★ 8,701

by sentry

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

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

xcodebuildmcp-runtime-boundary-review

✓★ 6,033

by getsentry

Use when reviewing XcodeBuildMCP runtime boundary changes across MCP, direct CLI invocation, daemon-routed tools, and Xcode IDE bridge routing.

🧰 Not standalone — use together with getsentry/xcodebuildmcp

warden-sweep

✓★ 6,033

by getsentry

Full-repository code sweep. Scans every file with warden, verifies findings via deep tracing, creates draft PRs for validated issues. Use when asked to "sweep the repo", "scan everything", "find all bugs", "full codebase review", "batch code analysis", or run warden across the entire repository.

🧰 Not standalone — use together with getsentry/xcodebuildmcp

xcodebuildmcp-packaging-resource-review

✓★ 6,033

by getsentry

Use when reviewing XcodeBuildMCP packaging, resource-root, build artifact, bundled AXe, schema, manifest, and portable macOS distribution changes.

🧰 Not standalone — use together with getsentry/xcodebuildmcp

xcodebuildmcp-cli

✓★ 6,033

by sentry

Official skill for the XcodeBuildMCP CLI. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).

🧰 Not standalone — use together with getsentry/xcodebuildmcp

warden

✓★ 6,033

by getsentry

Run Warden to analyze code changes before committing. Use when asked to "run warden", "check my changes", "review before commit", "warden config", "warden.toml", "create a warden skill", "add trigger", or any Warden-related local development task.

🧰 Not standalone — use together with getsentry/xcodebuildmcp

xcodebuildmcp-rendering-streaming-review

✓★ 6,033

by getsentry

Use when reviewing XcodeBuildMCP rendering, streaming fragment, next-step, and CLI output mode changes for boundary violations.

🧰 Not standalone — use together with getsentry/xcodebuildmcp

xcodebuildmcp-structured-output-review

✓★ 6,033

by getsentry

Use when reviewing XcodeBuildMCP structured output schema changes, schema versioning, manifest outputSchema metadata, and JSON fixture compatibility.

🧰 Not standalone — use together with getsentry/xcodebuildmcp

xcodebuildmcp

✓★ 6,033

by sentry

Official skill for XcodeBuildMCP. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).

🧰 Not standalone — use together with getsentry/xcodebuildmcp

xcodebuildmcp-docs-release-review

✓★ 6,033

by getsentry

Use when reviewing XcodeBuildMCP documentation, CLI command references, website manifest generation, changelog, release notes, and release script changes.

🧰 Not standalone — use together with getsentry/xcodebuildmcp

xcodebuildmcp-tool-contract-review

✓★ 6,033

by getsentry

Use when reviewing XcodeBuildMCP tool contract changes across implementation, manifests, workflow membership, output schema metadata, and next-step templates.

🧰 Not standalone — use together with getsentry/xcodebuildmcp

xcodebuildmcp-docs-command-review

✓★ 6,033

by getsentry

Use when reviewing XcodeBuildMCP changelog CLI command references for invalid current guidance while allowing historical migration examples.

🧰 Not standalone — use together with getsentry/xcodebuildmcp

xcodebuildmcp-snapshot-fixture-review

✓★ 6,033

by getsentry

Use when reviewing XcodeBuildMCP snapshot fixture changes for MCP, CLI, and JSON output contract integrity.

🧰 Not standalone — use together with getsentry/xcodebuildmcp

xcodebuildmcp-test-boundary-review

✓★ 6,033

by getsentry

Use when reviewing XcodeBuildMCP tests for correct unit, snapshot, schema, smoke, and external process boundaries.

🧰 Not standalone — use together with getsentry/xcodebuildmcp

find-bugs

✓★ 2,194

by sentry

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

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

code-review

✓★ 2,194

by sentry

Perform code reviews following Sentry engineering practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.

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

skill-scanner

✓★ 2,194

by sentry

Scan agent skills for security issues. Use when asked to "scan a skill",

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

security-review

✓★ 2,194

by sentry

Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.

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

testing-guidelines

✓★ 753

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/sentry-mcp

openspec-sync-specs

✓★ 753

by getsentry

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

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

openspec-explore

✓★ 753

by getsentry

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

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

openspec-archive-change

✓★ 753

by getsentry

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

🧰 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

openspec-apply-change

✓★ 753

by getsentry

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

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