Agent skill
anki-card-generator
Use this skill to generate Anki flashcards in simple-anki-sync format for active memorization of any knowledge. Invoke whenever the user wants to memorize, make flashcards, create study cards, or turn knowledge into reviewable cards — including phrases like 生成 Anki 卡片, 做闪卡, 帮我记忆, "anki cards", "flashcards", "study cards", "memorize this". The skill applies LessWrong spaced-repetition best practices: atomic questions, standardized templates, appropriate detail levels. Not for general learning plans, summaries, or explanations — only for producing actual Anki-formatted cards ready for import.
Install this agent skill to your Project
npx add-skill https://github.com/niracler/skill/tree/main/skills/learning/anki-card-generator
Metadata
Additional technical details for this skill
- openclaw
-
{ "emoji": "\ud83c\udccf" }
SKILL.md
Anki Card Generator
Generate high-quality Anki cards based on LessWrong best practices and simple-anki-sync format.
Pre-Generation Clarification
Before generating cards, clarify with user if unclear:
- Scope: "Which aspects to focus on?" (for broad topics)
- Depth: "Basic concepts only, or detailed Level 2/3 cards?"
- Quantity: "How many cards? (Recommend 5-10 for core concepts)"
- Context: "Any specific exam or application scenario?"
Proceed only after understanding requirements.
Output Format
Use simple-anki-sync format:
#anki/[domain]/[topic]
| [Question] |
| ---------- |
| [Core answer]<br><br><small>💡 [Supplementary info]</small> |
Format Options
Option A (Recommended): HTML tags
| 唐朝建立时间 |
| ---------- |
| 618年,李渊建立<br><br><small>💡 隋末农民起义后起兵</small> |
Option B: Separator
| 唐朝建立时间 |
| ---------- |
| 618年,李渊建立 ——— 💡 隋末农民起义后起兵 |
Option C: Parentheses
| 唐朝建立时间 |
| ---------- |
| 618年,李渊建立(趣闻:其子李世民功劳最大) |
Atomization Rules
Word Limits
- English: Max 9 words, absolute limit 18 words
- Chinese: Recommended 15-20 characters, absolute limit 30-35 characters
- Max items: 3 bullet points per card
Core Principle
If a card can be split into two shorter cards, split it.
Question Design
Standardized Templates
- Time: "X 时间" (not "X发生于何时?")
- Definition: "X 定义" (not "什么是X?")
- Person: "who X" (not "谁做了X?")
- Pros/Cons: "X 利弊" (not "X的优势是什么?")
Key Rules
- Match real-world recall scenarios
- Use plain, unremarkable wording
- Avoid words in question that appear in answer
- Keep all critical info in answer, not question
Answer Construction
Core Answer
- Strictly follow word limits
- Answer should be meaningful without the question
- All key information in answer
Supplementary Info (Optional)
Format: <br><br><small>💡 content</small>
Emoji Guide:
- 💡 Fun fact / trivia
- 📝 Note / explanation
- 🔗 Related concept
- ⚡ Tip / key point
- 📊 Data / statistics
- 📅 Date / timeline
Keep supplementary info to 10-20 characters.
Handle System
Use > to reference related cards:
| 牛顿贡献 |
| ------- |
| >运动定律 >万有引力 >微积分发展 |
Detail Levels
- Level 1: Basic concept (core answer)
- Level 2: Detailed info (supplementary section)
- Level 3: Advanced details (create separate cards)
Tag Naming
Use English tags: #anki/[domain]/[topic]
Common domains: history, programming, language, science, mathematics, psychology, economics, philosophy, medicine, art
Quality Checklist
Per Card
- Core answer within word limit?
- Correct supplementary format?
- Can it be further split?
- Question matches real recall scenario?
- No memory shortcuts?
- All key info in answer?
Card Set
- Appropriate cross-references?
- Proper detail levels?
- No redundancy?
Domain Examples
See references/examples.md for detailed examples:
- History (ancient China)
- Programming (Python)
- Language learning (English)
- Academic concepts (psychology)
- Complex topics (quantum mechanics)
- Error corrections
- Advanced techniques (reversible cards, redundancy design)
Workflow
- Receive input: Knowledge points, wiki links, study materials
- Clarify: Ask questions if uncertain
- Generate: Follow atomization and best practices
- Output: simple-anki-sync markdown format
Core Philosophy: Prioritize sustainability and real recall scenarios over comprehensive coverage. Focus on preventing cognitive and motivational barriers.
When NOT to Use
❌ 不适合卡片化的内容:
- 需要视觉理解的(图表、流程图)
- 超过 50 行的代码块
- 高度情境依赖的知识
✅ 替代方案:
- 视觉内容 → 配图索引卡片
- 大代码块 → 代码 Snippet 库
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
pinboard-manager
Use this skill for ALL Pinboard bookmark management tasks — this is the go-to skill whenever Pinboard (pinboard.in) is involved. Invoke immediately when the user wants to: audit or reorganize messy tags, check for broken/dead links, identify stale or outdated bookmarks, clean up their bookmark collection, or manage their Pinboard account in any way. Also use when the user says 整理书签, 检查死链, 整理 tag, 书签管理, pinboard cleanup, bookmark audit, tag consistency, timeliness check, pinboard 过时检测. Do NOT trigger for: browser bookmark management, Raindrop.io, or general URL checking without Pinboard context.
yunxiao
Use this skill for all Alibaba Cloud 云效 (Yunxiao) DevOps operations on codeup.aliyun.com. Invoke IMMEDIATELY when the user wants to: create or manage Merge Requests (MR) on codeup, update work items/tasks in 云效, query MR lists or task status, create version tags via 云效 API, or push code to a codeup remote. Key triggers: 创建 MR, 提交评审, 云效, yunxiao, codeup, 更新任务, 查看任务, 发布版本, 打 tag. Handles both MCP tool mode and aliyun CLI fallback. Do NOT use for GitHub PRs (use git-workflow), Jira, GitLab, or non-Alibaba platforms.
weekly-report
Use this skill whenever the user wants to write or generate a structured weekly work report (软件研发周报) — the formal 3-section corporate format with 本周工作总结, 下周工作计划, and 其他事项. This skill automatically collects data from git logs, Obsidian diary Work Log entries, schedule YAML files, GitHub PRs, and 云效 MRs/tasks to draft the report. Invoke when the user says 周报, 软件研发周报, 本周工作总结, 写周报, weekly report, end-of-week summary, or asks to prepare a work summary for their manager/team. Do NOT use for personal diary entries, monthly reviews, OKR summaries, meeting notes, or quarterly retrospectives.
code-sync
Use this skill to batch-sync all git repos across machines — pushing uncommitted changes at end of day or pulling latest at start of day. Invoke when the user wants to sync all repos (not just one), mentions 「下班同步」「上班更新」 「code-sync」, or describes end-of-day push / morning pull across ~/code. Triggers on: "sync all my repos", "end of day sync", "morning update", "push all dirty repos", "pull all projects", 「同步代码」「下班同步」「上班更新」. Do NOT trigger for: single-repo git operations, committing specific files (use git-workflow), general git push/pull questions, or workspace template updates.
ha-integration-reviewer
Strict Home Assistant integration code review for PR preparation. Covers Quality Scale rules, code style, Config Flow, test coverage, and docs. Invoke immediately when the user says "review my HA integration", "check HA compliance", "HA code review", "HA Quality Scale check", "home assistant PR review", "审查我的 HA 集成", "检查我的代码是否符合 HA 规范", "帮我 review 一下准备提交的代码". Launches parallel check agents across 5 dimensions. Do NOT use for: non-HA code review, configuring HA automations, HACS plugins, or Lovelace card development.
schedule-manager
(macOS only) Use this skill for ALL Apple Calendar and Reminders management tasks using osascript and reminders-cli, following GTD methodology. Invoke immediately when the user wants to: schedule a meeting or event, add a todo or reminder, check today's agenda, plan the week ahead, do a weekly review, or capture any task they don't want to forget. Also use when the user says 安排会议, 创建提醒, 查看日程, 规划下周, 添加待办, 记一下, 别忘了, 今天要做什么, 周回顾. This is the right skill any time the user wants to interact with macOS Calendar or Reminders apps.
Didn't find tool you were looking for?