filesystem-truth-audit

Name: filesystem-truth-audit
Availability: InStock
Author: HUMANERD

Validate filesystem paths claimed in memory against actual state.

2|7|Updated Jun 19, 2026

Search Tags:#data integrity #audit #diagnostics #filesystem #memory validation

Ready to run

npx skills add https://github.com/humanerd-drew/opencode-drewgent --skill filesystem-truth-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: filesystem-truth-audit
Source: https://github.com/humanerd-drew/opencode-drewgent/tree/main/skills/filesystem-truth-audit
Command: npx skills add https://github.com/humanerd-drew/opencode-drewgent --skill filesystem-truth-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that the 'Done' claims recorded in the memory/vault match the actual state of the filesystem, preventing discrepancies and ensuring data integrity.

Core Features & Use Cases

Filesystem Validation: Checks if 'Done' or 'exists' claims in memory are accurate.
Trigger Scenarios: Responds to suspected discrepancies, root consolidation, rename operations, and new skill/script path references.
Use Case: When a skill is created that requires referencing paths, this skill can be used to verify that the claimed paths exist in the filesystem.

Quick Start

Run the filesystem-truth-audit skill to validate the filesystem against memory claims.

Frequently Asked Questions about filesystem-truth-audit

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

FAQPage Schema

How do I verify filesystem paths claimed in memory records actually exist?▼

A filesystem truth audit validates memory claims by checking if the paths recorded as 'Done' or 'exists' are actually present on the filesystem, detecting discrepancies between vault records and actual storage states.

When do I need to run a filesystem path validation check?▼

You need filesystem path validation after root consolidation, rename operations, or when creating new scripts that reference paths, preventing broken references and ensuring memory records match the actual filesystem state.

What is the best way to audit memory claims against the actual filesystem state?▼

The best way to audit memory claims is to execute a diagnostic validation process that cross-references vault records with actual filesystem paths, automatically detecting and reporting any discrepancies in claimed data integrity.

Does this filesystem audit tool require any external dependencies or scripts to run?▼

No external dependencies are required to run the filesystem audit, as it operates using internal scripts to directly validate filesystem paths against memory claims without needing additional environment setup.

Why does my memory record show a path exists when the filesystem is missing it?▼

Memory records may show paths that are missing from the filesystem due to unlogged rename operations, root consolidation, or moved scripts, which this diagnostic audit detects by validating claimed paths against actual storage.