project-analyzerlisted

# Project Analyzer Analyze another Claude project against the full Cluide guide set and write a single, reviewable improvement plan (`CLUIDE_IMPROVEMENT_PLAN.md`) into that project. Read-only on the target except for that one file; it produces a reviewed plan and **stops** — it does not implement changes. > **This skill is a thin router.** The full procedure lives in `tasks/analyze-project.md` and its > criteria/template in `tasks/analyze-project-reference.md`. Do not duplicate that logic here — run the > task and follow it. Keeping a single source of truth avoids the bundled-copy drift that > `tasks/review-tasks.md` checks for. ## Rules > **Clarifying questions:** For any step with a fixed set of options, use `AskUserQuestion` with buttons > instead of plain text. - This skill must run from a **Cluide checkout** — the analysis criteria reference the root guides (`00_INDEX.md` and the numbered guides). If the guides aren't present in the working context, locate the Cluide repo, or tell the user to run this from Cluide, and stop. - Plan-only: never edit the target's `CLAUDE.md`, skills, tasks, settings, or config. The only write is `CLUIDE_IMPROVEMENT_PLAN.md` at the target root. - Never copy secret or credential **values** into the plan — reference their location only. ## What to do 1. Read `tasks/analyze-project.md` and execute it end-to-end (Steps 0–6): locate the target (local folder or GitHub repo) → inventory and detect type → clarify intent → analyze aga