Rolling Suds Workiz Lead Runner
v0.1.6Read-only Rolling Suds workflow for processing Workiz leads and associated client data. Use when the user wants to review current-day or specific-day leads,...
⭐ 0· 75·0 current·0 all-time
byMichael D@mwdearing
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (read-only Workiz lead runner) matches the instructions: it processes pasted/exported lead+client data and prepares summaries/estimates/notes. It does not request unrelated credentials or binaries and explicitly avoids write-back, so requested capabilities are proportionate to the stated purpose.
Instruction Scope
SKILL.md confines runtime behavior to reading user-provided lead data and composing outputs (summaries, estimator inputs, Workiz-ready notes). It explicitly forbids modifying Workiz and does not instruct the agent to read system files, environment variables, or send data to external endpoints. The 'future API mode' is conceptual and is appropriately gated by permissions.
Install Mechanism
No install spec and no code files — instruction-only skill. This minimizes on-disk risk; nothing is downloaded or installed by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. That aligns with its current read-only, manual-input design. It notes future API readiness but does not attempt to collect or describe credential flows now.
Persistence & Privilege
No 'always: true' flag, no system persistence, and no instructions to modify other skills or agent-wide settings. Autonomous invocation is allowed (default) but not combined with any elevated privileges or secret access.
Assessment
This skill appears coherent and low-risk: it only processes user-provided lead text and does not request credentials or install code. Before installing, consider: (1) only paste non-sensitive lead data (or scrub PII) because outputs could be shown or logged by your agent, (2) confirm the GitHub homepage/repo if you want source code provenance, and (3) if you later enable API integration, provide Workiz credentials only when you trust the skill and have reviewed any added code or install steps. If you need higher assurance, ask the publisher for an explicit implementation or code listing for review before enabling API mode.Like a lobster shell, security has layers — review code before you run it.
latestvk97cjkf2hk5rhqrh629svntmhd84apkm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📋 Clawdis