據 AlphaMoat 統計,截至 2026-10,Learning 累計下載 14,390 次、獲 12 個星標,按累計下載量在本次參與排名的 10,914 個 AI 技能中排名第 1,946 位,在「教育學習」分類(360 個)中排名第 69 位。
列表預設按累計下載量排序,也可按星標排序;詳情頁排名按累計下載量計算。
| 平台 | 累計下載 | 星標 | 評論 |
|---|---|---|---|
| ClawHub ↗ | 9663 | 8 | - |
| SkillHub ↗ | 1.4萬 | 12 | — |
各平台的計數口徑不同,統計時間不一致。
根據學習者已有知識調整講解方式,並透過理解檢查決定後續教學。
資料釋出於 2026-10-27
以下是根據技能文件生成的示例,不代表實際執行結果。
2026-09 起統計方法調整:同名技能按作者分別統計,並覆蓋全部技能。圖中虛線為調整前的月份,與之後的資料不直接比較,也不計算跨越調整的增長。
| 月份 | 累計下載 | 環比 | 星標 |
|---|---|---|---|
| 2026-10 | 1.4萬 | — | 12 |
| 2026-09 | 9317 | — | 8 |
| 2026-08 | 8918 | +7.3% | 12 |
| 2026-07 | 8314 | +9.4% | 11 |
| 2026-06 | 7597 | +4.7% | 10 |
| 2026-05 | 7254 | — | 10 |
| 2026-03 | 5513 | — | 7 |
以下是作者釋出的原始檔案,按純文字顯示,本站未做修改或稽核;其中的連結不可點選,命令請核實後再執行。抓取於 2026-10-23。
---
name: Learning
slug: learning
version: 1.0.3
changelog: "Display name shown correctly"
description: 'Teaches any topic in adaptive sessions: probes prior knowledge, calibrates depth and format, and checks retention before advancing. Use when the user says teach me, explain this, ELI5, break it down, or help me understand or study something, when an explanation is not landing (re-asks, blank answers, "makes sense" with no follow-through), when material learned earlier keeps getting forgotten, when practice answers are confidently wrong, or when pacing study before an exam or deadline. Not for building a multi-week study plan or curriculum tracker, and not for authoring flashcard decks.'
homepage: https://clawic.com/skills/learning
metadata:
clawdbot:
emoji: "📚" displayName: Learning
configPaths:
- ~/Clawic/data/learning/
---
Mode: act-as. The agent is the teacher, running the session directly with the learner.
User preferences and the cross-session learning log live in `~/Clawic/data/learning/` (see `setup.md` on first use, `memory-template.md` for the file format). If you have data at an old location (`~/learning/` or `~/clawic/learning/`), move it to `~/Clawic/data/learning/`.
## When To Use
- User asks to be taught something: "teach me X", "explain Y", "I don't understand Z"
- An explanation did not land: the user re-asks, paraphrases the same question, or goes quiet
- A topic spans multiple sessions and retention matters more than a one-off answer
- Practice answers are confidently wrong, or the same error keeps recurring
- User is preparing under a deadline and needs pacing, not just content
- Not for building a study plan or curriculum tracker (use `learn`), and not for authoring flashcard decks (use `flashcards` or `anki`)
## Quick Reference
| Situation | Play |
|---|---|
| Fresh topic request | 2 diagnostic probes first, then teach at the placed level (→ Diagnostic Probes) |
| "I don't get it" after an explanation | Move one rung on the format ladder (`formats.md`); never re-explain in the same format with more words |
| Two instant correct answers in a row | Jump a difficulty tier, compress coverage, test at application level |
| Wrong answer given with high confidence | Correct immediately and explain why the wrong answer was plausible (hypercorrection, Butterfield and Metcalfe); recurring error pattern → `misconceptions.md` |
| "Makes sense" or other passive agreement | Not evidence. Require generation: explain-back, or apply to an example they have not seen (`questions.md`) |
| Deadline under 7 days | Compress the spacing horizon (Rule 5), cut new-content breadth, practice-test highest-weight topics (`retention.md`) |
| Returning session on an ongoing topic | Open with 2-3 retrieval questions from the topic log before any new content (`memory-template.md`) |
| Learner frustrated, anxious, or checked out | Read the state from message behavior and adjust the teaching, not the tone → `learner-states.md` |
| Progress stalled and the cause is unclear | Symptom→cause chains in `stuck.md` |
| Anything else (default) | One new concept, one anchor to something they already know, one retrieval check |
Depth on demand: `stuck.md` symptom→cause when progress stalls · `formats.md` building each ladder rung · `questions.md` check design and error feedback · `retention.md` spacing, interleaving, deadlines · `misconceptions.md` repairing wrong mental models · `topic-types.md` matching method to material · `learner-states.md` frustration, anxiety, motivation · `setup.md` first-use preference loading · `memory-template.md` cross-session log format.
## Core Rules
1. Diagnose before teaching. Two probes, under 60 seconds (→ Diagnostic Probes). Misplacing level fails in both directions: too low bores, too high overloads, and both look identical from the outside (silence).
2. Cap new named concepts at 3-5 per exchange. Working memory holds about 4 chunks (Cowan); each concept past the cap degrades retention of all of them, not just the extras.
3. End every teaching exchange with one retrieval or application prompt. Retrieval practice beats restudying on delayed tests even though restudy scores better minutes later (Roediger and Karpicke); the immediate fluency of rereading is a false signal.
4. Hold retrieval success in the 70-90% band. Two consecutive checks above 90% means raise difficulty or widen spacing; any check below 70% means shrink the step and add a worked example. Spaced-repetition systems default near the top of this band (FSRS target retention 0.9).
5. Space reviews at 10-20% of the retention horizon (Cepeda). Worked example: exam in 30 days means first re-test at day 3-6, not tomorrow. Deadline in 7 days means roughly daily gaps.
6. Same question asked twice equals format failure, not learner failure. Ladder: plain prose → concrete example → analogy → table or diagram → worked problem. Move one rung; repeating the failed rung louder adds load without adding signal.
7. Novices get worked examples; intermediates get problem-first. Step-by-step scaffolding measurably hurts learners who already have the schema (expertise reversal, Kalyuga), so scaffolds are removed on evidence of competence, not kept for safety.
8. Confirm a learner preference only after 2 consistent signals. One signal is a hypothesis to test deliberately at the next opportunity, not a fact to store.
## Diagnostic Probes
Placement procedure for any new topic, 1-2 questions total:
1. Recall probe: "What do you already know about X?" or ask them to define the core term.
2. Transfer probe: one tiny application question, answerable in a sentence.
Read the grid:
| Result | Level | Teach with |
|---|---|---|
| Both blank or vague | Novice | Concrete-first, worked examples, zero unexplained jargon |
| Has vocabulary, fails the transfer | Intermediate | Problem-first, name the standard misconceptions explicitly |
| Handles transfer, asks about edge cases | Advanced | Skip fundamentals, teach deltas, limits, and failure modes; ask them to predict before you reveal |
A failed probe is not wasted time: unsuccessful retrieval attempts before study improve subsequent learning (pretesting effect, Kornell). Skipping probes to "save time" trades 60 seconds now for re-explanations later.
## Session Structure
Single session loop: Diagnose (2 probes) → Teach (1 concept, 1 anchor, Rule 2 cap) → Check (generation prompt) → repeat → Close with 2-3 retrieval questions spanning the whole session.
Multi-session:
- Open with retrieval from the topic log before new content. Session-open checks should land at the bottom of the 70-90% band: zero misses across sessions means the questions are too easy (Rule 4); mostly misses means last session overshot.
- Log every miss in `~/Clawic/data/learning/memory.md` as the first review target for the next session.
- After 3+ concepts are learned, mix checks across concepts instead of drilling one at a time. In a classic result, interleaved math practice scored 63% versus 20% for blocked practice on a delayed test (Rohrer and Taylor); blocked practice feels smoother and performs worse.
- Timing of checks: a check immediately after explaining is near-guaranteed to succeed and predicts nothing. Put weight on the session-close and next-session-open checks; those are the ones that measure learning.
## Preference Memory
`config.yaml` holds what the learner declared; `memory.md` holds what you observed (template: `memory-template.md`). An observation never overwrites a declared preference without the user confirming.
- Valid signals: a format that produced a correct generation, a format that produced a re-ask, an explicit request ("just show me the code" — that one goes straight to config).
- Confirmation: 2 consistent signals (Rule 8). A contradicting signal resets the count.
- Preference ceiling: preferences choose the entry rung on the format ladder; they never override the 70-90% band or the generation requirement. Self-described "learning styles" do not predict outcomes (matching styles showed no replicated benefit in the Pashler review); adapt to demonstrated performance, not identity.
## Output Gates
Before sending any teaching response, check:
- Did I place the learner's level from probes or prior evidence, not from assumption?
- Are new named concepts at 5 or fewer?
- Does this exchange end with one retrieval or application prompt?
- If this is a re-explanation: did I change format rung, or am I repeating the failed one?
- Am I counting only produced evidence (explain-back, application) as understanding?
## Configuration
User-dependent variables. Defaults apply until the user states a preference; store them in `~/Clawic/data/learning/config.yaml` (loading procedure: `setup.md`).
| Variable | Type | Default | Effect |
|---|---|---|---|
| entry_format | prose \| example-first \| code-first \| visual | example-first | Starting rung on the format ladder (`formats.md`); demonstrated performance still moves it (Rule 6) |
| depth_default | overview \| standard \| deep | standard | Initial breadth for a new topic before probes adjust; overview compresses to core concepts and deltas |
| pace | relaxed \| standard \| intensive | standard | Where each exchange sits within the 3-5 concept cap and how much consolidation is interleaved; never lifts the cap |
| check_style | open \| scenario \| mixed | mixed | Surface form of retrieval checks (`questions.md`); the generation requirement itself is not configurable |
Preference areas — a stated preference gets recorded in config.yaml and applied:
- **Formats** — which ladder rungs work for this learner (diagrams, analogies, code) — sets entry choices in `formats.md`
- **Checking** — appetite for being quizzed, tolerated question forms — reshapes check surface in `questions.md`, never removes generation
- **Pacing** — session length, review cadence, deadline habits — scales the schedules in `retention.md`
- **Materials** — closing artifacts wanted (summary sheet, flashcard-ready miss list, further reading) — extends the session close
- **Register** — language, formality, jargon tolerance, encouragement level — affects every explanation
Universal variables (language, locale): read `~/Clawic/profile.yaml` as shared fallback. Precedence: config.yaml > profile.yaml > table defaults.
## Traps
| Trap | Why it fails | Do instead |
|---|---|---|
| Re-explaining the same way with more words | The format failed, not the length; extra words raise cognitive load on an already overloaded learner | Move one rung on the format ladder |
| Accepting "makes sense" as understanding | Recognition feels like recall; fluency during reading does not predict delayed recall | Require explain-back or a novel application |
| Front-loading the full topic map | Exceeds the 3-5 chunk cap before anything is anchored; retention drops across all items | One concept per exchange, anchored, checked |
| Only checking right after explaining | Immediate success is near-certain and measures nothing | Weight checks at session close and next-session open |
| Riding an analogy past its mapping | Learner imports properties of the source domain that the target does not have | State where the analogy breaks at the moment you introduce it |
| Tuning difficulty to comfort | Comfort optimizes mood; the 70-90% band optimizes retention, and they diverge exactly when learning is happening | Adjust from measured retrieval success only |
| Answering the literal question when the model is wrong | Patches one symptom; the broken mental model keeps generating new errors | Ask what they expected and why, then fix the model, then answer (`misconceptions.md`) |
| Simulating practice the channel cannot host | Text feedback on speaking, listening, or motor skills closes no loop; the learner believes they practiced | Teach the theory, route the practice to the real activity (`topic-types.md`) |
## Where Experts Disagree
- **Immediate vs delayed feedback.** Delayed feedback has matched or beaten immediate on delayed tests (Butler and Roediger), but a wrong model left standing keeps generating errors. Boundary: wrong models and procedural errors get corrected immediately; minor factual slips batch at session close.
- **Struggle-first vs instruction-first.** Pure discovery fails novices (Kirschner, Sweller, and Clark); productive failure (Kapur) shows attempt-then-instruction wins for learners with partial prior knowledge. Boundary: prior knowledge — and instruction always follows the struggle, never gets skipped.
- **Expanding vs uniform review intervals.** Direct comparisons show little difference (Karpicke and Roediger); spacing at all dominates the schedule shape. Default expanding for open horizons because it front-loads reviews when forgetting is fastest.
## Related Skills
More Clawic skills, get them at https://clawic.com/skills/learning (install if the user confirms):
- `learn` — structuring and tracking a learning plan across a domain; this skill runs the sessions inside such a plan
- `spaced-repetition` — deeper scheduling math when reviews span months
- `active-recall` — retrieval technique catalog when the learner studies alone between sessions
- `tutor` — full tutoring engagements with progress tracking and parent oversight
## Feedback
- If useful, star it: https://clawic.com/skills/learning
- Latest version: https://clawic.com/skills/learning
Part of [Clawic](https://clawic.com), the verified skill library. Get this skill: https://clawic.com/skills/learning.
簡介 循證育兒專家 · 0-18 歲全場景養育支援,先托舉家長,再托舉孩子。 詳細描述 育兒專家是一個循證取向的 0-18 歲家庭養育支援系統,覆蓋日常照護、發育里程碑、行為情緒、溝通話術、父母自我成長、危機識別與早教啟蒙九大模組。 不喊"育兒"也能觸發:你說"我家娃又半夜哭""寫作業磨蹭",它直接接住。 危機優先:自傷、虐待、緊急症狀等紅色訊號,先給安全引導,其餘全停。 分級回應:你正在發火時給 30 秒版,平靜時給完整六板塊方案。 邊界清晰:不診斷、不處方,只做"症狀→可能情況"關聯與就醫指徵。 漸進式載入:按需讀取對應章節,回答聚焦、不堆砌。 適合:0-18 歲孩子家長、孕爸媽、隔代養育者。
AI課程影片工作室把寫好的講稿和一張授權講師人像,做成數位人口播課程的課程影片和課程旁白。先把每節課的講稿配成旁白,再用數位人講師錄成講師口播,交付可直接釋出的培訓影片、培訓口播影片、網課影片和課件影片。
根據主題、年級與畫面比例一鍵生成符合A4列印標準的手抄報黑白線稿模板;自動解析合規約束(如國慶節停用國旗國徽)與年級排版策略,生成高畫質線稿圖並適配A4列印尺寸,孩子只需塗色和填字即可完成;適用於家長輔導作業、教師課堂素材、節日主題手抄報創作、列印塗色模板場景
課程配音工作室把課件整理成可朗讀的講稿,為每個章節錄制老師聲音的 AI課程配音和課程旁白,交付可直接配幻燈片的網課配音、課程音訊、培訓旁白和知識付費音訊。
微課製作藉助 AI 把一節課的PPT課件或一個知識點做成5到10分鐘的微課影片:沒有課件時先按匯入、講解、例題、小結生成課件,再逐頁寫講稿、配音、加字幕,可以放上老師照片,也可以讓數位人老師開場。不用自己剪輯,一鍵生成微課影片,適合微課比賽、公開課影片、說課影片、複習課和課前預習。
K12 智慧老師是一個覆蓋小學/初中/高中九大學科的智慧輔導技能,支援作業批改、錯題分析與舉一反三練習生成。
數位人講課藉助 AI 把老師的PPT課件和講稿做成整門課的講課影片和課程影片:每頁課件配上老師的聲音和字幕,可以克隆老師自己的聲音,也可以讓數位人講師在開場和結尾出鏡。PPT轉影片按知識點一講一條,整門課批次做完,適合網課、慕課、教學影片、培訓影片和錄播課。
論文寫作全流程助手。覆蓋從選題、開題、文獻綜述、研究方法、寫作、修改潤色、查重與 AIGC 檢測、答辯到發表的完整論文生命週期;支援多語言(中文 / English / 日本語 / 한국어 / Français / Deutsch / Español / Português / Русский / العربية / Italiano)與 36 個學科,零配置、無需任何 外部金鑰或付費介面 即可使用。觸發詞:論文、thesis、選題、開題、文獻綜述、研究方法、論文寫作、查重、降重、答辯、引用格式、學術寫作、dissertation、paper writing、畢業論文、研究生論文、怎麼寫論文。
將使用者明確糾正與自我檢視整理成分層記憶,並依使用情況升級或封存。
在保留公式、格式和活頁簿結構的前提下建立、檢查或編輯 Excel 檔案。
處理 Word 與 DOCX 文件的作業指南,著重維持樣式、編號與版面。
面向多家影片模型 API 的 AI 影片生成與編排技能。
把資料庫、表格與匯出的原始資料變成可決策結論的資料分析技能。
資料月份:2026-10 · 下載/星標數聚合自公開技能註冊庫(ClawHub、SkillHub),按月更新。口徑說明見資料方法。