From teaching-pipeline
Gather authoritative documentation, official references, and canonical examples for a planned lesson or module — and attach the citations to the curriculum plan. Use when the learner asks to "research module X", "find docs/refs for the lesson on Y", "gather sources for Z", or before building lesson files. Outputs a research dossier (links, key passages, gotchas, version notes), not lesson content.
How this skill is triggered — by the user, by Claude, or both
Slash command
/teaching-pipeline:lesson-researcherThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Fills a planned lesson or module with verified, authoritative external references. The dossier produced here is what `lesson-builder` consumes when it generates the actual lesson files.
Fills a planned lesson or module with verified, authoritative external references. The dossier produced here is what lesson-builder consumes when it generates the actual lesson files.
curriculum-plannerlesson-builderlesson-review-boardprofessorIf a claim cannot be supported by sources 1–3, flag it as "needs verification" rather than promoting a weak source.
context7 MCP (if installed) — preferred for libraries, frameworks, SDKs, APIs, CLI tools (React, Anthropic SDK, Prisma, Next.js, etc.). Faster and fresher than scraping. Use even when you think you know the answer — your training data may be stale.firecrawl-search, firecrawl-scrape, firecrawl-map for web search and JS-rendered pages.WebFetch / WebSearch — fine for static pages and quick lookups.Read — when official docs already live in the repo or in a downloaded mirror.Always prefer context7 for SDK/library questions before falling back to web search, when it's available.
Open the curriculum plan (CURRICULUM_PLAN.md or equivalent). For the target module, list each learning objective and each key concept. The dossier needs at least one authoritative citation per concept.
For each concept:
For each load-bearing claim, find a second independent source. If you can't, mark the claim "single-source" so the review board can decide whether that's acceptable.
Lessons should be self-contained for core mechanics but explicit when the learner needs to consult external docs for peripheral concerns. Mark each citation as either:
The default is inline for core mechanics, docs-dive for periphery. See CONVENTIONS.md for more on this convention.
Save as research/<module-id>.md next to the curriculum plan (create the research/ dir if missing):
# Research Dossier — Module XX: <Title>
**Plan reference**: [CURRICULUM_PLAN.md#module-XX]
**Compiled**: <YYYY-MM-DD>
**Versions assumed**: <language / lib versions this lesson targets>
## Concept: <name>
**Authoritative source**: <Title>, <publisher>, <date>
**URL**: <link>
**Quote**:
> <1–4 sentences from the source>
**Why it matters here**: <one line tying to the learning objective>
**Treatment**: inline | docs-dive
**Second source** (if any): <link>
**Version notes**: <e.g., "valid for Python ≥ 3.10; behavior changed in 3.12">
## Concept: <next>
...
## Open questions / single-source claims
- <claim> — only found in <source>; flag for review
## Recommended further reading (optional)
- <link> — for learners who want to go deeper
lesson-builder's job.Recommend the next step: "Dossier ready at research/.md. Next: run lesson-review-board on plan + dossier together, or skip to lesson-builder if you want a draft to react to."
npx claudepluginhub geopopos/teaching-pipeline-plugin --plugin teaching-pipelineProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.