Skills for “ci”

…this skill when designing or refactoring content types, deciding field shapes, debating reusable versus nested content, planning omnichannel content models, or reviewing whether a schema is too page-shaped or…

…failures; asks about batch testing, regression suites, or CI/CD test integration; requests security testing, OWASP LLM Top 10, red-teaming, penetration testing, prompt-injection tests, a security grade, or a…

…alerts have fired (notification counts, or the per-alert Incidents view). DO NOT TRIGGER when: user creates, modifies, or debugs .agent files during development (use agentforce-generate); writes or runs test specs (use…

Reliability trend summary for a service, team, or the whole org. Reports incident volume, severity mix, and MTTR direction over a window (default 30 days). Use for standups, 1-on-1s, or quarterly reviews.

…based on availability, and creates an override after explicit confirmation. Write action - never executes without…

Show a compact service health overview including active incidents by severity. Use for a quick health check of your services.

[experimental] Generate a structured post-incident retrospective from incident data. Forked-subagent flow may not have MCP access in all Claude Code contexts.

[experimental] Investigate and respond to a production incident. Pulls context, finds similar past incidents, suggests solutions, and enables coordination. Forked-subagent flow may not have MCP access in all Claude Code…

Personal Rootly dashboard. Shows your open action items, your active incidents (where you're a responder), and your upcoming on-call shifts. Use to start the day or to context-switch back into incident work.

Look up a service, team, or catalog entity in Rootly. Returns owner, on-call, recent reliability, dependencies, and any active incidents. Use when something breaks and the first question is who owns this.

Prepare an incident or on-call handoff document. Creates structured summary for shift changes or incident commander transitions.

[experimental] Evaluate deployment risk by analyzing code changes against incident history, active incidents, and on-call readiness. Forked-subagent flow may not have MCP access in all Claude Code contexts.

…shifts on a team or schedule and creates an override placing you on the chosen one after explicit confirmation. Write action - never executes without…

Generate a concise stakeholder brief for an incident. Creates executive summary with key details, impact, timeline, and current status.

Ask natural language questions about incidents, on-call, services, and reliability data. Translates your question into Rootly API calls and returns structured answers.

Draft a stakeholder-facing status update for an active incident, then post it after explicit confirmation. Useful for incident commanders pushing public-status-page or internal updates without opening the Rootly UI.…

…timeline, related alerts in the same group, and any incident the alert is attached to. Use when a page comes in and you want context before opening…

Manage incident action items from the terminal. Subcommands - list (default - your open action items) or add <incident> "<summary>" (create one on an incident). Use to capture follow-ups during or after an incident…

…Paywall in the dashboard — including questions about a specific paywall or general paywall design recommendations, and uploading images or fonts to paywall resources / the Media Gallery. Not for presenting a paywall…

…Package Manager, on native iOS, Flutter, React Native, Capacitor, Unity, or…