triage-alert
Triage a security alert or case. Use when given an ALERT_ID or CASE_ID to assess if it's a real threat. Enriches IOCs, searches SIEM for context, and determines if the alert should be closed (false positive) or escalated for investigation.
74%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./skills/triage-alert/SKILL.mdW011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
In Step 1 the workflow retrieves full case/alert details (and related alerts/events) via secops-soar tools like `get_case_full_details(case_id)`, `list_alerts_by_case(case_id)`, and `list_events_by_alert(alert_id)`, which necessarily includes free-text fields from outsider-authored alert/case content that can be injected through the monitored case/alert inputs.
- Repository
dandye/ai-runbooks
- Revision
72a6863
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.