Skillv1.1.0

ClawScan security

Post-Purchase Flow · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

BenignApr 28, 2026, 2:26 PM

Verdict: benign
Confidence: high
Model: gpt-5-mini
Summary: This is an instruction-only post‑purchase design guide whose requested actions, data needs, and implementation notes are coherent with its stated purpose and do not request unrelated credentials or installs.
Guidance: This skill appears coherent and is an instruction-only guide for designing post-purchase journeys. Before using it: 1) do not paste or upload raw customer PII or full customer export files into third‑party tools without verifying data handling and privacy protections; 2) when implementing integrations (ESP, SMS carriers, carrier APIs, review platforms), provision credentials directly to those platforms and avoid sharing secrets in free-text prompts; 3) avoid embedding personally identifying data in public QR/URL parameters — use short tokens or server-side lookups; 4) ensure SMS usage and timing comply with TCPA and local regulations; and 5) test flows in a staging environment and verify suppression/opt-out logic to prevent accidental marketing sends. If you plan to grant the agent live access to systems, review logs and permissions and grant the minimum necessary scope.
Findings: [regex-scan-none] expected: Scanner found no code or patterns to analyze. This is expected for an instruction-only marketing/design guide; absence of findings is not proof of safety but consistent with the skill's format.

Review Dimensions

Purpose & Capability: okThe skill's name and description align with the included documents (SKILL.md and supporting guides). All required actions (email timing, shipping notifications, unboxing, review flows, cross-sell timing) are appropriate for a post-purchase experience design skill.
Instruction Scope: noteThe runtime instructions ask the agent (or user) to audit/export data from ESPs, shipping/tracking systems, and customer/order data sources — which is relevant to the task. The skill does not instruct the agent to read unrelated system files or environment variables, but it does implicitly rely on access to sensitive customer data and platform integrations; the user/agent should avoid transmitting raw PII to untrusted endpoints.
Install Mechanism: okNo install spec and no code files — this is instruction-only, so nothing will be written to disk or downloaded during install. That minimizes install-time risk.
Credentials: noteThe skill declares no required env vars or credentials, which is proportionate. However, the guidance assumes later integration with ESPs, carrier APIs, SMS providers, and review/loyalty platforms; those integrations will require credentials outside the skill and should be provisioned securely. The skill also recommends using order/customer identifiers in QR/URL parameters — be cautious not to expose PII in public URLs.
Persistence & Privilege: okNo elevated privileges, no always:true, and no installation actions. The skill is user-invocable and can be called autonomously per platform defaults, but it does not request persistent access or modify other skills/settings.