card
Skill1 starsChanged 51 days agoMITView on GitHub
Add, edit, or regenerate flashcards for a lesson or concept note, following the card-writing rules and preserving FSRS scheduling state on untouched cards.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- yiyaw-lab/agent-armortheir own version, first seen Jun 22, 2026
- dqtx760/skills-managetheir own version, first seen May 27, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- dqtx760/skills-manage★ 2same name
- yiyaw-lab/agent-armor★ 1same 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
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
- Very specific: line 16
Invariants: never modify a line containing <!--SR: except when the user explicitly regenerates/edits that exact card (removal of the …
≈ “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.
Files
/card <note-or-topic> [--add "<what>"] [--edit] [--regenerate]
Card surgery on one card file. Read docs/pedagogy.md (card rules) and docs/vault-schema.md (cards schema) first. Vault: <vault>.
- Locate the card file: for a lesson,
courses/<slug>/cards/NN Cards.md; for a concept or free topic, the inbox fileconcepts/Inbox Cards.md(deck#flashcards/inbox; create fromtemplates/cards.mdif missing). If ambiguous, list candidates and ask. - Mode:
--add: append new cards for the requested fact/idea (default 1–3, atomic, per card rules). Typical after a/tutorinsight.--edit: show the current cards numbered; user says what to change. Rewrite only the card(s) named.--regenerate: propose a fresh card set from the source note; show a diff-style summary (kept / replaced / new) and confirm before writing — replaced cards lose their FSRS history by design.
- Invariants: never modify a line containing
<!--SR:except when the user explicitly regenerates/edits that exact card (removal of the comment = deliberate reset — say so). Keep the deck tag as the first body line. Updatecard_countandupdated:. - Report what changed and how many cards are now due-new.
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
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.