← Back to Skills Marketplace
104
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install quarterly-database-cleanup
Description
Run a comprehensive quarterly CRM audit covering list health, bounce monitoring, data quality, scoring calibration, engagement metrics, and property cleanup....
Usage Guidance
This skill appears to be a valid plan for a HubSpot CRM audit, but there are missing and vague pieces you should clarify before installing or running it:
- Metadata mismatch: The SKILL.md says a HubSpot API token (in .env) and Python hubspot client are required, but the registry metadata declares no credentials or binaries. Ask the author to add a required env var (e.g., HUBSPOT_API_TOKEN) and any required binaries to the metadata.
- Limit credential scope: If you proceed, provide a HubSpot API token that is scoped to read-only audit operations (not full write/admin access) and avoid placing other secrets in the same .env file.
- Confirm /hubspot-audit: The instructions reference running '/hubspot-audit' and 'reuse audit script patterns' but no script is included. Confirm whether this is an existing internal CLI or a placeholder; get the concrete commands or scripts you'd run so you can review them first.
- Files and secrets: The skill tells the agent to read reports/ and .env. Review what lives in those locations before running the audit to avoid accidental disclosure of unrelated secrets. Consider copying only the needed HubSpot token into a minimal env file for the audit.
- Logging and output: Ensure reports do not inadvertently include sensitive raw contact data (PII) if you plan to store or share them.
If the author updates the metadata to declare the HubSpot credential and documents the exact commands or scripts to run (or includes vetted scripts), this would reduce the concerns and could be considered benign. Until then, treat it cautiously and do not supply broad credentials or let it run autonomously without human review.
Capability Analysis
Type: OpenClaw Skill
Name: quarterly-database-cleanup
Version: 1.0.0
The skill bundle contains standard markdown instructions for performing a quarterly HubSpot CRM audit, including list health, bounce monitoring, and data quality checks. The instructions in SKILL.md are consistent with the stated purpose, describe a read-only process, and do not contain any evidence of malicious intent, data exfiltration, or prompt injection attacks.
Capability Assessment
Purpose & Capability
The skill's stated purpose (quarterly HubSpot CRM audit) matches the actions described in SKILL.md (list health, bounces, properties, etc.). However, the SKILL.md explicitly requires a HubSpot API token and Python with the hubspot client, but the registry metadata lists no required environment variables or binaries — this mismatch should be resolved.
Instruction Scope
The instructions tell the agent to read a .env file, look in a local reports/ directory, save reports to disk, and to 'Run /hubspot-audit' and 'reuse audit script patterns' — but no scripts, CLI tools, or example commands are included. That leaves the agent with broad, undefined discretion (which files to read, what scripts to run, how to obtain HubSpot data), increasing the risk of accidental access to unrelated local secrets or running unexpected commands.
Install Mechanism
There is no install spec and no code files; this is instruction-only. That lowers supply-chain risk because nothing is downloaded or written by an installer. The risk comes from the runtime instructions, not an installer.
Credentials
SKILL.md requires a HubSpot API token stored in .env and a Python library, but the skill metadata does not declare any required environment variables or primary credential. Asking the agent to read a .env file can expose unrelated secrets. A HubSpot audit legitimately needs a HubSpot API token (preferably a scoped, read-only token), but this required credential should be declared explicitly in the metadata and instructions should limit which files/vars to read.
Persistence & Privilege
The skill does not request always:true and does not claim persistent/system-wide changes. It describes read-only audits and saving reports to a local reports/ folder; those are reasonable for this purpose.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install quarterly-database-cleanup - After installation, invoke the skill by name or use
/quarterly-database-cleanup - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release with comprehensive quarterly CRM audit and reporting.
- Audits database health across list management, bounce rates, data quality, scoring, engagement, and property usage.
- Compares key CRM metrics against the previous quarter and flags significant changes.
- Generates a detailed health report with trend analysis and actionable recommendations.
- Requires a HubSpot API token and Python environment.
- Designed for ongoing maintenance with easy scheduling and clear instructions.
Metadata
Frequently Asked Questions
What is Quarterly Database Cleanup?
Run a comprehensive quarterly CRM audit covering list health, bounce monitoring, data quality, scoring calibration, engagement metrics, and property cleanup.... It is an AI Agent Skill for Claude Code / OpenClaw, with 104 downloads so far.
How do I install Quarterly Database Cleanup?
Run "/install quarterly-database-cleanup" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Quarterly Database Cleanup free?
Yes, Quarterly Database Cleanup is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Quarterly Database Cleanup support?
Quarterly Database Cleanup is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Quarterly Database Cleanup?
It is built and maintained by TomGranot (@tomgranot); the current version is v1.0.0.
More Skills