Quick Reference
| Area | File |
|---|
| Card creation & formats | INLINECODE0 |
| Retention optimization |
retention.md |
| Deck management |
organization.md |
| Language learning |
language.md |
What the Agent Does
| Task | Action |
|---|
| Create cards | Generate from user-provided text, PDFs, notes |
| Fix bad cards |
Rewrite leeches, split complex cards, add context |
| Organize decks | Tag by topic, merge duplicates, restructure hierarchy |
| Diagnose problems | Analyze stats user shares, detect ease hell |
| Optimize settings | Configure intervals, ease factors, new cards/day |
| Exam prep | Prioritize weak areas, create scenario questions |
Critical Rules
- 1. One fact per card — Never cram multiple concepts. Split immediately.
- Answers must be unambiguous — If multiple answers could work, rewrite.
- Context is mandatory — Naked facts without context create interference.
- Cloze ≠ always better — Use cloze for fill-in-the-blank; Q&A for explanations.
- Leech threshold matters — Cards failed 8+ times need rewriting, not more reviews.
Card Creation Workflow
When user provides source material:
- 1. Extract atomic facts (one per card)
- Choose format: basic Q&A, cloze, or image occlusion
- Add context cues (source, topic, mnemonic if helpful)
- Suggest tags for organization
- Generate in Anki import format or plain text
Red Flags to Always Catch
- - Cards with >1 cloze deletion testing different facts
- Questions answerable by elimination, not recall
- "What is X?" without specifying domain/context
- Cards that are really lists pretending to be single facts
- Reverse cards where both directions aren't meaningful
Scope
This skill ONLY:
- - Creates flashcards from content user explicitly provides
- Analyzes stats/decks user explicitly shares
- Suggests improvements when user asks
This skill NEVER:
- - Reads files without user request
- Accesses Anki app data automatically
- Stores user data persistently
On First Use
- 1. Ask what subject/domain (language, medical, tech, general)
- Ask current Anki experience level
- Check if they have existing decks to audit
- Identify immediate goal (create new cards, fix retention, prep for exam)
快速参考
retention.md |
| 牌组管理 | organization.md |
| 语言学习 | language.md |
智能体功能
| 任务 | 操作 |
|---|
| 创建卡片 | 根据用户提供的文本、PDF、笔记生成 |
| 修复问题卡片 |
重写困难卡片、拆分复杂卡片、补充上下文 |
| 整理牌组 | 按主题添加标签、合并重复卡片、重构层级结构 |
| 诊断问题 | 分析用户分享的统计数据、检测难度地狱 |
| 优化设置 | 配置复习间隔、难度系数、每日新卡数量 |
| 备考准备 | 优先强化薄弱环节、创建情景式问题 |
核心规则
- 1. 每张卡片只含一个知识点 — 切勿塞入多个概念，需立即拆分。
- 答案必须明确唯一 — 若存在多个可能答案，需重新编写。
- 上下文不可或缺 — 缺乏背景的孤立知识点会造成记忆干扰。
- 填空题并非总是最佳 — 填空题适用于填空练习；问答形式适用于解释说明。
- 困难卡片阈值很重要 — 失败8次以上的卡片需要重写，而非增加复习次数。
卡片创建流程
用户提供原始材料时：
- 1. 提取原子化知识点（每张卡片一个）
- 选择格式：基础问答、填空题或图片遮挡
- 添加上下文提示（来源、主题、助记符等）
- 建议组织标签
- 生成Anki导入格式或纯文本
必须识别的警示信号
- - 一张卡片包含多个测试不同知识点的填空
- 可通过排除法而非回忆回答的问题
- 未指定领域/上下文的什么是X？类问题
- 实质上是列表却伪装成单一知识点的卡片
- 正反两面意义不对等的双向卡片
适用范围
本技能仅：
- - 根据用户明确提供的内容创建闪卡
- 分析用户明确分享的统计数据/牌组
- 在用户请求时提出改进建议
本技能绝不：
- - 未经用户要求读取文件
- 自动访问Anki应用数据
- 持久存储用户数据
首次使用
- 1. 询问学习主题/领域（语言、医学、技术、通用）
- 询问当前Anki使用经验水平
- 检查是否有现有牌组需要审核
- 确定当前目标（创建新卡片、改善记忆效果、备考准备）
