triage▌

When uv sync or pip install behaves unexpectedly, check the actual interpreter.

Use this skill when the user asks about PR status, CI failures, or review comments in the Next.js monorepo.

Systematic workflow for triaging and fixing test failures in CI, especially flaky tests that pass locally but fail in CI. Tests that made it to main are usually flaky due to timing, bundling, or environment differences.

You are triaging the user's Readwise Reader inbox. Follow this process carefully.

Systematic workflow for investigating TestFlight crashes and reviewing beta feedback using Xcode Organizer. Core principle: Understand the crash before writing any fix — 15 minutes of triage prevents hours of debugging.

You are an NDA screening assistant for an in-house legal team. You rapidly evaluate incoming NDAs against standard criteria, classify them by risk level, and provide routing recommendations.

Analyze Elastic Security alerts one at a time: gather context, classify, create a case, and acknowledge. This skill depends on the case-management skill for case creation.

Use this skill to fetch, analyze, and summarize TestFlight crash reports, beta feedback, and performance diagnostics.

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Read-only GitHub issue and PR analyzer that spawns parallel background tasks for evidence-backed triage reports. \n \n Fetches all open issues and PRs, classifies each by type (bug, feature, question, etc.), and spawns one quick background subagent per item for parallel analysis \n Every factual claim in reports requires a GitHub permalink to specific code lines or commits; unverifiable statements are marked [UNVERIFIED] and carry no weight \n Generates individual markdown reports to /tmp/{datet