Back to Skills

weekly-cleanup-routine

TomGranot
Updated 2 days ago
4 views
33
11
33
View on GitHub
Designautomationdesigndata

About

This Claude Skill performs a lightweight 5-minute weekly health check for HubSpot, covering bounce monitoring, contact quality, and workflow health. It acts as an early warning system to spot issues before they escalate, not as a deep audit. Developers should use it for quick, routine maintenance spot-checks on their portal's core metrics.

Quick Install

Claude Code

Recommended
Primary
npx skills add TomGranot/hubspot-admin-skills -a claude-code
Plugin CommandAlternative
/plugin add https://github.com/TomGranot/hubspot-admin-skills
Git CloneAlternative
git clone https://github.com/TomGranot/hubspot-admin-skills.git ~/.claude/skills/weekly-cleanup-routine

Copy and paste this command in Claude Code to install this skill

Documentation

Weekly Cleanup Routine

A fast, 5-minute weekly check that catches problems early. This is not a deep audit — it is a spot-check designed to surface issues before they compound.

Prerequisites

  • HubSpot portal access
  • Bounce monitoring workflow active (run /bounce-monitoring-workflow first)

The 5-Minute Checklist

Stage 1: Before — Open Dashboards

Open HubSpot in your browser. Have the following views ready:

  • Email health dashboard
  • Workflow dashboard
  • Contacts list view (sorted by create date, descending)

Stage 2: Execute — Five Spot Checks

1. Bounce Monitoring (1 min)

  • Check the email_health_flag list. How many contacts were flagged this week?
  • If more than 10, investigate the source (bad import? form spam?).
  • If zero, confirm the workflow is still active.

2. New Contact Quality (1 min)

  • Filter contacts created in the last 7 days.
  • Spot-check 5-10 new contacts. Do they have:
    • Valid email addresses?
    • Company name populated?
    • Lifecycle stage set?
  • If quality is low, check the source (which form, import, or integration created them).

3. Workflow Health (1 min)

  • Open the workflow dashboard. Look for:
    • Any workflows showing errors (red indicators)
    • Any workflows with zero enrollments that should be active
    • Any workflows that were accidentally turned off

4. List Growth Trends (1 min)

  • Check your key segment lists (customers, MQLs, suppressed).
  • Is any list growing or shrinking unexpectedly?
  • A sudden spike in suppressed contacts could indicate a deliverability problem.

5. Data Quality Sample (1 min)

  • Pull 10 random contacts from the database.
  • Check: email, company, lifecycle stage, owner.
  • If more than 2 out of 10 have gaps, flag for a deeper review.

Stage 3: After — Log and Escalate

Keep a simple weekly log (spreadsheet or note):

DateBouncesNew Contact QualityWorkflow IssuesList AnomaliesData Quality
YYYY-MM-DDX flaggedGood/BadNone/DetailsNone/DetailsX/10 complete

Escalate anything that appears two weeks in a row.

Stage 4: Rollback

This is a read-only review — no rollback needed. Any fixes identified are executed through their respective skills.

Scheduling

  • Run every Monday morning.
  • Set a recurring 15-minute calendar block (5 minutes for the check, 10 minutes buffer for any follow-up).
  • If you miss a week, do not double up — just run the next scheduled check.

GitHub Repository

TomGranot/hubspot-admin-skills
Path: skills/weekly-cleanup-routine
0

Related Skills

executing-plans

Design

Use the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.

View skill

requesting-code-review

Design

This skill dispatches a code-reviewer subagent to analyze code changes against requirements before proceeding. It should be used after completing tasks, implementing major features, or before merging to main. The review helps catch issues early by comparing the current implementation with the original plan.

View skill

connect-mcp-server

Design

This skill provides a comprehensive guide for developers to connect MCP servers to Claude Code using HTTP, stdio, or SSE transports. It covers installation, configuration, authentication, and security for integrating external services like GitHub, Notion, and custom APIs. Use it when setting up MCP integrations, configuring external tools, or working with Claude's Model Context Protocol.

View skill

web-cli-teleport

Design

This skill helps developers choose between Claude Code Web and CLI interfaces based on task analysis, then enables seamless session teleportation between these environments. It optimizes workflow by managing session state and context when switching between web, CLI, or mobile. Use it for complex projects requiring different tools at various stages.

View skill