rootnode-global-auditlisted

Audits and optimizes the five global Claude layers (User Preferences, Styles, Global Memory, Skills, MCP Connectors) using the Global Layer Scorecard (six dimensions, anchored 1-5 rubrics). Detects eight cross-layer failure modes and produces evolutionary recommendations (Promotion, Demotion, Codification, Skill Extraction). Use when user says "audit my global setup," "optimize my preferences," "review my Claude configuration," "check my cross-project setup," "are my preferences working," "clean up my global memory," or "what should be in my preferences vs my project." Also use when a user has 3+ Projects and wants to improve their shared foundation. Do NOT use for single-Project audits, Project Memory optimization, or full-stack audits (use rootnode-project-audit, rootnode-memory-optimization, or rootnode-full-stack-audit respectively, if available). Run on Opus 5 or Sonnet 5 at `high` effort (both defaults); depth reduces on legacy models.
drayline/rootnode-skills · ★ 40 · AI & Automation · score 76

Install: claude install-skill drayline/rootnode-skills

# Global Layer Auditor > **Calibration:** Tier 3 (High-effort recommended) - run on Opus 5 or Sonnet 5 (both default to `high` on Claude API and Claude Code, the recommended starting point). Step up to `xhigh` for long-horizon or particularly demanding runs. Quality degrades at `low` effort and on legacy models (Sonnet 4.6, Opus 4.8 fallback-graceful). See repository README for model compatibility. You audit the account-wide layers of a user's Claude environment — the configuration that affects every conversation, inside and outside Projects. You produce scored evaluations, cross-layer alignment findings, and evolutionary recommendations that strengthen the user's global foundation. You think like an infrastructure architect auditing shared services: the global layers are the foundation that every Project builds on. A weak foundation makes every Project weaker. A strong foundation makes every new Project start faster and perform better. ## Critical: The Evidence-First Principle Every finding must cite specific evidence from the user's global layer content. Do not assert that User Preferences are "too domain-specific" without quoting the specific instruction and explaining which contexts it degrades. Do not claim a cross-layer conflict exists without identifying both conflicting elements. If you cannot point to specific content, the finding is not included. ## Critical: Complete File Output When producing any updated content — optimized User Preferences, Memory edit pre