Agent skill · security · google
detection-engineering-coverage-evaluation
Automates the end-to-end detection engineering workflow in Google SecOps using MCP tools. Use when fetching threat intelligence from blogs, generating Threat Detection Opportunities (TDOs), simulating attacker behavior with synthetic UDM events, evaluating rule coverage, and deploying gap-closing rules. Don't use for standalone YARA-L 2.0 rule authoring/tuning (use secops-detection-engineering), threat hunting, or SOC investigation.
Why this skill is useful
Adds a comprehensive automated workflow for evaluating detection coverage and generating new security rules that the AI cannot generate on its own.
What it needs
About 7k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.
What this skill does
SecOps Detection Coverage Skill Routing Note: To author, test (Retrohunt), or tune YARA-L 2.0 detection rules directly, open secops-detection-engineering/SKILL.md. This skill guides the agent through an end-to-end detection engineering lifecycle using Google SecOps MCP tools. It handles multiple Threat Detection Opportunities (TDOs) and ensures exhaustive coverage evaluation for all generated synthetic events. Usage Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read and follow the instructions in Usage Attribution. Workflow Execution Checklist Copy this checklist and track progress for each iteration: [ ] Step 1: Extract raw text content from a source (for example, blog URL or raw text input). [ ] Step 2: Generate Threat Detection Opportunities (TDOs). [ ] Step 3: In parallel, call generate synthetic events for all TDOs. [ ] Step 4: After ALL synthetic events are generated across all TDOs, call evaluaterulecoveragelongrunning in parallel for each TDO, then loop getoperation with a 60-second schedule timer until done is true for all operations. [ ] Step 5: For identified rules, fetch and provide details. [ ] Step 6: Generate new rules ONLY for TDOs confirmed to have zero matching rules in Step 4. [ ] Step 7: Provide a structured summary of findings and gaps. [ ] Step 8: Ask the user to approve adding newly generated rules to their SecOps environment and create them. Detailed Steps 1. Extract Threat Intelligence If the input message contains a URL, use the available web fetching tool or capability to retrieve the HTML or raw text content from that URL. Follow this exact extraction process: 1. Decompose HTML Elements: Remove script, style, nav, footer, and header elements so only the core article text remains. 2. Extract & Normalize Text: Extract the text separating elements clearly and stripping leading/trailing whitespace. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/detection-engineering-coverage-evaluation