nightly-audit

Scan workspace state and report anomalies with remediation steps.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/ysgdepaula/x-deep-os --skill nightly-audit-ysgdepaula
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nightly-audit
Source: https://github.com/ysgdepaula/x-deep-os/tree/main/.claude/skills/nightly-audit
Command: npx skills add https://github.com/ysgdepaula/x-deep-os --skill nightly-audit-ysgdepaula

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Nightly audit of the workspace state to identify gaps, inconsistencies, and improvement opportunities across agents, skills, memory, config, and code.

Core Features & Use Cases

Core features include automated state validation, cross-checking with the changelog and queue, detection of stale rules, memory hygiene checks, and generation of a compact report with concrete remediation steps.

Quick Start

Run the nightly-audit to scan the workspace and generate an actionable improvement report.

Frequently Asked Questions about nightly-audit

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

FAQPage Schema
How do I automate a nightly workspace audit to find inconsistencies?

A nightly workspace audit scans state files like .agent/state.json and rules.md to detect inconsistencies. It cross-checks agents, skills, memory, config, and code against recent changes to surface anomalies and generate actionable remediation steps.

What is workspace state validation and how does it detect stale rules?

Workspace state validation checks configuration files such as .agent/rules.md and queue.md against the changelog to identify stale rules. It verifies workspace consistency by surfacing gaps in memory, code, and agent configurations during an automated scan.

Can I check my changelog and queue for workspace hygiene issues automatically?

Yes, you can check workspace hygiene by cross-referencing the changelog and queue.md with the current workspace state. The audit detects memory hygiene issues, configuration gaps, and outdated rules, outputting a compact report with concrete remediation steps.

What's the best way to monitor agent state and memory for anomalies overnight?

Monitoring agent state overnight requires scanning .agent/state.json and memory configurations to identify anomalies. The nightly audit proposes actionable improvements by validating workspace consistency and detecting gaps across agents and code.

Does nightly workspace auditing require any external dependencies or components?

Nightly workspace auditing requires no external dependencies or components to operate. It runs independently to scan workspace files and configurations, relying solely on internal state files like .agent/state.json, rules.md, queue.md, and the changelog to generate reports.

When should I not use an automated workspace audit?

Automated workspace audits are not suitable for real-time error detection during active development sessions. They are designed for nightly batch processing to identify accumulated gaps, stale rules, and inconsistencies across the entire workspace state rather than immediate code validation.