audit

Audit Founder OS ecosystem readiness, linting, wiki graph, brain staleness, and voice completeness.

2|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/ARCASSystems/FounderOS --skill audit-arcassystems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/ARCASSystems/FounderOS/tree/main/skills/audit
Command: npx skills add https://github.com/ARCASSystems/FounderOS --skill audit-arcassystems

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of understanding the overall health of the Founder OS ecosystem with a single, at-a-glance report, providing clear actions to improve system health.

Core Features & Use Cases

  • Comprehensive Health Check: Audits readiness, linting, wiki graph state, brain staleness, and voice completeness in one report.
  • Real-time Insights: Offers immediate feedback on the current health status of the OS.
  • Use Case: After a sprint roll, use this Skill to ensure that daily-anchors and the brain log are up-to-date, and that the OS is functioning optimally.

Quick Start

Run the 'audit the OS' command to generate a comprehensive health report.

Frequently Asked Questions about audit

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

FAQPage Schema
What is an OS health check and what does it cover?

An OS health check assesses system readiness, code linting, wiki graph integrity, brain staleness, and voice completeness. It generates a comprehensive report providing clear actions to improve the ecosystem's overall health.

How do I run a system maintenance audit after a sprint?

Run the audit command to perform a full system maintenance audit. This verifies that daily-anchors and the brain log are up-to-date, generating a real-time report on OS functioning after a sprint roll.

Do I need special permissions to perform an OS audit?

Yes, performing an OS audit requires access to OS files and execution permissions. This access is necessary to scan readiness, linting, wiki graph state, and voice completeness within the Founder OS environment.

What is the best way to identify issues in my personal OS ecosystem?

The best way to identify issues is running a comprehensive audit that checks system readiness, wiki graph integrity, and brain staleness. It offers immediate feedback and clear actions for system health monitoring.

Why does my system audit report show brain staleness?

Brain staleness appears in the audit report when the brain log is not up-to-date. Running the audit after a sprint roll identifies this issue and provides clear actions to refresh the brain log entries.