agentleFS
Sign inStart free
kevmookevmoo/kevmoo_skills/skills/quiz-me/SKILL.md

quiz-me

Skill22 starsChanged 10 days agoNo licenceView on GitHub

Builds a primary-source-grounded prerequisite graph (or linear mastery track) of atomic concepts and tests the user across unfamiliar technical domains, specifications, or codebases one concept at a time with hard comprehension gates, miss diagnosis, targeted teaching blocks, and fresh transfer questions. Use when invoking /quiz-me, "quiz me", verifying that you truly know and have internalized a complex domain or architecture from first principles, or mapping prerequisite concepts and key mental shifts with active comprehension checks. Don't use for single-turn factual lookups (use quick-question), unquizzed learning walkthroughs, document/code review, co-editing, or issue triage (use slice-and-dice), branching design decision trees (use grilling or clarify-confirm-continue), or passive text summarization.

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use reflect and handoff.

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.
  • Microsoft AzureSkill

    reflect

    Learning capture system that extracts HIGH/MED/LOW confidence patterns from conversations to prevent repeating mistakes. Use after user corrections ("no", "wrong"), praise ("perfect", "exactly"), or when discovering edge cases. Complements .squad/agents/{agent}/history.md and .squad/decisions.md.

    Also in 3 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 2 are distinctive, and 8 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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