Use when the user wants to see a topic's review progress or dashboard. 触发:「看进度」「stats」「复习到哪了」「进度如何」「还剩多少没复习」。
Scanned 8/31/2026
Install to Claude Code
npx -y skills add guoqiaoZhou/study-with-claude-code --skill stats --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Stats?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/guoqiaozhou-stats)More formats (shields.io, HTML) on the badges page.
---
name: swcc-stats
description: Use when the user wants to see a topic's review progress or dashboard. 触发:「看进度」「stats」「复习到哪了」「进度如何」「还剩多少没复习」。
argument-hint: "[topic]"
user-invocable: true
---
# swcc · stats — 复习进度展示
只读地展示一个专题的复习进度。
> 开始前先读数据契约:`${CLAUDE_PLUGIN_ROOT}/skills/_shared/data-contract.md`。本技能**只读不写**。
参数:`$ARGUMENTS` —— 可选 topic(默认 config 的 `activeTopic`)。
---
## 核心原则
1. **只读,不改任何文件。**
2. **不编数字。** 趋势/统计数据不足时如实留空或省略,绝不臆造。
3. **最该复习的排在最前。** 薄弱点按 `nextReview` 升序,让用户一眼看到今天该补什么。
---
## 流程
### 1. 加载数据
- topic 缺省 → 读 `$HOME/.study-with-cc/config.json` 的 `activeTopic`(config 不存在或缺 activeTopic 时,按数据契约第九节「兜底」扫 `topics/` 自愈,不要直接报错)。
- 该专题不存在 → 提示先 `/swcc-plan <topic>`,停止。
- 读 `progress.json`(必要时读 `review-sessions/` 做趋势聚合)。
### 2. 计算
- 按 `nodes` 的 `status` 统计:mastered / in_progress / not_started 各占多少、百分比。
- `weakPoints` 按 `nextReview` 升序排列(最该复习的在前)。
- 从 `stats` 取 streak、totalReviewCount、totalReviewTime。
### 3. 渲染
```
📊 <topic> 复习进度
━━━━━━━━━━━━━━━━━━━━
🟢 已掌握:<a> / <total> (<x%>)
🟡 学习中:<b> / <total> (<y%>)
🔴 未开始:<c> / <total> (<z%>)
🔴 薄弱点(<n>)
1. <concept>(节点:<node> 上次:<lastReviewed> 下次:<nextReview>)
2. …
🔥 连续复习:<streak> 天
🔢 总复习次数:<totalReviewCount>
⏱️ 总复习时长:<totalReviewTime> 分钟
```
掌握度变化趋势(可选):若 `review-sessions/` 有多份记录,可按日期聚合各节点掌握度,画一个简单的 ASCII 趋势条;数据不足时省略此段,不要编造数字。
---
## 质量基准
- 比例数字和 progress.json 对得上;薄弱点按 nextReview 正确排序。
- 数据不足的段落如实省略,不臆造趋势。
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.