report-status

Generates a plain-language summary of journal findings ranked by priority and status.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw monitoring findings stored in a SQLite journal are hard to act on. This Skill turns the journal into a human-readable status report so operators can immediately see what regressed, what is still open, and what has been fixed or ignored. ## Core Features & Use Cases - Prioritized Summary: Groups findings by status — regressed first, then open items by priority, then tallies of fixed and ignored entries. - Plain-Language Explanations: For each surfaced finding it states what it is, why it matters, its risk tier, and the suggested remediation without jargon. - Trend Reporting: Includes the latest Lynis hardening index, its direction since the last run, and the regression count. - Use Case: After an unattended monitoring cycle on a Linux server, run the report to get a terminal- or email-ready digest of security findings without touching the database directly. ## Quick Start Ask the assistant to run the watchman report and summarize the current journal status, leading with any regressions.

Frequently Asked Questions about report-status

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

FAQPage Schema
How do I get a summary of open security findings on my server?▼

Run the report-status skill, which reads the monitoring journal and prints a plain-language summary. It leads with regressed findings, then open items by priority, followed by counts of fixed and ignored entries.

How to prioritize security findings from a hardening scan?▼

Findings are ordered by the prioritize-redflags ranking, with regressions surfaced first as the loudest signal. Each item includes its risk tier and suggested remediation in plain language.

Does report-status modify the findings database?▼

No, it is strictly read-only. It reads the journal through lib/journal.sh functions via the bash dispatcher and makes no changes; sending email is handled separately by the send-report skill.

Can I use the report output in an email notification?▼

Yes, the output is formatted as plain text suitable for both a terminal and an email body. The send-report skill wraps this output to deliver it by email.

Why does the report show a Lynis hardening index?▼

The report includes the latest lynis_hardening_index metric and its direction since the last run so operators can see the overall hardening trend, alongside the count of regressed findings.