learn skill
✓ VerifiedExecutes a six-phase research workflow to transform raw source materials into structured mental models, reference notes, or publish-ready articles.
- GitHub stars
- 7,574
- Files
- 1
- Last commit
- Nov 11, 2026
- License
- MIT
- Allowed tools
- —
What does the learn skill do?
learn executes a six-phase research workflow to transform raw source materials into structured mental models, reference notes, or publish-ready articles.
Summary generated from the skill's SKILL.md.
About the learn skill
Transforming raw source materials into structured mental models, reference notes, or publish-ready articles is what this skill enables. It is designed for users researching unfamiliar domains or compiling large batches of information into a single cohesive resource. Unlike simple reading tools, this skill executes a rigorous six-phase workflow that moves from initial collection to a final, polished output.
An agent should load this skill when tasked with deep research or when a user needs to organize complex materials into a long-form document. The process relies on a sequence of phases including discovery, fetching via the /read tool, digestion, outlining, filling in, and refining. It produces specific artifacts based on the chosen mode, such as a Quick Reference for fast mental models or a Canonical Article for authoritative, all-encompassing guides. The workflow ensures that contradictions between sources are explicitly noted and that every claim is backed by primary source evidence.
What an agent can do with it
- 1Conduct deep domain researchPerform an intensive study of an unfamiliar subject to build a reliable mental model.
- 2Synthesize complex conversation dataTurn recent project reviews, transcripts, or diagnostic reports into structured guidance and transferable rules.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the learn skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the learn skill in Plugin
/plugin marketplace add tw93/Waza /plugin install waza@waza
Install the learn skill in Claude Code
~/.claude/skills/learn/SKILL.md
$ npx degit tw93/Waza/skills/learn ~/.claude/skills/learnInstall the learn skill in Claude Code (project)
.claude/skills/learn/SKILL.md
$ npx degit tw93/Waza/skills/learn .claude/skills/learnInstall the learn skill in Codex
~/.agents/skills/learn/SKILL.md
$ npx degit tw93/Waza/skills/learn ~/.agents/skills/learnInstall the learn skill in Gemini CLI
~/.gemini/skills/learn/SKILL.md
$ npx degit tw93/Waza/skills/learn ~/.gemini/skills/learnInstall the learn skill in Claude.ai
npx degit tw93/Waza/skills/learn learn && zip -r learn.zip learn # claude.ai → Customize → Skills → + → Create skill → Upload a skill → learn.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachabletw93/waza/skills/learn is public and reachablegithub.com/tw93/waza/tree/HEAD/skills/learn ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-11github.com/tw93/waza/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/tw93/waza/blob/HEAD/skills/learn/SKILL.md ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/tw93/waza/blob/HEAD/skills/learn/SKILL.md ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 113 linesgithub.com/tw93/waza/blob/HEAD/skills/learn/SKILL.md ↗Pass
SKILL.md
View on GitHubLearn: From Raw Materials to Published Output
Prefix your first line with 🥷 inline, not as its own paragraph.
Support the user's thinking; do not replace it.
Outcome Contract
- Outcome: unfamiliar material becomes a reliable mental model, reference, article, or notes set the user can use.
- Done when: primary sources are collected or supplied, contradictions are handled explicitly, and the final structure teaches the topic without hiding uncertainty.
- Evidence: source URLs or files, fetched content, notes from digestion, outline decisions, and self-review against the requested output.
- Output: research notes, outline, publish-ready draft, or canonical reference, matching the chosen mode.
Boundary: single URL that only needs fetching belongs in /read. A single URL that needs summary or analysis can use /read as the fetch step, but the final answer should satisfy the user's requested summary or analysis. /learn is for multi-source research that produces a new structured output.
Choose Mode
Infer the mode from the requested artifact and supplied materials. Ask only when plausible modes would change the scope or deliverable and the user's intent does not resolve the choice:
| Mode | Goal | Entry | Exit |
|---|---|---|---|
| Deep Research | Understand a domain well enough to write about it | Phase 1 | Phase 6: publish-ready draft |
| Quick Reference | Build a working mental model fast, no article planned | Phase 2 | Phase 2: notes only |
| Write to Learn | Already have materials, force understanding through writing | Phase 3 | Phase 6: publish-ready draft |
| Canonical Article | One article that covers a topic so thoroughly readers need nothing else | Phase 1 | Phase 6: single authoritative reference |
If unsure, suggest Quick Reference.
Canonical Article Mode
Activate when: "一篇就够", "一站式参考", "整理成长文", "目的是大家只需要看这篇就好了", or the user wants a single authoritative reference on a topic.
Goal: after reading the article, no one should need to search for anything else on this topic.
Additional requirements on top of standard Deep Research:
- Every major sub-topic must have its own section; nothing left as a footnote
- Include worked examples, not just principles
- Cover common mistakes and how to avoid them
- Add a "Further Reading" section with the 3-5 sources that go deepest; flag which ones are the best starting points
- Phase 6 self-review must confirm: "Could a reader implement/understand this from this article alone?"
Phase 1: Collect
Gather primary sources only: papers that introduced key ideas, official lab/product blogs, posts from builders, canonical "build it from scratch" repositories. Not summaries. Not explainers.
Three ordered steps per source -- no shortcuts, no merging:
- Discover -- use an installed search plugin to map the landscape, then deep-search the 2-3 most promising sub-topics. No plugin: use the environment's native web search. Output is a URL list; do not fetch content here.
- Fetch -- every URL goes through
/readwhen available./readowns the proxy cascade, paywall detection, and platform routing (WeChat, Feishu, PDF, GitHub). Native fetch tools and rawcurlsilently fail on JS-heavy or paywalled sites and skip all of that. If/readis not installed, warn once without blocking, fall back to native fetch, and state the reduced coverage on paywalled, JS-heavy, and Chinese-platform pages. - File -- tell
/readthe research project's source directory when one exists. If no directory was specified, let/readuse a per-session temp directory and return the saved path. Move or index saved files into sub-topic directories after fetch returns. Move, don't refetch.
Target: 5-10 sources for a blog post, 15-20 for a deep technical survey.
Phase 2: Digest
Work through the materials. For each piece: read it fully, keep what is good, cut ruthlessly what is not.
For key claims, ask before including in the outline:
- Does this idea appear in at least two different contexts from the same source?
- Can this framework predict what the source would say about a new problem?
- Is this specific to this source, or would any expert in the field say the same thing?
Generic wisdom is not worth distilling. Passes two or three: belongs in the outline. Passes one: background material. Passes zero: cut it.
Conversation Or Review Distillation
When the input is a recent conversation, project review, scorecard, or diagnostic report, treat it as raw material. Read distilled summaries, memory entries, and review outputs first; open raw transcripts only to verify a disputed detail or recover the exact source of a repeated pattern. Before editing durable guidance, build a candidate matrix (source/project, repeated failure, transferable rule, target layer, evidence count, redaction risk) and promote only candidates with cross-source support or a repeated failure in the same project family. Map each repeated workflow failure, invariant, or verifier surface to project docs, shared rules, skill references, or a deterministic script that can fail reliably without project context. Drop dated line numbers, current-score framing, private paths, one-machine setup, and repo-specific commands unless the output is for that same repo, and keep raw conversation history out of the final artifact.
Phase 3: Outline
Write the outline for the article. For each section: note the source materials it draws from. If a section has no sources, either it does not belong or a source needs to be found first.
Phase 4: Fill In
Work through the outline section by section. A section that is hard to write means the mental model is still weak there: return to Phase 2 for that sub-topic, not the whole article. Stall signals: an opening sentence rewritten three times without settling, a single-source claim with no cross-check, a source missing from Phase 1, or a claim you could not explain out loud. The outline may change, and that is fine.
Phase 5: Refine
Edits only: cut redundancy without changing meaning or voice, flag broken argument flow, and mark gaps (concepts used before they are explained, claims needing sources). Do not draft new sections from scratch. Then strip AI patterns: invoke /write when installed, otherwise warn once and scan manually for filler, binary contrasts, and dramatic fragmentation.
Phase 6: Self-review and Publish Readiness
The user reads the entire article linearly before publishing. Not with AI. Mark everything that feels off, fix it, read again. Two passes minimum.
When it reads clean from start to finish, the draft is ready for the user to publish.
Hard Rules
- No Phase 4 before the outline is solid, with a source behind every section (Phase 3).
- Contradictions stay visible. When two sources contradict on a factual claim, note both positions and the evidence each gives; never silently pick one.
- Stop at publish confirmation. After the user confirms the article is ready, do not upload, post, distribute, or perform any publish action unless explicitly asked.
Gotchas
| What happened | Rule |
|---|---|
| Phase 2 wrote summaries instead of teaching the concept | Digest means building the mental model. Summarizing is not digesting. |
Output
The artifact is the mode's exit from the table above. Report the saved path when files were written and complete the authorized handoff; publication requires an explicit request as stated in Hard Rules.
Within the requested format and scope, choose a representation for the reader's question: prose for conclusions, diagrams for relationships and branches, interactive examples for changing conditions, and animation or video for processes whose timing or motion matters. Add a representation only when it helps the reader understand or test the explanation; a research request alone does not require building an app or producing a video.
Across representations, preserve the same facts, conditions, failure branches, and uncertainty. Interactive results must follow a supported model or explicitly labeled assumptions, not decorative controls. Judge an explanation by whether its content lets the reader trace a relevant failure path, predict a condition change, or identify a load-bearing assumption; visual polish alone is not evidence of correctness.
Files in this skill
1learn skill questions
How do I install the learn skill in Claude Code?
Run npx degit tw93/Waza/skills/learn ~/.claude/skills/learn. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the learn skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
When should I use the learn skill instead of the read skill?
Use /read for single URLs that need fetching, summarizing, or analysis. Use /learn for multi-source research intended to produce a new, structured output like an article or reference guide.
How does the skill handle conflicting information from different sources?
The skill requires that contradictions remain visible; when sources disagree on a factual claim, both positions and their respective evidence must be noted rather than picking one.