agentleFS
Sign inStart free
kleyver14kleyver14/study-skills/skills/study-status/SKILL.md

study-status

Skill0 starsChanged 43 days agoMITView on GitHub

Show where the user stands in their study plan(s) — next session, progress, schedule drift, buffer left, pending concepts, last results, the projected end date at their real pace and whether the checkpoints still land before their milestones; list all plans and switch the active one; and replan cadence or deadline when life changes. Use whenever the user asks "cómo voy", "how am I doing", "what's my progress", "cuánto me falta", wants to see or switch between study plans, says their schedule or exam date changed, or asks to re-plan ("ahora solo puedo 2 veces por semana", "me adelantaron el examen").

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. loursCreatif/ours-stack★ 1same name
    2. Slava-code/slava-stack★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

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-only, except for two things: switching the active plan, and replan.

    line 8
  2. Very specific:

    milestones: if check reports milestone_without_checkpoint, say which milestone will arrive without a checkpoint before it, and offer to …

    line 29
  3. Very specific:

    If behind_sessions > 0, add one line: *"/study-next will propose how to absorb it."*

    line 34

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

/study-status — where do I stand

Read-only, except for two things: switching the active plan, and replan.

$ARGUMENTS: empty (active plan) · all (list plans, offer to switch) · <slug> · replan.

Step 0

SHARED="$HOME/.claude/skills/study-shared"; SS="$SHARED/scripts/study_state.py"
python3 $SS registry list
PLAN=$(python3 $SS registry resolve $SLUG) && python3 $SS status "$PLAN" && python3 $SS check "$PLAN"

Default — summary

Turn the JSON into a short, honest picture in the user's language (language.md):

  • next session (number, title, status, planned date) · progress closed/total
  • drift: on track / N behind / N ahead, and what that means for the horizon
  • buffer left x/y
  • projected end at the real pace (projected_end) vs the planned end. Say it even when it hurts; with fewer than two sessions opened it falls back to the planned pace, so say that too
  • milestones: if check reports milestone_without_checkpoint, say which milestone will arrive without a checkpoint before it, and offer to pull the checkpoint forward (only with approval)
  • concepts still pending (count, plus the three oldest from PLAN.md's concepts region)
  • last evaluation

If behind_sessions > 0, add one line: "/study-next will propose how to absorb it."

all

List every plan with * on the active one. Offer to switch: python3 $SS registry active <slug>.

replan

Life changed. Read $SHARED/references/recovery.md, section Replan. Ask only two things (AskUserQuestion): the new cadence, and whether the horizon changed (new date / roughly / none). Then:

python3 $SS project "$PLAN" --cadence <new> --start $(python3 $SS today) --from-session <next.session>
python3 $SS set "$PLAN/PLAN.md" horizon=<h> target_date=<d|null> target_week=<w|null>
python3 $SS check "$PLAN"

Show the new calendar and the check result. If horizon: fixed and the sessions no longer fit before target_date, enter the fixed-horizon policy (buffer → double → trim) with approval at each step. Never regenerate content here: dates move, content stays.

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