poke-b1a67a — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited poke-b1a67a (Agent Skill) and scored it 92/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 2 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
The user hit esc during a long generation and wants a heartbeat: are you stuck, still progressing, or done? Answer in ≤3 lines, then continue if fine.
| State | Signal | Action |
|---|---|---|
progressing | You were mid-task, tools were returning useful output, no repeat failures | Report + continue same approach |
waiting | Blocked on user confirmation, tool permission, or external process | Report + restate what you're waiting on |
stuck | Same step failed 2+ times, or you've been looping without forward progress | Report + stop; surface the block clearly |
done | Last task finished but reply wasn't closed out | Report result in 1-2 lines |
idle | Nothing active, user probably expected something running | Say so — don't invent work |
State: {progressing|waiting|stuck|done|idle}
Doing: {one clause — what you were mid-way on, or what just finished}
Next: {continuing → [action] | paused on [blocker] | nothing pending}Then — only if progressing — immediately continue with the next tool call for the task. Do NOT re-plan, do NOT summarize the whole session, do NOT ask "should I continue?"
TODO.md, PROGRESS.md, or docs — this is a heartbeat, not /next.stuck: say WHY in the "Next" line (e.g. Next: paused on tests failing 3× with same error — need user guidance).idle and the user seems to expect background work: list recent background handles from this session (agents, run_in_background Bash, /loop) so they know where to look — see /status for the fuller dashboard.stuck and root cause needs user input.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.