triage-suspicious-login
Triage suspicious login alerts like impossible travel, untrusted location, or multiple failures. Use when investigating authentication anomalies. Analyzes user history, source IP reputation, login patterns, and determines if escalation is needed.
76%
Does it follow best practices?
Impact
89%
1.01x2 of 3 eval scenarios. Add 1 more for a full score.
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./skills/triage-suspicious-login/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
Runtime path reads first-party SOAR case contents via `secops-soar.get_case_full_details(case_id=CASE_ID)` and `secops-soar.list_events_by_alert(...)`, so outsider-authored free text can be ingested if the case events/comments are populated from an external submitter (medium risk).
- 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.