agentleFS
ayleeaylee/agent-os/.agents/skills/recent/SKILL.md

recent

Skill0 starsChanged 4 months agoMITView on GitHub

Find recently active Agent-OS work when the user asks what changed or what they worked on. Prefer receipts and artifact metadata, work without Git, and use mtimes only as a fallback.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read workstream-transition receipts in the window and group them by workstream.

    line 10
  2. Very specific:

    Add workstreams whose updated_at metadata is in the window but lack a matching transition receipt.

    line 11
  3. Distinctive:

    If metadata is absent, use filesystem mtimes and label them as weak evidence.

    line 12
  4. Distinctive:

    If Git exists, use it only to enrich—not gate—the result.

    line 13

≈ “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

Recent work

Accept a window such as 3d, 7d, or 2w; default to seven days.

  1. Read workstream-transition receipts in the window and group them by workstream.
  2. Add workstreams whose updated_at metadata is in the window but lack a matching transition receipt; label the missing evidence. Add ordinary artifacts from their own updated_at metadata without expecting document receipts.
  3. If metadata is absent, use filesystem mtimes and label them as weak evidence.
  4. If Git exists, use it only to enrich—not gate—the result.
  5. Return a compact, deduplicated list with relative path, transition, time, current status, and next action where available.

Exclude generated adapters, caches, raw local state, and receipt noise from the primary list.

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.