add-opportunity-config-fieldAdd a new field to opportunity configs in the workflows admin panel. Use when asked to add a new config field, property, or attribute to the workflows opportunity configuration system.
commitCommit uncommitted changes with clear commit messages. Use when the user
create-workflow-epicCreate a complete workflow initiative with an epic, core workflow sub-issues,
create-pulse-data-issuesFile issues and tasks for the pulse-data repository. Use when the user asks to file, create, or track issues, tasks, tickets, or TODOs. Defaults to filing in Linear (which two-way-syncs to GitHub) and lets you set Linear-specific fields like project and milestone; falls back to filing directly in Gi
find_case_note_anecdotesFind illustrative anecdotes from supervision case notes for a given topic.
find_recidiviz_implicated_peopleFind people implicated by Recidiviz tools, in two modes. Cohort mode — given a
investigate-airflow-failureDiagnose a failed Airflow task running on Cloud Composer by pulling task logs from GCS, identifying the first real error in the traceback, and inspecting the task's source and recent git history. Use when the user wants to investigate an Airflow task failure (e.g. "why did X task fail", "investigate
investigate-pd-incidentInvestigate a PagerDuty incident by fetching it via the PagerDuty MCP server, classifying the alert type, and dispatching to the appropriate specialist skill. Use when the user provides a PagerDuty incident URL or ID (e.g. "investigate this PD alert", "what's going on with incident Q09D28GV4W96FQ",
investigate-pg-ticketInvestigate a GitHub bug ticket by fetching PII from the ticket's private PII
investigate-stable-counts-failureInvestigate a stable counts validation failure for a state supervision or incarceration period table by identifying which fields changed and why. Use when a stable counts validation is failing or has recently failed for a state entity (e.g. "why is the NC stable counts failing", "investigate stable
maintain-claude-md-documentationProactively update CLAUDE.md documentation when it becomes outdated or incorrect. Use when you notice documented commands, paths, or patterns don't match the actual codebase, when making code changes that invalidate documentation, or when user corrects stale information.
maintain-skill-filesProactively update SKILL.md files when they become outdated, incorrect, or need improvements. Use when you notice a skill doesn't match current workflow, when user corrects your skill usage, or when discovering better practices that should be documented.
notebook-to-google-docTurn a finished analysis notebook into a Google Doc write-up with the standard Summary / Background / Findings format. Use when the user asks to write up a notebook, create a doc from an analysis, share findings as a Google Doc, or turn notebook results into a document for a wider audience.
pollen-view-structureUse this skill when a user wants to structure BigQuery views into the standard Pollen view pattern. All Pollen analysis is in the research/notebooks/policy folder -- do not apply this skill outside that folder. Triggers include: "structure my views", "create view files", "pull views from my notebook
post-github-validation-commentPost a validation comment to a GitHub PR or issue using the standard format. Use when the user asks to post a comment to a PR or issue, post sandbox or ingest validation results, share validation findings on a PR or ticket, or anything similar that involves posting validation results as a GitHub com
tx_critically_understaffedupgrade-cloud-composerUpgrade Cloud Composer (Apache Airflow) to a new version. Use when the user asks to upgrade, update, or bump Airflow, Cloud Composer, or Airflow dependencies to a new version. Handles updating terraform config and Python dependencies.