PagerDuty オンコールカバレッジ監査

# PagerDuty On-Call Coverage Audit

Audit PagerDuty schedules, current and upcoming on-call assignments, and escalation-policy coverage for operational gaps.

## Required Aident Actions

- <action-tag>composio:pagerduty_tools:pagerduty_get_schedules</action-tag> (required inputs: inspect the current schema): Retrieves a list of all schedules from your PagerDuty account. This endpoint provides essential information about on-call rotations, helping teams manage and organize their incident response workflows. Use this when...
- <action-tag>composio:pagerduty_tools:pagerduty_retrieve_oncall_list</action-tag> (required inputs: inspect the current schema): Retrieves the current on-call information for your PagerDuty account. This endpoint provides a comprehensive view of who is currently on-call across various schedules and escalation policies. It's particularly useful...
- <action-tag>composio:pagerduty_tools:pagerduty_fetch_escalation_polices_list</action-tag> (required inputs: inspect the current schema): Retrieves a list of escalation policies configured in the PagerDuty account. This endpoint allows users to access detailed information about how incidents are escalated within their organization, including the...

Use Aident Loadout to read the current Action schema before constructing inputs. Check the required integration connection in Aident Vault. If an Action is billable or mutating, run Aident preflight, show the affected target and quoted cost or risk, and wait for explicit user confirmation before execution.

## Workflow

1. Confirm the requested outcome, source material, destination, audience, constraints, and acceptance criteria.
2. Apply the source-derived guidance below to create a concrete plan. Resolve ambiguity before invoking an Action.
3. Select only the Aident Actions whose documented effect directly advances the requested outcome. Do not invoke every listed Action by default.
4. Inspect the current schema and prepare the minimum valid input for each selected Action.
5. Preflight each selected Action. Execute it only after any required confirmation, in dependency order, and carry returned IDs or asset URLs into later steps.
6. Verify the returned IDs, URLs, statuses, or artifacts against the acceptance criteria. Report partial completion precisely and do not repeat paid or mutating calls blindly.

## Source-Derived Guidance

- Confirm the PagerDuty team or service scope and the review time window before reading operational coverage.
- Use composio:pagerduty_tools:pagerduty_get_schedules to inventory the schedules in scope.
- Use composio:pagerduty_tools:pagerduty_retrieve_oncall_list to inspect current and upcoming assignments for the approved time window.
- Use composio:pagerduty_tools:pagerduty_fetch_escalation_polices_list to cross-check escalation coverage.
- Report uncovered periods, missing escalation paths, and concentrated rotation burden with schedule evidence; do not change assignments or policies.

## Execution Boundaries

- Treat upstream provider-specific commands as background knowledge only. Execute the workflow through the exact Aident Actions above.
- Never request raw credentials in chat. Use Aident Vault connection flows for required accounts.
- Preserve user-provided wording, brand constraints, rights restrictions, and target identifiers. Do not invent authorization.
- Read current state before a mutation, state the exact target, and include a rollback or recovery step in the result.
- Stop when a required integration is disconnected, preflight rejects the input, the target is ambiguous, or the user declines a required confirmation.

## Output

Return the execution plan, selected Action names, confirmed targets, Aident result identifiers or asset URLs, verification evidence, and any remaining blocked step.

## Attribution

This Skill adapts the reviewed upstream workflow. See [UPSTREAM.md](UPSTREAM.md) for the pinned source and [LICENSE.txt](LICENSE.txt) for the preserved license.