ecommerce-gmail-customer-service@1.2.8
CAUTION· static onlyPublisher claims: "Privacy-first ecommerce Gmail customer-service skill for OpenClaw. It triages inbox messages, researches public storefront data, creates draft-first replies, learns approved patterns, and auto-replies only in owner-enabled categories. Private data needs an approved least-privilege connector." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-10 and scored it 60/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
…age-id '<SENT_MESSAGE_ID>' --input /controlled-temporary-directory/atomic-issues.json --delete-input python3 scripts/auto_reply_permissions.py confirm --event-id '<EVENT_ID>' --int…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.… and the number of historical evidence. 7. After the owner confirms the current write, write `user_memory.md` through the onboarding-only command below. This does not turn on ongoing Draft…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.… merchant connectors; it never replaces order, customer, payment, inventory, or admin access. ## Run discovery Initialize the runtime first, then run from the Skill direc…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.If `memory.usage_enabled=false`, do not add a `user_memory.md` preference or playbook to the Draft-generation context; continue with the standard process.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.if lower_name.endswith(SENSITIVE_SUFFIXES) or lower_name == ".env" or lower_name.startswith(".env."):Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.errors.append("user_memory.md is missing its managed-memory markers")Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.return subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.5. Clearly tell users: past reply methods and later Draft-edit learning results are saved in the running version `user_memory.md`; view it read-only with:Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.return subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.unconfirmed = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.python3 scripts/auto_reply_permissions.py check --input /controlled-temporary-directory/atomic-issues.json --delete-inputFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.python3 scripts/user_memory.py merge --source onboarding --input /controlled-temporary-directory/memory-update.json --confirm-owner-request --delete-inputFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…"Default sending mode: draft_only") print( "Next step: Review config.json, system-prompt.md, workflow.md, persona.md, user_memory.md, and auto_reply_permissions.json. Automatic sending stays disabled until the owner enables it and confirms…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
20 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim ecom-agent-tools: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.