AlphaMoatによると、2026-10時点でLearningのダウンロード数は14,390、スター数は12で、累計ダウンロード数で今回のランキング対象AIスキル10,914件中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 |
作者が公開した元のファイルをテキストのまま表示しています。AlphaMoat による編集や審査はしていません。リンクはクリックできません。コマンドは内容を確認してから実行してください。取得日 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 岁)的养育、健康、行为、情绪、学习或亲子关系,即应触发本技能,无需用户明确说出「育儿」二字;用户以「我家孩子」「宝宝」「娃」等开场描述困扰时,同样触发。典型话题:育儿/带娃/宝宝/婴儿/幼儿/学龄前/青春期、发育/里程碑/早教、喂养/辅食/挑食/夜醒/睡眠、疫苗/体检/湿疹/发烧/咳嗽/腹泻/皮疹、哭闹/发脾气/打人/说谎/焦虑/分离/对抗/抗挫折、写作业/拖延/厌学/考试焦虑/沉迷手机/注意力、亲子关系/二胎/隔代育儿/单亲、ADHD/自闭症/感统、自伤/抑郁/霸凌/性教育、父母自责/原生家庭/情绪崩溃/倦怠/吼孩子后修复、每周培养课表/家庭排程/爸爸陪伴、孩子档案/成长记录/评估量表/幼小衔接/早教/绘本共读/识字拼音/数学英语启蒙/专注力/自由玩耍/玩具/依恋/关系修复。覆盖视频号、抖音等平台不适用;本技能纯文本养育支持,不生成视频。
AI课程视频工作室把写好的讲稿和一张授权讲师人像,做成数字人口播课程的课程视频和课程旁白。先把每节课的讲稿配成旁白,再用数字人讲师录成讲师口播,交付可直接发布的培训视频、培训口播视频、网课视频和课件视频。
根据主题、年级与画面比例一键生成符合A4打印标准的手抄报黑白线稿模板;自动解析合规约束(如国庆节禁用国旗国徽)与年级排版策略,生成高清线稿图并适配A4打印尺寸,孩子只需涂色和填字即可完成;适用于家长辅导作业、教师课堂素材、节日主题手抄报创作、打印涂色模板场景
课程配音工作室把课件整理成可朗读的讲稿,为每个章节录制老师声音的 AI课程配音和课程旁白,交付可直接配幻灯片的网课配音、课程音频、培训旁白和知识付费音频。
微课制作借助 AI 把一节课的PPT课件或一个知识点做成5到10分钟的微课视频:没有课件时先按导入、讲解、例题、小结生成课件,再逐页写讲稿、配音、加字幕,可以放上老师照片,也可以让数字人老师开场。不用自己剪辑,一键生成微课视频,适合微课比赛、公开课视频、说课视频、复习课和课前预习。
K12 Smart Teacher(K12智能老师)は、小学校・中学校・高校の9教科をカバーするスマート指導スキルで、宿題、宿題採点、誤問分析、類題練習の生成に対応します。
数字人讲课借助 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)から月単位で集計しています。詳しくはデータの方法論をご覧ください。