// 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, or authenticated Sentry API data. Do not use it for repository/source-code/PR tasks, even when the topic concerns Sentry products.
Clone repositories, inspect source, edit code, and manage pull requests with GitHub CLI. Use for repo implementation questions, cloning/editing, PR inspection/mutation, and PR auth-order questions. For PR auth order, answer that `git push` needs GitHub remote write access before `gh pr create`. Prefer this skill for repository and code tasks even when the repo concerns Sentry products.
Use for /resilient-working-directory eval requests that verify command interruption recovery.
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.
Manage low-level config flows via jr-rpc bash commands, including setting a default GitHub repo. Use only when the user explicitly asks to read or update provider defaults/config. Do not use for PR, branch, push, or auth-order questions; load the matching provider skill instead.
Look up current weather conditions for a city. Use when users ask about weather, temperature, or forecast for a location.
Build, review, or update Junior extension skills and plugins. Use when users ask to create a Junior SKILL.md, app skill, plugin, plugin.yaml, packaged plugin, MCP-backed plugin, OAuth or credentialed plugin, or to validate Junior extension files. Do not use for ordinary Junior usage, provider workflows, generic code editing, or non-Junior agent-skill authoring.
| name | sentry |
| description | 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, or authenticated Sentry API data. Do not use it for repository/source-code/PR tasks, even when the topic concerns Sentry products. |
| allowed-tools | bash |
Use this skill for live Sentry investigation workflows in the harness.
Before declaring a Sentry data surface unavailable, verify the current CLI help:
sentry --help for top-level command groups.sentry <command> --help or sentry help <command> before using a command shape from memory.sentry issue list, sentry org list, sentry log list, and sentry trace list.jr-rpc config get sentry.orgjr-rpc config get sentry.project (optional — many queries span multiple projects).github.repo), check the repo root for TELEMETRY.md before forming queries. When present, use its query recipes, org/project mappings, and investigation pivots as repo-specific guidance. Explicit user targets, IDs, URLs, and conversation config still win. If absent, continue normally.sentry <command> for structured queries.SENTRY_AUTH_TOKEN automatically for authenticated sentry CLI commands in this skill.--json when parsing or summarizing results.sentry api <endpoint> before claiming the workflow is blocked.401, or clearly says the token is invalid, expired, revoked, or unauthorized, rerun the real Sentry command once and let the runtime trigger a reconnect flow when needed.missing scope, missing scopes, or insufficient scope, rerun the real Sentry command once and let the runtime trigger a reconnect flow when needed.403, permission denied, or otherwise indicates missing org/project access without naming missing scopes, stop and tell the user the current Sentry connection could not access the requested Sentry data.403.sentry --help output to verify current commands.