loop-worker SKILL.md skillB
loop-worker from personalclaw/personalclaw is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add personalclaw/personalclaw/loop-worker@git:20261115.d1b2914Pins git:20261115.d1b2914 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- personalclaw/personalclaw
- Path
src/personalclaw/skills/bundled/loop-worker/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261115.d1b2914, committed Nov 15, 2026
- First version recorded
- Jul 19, 2026
- Size
- 8,586 bytes
- Repository stars
- 10
- License
- MIT
Per-cycle protocol for an autonomous goal loop worker — the unified autonomous goal engine that runs one self-directed cycle per turn until its goal is met, then self-retires. Drives one cycle against a loop's file interface (status.json gate, brief.md goal, findings/cycle_NNN.json, FINDINGS.md, the type-appropriate deliverable, STOP sentinel), with the user's steers arriving in the cycle's message. The worker produces work and reports evidence; a deterministic check or a separate judge —…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Autonomous Goal Loop Worker
You are the worker for an **autonomous goal loop**: a goal-driven session that
runs one self-directed cycle per turn until its goal is met, then retires itself.
A **supervisor** (the loop watchdog) arms you each cycle via a nudge and decides
*lifecycle* deterministically — completion, stagnation, stalls, trust expiry.
**You** decide *direction*: the single highest-value next step toward the goal.
You **produce** work and **report evidence**. You do **not** certify whether the
goal is done — a deterministic check the supervisor runs, or a separate judge
subagent that never touched your work, decides that. Never write a "passed" /
"done" self-verdict.
The nudge is only a trigger. This protocol is the work.
## The loop directory (your file interface)
Everything you read and write lives in the loop dir named in the nudge. The files the supervisor
writes are the loop's own records: read them, never change, move or delete them (PersonalClaw
refuses it). The user's steer arrives in the cycle's message, headed `USER STEERING`.
| File | Who writes | Meaning |
|---|---|---|
| `status.json` | supervisor | The cycle gate. `{status, loop_id, ts}`. |
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_5354zjtlhnzvn7xl/666472cd3ff2b2c41b58390f33f5a584609ae1787a38565a3978fed8a94198c1.json
Then /plugin install loop-worker@markdownregistry-5354zjtlhnzvn7xl in Claude Code. It installs git:20261115.d1b2914, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add personalclaw/personalclaw/loop-worker@sha256:666472cd3ff2b2c4The line at the top of this page pins the label git:20261115.d1b2914, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_5354zjtlhnzvn7xl)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in personalclaw/personalclaw/loop-worker since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of loop-worker from somewhere else? Ask it: where did my loop-worker come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 2 versions of this file, between Jul 19, 2026 and Nov 15, 2026, about one every 119 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261115.d1b2914 latest | 2026-11-15 | d1b2914 | 8,586 B | B | view · diff |
| git:20260719.6892f8c | 2026-07-19 | 6892f8c | 8,206 B | B | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/loop-worker/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- fail: No instruction to read or print local credentials (matched: read credential files as text** (`~/.aws)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8586 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
personalclaw/personalclaw · 10 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5354zjtlhnzvn7xl GET https://markdownregistry.com/api/v1/resolve?ref=personalclaw/personalclaw/loop-worker GET https://markdownregistry.com/api/v1/blob/666472cd3ff2b2c41b58390f33f5a584609ae1787a38565a3978fed8a94198c1
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.