peec-checkup

Peec Checkup

Role

Single read-only pass over a Peec project that answers three questions:

1. Setup quality — is the project configured correctly, or are there structural problems holding back every measurement?
2. Brand performance now — where does the brand actually stand, snapshot today?
3. Top improvements — which 5–8 concrete moves would move the needle most, ranked?

No writes. No content production. No outreach. Pure diagnosis + recommendations.

Input

• project_id — Peec project (read from setup_state.json per pre-flight; fallback to mcp__peec-ai__list_projects if state missing)
• optional date_range — default last 28 days (falls back to whatever data exists if project is younger)
• optional top_n — number of improvements to surface, default 5, max 8

Output

One markdown report saved to <project>/checkups/YYYY-MM-DD_checkup.md (schema in §6). Mirrored to stdout for the user. Never modifies setup_state.json or any Peec data.

When to use

• "Wo stehe ich bei Peec?" / "Wie ist mein Status?"
• "Mein Setup checken" / "Was läuft falsch bei meinem Peec-Projekt?"
• "Welche Verbesserungspotenziale gibt es?"
• Onboarding a project from another consultant — first pass to see what was set up
• Periodic ritual: monthly without 4 weeks of action history (use peec-report instead when history exists)
• After someone else changed the Peec project and you want to see what shifted

Do not use when:

• The user wants ONE next action — that is /peec-agent
• The user wants attribution of past actions — that is /peec-report
• The project is empty — that is /peec-setup (full mode)
• The user wants to mutate Peec — every other skill, not this one

---

Pipeline

0. Pre-flight — setup state required (lenient)

Per _shared/SETUP_STATE.md, this skill prefers a state file but does not hard-stop without one — checkup is itself the audit you'd run when state is missing. Logic:

Read <project>/growth_loop/setup_state.json
If present:
  Use peec_project_id, target_country, prompt_language from state.
  Note the setup age in the report.
If missing:
  Resolve project via mcp__peec-ai__list_projects.
  Note in the report: "no setup_state.json — run /peec-setup
  (mode: import) after this checkup to persist findings."
  Default target_country=DE, prompt_language=de UNLESS the user said otherwise.