workspace-auditlisted

Audits a WorkOS workspace for drift — misplaced entries, size-ceiling violations, archive candidates, format violations, and engagement-specific content that should cascade to a project. Use when the user says 'workspace audit,' 'audit my workspace,' 'check my CLAUDE.md,' 'check my MEMORY.md,' 'is my workspace healthy,' or when periodically maintaining a WorkOS-style workspace. Distinct from session-audit, which only captures new learnings from the current conversation — this skill audits the workspace files themselves.
dylanmoo/workos-plugin · ★ 0 · Data & Documents · score 72

Install: claude install-skill dylanmoo/workos-plugin

# Starter Workspace Audit A periodic health check for any WorkOS-style workspace. Catches drift before it costs token usage or output quality. ## What This Skill Does Five checks, then a single grouped report. Never writes changes without explicit approval. 1. **Wrong-location check.** Factual entries in `CLAUDE.md` (should move to `MEMORY.md`) and prescriptive entries in `MEMORY.md` (should move to `CLAUDE.md`). 2. **Archive candidacy check.** `MEMORY.md` entries that look historical or stale and should move to `ARCHIVE.md`. 3. **Size ceiling check.** Current line counts vs. target (`CLAUDE.md` target 200–250, max 300; `MEMORY.md` max 150). 4. **Entry format check.** `MEMORY.md` entries longer than two sentences. 5. **Cascade check.** Engagement-, project-, or domain-specific entries in root `MEMORY.md` that should live in a deeper-level `MEMORY.md`. ## Step 1: Discover the Workspace Root Find the WorkOS root dynamically. Look for a `CLAUDE.md` with a Routing Map section in the mounted workspace. That's the root. If the user named a specific project to audit (e.g., "audit my Email HQ project"), audit that one instead of the root. If you can't find a root, stop and tell the user — don't invent structure. ## Step 2: Read the Files For the chosen scope, read: - `CLAUDE.md` - `MEMORY.md` - `ARCHIVE.md` (if it exists) If `ARCHIVE.md` doesn't exist at the root level, flag that as the first finding before running any other check — the WorkOS isn't fully set up and sever