detection-engineering-behaviour-to-observable — Claude Code skill
detection-engineering-behaviour-to-observable is a Claude Code skill that maps attacker actions to observable telemetry. It activates for sensor-coverage analysis and detection-rule work.
no license ★ 73 updated 2026-11-15
npx skills add W4L33Dx/Cyber-Monster --skill detection-engineering-behaviour-to-observable -a claude-codeWhat detection-engineering-behaviour-to-observable does
The skill helps identify which event fields a sensor emits for a given behaviour, then select a signal that a detection rule can use. It compares telemetry sources and their limits. For instance, a process-access record can include the access mask without carrying the full call stack.
For a sequence of actions, the observable needs both events and the interval between them; a single API call needs an event with its arguments. On Windows, check which Sysmon event IDs the deployed schema includes. If the relevant telemetry is not collected, the result is INCONCLUSIVE (Telemetry Gap), not Clean/Benign.
What it helps with
- map process behaviour to fields emitted by a sensor
- choose a signal that separates malicious activity from legitimate use
- spot gaps in telemetry coverage
- identify events to correlate for a multi-step behaviour
Example prompts for the agent
- Find telemetry fields that show one process reading another process’s memory.
- Compare Sysmon events with EDR data for this sequence of actions.
- Work out which events need correlation to detect this behaviour.
How to install detection-engineering-behaviour-to-observable
1Skills CLI (Vercel)
npx skills add W4L33Dx/Cyber-Monster --skill detection-engineering-behaviour-to-observable -a claude-code2Manually: put the files in place
~/.claude/skills/detection-engineering-behaviour-to-observable/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/detection-engineering-behaviour-to-observable/
1Skills CLI (Vercel)
npx skills add W4L33Dx/Cyber-Monster --skill detection-engineering-behaviour-to-observable -a codex2Manually: put the files in place
.agents/skills/detection-engineering-behaviour-to-observable/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add W4L33Dx/Cyber-Monster --skill detection-engineering-behaviour-to-observable -a cursor2Manually: put the files in place
.cursor/skills/detection-engineering-behaviour-to-observable/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install W4L33Dx/Cyber-Monster blue-team/detection-and-monitoring/detection-engineering-behaviour-to-observable2Manually: put the files in place
.github/skills/detection-engineering-behaviour-to-observable/SKILL.md1Skills CLI (Vercel)
npx skills add W4L33Dx/Cyber-Monster --skill detection-engineering-behaviour-to-observable -a gemini-cli2Platform CLI
gemini skills install https://github.com/W4L33Dx/Cyber-Monster --path blue-team/detection-and-monitoring/detection-engineering-behaviour-to-observableManually: put the files in place
.devin/skills/detection-engineering-behaviour-to-observable/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about detection-engineering-behaviour-to-observable
How do I install detection-engineering-behaviour-to-observable in Claude Code?
Run npx skills add W4L33Dx/Cyber-Monster --skill detection-engineering-behaviour-to-observable -a claude-code. The skill file is at ~/.claude/skills/detection-engineering-behaviour-to-observable/SKILL.md.
What does detection-engineering-behaviour-to-observable do?
It maps attacker actions to events and fields that sensors actually emit, then helps select an observable signal for a detection rule.
How does the skill handle missing telemetry?
When the source for an observable is disabled or not collected, it calls for INCONCLUSIVE (Telemetry Gap) rather than Clean/Benign.