agentleFS
Sign inStart free
b0r1spb0r1sp/claude-skill-anki/SKILL.md

anki

Skill1 starsChanged 7 months agoMITView on GitHub

Anki flashcard skill — create cards from documents or conversation and import via AnkiConnect. Proactively suggest a card whenever a concept worth remembering comes up, even without /anki. Triggers: anki, flashcards, Lernkarten, Karteikarten, spaced repetition, "Karten erstellen", "cards from PDF", exam prep.

6 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions6 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 6

    1. nailuoGG/anki-mcp-server★ 253same name
    2. djt97/anki-skill★ 4same name
    3. anath2/anki-skill★ 3same name
    4. andrevictor23-tech/claude-skills★ 0same name
    5. jstilb/ai-assistant★ 0same name
    6. jvgitty/claude-anki-skill★ 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.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    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
  1. Very specific:

    When this skill is invoked (via /anki or a matching trigger), ask the user to choose a mode — unless it is already obvious from context …

    line 14
  2. Very specific:

    Strict step adherence: every step in the chosen mode file must be completed in order.

    line 25

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

Anki Skill — Dispatcher

When this skill is invoked (via /anki or a matching trigger), ask the user to choose a mode — unless it is already obvious from context (e.g. one or more files were attached → Mode 1; a concept was just explained → Mode 2).

What would you like to do?
[1] Import from document(s)  — batch cards from one or more PDFs, PPTXs, or other files
[2] Create cards             — for a concept from our conversation
[3] Research & create cards  — give me a topic, I'll research it and build a learning plan first

Strict step adherence: every step in the chosen mode file must be completed in order. Do not skip, combine, or anticipate steps. Wait for explicit user confirmation at every [y/n] prompt before proceeding to the next step.

Then load and follow the instructions for the chosen mode:

ChoiceInstructions
1 — Import from document(s)references/mode_import_docs.md
2 — Create from conversationreferences/mode_conversation.md
3 — Research & createreferences/mode_research.md

All modes share:

  • Card preview format → references/shared_preview.md
  • Pre-import check & import → references/shared_import.md
  • Card creation rules → references/card_guidelines.md

Proactive suggestions (no invocation needed)

Even without /anki, follow the proactive suggestion rules in references/mode_conversation.md whenever the user explains a concept or encounters a gotcha worth remembering long-term.

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