Enrich Company Name
Analysis
The skill is coherent and purpose-aligned, but it should be used deliberately because it can use HubSpot access and bulk-fill a CRM contact field through an ongoing workflow.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
Copy FROM: Company > Name ... Copy TO: Contact > Company name ... select **Yes, enroll existing contacts**. This enrolls the entire backlog.
The skill instructs a HubSpot workflow that can update the contact company-name property across the existing CRM backlog.
The **workflow** handles both backlog (enrolled on activation) AND future contacts automatically. It is the long-term solution.
The recommended workflow is a persistent automation that continues applying the enrichment to future contacts.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
TOKEN = os.environ["HUBSPOT_ACCESS_TOKEN"]
HEADERS = {
"Authorization": f"Bearer {TOKEN}",The audit script requires a HubSpot access token and uses it to call HubSpot CRM APIs.