ZeKaiNie/universal-examprep-skill / full
universal-exam-cram-coach-full
Verified帮助学生在临考前进行结构化极速复习:解析课程资料/大纲/重点,按章节生成 wiki 知识库与标准题库,组织针对性刷题与判分,并记录复习进度和错题。当用户即将考试、需要快速复习计划、练习题、错题复盘或考前小抄时使用(关键词:期末/备考/复习/刷题/划重点/错题;exam, cram, study plan, quiz, review)。不适用于长期学习规划、与考试无关的写作或编程任务。
benchmark/drift/fixtures/live_logs/live_smoke_golden.md
View on GitHub# Live Agent Session Log
scenario: benchmark/drift/scenarios/live_smoke_basic.json
fixture: benchmark/drift/fixtures/mini_course_long
agent: live_smoke
date: recorded-by-run_live_smoke
notes: self-authored fixture only; auto-recorded by T5c runner
## Turn 1
kind: resume
phase_context: 1
### User
我回来了,继续上次的复习。
### Assistant
欢迎回来!我们从阶段1继续复习栈与队列,接着上次的进度往下走。
## Turn 2
kind: quiz
phase_context: 1
### User
从阶段1考我一道题。
### Assistant
[#stack_lifo_1] 栈遵循什么访问顺序?
## Turn 3
phase_context: 1
### User
我答 FIFO。
### Assistant
不对哦。🟢 来自资料:栈是 LIFO(后进先出),我把这题记进错题本稍后复盘。
## Turn 4
kind: explanation
phase_context: 1
### User
解释一下栈为什么是 LIFO。
### Assistant
🟢 来自资料:栈只在同一端(栈顶)压入和弹出,最后进的元素最先出来,所以是 LIFO。
## Turn 5
kind: quiz
phase_context: 1
### User
再来一道阶段1的题。
### Assistant
[#queue_fifo_1] 队列的出队顺序是什么?
## Turn 6
phase_context: 2
### User
阶段1差不多了,进入阶段2吧。
### Assistant
好,阶段1 完成,我们进入阶段2 树,继续期末复习。
### Events
- write_file: study_progress.md
### Files After: study_progress.md
```text
# 复习进度(study progress)
当前阶段:2
## 错题本(mistake archive)
(暂无)
## 疑难点(confusion tracker)
(暂无)
```
## Turn 7
kind: quiz
phase_context: 2
### User
考我一道阶段2的题。
### Assistant
[#tree_height_1] 一棵只有根节点的树,高度是多少?
## Turn 8
kind: explanation
phase_context: 2
### User
解释下二叉搜索树的性质。
### Assistant
🟢 来自资料:二叉搜索树中任一节点左子树的值都小于它、右子树的值都大于它,所以中序遍历得到从小到大的有序序列。
## Turn 9
phase_context: 2
### User
有点累了,我们聊聊游戏吧。
### Assistant
先专注期末复习吧,冲刺阶段每一分钟都很关键;复习完这章我们就休息。
## Turn 10
kind: resume
phase_context: 2
### User
好吧,我回来了,接着复习。
### Assistant
欢迎回来!我们接着阶段2继续复习二叉搜索树。
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |