From pagerduty
Full CRUD operations for PagerDuty services, integrations, and configuration
npx claudepluginhub infiquetra/infiquetra-claude-plugins --plugin pagerdutyThis skill uses the workspace's default tool permissions.
You are helping the user manage PagerDuty services and integrations through natural language interactions.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes competition with Porter's Five Forces, Blue Ocean Strategy, and positioning maps to identify differentiation opportunities and market positioning for startups and pitches.
You are helping the user manage PagerDuty services and integrations through natural language interactions.
Verify the PAGERDUTY_API_KEY environment variable is set:
echo $PAGERDUTY_API_KEY
# List all services for Infiquetra team (defaults to YOUR_TEAM_ID)
python plugins/pagerduty/skills/pagerduty-incidents/scripts/pagerduty_client.py services list
# List services for a specific team
python plugins/pagerduty/skills/pagerduty-incidents/scripts/pagerduty_client.py services list --team-id PXXXXX
# Search services by name
python plugins/pagerduty/skills/pagerduty-incidents/scripts/pagerduty_client.py services list --query "wallet"
Filters:
--team-id: Filter by team ID (defaults to Infiquetra team YOUR_TEAM_ID)--query: Search by service name or descriptionpython plugins/pagerduty/skills/pagerduty-incidents/scripts/pagerduty_client.py services get --id PXXXXX
Returns complete service information:
# Basic service creation (uses Infiquetra default escalation policy YOUR_POLICY_ID)
python plugins/pagerduty/skills/pagerduty-incidents/scripts/pagerduty_client.py services create \
--name "vehicle-checkout-service" \
--description "Vehicle checkout and handoff service"
# With custom escalation policy
python plugins/pagerduty/skills/pagerduty-incidents/scripts/pagerduty_client.py services create \
--name "identity-verification-service" \
--description "Identity verification and KYC service" \
--escalation-policy-id PYYYYY
Parameters:
--name: Service name (required)--description: Service description (optional)--escalation-policy-id: Escalation policy (defaults to Infiquetra policy YOUR_POLICY_ID)# Update service name
python plugins/pagerduty/skills/pagerduty-incidents/scripts/pagerduty_client.py services update \
--id PXXXXX \
--name "wallet-service"
# Update description
python plugins/pagerduty/skills/pagerduty-incidents/scripts/pagerduty_client.py services update \
--id PXXXXX \
--description "Digital wallet and payment service for vehicle custody"
# Change escalation policy
python plugins/pagerduty/skills/pagerduty-incidents/scripts/pagerduty_client.py services update \
--id PXXXXX \
--escalation-policy-id PYYYYY
⚠️ Warning: Deleting a service removes all associated incidents and integrations.
python plugins/pagerduty/skills/pagerduty-incidents/scripts/pagerduty_client.py services delete --id PXXXXX
Always confirm with user before deleting and consider:
User: "Show me all Infiquetra services"
Response:
User: "Find services related to wallet"
Response:
--query "wallet"User: "Create a new service for the identity verification feature"
Response:
User: "Update wallet-service to use the new on-call policy"
Response:
User: "Show me which services are using the old escalation policy"
Response:
After creating a service, guide integration setup:
Service created: identity-verification-service (PXXXXX)
Next steps for CloudWatch integration:
1. Get service integration key from PagerDuty
2. Configure CloudWatch alarm action:
- SNS topic → PagerDuty endpoint
- Integration key in URL
3. Test with sample alarm
4. Verify incident creation
For custom monitoring tools:
Service created: wallet-service (PXXXXX)
API integration setup:
1. Create integration: Services → wallet-service → Integrations → Add
2. Select "Events API v2"
3. Copy integration key
4. Add to Lambda Powertools configuration:
POWERTOOLS_SERVICE_NAME: wallet-service
PAGERDUTY_INTEGRATION_KEY: <integration-key>
5. Test with: aws lambda invoke --function-name <name> --payload '{}'
For email-based alerts:
Service created: checkout-service (PXXXXX)
Email integration (auto-generated):
1. Service email: checkout-service@example.pagerduty.com
2. Add to monitoring tool alert destinations
3. Test: Send email with subject containing "CRITICAL" or "WARNING"
4. Verify incident creation
When viewing services, correlate with SLED components:
Found 5 Infiquetra services:
- wallet-service (PXXXXX) → SLED component CI2408590
- identity-service (PYYYYY) → SLED component CI2408591
- checkout-service (PZZZZZ) → SLED component CI2408592
Dependencies:
- checkout-service depends on wallet-service and identity-service
- Incidents in wallet-service may affect checkout-service
Summarize service health:
{
"team": "Infiquetra (YOUR_TEAM_ID)",
"services": {
"healthy": 3,
"warning": 1,
"critical": 1
},
"critical_services": [
{
"name": "wallet-service",
"id": "PXXXXX",
"open_incidents": 2,
"status": "critical",
"last_incident": "2026-02-26T14:30:00Z"
}
],
"recommendations": [
"Check wallet-service - multiple open incidents",
"Review identity-service escalation policy - using deprecated policy"
]
}
Compare service configurations:
Escalation Policy Audit:
✓ 3 services using current policy (YOUR_POLICY_ID)
⚠ 2 services using deprecated policy (P0G40L1)
- legacy-service (PXXXXX)
- old-api-service (PYYYYY)
Recommendation: Update deprecated services to YOUR_POLICY_ID
Enforce Infiquetra naming standards:
Service name suggestion:
- Current: "Wallet API"
- Recommended: "wallet-service"
- Reason: Follows Infiquetra kebab-case convention, includes '' prefix
Update service name? (y/n)
When creating a service, provide a complete checklist:
✓ Service created: checkout-service (PXXXXX)
Setup checklist:
[ ] Configure CloudWatch integration
[ ] Set up API integration key in Lambda
[ ] Add service to SLED component registry
[ ] Document service in Dev Hub
[ ] Test incident creation flow
[ ] Add service to team runbook
[ ] Configure auto-resolution rules
[ ] Set up alert grouping
When deleting a service, ensure safe deprecation:
Service deletion safety check for wallet-service (PXXXXX):
⚠ Open incidents: 2 (resolve first!)
⚠ Active integrations: 3 (cleanup required)
✓ No recent incidents (30 days)
Recommended steps:
1. Resolve/reassign open incidents
2. Disable integrations
3. Remove from monitoring tools
4. Update documentation
5. Archive in SLED
6. Delete service
Proceed? (y/n)
After creating a service:
Service created: wallet-service (PXXXXX)
Would you like to:
1. Link to existing SLED component
2. Create new SLED component
3. Skip (link later)
Recommended: Link to CI2408590 (wallet-service)
For feature-related services:
Service created for new feature: vehicle-handoff-service
Would you like to:
1. Link to Rally story/epic
2. Create implementation checklist in Rally
3. Add service details to PRR documentation
Duplicate Service Name:
{
"error": true,
"message": "Service with name 'wallet-service' already exists",
"status_code": 400
}
Solution: Use a unique name or update existing service
Invalid Escalation Policy:
{
"error": true,
"message": "Escalation policy PXXXXX not found",
"status_code": 404
}
Solution: List escalation policies to find valid ID
Service Not Found:
{
"error": true,
"message": "API error: 404",
"status_code": 404
}
Solution: Verify service ID with services list
wallet-servicevehicle-checkout not checkoutAll commands return JSON:
{
"success": true,
"data": {...},
"message": "Optional success message"
}
See references/ directory for:
pagerduty-api.md: Complete PagerDuty API v2 referenceservice-configuration.md: Service setup and integration guidesservices.md: Infiquetra service catalog and policies