agentleFS
Sign inStart free
HolojermHolojerm/drawthesystem/skills/progress/SKILL.md

progress

Skill0 starsChanged 2 months agoMITView on GitHub

Summarise practice history from progress.md and session feedback — trends per rubric dimension, recurring gaps, and what to drill next. Usage — /progress

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use quiz, teach and 1 more.

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.
  • andrewn6Skill

    quiz

    Test understanding with targeted questions — adapts to skill level and researches the stack for relevant questions

    Also in 4 projects that use this

  • GoogleSkill

    teach

    Teach the user a new skill or concept, within this workspace.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 3 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 16 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:

    Read progress.md and every sessions/*/feedback.md.

    line 9
  2. Distinctive:

    Keep it under ~40 lines. No fluff.

    line 17

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

/progress

  1. Read progress.md and every sessions/*/feedback.md.
  2. Report:
    • Sessions completed, by company and mode; overall score trend (list, oldest → newest).
    • Per-dimension average and trend (↑ ↓ →) for the 10 rubric dimensions.
    • Recurring gaps: phrases/failure modes that appear in ≥ 2 feedbacks.
    • Cruxes missed vs. found.
    • Companies researched but not yet practised.
  3. Recommend the next session: company + seed + mode, targeting the weakest dimension, and one 10-minute standalone drill (e.g. "estimate storage for 1B 280-char posts w/ 5 yr retention, out loud, in 3 min").
  4. Keep it under ~40 lines. No fluff.

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