correlate-findings

Computes the delta between security audit runs and records a run summary in a SQLite journal.

2|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/odysseyalive/claude-watchman --skill correlate-findings-odysseyalive
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: correlate-findings
Source: https://github.com/odysseyalive/claude-watchman/tree/main/skills/logic/correlate-findings
Command: npx skills add https://github.com/odysseyalive/claude-watchman --skill correlate-findings-odysseyalive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repeated security audits produce the same findings over and over, making it hard to tell what actually changed. This Skill compares the current audit against the previous run so only genuinely new problems, regressions, and cleared items surface for reporting. ## Core Features & Use Cases - Delta computation: Compares current findings against the previous run using journal timestamps to identify newly-opened findings at or above the notify severity. - Regression detection: Highlights fixed-to-regressed transitions as the highest-signal event, since a fix that came back demands immediate attention. - Profile-aware signals: Applies different delta rules for server versus workstation profiles, including new outbound network destinations and log-retention regressions on workstations. - Run summary recording: Writes a one-line summary of new, regressed, and cleared counts via the journal, which the loop threshold-checks to decide whether to email a report. - Use Case: After running a nightly hardening scan on a Debian server, use this Skill to determine that one previously-fixed SSH configuration issue has regressed and two new medium-severity findings appeared, then record the summary so the reporting step emails you. ## Quick Start Run the correlate-findings step after the observe skills in a watchman audit to compute what changed since the last run and record the run summary.

Frequently Asked Questions about correlate-findings

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

FAQPage Schema
How do I detect what changed between two security audit runs?▼

Run this Skill after the observe skills in a watchman audit. It compares current findings against the previous run using journal timestamps and counts new, regressed, and cleared items in a run summary.

How does security finding deduplication work across repeated scans?▼

Deduplication is automatic through a stable fingerprint upsert in the journal library, so re-running never creates duplicates. This Skill builds on that by computing the delta of what actually changed since the last run.

What is a regression in security audit monitoring?▼

A regression is a finding that transitioned from fixed back to open, meaning a problem you resolved has returned. It is treated as the highest-signal event and surfaced prominently in the run summary.

Does the delta analysis differ between servers and workstations?▼

Yes. Server profiles track regressed findings and new findings at or above the notify severity, while workstation profiles additionally track new outbound network destinations and log-retention regressions.

Can this Skill modify system state during analysis?▼

No. It is read-and-record only, with writes limited to routine journal updates through the journal library. A prime directive forbids any destructive action such as deleting files, modifying databases, or stopping services.