[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-sentry-amplitude":3,"mdc-ks0gy9-key":37,"related-repo-sentry-amplitude":368,"related-org-sentry-amplitude":462},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":26,"repoUrl":27,"updatedAt":28,"license":29,"forks":30,"topics":31,"repo":33,"sourceUrl":35,"mdContent":36},"amplitude","query Amplitude product analytics","Query read-only Amplitude product analytics. Use when users ask about active users, product usage, events, segmentation, funnels, conversion, retention, charts, dashboards, experiments, cohorts, taxonomy, session replay, feature flags, guides, surveys, feedback, agent analytics, or individual user activity in Amplitude. Do not use for changing Amplitude charts, dashboards, experiments, cohorts, flags, taxonomy, or project configuration.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"sentry","Sentry","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fsentry.png","getsentry",[13,17,20,23],{"name":14,"slug":15,"type":16},"Dashboards","dashboards","tag",{"name":18,"slug":19,"type":16},"Reporting","reporting",{"name":21,"slug":22,"type":16},"Charts","charts",{"name":24,"slug":25,"type":16},"Analytics","analytics",300,"https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fjunior","2026-07-11T05:53:26.659115",null,29,[32],"tag-non-production",{"repoUrl":27,"stars":26,"forks":30,"topics":34,"description":29},[32],"https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fjunior\u002Ftree\u002FHEAD\u002Fpackages\u002Fjunior-amplitude\u002Fskills\u002Famplitude","---\nname: amplitude\ndescription: Query read-only Amplitude product analytics. Use when users ask about active users, product usage, events, segmentation, funnels, conversion, retention, charts, dashboards, experiments, cohorts, taxonomy, session replay, feature flags, guides, surveys, feedback, agent analytics, or individual user activity in Amplitude. Do not use for changing Amplitude charts, dashboards, experiments, cohorts, flags, taxonomy, or project configuration.\n---\n\n# Amplitude Analytics\n\nUse this skill for read-only product analytics through Amplitude's hosted MCP server.\n\n## Workflow\n\n1. Define the question before querying:\n\n- Identify the metric or analysis type: active users, event segmentation, funnel, retention, chart, dashboard, experiment, cohort, taxonomy, session replay, feature flag, guide or survey, feedback, agent analytics, or user activity.\n- Preserve explicit event names, property names, chart IDs, dashboard IDs, experiment IDs, cohort IDs, and user IDs exactly.\n- Use the user's explicit time range. For relative ranges, state the concrete dates in the answer.\n- If the request has no time range, use the shortest conventional range that answers it and state the assumption.\n\n2. Discover the current Amplitude tool:\n\n- Inspect the available Amplitude MCP tools for the required analysis.\n- Use the exact live tool name and schema. Do not guess Amplitude MCP tool names or arguments.\n- Prefer direct chart, dashboard, experiment, cohort, or user lookup when the user provides its identifier.\n- If project or organization scope is ambiguous, inspect accessible scope through the read-only catalog and ask one focused question only when multiple plausible targets remain.\n\n3. Query narrowly:\n\n- Request only the events, properties, segments, metrics, and dates needed for the answer.\n- Prefer one complete query over several overlapping queries.\n- For comparisons, keep metric definitions and windows consistent.\n- Stop once the requested result is supported; do not enumerate unrelated project metadata.\n\n4. Report the result:\n\n- Lead with the metric, trend, conversion, retention, or experiment finding.\n- Include the date range, project or scope, filters, and metric definition needed to interpret it.\n- Distinguish unique users, event totals, sessions, and percentages explicitly.\n- Include Amplitude links returned by the MCP server when available.\n- State when data is empty, delayed, inaccessible, or insufficient rather than inferring a value.\n\n## Common Analyses\n\n- **DAU, WAU, MAU:** use active-user or event-segmentation tools with the requested interval and clarify whether the result is unique users or event totals.\n- **Event segmentation:** preserve the exact event and property filters; report the aggregation and interval.\n- **Funnels:** preserve ordered steps, conversion window, exclusions, and segment filters; report overall conversion and material drop-off steps.\n- **Retention:** report the starting event, returning event, cohort interval, and retention horizon.\n- **Saved charts and dashboards:** fetch by ID when available and summarize the returned definition and results without recreating the analysis from memory.\n- **Experiments:** report status, variants, exposure window, primary metric, and result confidence exactly as returned.\n- **Session replay:** narrow by time, user, or event before retrieving replay details; summarize only the interactions needed to answer the question.\n- **Feature flags:** report definitions, variants, and configuration without exposing deployment API keys or other credential fields.\n- **Guides, surveys, and feedback:** preserve source and date filters, distinguish processed themes from raw comments, and avoid returning unrelated customer text.\n- **Agent analytics:** distinguish sessions, spans, conversations, quality metrics, cost, and latency; return transcript content only when the user explicitly requests it.\n- **User activity:** use an explicit user identifier when possible and avoid exposing unrelated profile properties or event history.\n\n## Guardrails\n\n- Read-only only. The plugin exposes a fixed allowlist of Amplitude search, retrieval, and query tools.\n- Do not create, update, archive, delete, launch, stop, or otherwise modify Amplitude resources.\n- If the user asks for a change, explain that this plugin is read-only and offer to inspect the current state or describe the change they would need to make.\n- Do not weaken or bypass the plugin's tool filter, including by calling Amplitude APIs through shell commands.\n- Treat event and user properties as potentially sensitive. Return only fields needed to answer the request.\n- Never expose API keys, credential fields, or unrelated conversation and feedback content returned by read tools.\n- Do not fabricate event names, property values, metric definitions, experiment conclusions, or missing data.\n- On authorization failure, let Junior present Amplitude's OAuth flow. On permission failure, report that the connected Amplitude account cannot access the requested scope.\n",{"data":38,"body":39},{"name":4,"description":6},{"type":40,"children":41},"root",[42,51,57,64,74,98,107,130,139,162,171,199,205,319,325],{"type":43,"tag":44,"props":45,"children":47},"element","h1",{"id":46},"amplitude-analytics",[48],{"type":49,"value":50},"text","Amplitude Analytics",{"type":43,"tag":52,"props":53,"children":54},"p",{},[55],{"type":49,"value":56},"Use this skill for read-only product analytics through Amplitude's hosted MCP server.",{"type":43,"tag":58,"props":59,"children":61},"h2",{"id":60},"workflow",[62],{"type":49,"value":63},"Workflow",{"type":43,"tag":65,"props":66,"children":67},"ol",{},[68],{"type":43,"tag":69,"props":70,"children":71},"li",{},[72],{"type":49,"value":73},"Define the question before querying:",{"type":43,"tag":75,"props":76,"children":77},"ul",{},[78,83,88,93],{"type":43,"tag":69,"props":79,"children":80},{},[81],{"type":49,"value":82},"Identify the metric or analysis type: active users, event segmentation, funnel, retention, chart, dashboard, experiment, cohort, taxonomy, session replay, feature flag, guide or survey, feedback, agent analytics, or user activity.",{"type":43,"tag":69,"props":84,"children":85},{},[86],{"type":49,"value":87},"Preserve explicit event names, property names, chart IDs, dashboard IDs, experiment IDs, cohort IDs, and user IDs exactly.",{"type":43,"tag":69,"props":89,"children":90},{},[91],{"type":49,"value":92},"Use the user's explicit time range. For relative ranges, state the concrete dates in the answer.",{"type":43,"tag":69,"props":94,"children":95},{},[96],{"type":49,"value":97},"If the request has no time range, use the shortest conventional range that answers it and state the assumption.",{"type":43,"tag":65,"props":99,"children":101},{"start":100},2,[102],{"type":43,"tag":69,"props":103,"children":104},{},[105],{"type":49,"value":106},"Discover the current Amplitude tool:",{"type":43,"tag":75,"props":108,"children":109},{},[110,115,120,125],{"type":43,"tag":69,"props":111,"children":112},{},[113],{"type":49,"value":114},"Inspect the available Amplitude MCP tools for the required analysis.",{"type":43,"tag":69,"props":116,"children":117},{},[118],{"type":49,"value":119},"Use the exact live tool name and schema. Do not guess Amplitude MCP tool names or arguments.",{"type":43,"tag":69,"props":121,"children":122},{},[123],{"type":49,"value":124},"Prefer direct chart, dashboard, experiment, cohort, or user lookup when the user provides its identifier.",{"type":43,"tag":69,"props":126,"children":127},{},[128],{"type":49,"value":129},"If project or organization scope is ambiguous, inspect accessible scope through the read-only catalog and ask one focused question only when multiple plausible targets remain.",{"type":43,"tag":65,"props":131,"children":133},{"start":132},3,[134],{"type":43,"tag":69,"props":135,"children":136},{},[137],{"type":49,"value":138},"Query narrowly:",{"type":43,"tag":75,"props":140,"children":141},{},[142,147,152,157],{"type":43,"tag":69,"props":143,"children":144},{},[145],{"type":49,"value":146},"Request only the events, properties, segments, metrics, and dates needed for the answer.",{"type":43,"tag":69,"props":148,"children":149},{},[150],{"type":49,"value":151},"Prefer one complete query over several overlapping queries.",{"type":43,"tag":69,"props":153,"children":154},{},[155],{"type":49,"value":156},"For comparisons, keep metric definitions and windows consistent.",{"type":43,"tag":69,"props":158,"children":159},{},[160],{"type":49,"value":161},"Stop once the requested result is supported; do not enumerate unrelated project metadata.",{"type":43,"tag":65,"props":163,"children":165},{"start":164},4,[166],{"type":43,"tag":69,"props":167,"children":168},{},[169],{"type":49,"value":170},"Report the result:",{"type":43,"tag":75,"props":172,"children":173},{},[174,179,184,189,194],{"type":43,"tag":69,"props":175,"children":176},{},[177],{"type":49,"value":178},"Lead with the metric, trend, conversion, retention, or experiment finding.",{"type":43,"tag":69,"props":180,"children":181},{},[182],{"type":49,"value":183},"Include the date range, project or scope, filters, and metric definition needed to interpret it.",{"type":43,"tag":69,"props":185,"children":186},{},[187],{"type":49,"value":188},"Distinguish unique users, event totals, sessions, and percentages explicitly.",{"type":43,"tag":69,"props":190,"children":191},{},[192],{"type":49,"value":193},"Include Amplitude links returned by the MCP server when available.",{"type":43,"tag":69,"props":195,"children":196},{},[197],{"type":49,"value":198},"State when data is empty, delayed, inaccessible, or insufficient rather than inferring a value.",{"type":43,"tag":58,"props":200,"children":202},{"id":201},"common-analyses",[203],{"type":49,"value":204},"Common Analyses",{"type":43,"tag":75,"props":206,"children":207},{},[208,219,229,239,249,259,269,279,289,299,309],{"type":43,"tag":69,"props":209,"children":210},{},[211,217],{"type":43,"tag":212,"props":213,"children":214},"strong",{},[215],{"type":49,"value":216},"DAU, WAU, MAU:",{"type":49,"value":218}," use active-user or event-segmentation tools with the requested interval and clarify whether the result is unique users or event totals.",{"type":43,"tag":69,"props":220,"children":221},{},[222,227],{"type":43,"tag":212,"props":223,"children":224},{},[225],{"type":49,"value":226},"Event segmentation:",{"type":49,"value":228}," preserve the exact event and property filters; report the aggregation and interval.",{"type":43,"tag":69,"props":230,"children":231},{},[232,237],{"type":43,"tag":212,"props":233,"children":234},{},[235],{"type":49,"value":236},"Funnels:",{"type":49,"value":238}," preserve ordered steps, conversion window, exclusions, and segment filters; report overall conversion and material drop-off steps.",{"type":43,"tag":69,"props":240,"children":241},{},[242,247],{"type":43,"tag":212,"props":243,"children":244},{},[245],{"type":49,"value":246},"Retention:",{"type":49,"value":248}," report the starting event, returning event, cohort interval, and retention horizon.",{"type":43,"tag":69,"props":250,"children":251},{},[252,257],{"type":43,"tag":212,"props":253,"children":254},{},[255],{"type":49,"value":256},"Saved charts and dashboards:",{"type":49,"value":258}," fetch by ID when available and summarize the returned definition and results without recreating the analysis from memory.",{"type":43,"tag":69,"props":260,"children":261},{},[262,267],{"type":43,"tag":212,"props":263,"children":264},{},[265],{"type":49,"value":266},"Experiments:",{"type":49,"value":268}," report status, variants, exposure window, primary metric, and result confidence exactly as returned.",{"type":43,"tag":69,"props":270,"children":271},{},[272,277],{"type":43,"tag":212,"props":273,"children":274},{},[275],{"type":49,"value":276},"Session replay:",{"type":49,"value":278}," narrow by time, user, or event before retrieving replay details; summarize only the interactions needed to answer the question.",{"type":43,"tag":69,"props":280,"children":281},{},[282,287],{"type":43,"tag":212,"props":283,"children":284},{},[285],{"type":49,"value":286},"Feature flags:",{"type":49,"value":288}," report definitions, variants, and configuration without exposing deployment API keys or other credential fields.",{"type":43,"tag":69,"props":290,"children":291},{},[292,297],{"type":43,"tag":212,"props":293,"children":294},{},[295],{"type":49,"value":296},"Guides, surveys, and feedback:",{"type":49,"value":298}," preserve source and date filters, distinguish processed themes from raw comments, and avoid returning unrelated customer text.",{"type":43,"tag":69,"props":300,"children":301},{},[302,307],{"type":43,"tag":212,"props":303,"children":304},{},[305],{"type":49,"value":306},"Agent analytics:",{"type":49,"value":308}," distinguish sessions, spans, conversations, quality metrics, cost, and latency; return transcript content only when the user explicitly requests it.",{"type":43,"tag":69,"props":310,"children":311},{},[312,317],{"type":43,"tag":212,"props":313,"children":314},{},[315],{"type":49,"value":316},"User activity:",{"type":49,"value":318}," use an explicit user identifier when possible and avoid exposing unrelated profile properties or event history.",{"type":43,"tag":58,"props":320,"children":322},{"id":321},"guardrails",[323],{"type":49,"value":324},"Guardrails",{"type":43,"tag":75,"props":326,"children":327},{},[328,333,338,343,348,353,358,363],{"type":43,"tag":69,"props":329,"children":330},{},[331],{"type":49,"value":332},"Read-only only. The plugin exposes a fixed allowlist of Amplitude search, retrieval, and query tools.",{"type":43,"tag":69,"props":334,"children":335},{},[336],{"type":49,"value":337},"Do not create, update, archive, delete, launch, stop, or otherwise modify Amplitude resources.",{"type":43,"tag":69,"props":339,"children":340},{},[341],{"type":49,"value":342},"If the user asks for a change, explain that this plugin is read-only and offer to inspect the current state or describe the change they would need to make.",{"type":43,"tag":69,"props":344,"children":345},{},[346],{"type":49,"value":347},"Do not weaken or bypass the plugin's tool filter, including by calling Amplitude APIs through shell commands.",{"type":43,"tag":69,"props":349,"children":350},{},[351],{"type":49,"value":352},"Treat event and user properties as potentially sensitive. Return only fields needed to answer the request.",{"type":43,"tag":69,"props":354,"children":355},{},[356],{"type":49,"value":357},"Never expose API keys, credential fields, or unrelated conversation and feedback content returned by read tools.",{"type":43,"tag":69,"props":359,"children":360},{},[361],{"type":49,"value":362},"Do not fabricate event names, property values, metric definitions, experiment conclusions, or missing data.",{"type":43,"tag":69,"props":364,"children":365},{},[366],{"type":49,"value":367},"On authorization failure, let Junior present Amplitude's OAuth flow. On permission failure, report that the connected Amplitude account cannot access the requested scope.",{"items":369,"total":461},[370,377,395,412,431,446],{"slug":4,"name":4,"fn":5,"description":6,"org":371,"tags":372,"stars":26,"repoUrl":27,"updatedAt":28},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[373,374,375,376],{"name":24,"slug":25,"type":16},{"name":21,"slug":22,"type":16},{"name":14,"slug":15,"type":16},{"name":18,"slug":19,"type":16},{"slug":378,"name":378,"fn":379,"description":380,"org":381,"tags":382,"stars":26,"repoUrl":27,"updatedAt":394},"cloudflare","investigate Cloudflare production operations","Cloudflare production operations via the Cloudflare API MCP server. Use when users ask to investigate Workers errors or performance, check build or deployment status, query logs, inspect DNS records, check load balancer pool health, review Zero Trust tunnels, or manage Cloudflare resources. Do not use for Sentry issues, GitHub\u002FLinear ticketing, or non-Cloudflare infrastructure.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[383,385,388,391],{"name":384,"slug":378,"type":16},"Cloudflare",{"name":386,"slug":387,"type":16},"Deployment","deployment",{"name":389,"slug":390,"type":16},"Monitoring","monitoring",{"name":392,"slug":393,"type":16},"Observability","observability","2026-07-01T07:46:37.892035",{"slug":396,"name":396,"fn":397,"description":398,"org":399,"tags":400,"stars":26,"repoUrl":27,"updatedAt":411},"datadog","query Datadog telemetry and investigate behavior","Query live Datadog telemetry (logs, metrics, traces, spans, monitors, incidents, dashboards, services, hosts) through Datadog's Pup CLI. Use when users ask to investigate production behavior in Datadog, including searching logs, checking monitor status, inspecting traces or spans, looking up incidents, finding services, or correlating metrics. Do not use it for Sentry issues, repository\u002Fsource-code work, or ticketing.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[401,403,406,407,408],{"name":402,"slug":396,"type":16},"Datadog",{"name":404,"slug":405,"type":16},"Debugging","debugging",{"name":389,"slug":390,"type":16},{"name":392,"slug":393,"type":16},{"name":409,"slug":410,"type":16},"SRE","sre","2026-04-18T04:45:22.733842",{"slug":413,"name":413,"fn":414,"description":415,"org":416,"tags":417,"stars":26,"repoUrl":27,"updatedAt":430},"junior","build and update Junior plugins","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.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[418,421,424,427],{"name":419,"slug":420,"type":16},"Automation","automation",{"name":422,"slug":423,"type":16},"Engineering","engineering",{"name":425,"slug":426,"type":16},"MCP","mcp",{"name":428,"slug":429,"type":16},"Plugin Development","plugin-development","2026-07-31T06:23:36.591638",{"slug":432,"name":432,"fn":433,"description":434,"org":435,"tags":436,"stars":26,"repoUrl":27,"updatedAt":445},"junior-qa","validate Junior application changes","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\u002Ftool\u002Fprompt\u002Fplugin behavior, and behavior that tests do not cover well but can be exercised with `pnpm cli -- chat ...`, another `pnpm cli` command, or `JUNIOR_DASHBOARD_MOCK_CONVERSATIONS=true pnpm dev`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[437,438,439,442],{"name":404,"slug":405,"type":16},{"name":422,"slug":423,"type":16},{"name":440,"slug":441,"type":16},"QA","qa",{"name":443,"slug":444,"type":16},"Testing","testing","2026-07-31T06:23:35.910415",{"slug":447,"name":447,"fn":448,"description":449,"org":450,"tags":451,"stars":26,"repoUrl":27,"updatedAt":460},"vercel","debug Vercel deployments and logs","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.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[452,455,456,457,458],{"name":453,"slug":454,"type":16},"CLI","cli",{"name":404,"slug":405,"type":16},{"name":386,"slug":387,"type":16},{"name":392,"slug":393,"type":16},{"name":459,"slug":447,"type":16},"Vercel","2026-07-24T05:40:46.832412",6,{"items":463,"total":633},[464,485,497,510,524,541,557,571,581,592,602,620],{"slug":465,"name":465,"fn":466,"description":467,"org":468,"tags":469,"stars":482,"repoUrl":483,"updatedAt":484},"xcodebuildmcp","build and test Apple apps with XcodeBuildMCP","Official skill for XcodeBuildMCP. Use when doing iOS\u002FmacOS\u002FwatchOS\u002FtvOS\u002FvisionOS work (build, test, run, debug, log, UI automation).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[470,471,474,477,478,479],{"name":404,"slug":405,"type":16},{"name":472,"slug":473,"type":16},"iOS","ios",{"name":475,"slug":476,"type":16},"macOS","macos",{"name":9,"slug":8,"type":16},{"name":443,"slug":444,"type":16},{"name":480,"slug":481,"type":16},"Xcode","xcode",6176,"https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP","2026-04-06T18:13:34.8719",{"slug":486,"name":486,"fn":487,"description":488,"org":489,"tags":490,"stars":482,"repoUrl":483,"updatedAt":496},"xcodebuildmcp-cli","build and test Apple apps via CLI","Official skill for the XcodeBuildMCP CLI. Use when doing iOS\u002FmacOS\u002FwatchOS\u002FtvOS\u002FvisionOS work (build, test, run, debug, log, UI automation).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[491,492,493,494,495],{"name":453,"slug":454,"type":16},{"name":472,"slug":473,"type":16},{"name":475,"slug":476,"type":16},{"name":443,"slug":444,"type":16},{"name":480,"slug":481,"type":16},"2026-04-06T18:13:36.13414",{"slug":498,"name":498,"fn":499,"description":500,"org":501,"tags":502,"stars":507,"repoUrl":508,"updatedAt":509},"agents-md","maintain project instruction files","Creates and maintains concise AGENTS.md and CLAUDE.md project instruction files. Use when asked to create AGENTS.md, update AGENTS.md, maintain agent docs, set up CLAUDE.md, document repository agent conventions, or keep coding-agent instructions minimal and reference-backed.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[503,506],{"name":504,"slug":505,"type":16},"Documentation","documentation",{"name":422,"slug":423,"type":16},861,"https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fskills","2026-05-15T06:16:29.695991",{"slug":511,"name":511,"fn":512,"description":513,"org":514,"tags":515,"stars":507,"repoUrl":508,"updatedAt":523},"blog-writing-guide","write and review engineering blog posts","Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions \"blog post,\" \"blog draft,\" \"write-up,\" \"announcement post,\" \"engineering post,\" \"deep dive,\" \"postmortem,\" or asks for help with technical writing for Sentry. Even if the user just says \"help me write about [feature\u002Ftopic]\" — if it sounds like it could become a Sentry blog post, use this skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[516,519,520],{"name":517,"slug":518,"type":16},"Communications","communications",{"name":9,"slug":8,"type":16},{"name":521,"slug":522,"type":16},"Technical Writing","technical-writing","2026-05-15T06:16:33.38217",{"slug":525,"name":525,"fn":526,"description":527,"org":528,"tags":529,"stars":507,"repoUrl":508,"updatedAt":540},"brand-guidelines","write copy following Sentry brand guidelines","Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[530,533,536,537],{"name":531,"slug":532,"type":16},"Branding","branding",{"name":534,"slug":535,"type":16},"Content Creation","content-creation",{"name":9,"slug":8,"type":16},{"name":538,"slug":539,"type":16},"UX Copy","ux-copy","2026-05-15T06:16:22.395707",{"slug":542,"name":542,"fn":543,"description":544,"org":545,"tags":546,"stars":507,"repoUrl":508,"updatedAt":556},"claude-settings-audit","generate Claude Code settings permissions","Analyze a repository to generate recommended Claude Code settings.json permissions. Use when setting up a new project, auditing existing settings, or determining which read-only bash commands to allow. Detects tech stack, build tools, and monorepo structure.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[547,550,553],{"name":548,"slug":549,"type":16},"Claude Code","claude-code",{"name":551,"slug":552,"type":16},"Configuration","configuration",{"name":554,"slug":555,"type":16},"Security","security","2026-05-15T06:16:44.335977",{"slug":558,"name":558,"fn":559,"description":560,"org":561,"tags":562,"stars":507,"repoUrl":508,"updatedAt":570},"code-review","perform code reviews for Sentry projects","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.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[563,565,566,569],{"name":564,"slug":558,"type":16},"Code Review",{"name":422,"slug":423,"type":16},{"name":567,"slug":568,"type":16},"Performance","performance",{"name":554,"slug":555,"type":16},"2026-05-15T06:16:35.824864",{"slug":572,"name":572,"fn":573,"description":574,"org":575,"tags":576,"stars":507,"repoUrl":508,"updatedAt":580},"code-simplifier","simplify and refine source code","Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to \"simplify code\", \"clean up code\", \"refactor for clarity\", \"improve readability\", or review recently modified code for elegance. Focuses on project-specific best practices.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[577],{"name":578,"slug":579,"type":16},"Code Analysis","code-analysis","2026-05-15T06:16:32.127981",{"slug":582,"name":582,"fn":583,"description":584,"org":585,"tags":586,"stars":507,"repoUrl":508,"updatedAt":591},"commit","create commits with Sentry conventions","Use for every request to commit changes or draft a commit message. Creates Sentry-style conventional commits with issue references.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[587,590],{"name":588,"slug":589,"type":16},"Git","git",{"name":9,"slug":8,"type":16},"2026-07-18T05:15:10.723937",{"slug":593,"name":593,"fn":594,"description":595,"org":596,"tags":597,"stars":507,"repoUrl":508,"updatedAt":601},"create-branch","create git branches for Sentry workflows","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.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[598,599,600],{"name":422,"slug":423,"type":16},{"name":588,"slug":589,"type":16},{"name":9,"slug":8,"type":16},"2026-05-15T06:16:39.458431",{"slug":603,"name":603,"fn":604,"description":605,"org":606,"tags":607,"stars":507,"repoUrl":508,"updatedAt":619},"django-access-review","review Django access control and IDOR","Django access control and IDOR security review. Use when reviewing Django views, DRF viewsets, ORM queries, or any Python\u002FDjango code handling user authorization. Trigger keywords: \"IDOR\", \"access control\", \"authorization\", \"Django permissions\", \"object permissions\", \"tenant isolation\", \"broken access\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[608,611,612,615,618],{"name":609,"slug":610,"type":16},"Access Control","access-control",{"name":578,"slug":579,"type":16},{"name":613,"slug":614,"type":16},"Django","django",{"name":616,"slug":617,"type":16},"Python","python",{"name":554,"slug":555,"type":16},"2026-05-15T06:16:43.098698",{"slug":621,"name":621,"fn":622,"description":623,"org":624,"tags":625,"stars":507,"repoUrl":508,"updatedAt":632},"django-perf-review","review and optimize Django performance","Django performance code review. Use when asked to \"review Django performance\", \"find N+1 queries\", \"optimize Django\", \"check queryset performance\", \"database performance\", \"Django ORM issues\", or audit Django code for performance problems.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[626,627,630,631],{"name":564,"slug":558,"type":16},{"name":628,"slug":629,"type":16},"Database","database",{"name":613,"slug":614,"type":16},{"name":567,"slug":568,"type":16},"2026-05-15T06:16:24.832813",88]