agentleFS
Sign inStart free
junho5400junho5400/cramcode/.claude/skills/next/SKILL.md

next

Skill1 starsChanged 4 months agoMITView on GitHub

Decide what to study next in cramcode. Runs the deterministic recommender over the knowledge tree and explains the plan. Use when the user asks "what should I work on", "let's study", or starts a session.

40 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use quick, project and 8 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.
  • codebycoreySkill

    quick

    Quick start a change with minimal interaction. Use when fast-tracking a straightforward change that needs proposal, design, and tasks in one step.

    Also in 3 projects that use this

  • BugRogerSkill

    project

    Project lifecycle management. Dispatches to Ada.

    Also in 3 projects that use this

  • MicrosoftSkill

    cleanup

    Also in 4 projects that use this

  • ArvorCoSkill

    clarify

    Identify and resolve ambiguities in feature specifications. Use when spec has unclear requirements. Triggers on: clarify spec, resolve ambiguities, clarify requirements.

    Also in 3 projects that use this

  • genomewalkerSkill

    explore

    RLM-style recursive memory exploration - dynamically navigate the memory graph

    Also in 3 projects that use this

  • GoogleSkill

    critique

    Expertise in auditing and fixing repository scripts and GitHub Actions workflows to ensure technical robustness and security.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 2

    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:

    If it errors with "no memory found", run python3 scripts/init_memory.py first, then suggest /import before continuing.

    line 12
  2. Distinctive:

    If topics are locked, mention at most one sentence about what unlocks next.

    line 24
  3. Distinctive:

    Do NOT override the recommendation (PROTOCOL.md, iron rule 6).

    line 26

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

/next — what to study today

  1. Run:
    python3 scripts/recommend.py --json
    If it errors with "no memory found", run python3 scripts/init_memory.py first, then suggest /import before continuing.
  2. Present the plan conversationally, grounded in the JSON:
    • The focus topic and its effective coverage.
    • Each target KC by NAME with its one-line reason (never studied / decayed / failed last attempt). Pull the KC names from curriculum/topics/<topic>.json if you want richer phrasing.
    • The chosen problem and the pairing: in learn mode, "I'll teach <teach problem>, then you'll take on <test problem> yourself"; in review mode, "you've covered these before — go straight to a cold /test on <test problem>".
    • If topics are locked, mention at most one sentence about what unlocks next.
  3. Do NOT override the recommendation (PROTOCOL.md, iron rule 6). If the user asks for a different topic or problem, honor it explicitly: use their choice for /teach or /test and note the tree will record it all the same.
  4. End by offering the next step: /teach (learn mode) or /test (review mode).

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