check-security-currency

Detects stale security updates, outdated threat-intel signatures, and disabled auto-update automation across Linux and macOS.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A hardened server quietly drifts out of date: pending security patches pile up, ClamAV or CrowdSec signatures go stale, and auto-update automation silently turns off. This Skill detects that drift and reports it before attackers exploit the gap. ## Core Features & Use Cases - Freshness Scanning: Checks pending security updates, known-CVE packages (debsecan, arch-audit), and threat-intel freshness (CrowdSec hub, ClamAV signatures, AIDE database) across Debian, RHEL, Arch, and macOS. - Automation Guard: Verifies that auto security-update mechanisms are actually enabled, so a once-configured defense cannot silently turn off. - Regression Alerting: Journals every finding with a stable fingerprint in SQLite, so a defense that goes stale again after being fixed is flagged as a regression and emailed to the operator. - Use Case: During a scheduled /watchman audit, the Skill finds 14 pending security updates and a 30-day-stale ClamAV signature database, journals both as review-tier findings, and proposes the exact update commands for the operator to approve. ## Quick Start Ask the AI to run a security currency check on this machine and report any stale defenses or pending security updates.

Frequently Asked Questions about check-security-currency

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

FAQPage Schema
How do I check for pending security updates on Linux servers?▼

Run the security currency scan, which reads cached package state via the platform resolver (apt, dnf, pacman, or brew) and reports pending security updates as review-tier findings. It never applies updates itself; it proposes the exact command for operator approval.

How to detect stale ClamAV or CrowdSec threat intelligence?▼

The scan stats local threat-intel files, including ClamAV signature databases and CrowdSec hub state, and flags them when they exceed the staleness threshold set by WATCHMAN_SIG_STALE_DAYS. Stale entries are journaled so repeated staleness triggers a regression alert.

Does this work on macOS and different Linux distributions?▼

Yes, it supports Debian/Ubuntu, RHEL-family, Arch, and macOS through cross-platform resolvers. On macOS it checks brew outdated packages, Software Update preferences, and notes that no CVE scanner exists for Homebrew packages.

Will the scan automatically install security updates?▼

No, the Skill is strictly detect-and-propose. It never runs package syncs, installs, or updates; every finding includes the proposed command at review or manual tier, and the operator applies it through the fix workflow.

Why does the scan skip under heavy system load?▼

Package database queries touch disk, so the Skill checks io_should_defer_heavy before scanning. If the machine is under load, it journals a diagnostic_deferred info record and skips the pass to avoid adding I/O pressure.