agentleFS
ProjectAJ14ProjectAJ14/eklavya/skills/skip/SKILL.md

skip

Skill29 starsChanged 22 days agoMITView on GitHub

Skip Eklavya's questions for the rest of this session only — no file changes, memory keeps recording, and the next session asks as usual.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call set_config with scope: "session" and quiz: { enabled: false }.

    line 11

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

/eklavya:skip

The shortcut for /eklavya:mode off --session. Take no argument and ask nothing first: the developer has already said what they want, and a question about it is the interruption they are skipping.

Call set_config with scope: "session" and quiz: { enabled: false }. Nothing else goes in that call — session scope takes only quiz, and it writes no file, so the project and global settings are untouched and every other session, open now or started later, still asks as usual.

Say one line back:

  • that questions are off until this session ends, naming the session_id if set_config reports one you did not pass;
  • that memory is still recording — this was a request for quiet, not for a gap in the history;
  • how to resume sooner: /eklavya:mode on --session, or just ask to turn Eklavya back on.

If set_config returns a note, the project enforces the commit gate: say that a commit still waits for the quiz, and keeps growing while the session is silent. If it returns no_session, no hook has registered this session — say so and offer /eklavya:mode off at global scope instead, which they will have to turn back on themselves. Do not fall back to it without asking.

Memory keeps recording, but concepts logged while skipped are not asked later: a later session start removes logged work that no question reached.

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.