cleanup-dashboards
About
This skill audits HubSpot dashboards to identify unused, duplicate, or outdated reports for consolidation. It requires manual execution in the HubSpot UI since no dashboard API exists. Use this for ongoing maintenance when dashboards become cluttered and ineffective.
Quick Install
Claude Code
Recommendednpx skills add TomGranot/hubspot-admin-skills -a claude-code/plugin add https://github.com/TomGranot/hubspot-admin-skillsgit clone https://github.com/TomGranot/hubspot-admin-skills.git ~/.claude/skills/cleanup-dashboardsCopy and paste this command in Claude Code to install this skill
Documentation
Cleanup Dashboards
Audit HubSpot dashboards to remove clutter and consolidate reporting. Too many dashboards means nobody uses any of them effectively.
Important Limitation
HubSpot does not provide a Dashboard API. This entire process must be performed manually in the HubSpot UI under Reports > Dashboards.
Prerequisites
- HubSpot portal access with dashboard management permissions
- Input from team members on which dashboards they actively use
Step-by-Step Instructions
Stage 1: Before — Inventory All Dashboards
- Navigate to Reports > Dashboards in HubSpot.
- Create a spreadsheet listing every dashboard:
- Name, owner/creator, number of reports, last viewed date (if visible), purpose
Stage 2: Execute — Identify Candidates for Removal
Flag dashboards matching any of these criteria:
- Not viewed in 90+ days (check with the owner first)
- Duplicate dashboards covering the same metrics
- Test dashboards (names containing "test", "draft", "copy of")
- Personal dashboards belonging to departed employees
- Default dashboards that were never customized
Consolidation targets:
- Merge dashboards with overlapping report widgets into a single comprehensive dashboard.
- Aim for 5-10 core dashboards maximum (e.g., Marketing Overview, Sales Pipeline, Email Health, Data Quality, Executive Summary).
Stage 3: After — Clean Up and Reorganize
- Delete confirmed unused dashboards.
- Rename remaining dashboards with a clear naming convention (e.g.,
[Team] - Purpose). - Set appropriate sharing/visibility for each dashboard.
- Communicate changes to the team — share links to the consolidated dashboards.
Stage 4: Rollback
- Deleted dashboards cannot be restored.
- Before deleting, screenshot each dashboard or note which reports it contained.
- Individual reports within a dashboard are not deleted when the dashboard is removed — they remain available for re-use.
Tips
- Assign a dashboard owner for each core dashboard — someone responsible for keeping it current.
- Review dashboards quarterly as part of the database cleanup routine.
- If a report on a dashboard shows stale or broken data, fix the underlying report rather than creating a new dashboard.
GitHub Repository
Related Skills
railway-docs
DocumentationThis skill fetches current Railway documentation to answer questions about features, functionality, or specific docs URLs. It ensures developers receive accurate, up-to-date information directly from Railway's official sources. Use it when users ask how Railway works or reference Railway documentation.
n8n-code-python
DocumentationThis Claude Skill provides expert guidance for writing Python code in n8n's Code nodes, specifically for using Python's standard library and working with n8n's special syntax like `_input`, `_json`, and `_node`. It helps developers understand Python's limitations within n8n and recommends using JavaScript for most workflows while offering Python solutions for specific data transformation needs.
archon
DocumentationThe Archon skill provides RAG-powered semantic search and project management through a REST API. Use it for querying documentation, managing hierarchical projects/tasks, and performing knowledge retrieval with document upload capabilities. Always prioritize Archon first when searching external documentation before using other sources.
n8n-code-javascript
DocumentationThis Claude Skill provides expert guidance for writing JavaScript code in n8n's Code nodes. It covers essential n8n-specific syntax like `$input`/`$json` variables, HTTP helpers, and DateTime handling, while troubleshooting common errors. Use it when developing n8n workflows that require custom JavaScript processing in Code nodes.
