Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
Tracks session occupancy by logging a timestamp to a file on start, end, and before file-editing tool calls. Writes to disk on each event.
3 events · 4 hooks
Safety signals detected in this hook configuration
Where this hook configuration is defined
Defined in hooks/hooks.json
Event handlers and matchers — expand Raw Configuration for the full JSON
Write|EditFirst, check the file path being written/edited. If the file is NOT inside a marketing plugin directory (skills/, agents/, scripts/, hooks/, .claude-plugin/) AND is NOT marketing deliverable content (ad copy, email content, social posts, blog articles, landing pages, press releases, or branded marketing content being created for the user), respond 'SKIP' immediately. Do NOT check files in the user's own project directories, config files, source code, or non-marketing outputs — those are always SKIP. Only proceed with the check if this IS marketing content being generated as part of a plugin workflow. In that case, and only if a brand profile exists, briefly verify: (1) content aligns with brand voice guidelines, (2) no industry compliance violations, (3) FTC disclosure included if this is influencer/sponsored content, (4) if brand guidelines exist at ~/.claude-marketing/brands/{slug}/guidelines/ — check restrictions.md for banned words and restricted claims in the content, flag violations with the specific rule and a suggested alternative. Keep the check concise — flag only real issues, not stylistic preferences. Additionally, if this IS marketing content, scan for hallucination indicators: (1) statistics or percentages without source attribution, (2) URLs with placeholder patterns (example.com, your-site.com), (3) superlative claims ('best', '#1', 'leading') without substantiation, (4) specific citations to studies or named sources that could be fabricated. Flag any found with severity CRITICAL (for fabricated stats in headlines/CTAs) or WARNING (for unattributed claims in body text). Include the specific text and a fix suggestion. $ARGUMENTSmcp_.*Check if this MCP tool call involves a WRITE operation (creating, publishing, sending, updating, scheduling, or deleting content on an external platform — including CRM record creation, email sending, social posting, ad campaign creation, SMS sending, database writes, or file uploads). If this is a READ-ONLY operation (fetching data, querying analytics, listing items, searching), respond 'SKIP' immediately. For WRITE operations: (1) Verify the user has explicitly approved this specific action in the current conversation — look for clear approval language, (2) Check that content has passed brand compliance review if applicable, (3) Confirm the target platform matches the user's stated intent, (4) For ad campaigns: verify budget is within the brand's stated budget_range from profile.json, (5) For email/SMS: verify list size and consent compliance, (6) For CRM writes: verify data doesn't overwrite existing records without confirmation. If ANY check fails, BLOCK the operation and explain why. If all checks pass, respond 'ALLOW'. $ARGUMENTSIf marketing work was done this session (campaign plans created, content produced, performance analyses run, strategic decisions made, or brand positioning discussed): 1. Summarize 1-3 key marketing insights or decisions from this session. 2. If an active brand exists (check the session start context for the brand slug), save each insight by running: python3 "${CLAUDE_PLUGIN_ROOT}/scripts/campaign-tracker.py" --brand {slug} --action save-insight --data '{"type":"session_learning","insight":"[the insight]","source":"session","context":"[what work produced this insight]"}' — replace {slug} with the active brand slug, and fill in the insight and context fields with actual session data. 3. If any guideline violations were flagged during this session, save them by running: python3 "${CLAUDE_PLUGIN_ROOT}/scripts/campaign-tracker.py" --brand {slug} --action save-violation --data '{"rule":"[violated rule]","category":"[guideline category]","severity":"[low/medium/high]","content":"[violating text snippet]","suggestion":"[compliant alternative]"}' for each violation. 4. Tell the user: 'Session insights saved. Key takeaways: [list them]. To update brand settings, just ask.' If no brand profile exists or no meaningful marketing work was done, skip silently. $ARGUMENTSpython3 ${CLAUDE_PLUGIN_ROOT}/scripts/setup.py --check-deps --summary4plugins reuse this hooks config
First indexed Dec 5, 2025
npx claudepluginhub anotherifmg/digital-marketing-pro