Learn

Skill Lemonaderrrrr/flow-kit/skills/learn

Stop Claude from winging it — 7 workflow skills that route every task through two thinking modes (Philosopher = absorb / Engineer = ship). Works in Claude Code + Codex.

Install

npx -y skills add Lemonaderrrrr/flow-kit --skill learn

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Absorb a topic, paper, or lesson into reusable knowledge. Default Philosopher mode (first-principles decomposition + optional Feynman check + a distilled note); Engineer mode for time-boxed extraction of usable takeaways. Saves notes to outputs/notes/. Use when the user says "I want to learn X", "help me understand this paper", or invokes the skill.

SKILL.md

2.3 KB, as published. Nobody here has run it

Learn Workflow

Turn a topic / paper / lesson into reusable, durable knowledge.

Start

Route-confirm (see CONVENTIONS.md): in one line, say this is the learn workflow and which mode you suggest; wait for the go-ahead.
Confirm mode: default 🧠 Philosopher; the user may switch to ⚙️ Engineer.
(Optional) Anchor the material to the user's own focus area so new knowledge connects to what they care about.

🧠 Philosopher mode (default)

Goal: truly understand, reusable for life. Slow is fine; half-baked is not.

Frame — What is this? What field? Why does it matter?
Decompose to first principles — Break down to irreducible concepts; at each layer ask "why this way, why not otherwise?"
Feynman check (optional) — Have the user explain it back in plain words. Where they stumble = not yet understood → go back and fill the gap. Skippable on request.
Connect — Link to what they already know (prior topics, notes).
Capture — Write outputs/notes/note_<english-slug>.md: one-sentence essence + 3 key insights + open questions.

⚙️ Engineer mode

Goal: get usable conclusions, time-boxed. For exams / reproducing a result / looking up one thing.

Anchor the goal — What will you do with this? (exam / reproduce / ship)
Extract — Go straight to takeaways + key formulas / APIs; skip derivations.
Action list — Turn it into executable steps or a code skeleton.
Capture — Write outputs/notes/cheat_<english-slug>.md: a quick-reference card.

Wrap-up conventions

Live-search principle: look up external facts (papers, recipes, APIs, data) online; don't rely on training memory. Pure reasoning / math is exempt.
Promote: if it's directional/reusable, offer to save it to long-term memory; one-off outputs stay put.
Filenames use English slugs (e.g. note_transformers.md).
Follow the host repo's CLAUDE.md style if present.