task-executor@1.0.2
CAUTION· static onlyPublisher claims: "Disciplined, legible, resumable execution of a single already-defined task — one task, one plan the user approves before any code is written, every change validated. Use this skill whenever the user says "/task-executor", "task-executor", "Work on task: <description>", "execute this task", "implement this ticket", "work this item", or hands you one concrete, already-specified task — even if they don't name the skill. Do NOT auto-trigger on a greenfield idea with a fuzzy spec (design-brief) or on something broken (diagnose) — the spec is assumed given." 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-07 and scored it 71/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. 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
No findings across 356 lines in 2 files.
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
9 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim dennisrongo: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.