Slava-codeSlava-code/slava-stack/.claude/skills/study-status/SKILL.md

study-status

Skill0 starsChanged 29 days agoMITView on GitHub

Read-only: where we left off studying a source or concept (latest checkpoint, open threads). Use when the user asks: where were we on X, what have we studied about Y.

2 other projects use a version of this.

Adopted by

Most recently taken up by

kleyver14/study-skillstheir own version, first seen Sep 30, 2026
loursCreatif/ours-stacktheir own version, first seen Jul 4, 2026

Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
loursCreatif/ours-stack★ 1same name
kleyver14/study-skills★ 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 repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-entrySkill
- add-todoSkill
- complete-todoSkill
- deadlinesSkill
- financeSkill
- financial-summarySkill
- kb-add-folderSkill
- kb-archiveSkill
- kb-auditSkill
- kb-promoteSkill
- kbSkill
- kb-synthesizeSkill
- meetingSkill
- studySkill
- study-unstudiedSkill

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
If caller is /study in resume mode, return this block as-is for use as session preamble.
line 50
Very specific:
Not /study: Does not start a session.
line 58

≈ “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 — Read-only study-log resume query

Compact summary of where a source or concept study log currently stands. Read-only — no lock, no writes, no session created.

Arguments

/study-status <source-slug> — source study log (looks up study-sessions/*-<arg>-*.md)
/study-status <concept-slug> — concept study log (looks up concepts/<arg>/study-log.md)

Fuzzy-match on slug-contains / tag-match / title-keyword if the exact match fails.

Flow

Resolve target. Same resolution order as /study (source filename → concept folder → fuzzy). If ambiguous, list candidates and stop (don't pick).
If no study log exists → report: "never studied. Last touch via [[brainstorming/<matching-brainstorm>]] if one exists, else none." For concepts, report the folder doesn't exist.
If study log exists → parse frontmatter + body. Extract:
- last_checkpoint: date
- Count of ## Checkpoint — headers (the session count)
- Latest checkpoint's **Open threads → next session** bullets
- Latest checkpoint's **Open threads** content as-is (those ARE the resume hints)
- Last 3 bullets from the latest checkpoint's **What we covered** section (for recent-context recall)
- Any [?question] / [?decision] tags still open in the latest checkpoint
Render compact output:

## Study log — <source or concept name>

Studied <N> session(s); last checkpoint <date>.

**Where we left off:**
- <open threads bullets>

**Recent context (last 3 from "What we covered"):**
- <bullet>
- <bullet>
- <bullet>

**Open candidate flags:**
- [?question] <text>
- [?decision] <text>

To continue: `/study <slug>`

If caller is /study in resume mode, return this block as-is for use as session preamble.

Voice mode stub

--mode voice: same retrieval, renderer drops markdown, phrases wikilinks naturally, prefers "last session we covered..." narration over bullet dumps.

What `/study-status` is NOT

Not /study. Does not start a session.
Not /study-unstudied. Answers "where are we on X?" not "what haven't we touched?"
Not a diff of checkpoints. Shows latest only. For history, read the study-log file directly or git log.

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