Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Cleanup Workflows
v1.0.0Audit and remove inactive, test, or deprecated workflows from HubSpot. Identifies workflows that have never enrolled contacts, workflows turned off for 90+ d...
⭐ 0· 69·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The SKILL.md describes auditing and deleting HubSpot workflows and the instructions use the HubSpot Workflows API — that aligns with the stated purpose. However, the skill metadata declares no required environment variables or primary credential, while the instructions explicitly require a HubSpot API token in a .env file. This mismatch (a core credential required by the runtime but not declared) is incoherent and should be clarified.
Instruction Scope
The instructions tell the agent to read a HubSpot API token from environment (.env / os.getenv) and call api.hubapi.com automation endpoints — those actions are appropriate for the stated task. But the SKILL.md also references installing 'hubspot-api-client' while the example uses requests/os.getenv (and the snippet omits the os import). The doc also instructs deletion of workflows (sensitive write actions) but does not include example safe-delete code, nor does it enumerate required API scopes. These are gaps that increase risk if you run the steps without review.
Install Mechanism
This is an instruction-only skill with no install spec or code files, so there is no installer risk. There is a minor inconsistency: the prereqs say 'hubspot-api-client' installed via 'uv' (likely a typo) even though the shown sample uses requests. No downloads or arbitrary URLs are suggested.
Credentials
The runtime requires a HubSpot API token to call/modify workflows, which is expected for the task — but the skill registry lists no required env vars or primary credential. The absence of declared credential requirements in metadata is concerning because it prevents automated permission checks and hides that a high-privilege token is needed. The instructions do not recommend limiting token scopes or using a read-only/test account prior to deletion operations.
Persistence & Privilege
The skill does not request persistent installation, system paths, or 'always' inclusion. It is user-invocable and can be invoked autonomously (the platform default), which is normal; nothing indicates elevated or persistent privileges beyond normal API access.
What to consider before installing
This skill’s instructions legitimately require a HubSpot API token and call HubSpot’s Workflows API, but the skill metadata fails to declare that credential — an important mismatch. Before using or granting any token: (1) verify the author/source (homepage is missing), (2) prefer using a least-privilege or test HubSpot API token (restrict scopes; avoid full-admin tokens), (3) review the exact code you will run (the SKILL.md has small typos/mismatches: mentions hubspot-api-client but example uses requests; 'uv' looks wrong), (4) don't run delete operations until you confirm required API scopes and have backups/documentation, and (5) consider running the audit read-only first to produce a candidate list and only perform deletions after human review. If possible, ask the publisher to update the skill metadata to declare HUBSPOT_API_TOKEN (primaryEnv) and to provide explicit delete code with recommended scopes and safety checks.Like a lobster shell, security has layers — review code before you run it.
latestvk9703s9vcmf5mxgtm88tn296rx83nmwv
License
MIT-0
Free to use, modify, and redistribute. No attribution required.