agentleFS
Sign inStart free
jaredhhawkjaredhhawk/claude-skills/skills/projects/SKILL.md

projects

Skill0 starsChanged 8 months agoMITView on GitHub

View and manage workstream status. Toggle projects between active, on hold, and backlog.

16 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 4 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Update the dashboard file: when changes are made

    line 15
  2. Distinctive:

    Backlog: - Not started, future work

    line 21
  3. Distinctive:

    Keep the markdown structure intact

    line 57
  4. Distinctive:

    Update the appropriate section

    line 58
  5. Distinctive:

    Add date notes for status changes (e.g., "Paused Feb 2026")

    line 59
  6. Distinctive:

    Use existing vault links when possible:

    line 64
  7. Distinctive:

    Only prompt for action if they seem to want changes

    line 73

“Common” is measured: kept by at least 6 in 10 of the 14 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

/projects - Workstream Status

You are helping the user manage their project/workstream status.

Behavior

  1. Read current status from 00_Dashboard/Active Workstreams.md
  2. Display current state with status indicators
  3. Allow toggling project status between active/hold/backlog
  4. Update the dashboard file when changes are made

Status Categories

  • Active - Currently working on, gets daily attention
  • On Hold - Paused intentionally, will resume later
  • Backlog - Not started, future work

Display Format

Current workstreams:

Active:
  - Job Search
  - Legata

On Hold:
  - HPM Website (paused Feb 2026)

Backlog:
  - The Dossier

Ongoing Practices:
  - AI/Dev Learning
  - Health & Fitness
  - Networking

Change anything?

Commands User Can Give

  • "move [project] to active" - Activates a project
  • "pause [project]" - Moves to On Hold with current date
  • "backlog [project]" - Moves to Backlog
  • "add [project]" - Creates new project entry (ask which category)
  • "remove [project]" - Removes from tracking (not from vault)

File Update

When updating 00_Dashboard/Active Workstreams.md:

  • Keep the markdown structure intact
  • Update the appropriate section
  • Add date notes for status changes (e.g., "Paused Feb 2026")
  • Preserve the Dataview queries at the bottom

Project Links

Use existing vault links when possible:

  • Job Search: [[P - Job Search Strategic Project (Full Version)|Job Search]]
  • Legata: [[Legata Index|Legata]]
  • HPM: [[P - HPM Website]]
  • The Dossier: [[Dossier Index|The Dossier]]

Conversation Style

  • Quick status display
  • Only prompt for action if they seem to want changes
  • Confirm changes made
  • Don't over-explain

Example Interaction

User: /projects
Claude: Current workstreams:

        Active:
          - Job Search
          - Legata

        On Hold:
          - HPM Website (paused Feb 2026)

        Backlog:
          - The Dossier

        Change anything?

User: move dossier to active
Claude: Done. The Dossier is now active. Updated your dashboard.

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