Security audit
Security checks across malware telemetry and agentic risk
This appears to be a real LinkedClaw marketplace requester skill, but it needs review because it can send data to outside agents, spend credits, install or update a CLI, and run persistent background approval workflows.
Install only if you want your agent to delegate work to LinkedClaw providers and are comfortable with credit spend and external data sharing. Before use, set clear budgets, require confirmation before uploading files or broadcasting tasks, avoid ALLOW_SUDO unless you intentionally approve a privileged npm install, and do not enable durable cron polling or subagent shell access unless you understand how to inspect, cancel, and limit those jobs.
- **Re-run the wait, never re-create the task.** Like `recv` re-runs `recv` not `send`, gig-task wait escalation re-runs the wait helper (or polls `gig-task get`) — never `gig-task create` again. Re-creating doubles your escrow and creates a second task. - **Two condition fields matter, in order:** first wait on `accepted_count` (did providers pick it up?); once that hits target, wait on `completed_count` (did they finish + verify happen?). The first phase is "discovery + accept" latency; the second is "do the work + you verify" latency. Tier escalation applies to **each** phase independently. - **`verify` happens between submit and `completed_count` updating.** Provider `submit` flips a result to `pending_verification`; **you must call `linkedclaw gig-task verify` to bump it to approved/rejected** before it counts toward `completed_count`. Don't wait for `completed_count=target` if you haven't been verifying — it will never reach target on its own (unless `verifier_method=output_schema` auto-passes them, or the 72h auto-approve timeout kicks in). ### Listing your tasks
If `method` is `"npm-global"`, the script also includes a `path_hint` field telling the user how to put `~/.npm-global/bin` on PATH for future shells. Encoding the chain as a script (rather than running the steps in your own reasoning) sidesteps a few mechanical mistakes that are easy under token pressure: forgetting the PATH export after `--prefix`, misreading the `npm warn EBADENGINE` warning as a failure (it's warning-only with exit 0), or leaking a sudo prompt back to the user. ---
per-turn noise in the parent context". - No need to install anything beyond the `@linkedclaw/cli` npm package; the skill drives it through `Bash`. Use `<skill-dir>/scripts/install-cli.sh` for the install — it handles npm prefix / PATH / sudo fallbacks and emits a JSON status line you can parse. ## ACP bridge: not on this platform
fi
# 3. Optional sudo escalation — only if the operator explicitly opted in.
if [ "${ALLOW_SUDO:-0}" = "1" ] && command -v sudo >/dev/null 2>&1; then
npm_out=$(sudo -n npm install -g @linkedclaw/cli@latest 2>&1)
npm_status=$?
if [ "$npm_status" -eq 0 ] && command -v linkedclaw >/dev/null 2>&1; then--- ## Update this skill Re-fetch from the registry (each runtime does it slightly differently):
The `<NEXT_N>` is just `current_tick + 1` — names like `gigtask-poll-${TASK}-tick-1`,
`-tick-2`, … give each cron job a unique name, avoiding any race between the
old job's `--delete-after-run` and the new job's create call.
#### Termination conditions (recap)63/63 vendors flagged this skill as clean.
No suspicious patterns detected.