Tasker
v1.1.1Use for task execution, debugging, implementation, analysis, review, planning, workflow execution, and user dissatisfaction handling in agent interactions. 任...
⭐ 0· 135·1 current·1 all-time
by@tealun
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (general task execution, debugging, planning, review) match the SKILL.md instructions. The skill requests no environment variables, binaries, or config paths and has no install steps, which is proportionate for an instruction-only workflow controller.
Instruction Scope
The SKILL.md explicitly requires and enforces the use of executive tool calls (WriteFile, Shell, ReadFile, etc.) for any external side effects and mandates artifacts and verification. That behavior is coherent for a task executor but means the agent will attempt real side effects when platform tools are available — the file does not instruct reading unrelated system secrets or arbitrary external endpoints.
Install Mechanism
No install spec and no code files — instruction-only. There is nothing downloaded or written to disk by the skill itself.
Credentials
The skill declares no required env vars, credentials, or config paths. The runtime instructions do not request extra secrets or unrelated credentials.
Persistence & Privilege
always is false, user-invocable is true, and model invocation is enabled (platform default). The skill does not request permanent presence or claim to modify other skills or system-wide settings.
Assessment
This skill is coherent: it describes a workflow controller that requires actual tool calls to perform side effects and verification. Because it mandates executing platform tools (shell, read/write, etc.) when those are available, only install it if you trust the agent runtime and its tool permissions. Confirm what concrete executor APIs/permissions (shell access, file write/read, network) the platform will allow the skill to use, test the skill in a low-privilege environment first, and verify logging/auditing so you can see any actions it takes. If provenance of the skill (owner, homepage, source) matters to you, ask the publisher for more information before enabling it in a high-privilege context.Like a lobster shell, security has layers — review code before you run it.
executionvk97awzxz79k07mer3zaj53d8z583bt8tlatestvk97f0g6tt127j8zvag6219deqd843f49planningvk97awzxz79k07mer3zaj53d8z583bt8treviewvk97awzxz79k07mer3zaj53d8z583bt8ttaskvk97awzxz79k07mer3zaj53d8z583bt8tworkflowvk97awzxz79k07mer3zaj53d8z583bt8t
License
MIT-0
Free to use, modify, and redistribute. No attribution required.