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

study-unstudied

Skill0 starsChanged 29 days agoMITView on GitHub

List sources and concepts with no study log yet, ranked by priority. Use when the user asks: what haven't we studied, what should I study next.

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 each unstudied source's matching brainstorm from brainstorming/ (filename pattern *<source-slug>*)

    line 17
  2. Very specific:

    Keep the list scannable. Full /study-status output belongs in that skill — here, one line per item.

    line 40
  3. Very specific:

    Not a writeable queue: If you want to pin specific sources for later, add them to todos/ via /add-todo.

    line 48

≈ “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-unstudied — What hasn't been studied yet

Live query over sources/ + concepts/ + study-sessions/. No persisted queue — regenerated on every invocation so state is always accurate.

Flow

  1. Enumerate sources. List every sources/YYYY-MM-DD-*.md file (exclude README.md, INDEX.md).
  2. Enumerate concepts. List every concepts/<slug>/ subfolder with a README.md.
  3. For each source — check if study-sessions/<source-filename>.md exists. If not → unstudied source.
  4. For each concept — check if concepts/<slug>/study-log.md exists AND has at least one ## Checkpoint — header. If not → unstudied concept.
  5. Score + rank unstudied items:
    • Read each unstudied source's matching brainstorm from brainstorming/ (filename pattern *<source-slug>*)
    • Count convergence-tag membership (from brainstorm frontmatter convergence: list) — higher count = more leverage
    • Sources in clusters of 3+ brainstorms (per scripts/kb-convergence-scan.py threshold) rank first
    • Concepts rank by number of referenced KB signals in their README.md
  6. Render:
## Unstudied

### Sources (<N>)

**High-leverage cluster: <cluster-tag>** (<N> brainstorms converge here)
- [[sources/YYYY-MM-DD-<slug>]] — <short description>
- ...

**Other unstudied:**
- [[sources/...]] — ...

### Concepts (<N>)
- [[concepts/<slug>]] — <description>
- ...

Keep the list scannable. Full /study-status output belongs in that skill — here, one line per item.

Voice mode stub

--mode voice: same query, renderer narrates "you have 23 unstudied sources, most clustered around <top-cluster> — top three are <X>, <Y>, <Z>. Want to start with one of those?"

What /study-unstudied is NOT

  • Not a writeable queue. If you want to pin specific sources for later, add them to todos/ via /add-todo.
  • Not a ranking of importance. Convergence-tag count is a proxy for leverage, not intrinsic value — a standalone source can still be worth studying.
  • Not a replacement for /kb-audit. That skill flags stale/broken things; this one flags unstudied ones.

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.