v1.0.0

Revops

BenignClawScan verdict for this skill. Analyzed May 1, 2026, 7:40 AM.

Analysis

This is an instruction-only RevOps guidance skill with no code, install steps, or credential requirements; its only notable risks are purpose-aligned use of local business context and CRM workflow data-sharing advice.

GuidanceThis skill appears safe to install for RevOps planning and process design. Review any local product-marketing context file it may read, and treat the CRM/Zapier/Slack automation examples as templates that should be approved, scoped, and tested before being applied to real lead or customer data.

Findings (2)

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.

Sensitive data protection

Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.

Memory and Context Poisoning

SeverityLowConfidenceHighStatusNote

SKILL.md

If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context

The skill relies on a persistent local context file to shape answers. This is narrow and relevant to RevOps/product marketing, but stale or unsafe content in that file could influence recommendations.

User impactLocal business context may be used in the agent’s answers, so inaccurate or sensitive content in that file could affect the advice produced.

RecommendationKeep the context file current, avoid storing credentials or secrets in it, and review its contents if RevOps recommendations seem unexpected.

Insecure Inter-Agent Communication

SeverityLowConfidenceHighStatusNote

references/automation-playbooks.md

Actions:
1. Create/update contact in CRM
2. Enrich with Clearbit (if available)
3. Post to Slack #new-leads with enriched data

The playbooks recommend cross-tool workflows that can move lead/contact data among CRM, enrichment, Slack, scheduling, and automation tools. This is expected for RevOps guidance, but it involves business and prospect data flows.

User impactIf implemented, lead or customer information could be shared across third-party tools and internal channels.

RecommendationBefore implementing these workflows, confirm data-sharing permissions, limit posted fields, and test automations in a controlled way.