/investigate-finding
Deep investigation of a specific Blumira finding with details, context, and comment history
$ 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.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/investigate-finding
Context preview
What this command does when you run it.
Deep investigation of a specific Blumira finding with details, context, and comment history
Command definition
investigate-finding.mddescription: Deep investigation of a specific Blumira finding with details, context, and comment history
argument-hint: "<finding_id>"
arguments: [finding_id]
Investigate Finding
Prerequisites
- Valid Blumira JWT token configured
- A finding ID to investigate
Steps
1. Call `blumira_findings_get` with the provided finding ID to get basic finding data 2. Call `blumira_findings_details` for enriched context, evidence, and recommended actions 3. Call `blumira_findings_comments_list` to retrieve investigation history 4. Present a comprehensive report including:
- Finding summary (severity, status, detection rule, timestamps)
- Detailed evidence and context from the details endpoint
- Timeline of comments and investigation notes
- Recommended next steps based on finding type
5. If finding is Open, suggest assignment or resolution actions
Parameters
| Parameter | Type | Required | Description | |-----------|------|----------|-------------| | finding_id | string | Yes | UUID of the finding to investigate |
Examples
Basic Usage
/investigate-finding --finding_id "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
Error Handling
- **Finding not found:** Verify the ID and suggest using `/finding-triage` to find valid IDs
- **Insufficient permissions:** Check token scope
- **MSP finding:** Suggest using MSP-specific tools with account context
Related Commands
- `/finding-triage` - Find findings to investigate
- `/resolve-finding` - Resolve after investigation
Read more
description: Deep investigation of a specific Blumira finding with details, context, and comment history argument-hint: "<finding_id>" arguments: [finding_id]
Investigate Finding
Prerequisites
- Valid Blumira JWT token configured
- A finding ID to investigate
Steps
1. Call `blumira_findings_get` with the provided finding ID to get basic finding data 2. Call `blumira_findings_details` for enriched context, evidence, and recommended actions 3. Call `blumira_findings_comments_list` to retrieve investigation history 4. Present a comprehensive report including:
- Finding summary (severity, status, detection rule, timestamps)
- Detailed evidence and context from the details endpoint
- Timeline of comments and investigation notes
- Recommended next steps based on finding type
5. If finding is Open, suggest assignment or resolution actions
Parameters
| Parameter | Type | Required | Description | |-----------|------|----------|-------------| | finding_id | string | Yes | UUID of the finding to investigate |
Examples
Basic Usage
/investigate-finding --finding_id "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
Error Handling
- **Finding not found:** Verify the ID and suggest using `/finding-triage` to find valid IDs
- **Insufficient permissions:** Check token scope
- **MSP finding:** Suggest using MSP-specific tools with account context
Related Commands
- `/finding-triage` - Find findings to investigate
- `/resolve-finding` - Resolve after investigation
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
Other commands on msp-claude-plugins.
- /case-review
Review and triage abuse mailbox cases in Abnormal Security
Open command - /search-threats
Search for specific threat patterns in Abnormal Security by sender, recipient, attack type, or keywords
Open command - /threat-triage
Triage recent email threats detected by Abnormal Security by severity and attack type
Open command - /list-overdue-invoices
List open and overdue Alternative Payments invoices and optionally generate hosted payment links for them
Open command - /reconcile-payout
Reconcile an Alternative Payments payout by listing its transactions and matching them against invoices and customers
Open command - /eol-report
EOL/EOS risk report โ devices, OS versions, and firmware approaching or past end-of-life/end-of-support, prioritized by criticality
Open command

