agentleFS
Sign inStart free
ExarLabsExarLabs/paros-advisor/skills/project-state/SKILL.md

project-state

Skill4 starsChanged 41 days agoMITView on GitHub

Create, update or read the short versioned state file of an area or long-running project in a PAROS vault (objective, status, metrics, problems, focus, next actions, map). Use when the person asks "where are we", "project status", "update the state", "initialize this project", or when starting work in an area that has a state file.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read it in full. Read its version: field.

    line 14
  2. Very specific:

    Follow it. Its ## Constitution always wins.

    line 18
  3. Very specific:

    If the person corrects the result, write a learning packet to the skill's observations/ folder (P05).

    line 19

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

project-state

Thin entry (PAROS P04). The knowledge lives in a live definition; this file only finds it.

  1. Locate the live definition, first match wins:
    • where the vault entry file (AGENTS.md or CLAUDE.md) says skills live: <skills folder>/project-state/CURRENT.md;
    • <vault>/PAROS/skills/project-state/CURRENT.md;
    • the PAROS reference copy: <paros repo>/skills/project-state/CURRENT.md.
  2. Read it in full. Read its version: field.
  3. Report one line before working:
    • from the vault: Running project-state v<X> from your vault;
    • from the reference copy: Running project-state v<X> from the PAROS reference, not yet adopted.
  4. Follow it. Its ## Constitution always wins.
  5. If the person corrects the result, write a learning packet to the skill's observations/ folder (P05).

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