Search for existing cases related to specific indicators or entities. Use to find correlation with other investigations before starting new analysis. Takes search terms and returns matching case IDs.
Install with Tessl CLI
npx tessl i github:dandye/ai-runbooks --skill find-relevant-case75
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Identify existing cases that may be related to the current investigation based on IOCs, hostnames, usernames, or other entities.
SEARCH_TERMS - List of values to search for (e.g., ["198.51.100.10", "mikeross-pc", "jsmith"])CASE_STATUS_FILTER - Filter by status: "Opened", "Closed" (default: "Opened")TIME_FRAME_HOURS - Lookback period for case creation/updateMAX_RESULTS - Maximum cases to returnBuild a filter for list_cases based on search terms and filters.
Note: The list_cases tool may have limited ability to search within case entities. If direct entity search isn't supported, use broader filters and refine results.
secops-soar.list_cases(
filter=constructed_filter,
limit=MAX_RESULTS
)Extract case IDs and basic details (DisplayName, Priority) from results.
If too many results, use get_case_full_details on a subset to verify entity presence:
secops-soar.get_case_full_details(case_id=candidate_case_id)| Output | Description |
|---|---|
RELEVANT_CASE_IDS | List of case IDs that match the search |
RELEVANT_CASE_SUMMARIES | Brief summaries (ID, name, priority) |
FIND_CASE_STATUS | Success/failure status of the search |
The list_cases tool may not support direct entity searching. Alternatives:
67a00be
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.