← ClaudeAtlas

ecosystem-auditlisted

Blind audit of the apothem ecosystem — matched when the user asks to 'double check', 'audit', 'verify ecosystem', 'sweep', 'validate ecosystem', 'review configuration', 'check the apothem tree', or any phrasing that asks for a comprehensive validation of the apothem configuration tree as a whole. Detects drift, staleness, orphans, dangling references, conflicting directives, frontmatter invalidity, registry-vs-disk count mismatches, and secret exposure. Optionally applies FIX-class fixes under --fix; ENHANCE / CONSIDER / DEFER classifications surface for operator decision via the structured-inquiry channel. User-invocable directly; also dispatchable from /plan-execute discovery contexts.
Ahmed-G-Gad/apothem · ★ 0 · Code & Development · score 76
Install: claude install-skill Ahmed-G-Gad/apothem
<!-- # SPDX-License-Identifier: MIT # Copyright (c) Ahmed G. Gad ---------------------- # # Website: https://ahmedgad.com # # Email: mailto:me@ahmedgad.com # # Github: https://github.com/ahmed-g-gad # # Licensed under MIT; see LICENSE for terms ------- # --> ## Purpose Execute a blind, fresh audit of the apothem ecosystem. Verify cross-references, registry accuracy, file counts, frontmatter validity, hook alignment, and content quality. Optionally apply FIX-classified findings under `--fix`. ## Detection Signal User requests "double check", "audit", "verify ecosystem", "sweep", "validate ecosystem", "review configuration", or "check the apothem tree" — any phrasing that asks for a comprehensive validation of the apothem configuration tree as a whole. ## Non-Goals The skill carries a deliberately narrow surface. It is NOT: - **Not a fix tool beyond the FIX classification.** Only mechanically-verifiable defects (false claims, broken cross-references, missing files, invalid frontmatter) are auto-applicable under `--fix`. ENHANCE / CONSIDER / DEFER classifications NEVER auto-apply — each requires operator judgment solicited via the structured-inquiry channel. - **Not a refactoring pipeline.** Structural reorganization (renames, moves, registry restructures, taxonomy changes) is OUT of scope. The audit reports the smell; refactoring lands as a separate, operator-driven workstream. - **Not a content generator.** Th