agentleFS
Sign inStart free
arbelharbelh/perdure/skills/list/SKILL.md

list

Skill0 starsChanged 28 days agoMITView on GitHub

List all perdure workflows in the current project. Scans

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use status.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 8 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 1

    Distinctive

    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. Very specific:

    If the directory doesn't exist or is empty: say "No workflows yet.

    line 29
  2. Distinctive:

    Never block or fail — a gentle hint only.

    line 50

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “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

List Workflows

Not the same as Claude Code's built-in /workflows. That lists Dynamic Workflow runs (ephemeral in-session scripts). This lists the perdure plugin's durable, cross-session workflow state files under perdure/workflows/.

Steps

1. Scan the files directly

List perdure/workflows/*.md (and perdure/workflows/*/*.md — terminal files may be aged into <YYYY>/ subdirectories). Skip INDEX.md if present — it's a legacy artifact, not a workflow file. There is no index file to maintain or trust: the files ARE the source of truth. For each file, read just enough to get its status and current step — the frontmatter block when present (workflow:, status:, updated:), else the first heading lines. Real files are freeform markdown; missing frontmatter means "read the first ~20 lines and infer".

If the directory doesn't exist or is empty: say "No workflows yet. Start one with /perdure:start <slug>" and exit.

2. Display

## Active workflows (2)

| Slug | Goal | Next step | Updated |
|------|------|-----------|---------|
| add-jwt-refresh-tokens | Add JWT refresh flow | Implement refresh endpoint | 2026-04-17 |
| migrate-auth-db | Move auth to separate DB | Blocked on infra | 2026-04-16 |

Completed: 3 · Parked: 1 · Abandoned: 1  (ask to see details)

Resume: /perdure:continue <slug> · New: /perdure:start <slug>

3. Staleness hint (soft)

Flag active workflows not updated in >7 days as "stale — resume, park, or close?". Never block or fail — a gentle hint only.

Safety rules

  • Read-only — never modify files
  • Graceful when empty
  • Always offer the next action (resume / start)

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.

Check your setup, free