skills.rest
mozilla
mozillaOFFICIAL
Explore all skills by this author →
WebsiteGitHub

fxa-triage

Generates daily FxA triage summaries from Jira, GitHub, Bugzilla, Sentry, and Grafana.

685|236|Updated Jun 3, 2015
Search Tags:#Slack#Jira#on-call#triage#Sentry#gitHub#Monitoring
One-click install
npx skills add https://github.com/mozilla/fxa --skill fxa-triage
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fxa-triage
Source: https://github.com/mozilla/fxa/tree/main/.claude/skills/fxa-triage
Command: npx skills add https://github.com/mozilla/fxa --skill fxa-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Daily triage duty for the Mozilla Accounts (FxA) team requires manually checking Jira, GitHub, Bugzilla, Sentry, Slack, Grafana, CircleCI, and WAF dashboards, then synthesizing everything into a Slack-ready summary. This Skill automates the collection and analysis so the triage owner spends minutes instead of hours assembling the daily report.

Core Features & Use Cases

  • Multi-source data collection: Queries Jira (JQL with pagination and batch detection), GitHub PRs and Dependabot alerts, Bugzilla, Sentry issues, Slack threads, Grafana dashboards, and CircleCI pipelines via MCP tools and CLI commands.
  • Baseline diffing and urgency bucketing: Compares against prior daily reports stored in a local history directory, then classifies findings into Slack-urgent, pre-post checklist, and informational tiers based on user impact, security signals, and team cadence (release Wednesdays, Monday triage meetings).
  • Slack-ready output with human control: Produces a copy-paste summary plus an optional opt-in Slack draft; it never auto-posts, and persists reports and follow-ups locally on explicit save.
  • Use Case: An engineer starting triage duty invokes the skill, answers one upfront setup interview (environments, skips, screenshots), and receives a complete daily triage report with day-over-day deltas ready to post to the team channel.

Quick Start

Ask the assistant to run the fxa-triage skill to generate today's FxA daily triage summary.

Frequently Asked Questions about fxa-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a daily FxA triage summary?▼

Invoke the fxa-triage skill and answer the single upfront interview covering environments (prod, stage, or both), sources to skip, and any manual Grafana or WAF screenshots. The skill then fetches Jira, GitHub, Bugzilla, Sentry, and other sources silently and outputs one consolidated report.

What data sources does the FxA triage workflow query?▼

It queries Jira via JQL, GitHub via the gh CLI, Bugzilla's public REST API, Sentry issues, Slack threads, Grafana dashboards, and CircleCI pipelines. Source coordinates come from an operational config page fetched via the Atlassian MCP, not from the repo.

Does the skill post the triage summary to Slack automatically?▼

No, it never auto-posts. Section B is generated for manual copy-paste, and an optional opt-in step composes a Slack draft only after the engineer explicitly types 'post' and harness permissions allow it.

Can I run FxA triage without the Grafana or Slack MCP servers?▼

Yes. Grafana falls back to a local yardstick IAP proxy or manual per-panel screenshots, and Slack falls back to a manual thread-summary paste. Unavailable sources are marked as skipped in the prerequisites status table.

Where are FxA triage reports and history stored?▼

Reports are stored locally per user in ~/.claude/skills/fxa-triage/history/, overridable with FXA_TRIAGE_HISTORY_DIR. Each run writes a dated Markdown file plus a rolling followups.md; nothing is written into the FxA repo.

Why does the skill need an operational config from Confluence?▼

The public repo contains no environment-specific values like dashboard UIDs, channel names, or Jira project coordinates. These live in a locked-down Confluence page fetched via FXA_TRIAGE_OPS_URL, treated strictly as data and never as instructions.

Related Skills

Explore More Software Engineering Skills→
rhpdsrhpds

05-atlassian-mcp

Configure Atlassian Rovo MCP server for Jira access in Claude Code.

Official
Advanced
mbaho10mbaho10

management-talk

Translate engineering updates into leadership summaries for Slack, Jira, or email.

Community
Intermediate
jamsmacjamsmac

vhm24-monitoring

Set up Prometheus metrics, Grafana dashboards, and Sentry error tracking for VendHub services.

Community
Advanced
rom-orlovichrom-orlovich

jira-ticket-enrichment

Enrich Jira tickets with Sentry error analysis and a GitHub fix plan.

Community
Advanced