find-contact
Resolve a 3CX contact or extension by email, extension, or name
Create a new PagerDuty incident on a service
$ npx -y skills add wyre-technology/msp-claude-plugins --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
/create-incidentContext preview
What this command does when you run it.
Create a new PagerDuty incident on a service
description: Create a new PagerDuty incident on a service argument-hint: "<title> <service_name> [urgency] [details]" arguments: [title, service_name, urgency, details]
Create a new incident on a specified service. The incident will be routed through the service's escalation policy, notifying the on-call responder according to urgency-based notification rules.
1. **Resolve the service**
Call `list_services` with `query` set to the provided `service_name`. If multiple services match, present them and ask the user to clarify. Extract the service ID.
2. **Confirm the on-call responder**
Call `list_oncalls` filtered by the service's escalation policy to show who will be notified. Present the on-call chain so the user can confirm before creating.
3. **Create the incident**
Call `create_incident` with:
4. **Confirm creation**
Display the created incident number, ID, title, service, urgency, and assigned responder.
5. **Provide next steps**
Suggest monitoring the incident with `/incident-triage` and checking the on-call responder's acknowledgement status.
| Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| | title | string | Yes | | Short summary of the incident | | service_name | string | Yes | | Name of the service to create the incident on | | urgency | string | No | high | Urgency level (high, low) | | details | string | No | | Detailed description of the incident |
/create-incident --title "Payment processing failures" --service_name "Payment API"
/create-incident --title "Elevated latency on search" --service_name "Search Service" --urgency low --details "P99 latency increased from 200ms to 800ms starting at 14:00 UTC. No errors, just slowness."
One command to supercharge Claude Code for MSP workflows. Then restart Claude Code. That's it. Documentation: mcp.wyre.ai
Repo: wyre-technology/msp-claude-plugins
Resolve a 3CX contact or extension by email, extension, or name
Search for specific threat patterns in Abnormal Security by sender, recipient, attack type, or keywords
Triage recent email threats detected by Abnormal Security by severity and attack type