gmail-skill@1.2.0
CAUTION· static onlyPublisher claims: "Gmail automation: summarize, labels, spam purge, filing, deletion, permanent delete" 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-18 and scored it 55/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: Coercive compliance language; 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
if kill -0 $TASK_PID 2>/dev/null && [[ $ELAPSED -ge $UPDATE_INTERVAL ]]; thenFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.while kill -0 $TASK_PID 2>/dev/null; doFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.2. **ALWAYS run the script.** Every capability below has a specific command. You MUST execute it. Do NOT skip execution based on assumptions or prior results.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.if ! kill -0 "$PID" 2>/dev/null; thenFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.**`gmail-bg`** — Shortcut for `gmail-background-task.sh` that auto-sources `.env`:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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
25 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Text that tells the agent to ignore its instructions≈ +9 on the totalDelete phrases like "ignore previous instructions", "override", "bypass" from SKILL.md and tool descriptions. Describe what the skill does; do not instruct the agent about other rules.
- Unclaimed publisher≈ +8 on the totalClaim r39132: 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.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.