--- title: "GEO + Crew hook bundles, auto-audit content edits, auto-activate persona on session start | Recipe — StudioMeyer Academy" description: "Stop hook with file-pattern filter triggers GEO audit when you edit markdown. SessionStart hook activates the right Crew persona based on cwd. Two bundles, two MCPs, both production-ready." canonical: "https://studiomeyer.academy/en/recipes/16.4-geo-crew-hook-bundle" language: en markdown_versions: ["https://studiomeyer.academy/en/recipes/16.4-geo-crew-hook-bundle.md"] publisher: "StudioMeyer Academy, https://studiomeyer.academy (llms.txt: https://studiomeyer.academy/llms.txt)" --- [← Alle Recipes](https://studiomeyer.academy/recipes) Phase 16 · Claude Code Hooks·6 steps # GEO + Crew hook bundles, auto-audit content edits, auto-activate persona on session start Stop hook with file-pattern filter triggers GEO audit when you edit markdown. SessionStart hook activates the right Crew persona based on cwd. Two bundles, two MCPs, both production-ready. 6 steps0% Du liest ohne Account. Mit [Login](https://studiomeyer.academy/login?next=/recipes/16.4-geo-crew-hook-bundle) speichern wir Step-Fortschritt + Notes. # GEO + Crew hook bundles, auto-audit content edits, auto-activate persona on session start Two more SaaS-MCP bundles, similar pattern. GEO does AI-visibility scoring across LLMs (`geo.studiomeyer.io`, 24 tools). Crew is persona-switching (`crew.studiomeyer.io`, 10 tools, 8 personas). Both have one obvious hook each. ### Step 1: GEO, Stop hook with file-filter triggers audit When you edit content (markdown files in `/blog`, `/recipes`, `/lessons`, etc.), you should know if the edit improved or hurt your AI-visibility score. The Stop hook with an `if`\-filter on `*.md` and `*.mdx` does exactly that: ```json { "Stop": [ { "hooks": [ { "type": "mcp_tool", "server": "studiomeyer-geo", "tool": "geo_check", "input": { "url": "https://studiomeyer.academy", "brand": "StudioMeyer Academy" }, "timeout": 60, "statusMessage": "GEO: auto-audit after content edit..." } ], "if": "Edit(*.md|*.mdx)|Write(*.md|*.mdx)" } ] } ``` The `if`\-filter ensures the hook only fires on Stop AFTER an Edit/Write to a markdown file in the session. Pure code edits don't trigger a GEO check. `geo_check` queries 8 LLM platforms (Claude, GPT, Gemini, Perplexity, Grok, Copilot, Bing, You.com) for brand mentions on the given URL and returns a 0-100 score. Default mode: `training` (uses LLM training-data recall, free). For native web-search, swap to `mode: "search"` (costs $0.30-0.50/run depending on provider). ### Step 2: GEO, UserPromptSubmit on visibility questions Less aggressive than Memory's auto-recall: only fire `geo_simulate` when the user explicitly asks about visibility: ```json { "UserPromptSubmit": [ { "hooks": [ { "type": "command", "command": "~/.claude/hooks/geo-trigger-check.sh", "timeout": 3 } ] } ] } ``` Where `geo-trigger-check.sh` is a small bash hook: ```bash #!/usr/bin/env bash input=$(cat) prompt=$(echo "$input" | jq -r '.prompt // .user_prompt // ""') if echo "$prompt" | grep -qiE 'how visible|visibility|geo score|cited by|llm cite'; then echo '{"hookSpecificOutput":{"additionalContext":"GEO context: if checking visibility, call geo_simulate(url) for a free zero-key estimate or geo_check(url, brand) for full LLM coverage."}}' fi ``` Why bash and not `mcp_tool`? Because `geo_simulate` needs a URL parameter that we cannot reliably parse from the user prompt. Better to inject context that nudges the assistant to call the tool with the right arguments. ### Step 3: Crew, SessionStart activates default persona per project Different projects, different personas. The Crew bundle picks the right one automatically based on cwd: ```json { "SessionStart": [ { "hooks": [ { "type": "command", "command": "~/.claude/hooks/crew-auto-persona.sh", "timeout": 5 } ] } ] } ``` Where `crew-auto-persona.sh` maps directory patterns to personas: ```bash #!/usr/bin/env bash cwd="${PWD:-$(pwd)}" case "$cwd" in *studiomeyer*|*academy*|*nex-hq*) persona="cto" ;; *aklow*|*kunden*) persona="pm" ;; *blog*|*content*) persona="cmo" ;; *legal*|*agb*|*datenschutz*) persona="legal-advisor" ;; *) persona="cto" ;; esac cat <