agentleFS
wayne930242wayne930242/straw-boss/skills/peeking-work/SKILL.md

peeking-work

Skill5 starsChanged 54 days agoMITView on GitHub

Use to read a dispatched task's progress when asked or when evidence disagrees with its recorded state.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask when several instructions match.

    line 9
  2. Very specific:

    Read its status and the recent entries of its sibling .progress.jsonl first.

    line 11
  3. Very specific:

    If these answer the question, report that result.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Read progress

Resolve one canonical instruction from the task, plan, or session identity using peek mechanics. Ask when several instructions match.

Read its status and the recent entries of its sibling .progress.jsonl first. If these answer the question, report that result. Otherwise use the reference's read-only herdr agent read command.

Summarize current activity and any evidence/status discrepancy. Checkpoint resolution returns to dispatching-work.

Complete when: the caller has an evidence-backed progress answer or the specific reason the dispatch cannot be read.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.