Security audit
Security checks for vulnerabilities and agentic risk
This CRM-cleaning skill is purpose-aligned, but it asks for CRM credentials and includes broad bulk-update and third-party enrichment guidance that should be reviewed before use.
Install only if you are comfortable giving an agent access to CRM data. Start with least-privilege or read-only credentials, use exports or a sandbox first, require human approval before merges/imports/batch updates, keep backups, and verify legal/privacy approval before using Clearbit, Apollo, scraping, or social-data enrichment.
The description promotes external enrichment providers and CRM update workflows but does not clearly warn that contact/company data may be sent to third parties or that privacy obligations may apply. Users may trigger enrichment assuming a local cleanup task, resulting in unintended disclosure of customer or prospect data to outside services.
The opening guidance describes deduplication, normalization, and enrichment workflows but lacks an immediate warning that merges and bulk updates can be irreversible or affect linked records, reports, and automation. In CRM systems, premature or automated merges can destroy auditability, overwrite accurate values, and disrupt downstream business processes.
The manifest explicitly claims the skill is instruction-only with no scripts or code execution, yet the document embeds multiple executable Python, JavaScript, SQL, and Apex snippets and references implementation workflows. This mismatch can mislead downstream tooling, reviewers, or users into granting the skill broader trust than warranted and increases the chance an agent copies or adapts code that performs external access or data mutation.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
import requests
def find_hubspot_duplicates(api_key, batch_size=100):
url = f"https://api.hubapi.com/contacts/v1/lists/all/contacts/all"
params = {
'hapikey': api_key,
'count': batch_size,
The skill recommends web scraping, social-media harvesting, and use of public databases to enrich CRM records, which can cause collection and transfer of personal data beyond what is necessary for basic deduplication/normalization. In a CRM context this creates privacy, consent, and terms-of-service risks, especially if an agent operationalizes scraping without legal review or user awareness.
The inline note stating that implementation details exist in a scripts directory directly contradicts the no-scripts claim in the manifest. Even without the scripts present, this suggests hidden or omitted executable components and undermines trust in the declared security boundary of the skill.