opentide-detection-objective

Defines structured detection objectives for mapping between threats and MDR rules.

4|1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/OpenTideHQ/AgentTide --skill opentide-detection-objective
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opentide-detection-objective
Source: https://github.com/OpenTideHQ/AgentTide/tree/main/skills/opentide-detection-objective
Command: npx skills add https://github.com/OpenTideHQ/AgentTide --skill opentide-detection-objective

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenTide Detection Objectives (DOM) provide a structured way to define detection goals bridging threat modelling and deployable detection rules, ensuring coverage traceability and reduced duplication.

Core Features & Use Cases

  • Defines top-level objective with priority, threat links, and signal composition for MDR
  • Establishes data requirements, signal taxonomy, and ATT&CK mapping alignment
  • Helps teams plan and refactor detection coverage before writing rules, with traceability to TVMs and MDRs example usage across detection programs like MDR deployments

Quick Start

Create a DOM by specifying an objective with a priority, linked TVMs, and signals that describe required data and ATT&CK mappings.

Frequently Asked Questions about opentide-detection-objective

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are detection objectives in threat modelling and MDR?

Detection objectives are structured goals that bridge threat modelling and MDR rule development by defining priority, threat links, and signal composition to ensure coverage traceability and reduce duplication across detection programs.

How do I structure detection coverage before writing MDR rules?

Structure detection coverage by defining a top-level objective with priority, linked TVMs, and signals that describe required data and ATT&CK mappings, ensuring traceability to threat models and MDR deployments.

How does ATT&CK mapping align with detection objectives?

ATT&CK mapping aligns with detection objectives through the signal taxonomy, where each signal describes required data and maps directly to specific ATT&CK techniques to maintain threat coverage traceability.

Can I link threat models to MDR rule development using detection objectives?

Yes, detection objectives bridge threat modelling and MDR rule development by establishing traceability links to TVMs and MDRs, ensuring data requirements and signal composition map directly to defined threat coverage.

What fields are required to define a detection objective?

Required fields include name, description, metadata, objective, signals, references, and traceability links to TVMs and MDRs to enforce structured detection planning and reduce duplicated rules.