study-system
Converts a syllabus or topic list into an evidence-based study plan - material atomized into testable units, a spaced-repetition flashcard schedule with expanding intervals, active recall and Feynman-technique prompts instead of rereading, interleaved weekly sessions, and a practice-testing cadence with an error log. Use when someone says "help me study for this exam", "build me a study schedule", "I keep rereading and forgetting everything", or wants to learn a curriculum efficiently. Do NOT use for acquiring a spoken language specifically - use language-learning instead - or for building everyday habits - use habit-builder instead.
- License 许可
- MIT
- 最近更新
- 2026-10-14
- Stars
- ★ 25
- Forks
- 3
01 前言 Front Matter
- name
- study-system
- metadata
- { "title": "Study System" }
- description
- Converts a syllabus or topic list into an evidence-based study plan - material atomized into testable units, a spaced-repetition flashcard schedule with expanding intervals, active recall and Feynman-technique prompts instead of rereading, interleaved weekly sessions, and a practice-testing cadence with an error log. Use when someone says "help me study for this exam", "build me a study schedule", "I keep rereading and forgetting everything", or wants to learn a curriculum efficiently. Do NOT use for acquiring a spoken language specifically - use language-learning instead - or for building everyday habits - use habit-builder instead.
03 SKILL.md 正文
Study System
Use this skill to convert a syllabus or topic list into an evidence-based study plan.
1. Clarify the target
Ask:
- What is being learned and by when (exam, project, fluency level)?
- How will success be tested (recall, application, performance)?
- Hours per week available?
2. Break the material into atoms
Decompose the curriculum into small, testable units (concepts, formulas, vocabulary, procedures). Each atom should be answerable in one question.
3. Active recall over rereading
Replace passive rereading and highlighting with retrieval:
- After reading a section, close the material and write/say what you remember.
- Turn notes into questions, not summaries.
- Use the Feynman technique: explain the concept in plain language as if teaching a beginner; gaps reveal what to restudy.
4. Spaced repetition
Schedule reviews at expanding intervals so each item is revisited just before it would be forgotten.
- A practical schedule: review at 1 day, 3 days, 7 days, 16 days, 35 days.
- Use a flashcard app with a spaced algorithm, or a manual Leitner box of physical cards moving through boxes.
- Cards that are missed reset to the shortest interval.
5. Interleaving
Mix related topics within a study session rather than blocking one topic at a time. Interleaving feels harder but improves the ability to choose the right method on a test. Example: alternate problem types instead of doing 20 of the same type in a row.
6. Practice testing
- Do full practice problems and past exams under realistic conditions.
- Grade honestly and log every error with its cause (concept gap, careless, misread).
- Restudy only the items you missed.
7. Manage cognitive load
- Study in focused blocks (e.g., 25-50 minutes) with short breaks.
- Sleep consolidates memory; review lightly before bed and re-test in the morning.
- Avoid cramming; distribute sessions across days.
8. Weekly review loop
Each week:
- What proportion of cards/questions am I answering correctly?
- Which atoms keep failing? Rewrite those cards more clearly.
- Is the schedule realistic, or do I need to cut scope?
Do NOT
- Do NOT let rereading and highlighting count as study time - they produce fluency illusion (the material feels familiar but cannot be retrieved). Retrieval attempts are the unit of study.
- Do NOT block-practice one topic to exhaustion - 20 identical problems in a row trains recognition of the problem type, not the choice of method the test demands. Interleave.
- Do NOT write multi-fact cards - a card asking two things gets graded on the easier half and the other fact silently rots. One atom per card.
- Do NOT skip the error log after practice tests - restudying everything instead of the misses wastes the scarcest resource, and errors without a cause label (concept gap / careless / misread) can't be fixed.
- Do NOT drill only the comfortable decks - time goes to the atoms with the lowest recall rate, precisely because it feels worse.
- Do NOT cram the night before as a substitute for the schedule - massed practice inflates next-day recall and collapses within a week; the intervals are the mechanism.
Quality bar
- Every atom is phrased as one answerable question, not a topic name.
- Each card has a scheduled next-review date from the expanding-interval ladder; misses demonstrably reset to day 1.
- Weekly sessions interleave at least two topics, and total scheduled hours fit the user's stated availability.
- The plan includes at least one full-length practice test under realistic conditions before the exam, with the error log template attached.
Output for the user
Produce: the atomized topic list, a flashcard plan with intervals, an interleaved weekly schedule, and a practice-testing cadence with an error log template.
04 同仓库更多 Skills
有氧运动计划
zone-2-cardio-plan
当有人要求制定稳态有氧训练计划、进行有氧基础训练或达到第二区间、安排轻松或耐力型的每周有氧训练、按心率区间训练，或提高静息心率、最大摄氧量或耐力时，可以使用此方案。该方案构建了一个包含训练计划结构、训练方式选择和进度安排的心率区间有氧训练模块。本方案仅提供一般健身指导，不构成医疗建议。请勿用于设计力量或举重训练计划（请使用力量训练计划）、高强度间歇训练 (HIIT) 或循环训练（请使用体能训练和 HIIT 计划），或灵活性/柔韧性训练（请使用灵活性训练计划）。
youtube-script-writer
Writes retention-engineered long-form YouTube scripts on a hook/body/payoff architecture - a first-30-seconds hook that survives the retention cliff, a beat-sheet body with mini-hooks and bridges, timed pattern interrupts, and a payoff that over-delivers - with B-roll and editing cues marked inline. Use when someone says "script my next video", "my retention graph dies at the start", "tighten this draft", or "outline a video on X". Do NOT use for the 3-second opener of TikTok, Reels, or Shorts - use video-hook-writer instead; do NOT use for spoken voiceover synced to on-screen tutorial actions - use narration-script instead; do NOT use for a sales demo built on a buyer's discovery notes - use demo-script instead; do NOT use to design the thumbnail and title - use thumbnail-concept instead.
win-back-campaign
Designs segmented win-back email sequences for dormant users - dormancy tiers, a three-beat sequence with a single proportional incentive, and a suppression rule - and measures success by re-activation, not opens. Use when someone says "our users went quiet", "design a win-back campaign", "how do I re-engage lapsed customers", "should we email people who haven't logged in for months", or lifecycle messaging has stopped landing with a lapsed segment. Do NOT use for recovering an unfinished checkout - use abandoned-cart-sequence instead. Do NOT use for diagnosing and fixing why active customers cancel - use churn-reduction instead. Do NOT use for building always-on onboarding or nurture flows - use email-drip-builder instead.
wikipedia-style
Writes neutral, verifiable, encyclopedic prose following Wikipedia's core content policies and manual of style - NPOV, inline citations, notability-backed claims, and a strict ban on promotional language. Use when someone asks "write this like a Wikipedia article", "draft a Wikipedia page for this company or person", "make this neutral and encyclopedic", or "why does my article draft keep getting rejected". Do NOT use for persuasive or opinion writing - use op-ed-writer instead; for thesis-driven academic papers, use academic-essay; for verifying claims in existing text, use fact-checker.
whitepapers
Structures and writes authoritative B2B whitepapers - a standalone executive summary, a data-sized problem statement, methodology, evidence-driven findings, recommendations, and a soft call to action - flagging every claim that needs a real citation. Use when a marketer asks "write a whitepaper on this topic", "turn our research into a lead-gen asset", "make this credible enough for executives", or a draft reads like a product pitch instead of analysis. Do NOT use for customer-story-driven proof - use case-study-builder instead; for policy audiences, use policy-brief.
white-space-analysis
Finds unmet market gaps by ranking jobs-to-be-done on importance versus satisfaction, overlaying them against current solutions and workarounds, and validating that each gap is real, winnable, and worth winning. Use when someone asks "where are the gaps in this market", "what's underserved here", "where should we play next", or is hunting for product, feature, or market-entry opportunities. Do NOT use for profiling competitors and building battle cards - use competitive-intelligence instead; for putting a dollar figure on an identified opportunity - use market-sizing instead; for extracting jobs-to-be-done from raw customer interviews - use jtbd-extractor instead.