Semester OS

    1

    Consolidates your syllabi into one semester dashboard with a master deadline calendar, crunch-week heat map, weekly rhythm, and grade math.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    Semester OS

    Example session with this skill installed

    Plan my semester from these two syllabi. Term runs Feb 3 through May 16, with break week Mar 24 to 28. Linear algebra meets Mon-Wed-Fri; algorithms meets Tue-Thu. Algorithms Quiz 1 is Mar 11 and Quiz 2 is Apr 15, both evening. My linear algebra target is a 90 and I am averaging 85 on the problem sets so far.

    [MIT 18.06 Linear Algebra, Spring 2010 syllabus and calendar, pasted]

    [MIT 6.006 Introduction to Algorithms, Fall 2011 syllabus and calendar, pasted]

    • Read your context and instructions
    • Compiled the semester os

    Built from the two syllabi you provided: linear algebra (sessions scheduled Mon-Wed-Fri) and intro algorithms (lectures scheduled Tue-Thu). The plan maps both published schedules onto your term (Feb 3 through May 16, break week of Mar 24), consolidates every deadline into one calendar, flags the crunch weeks, sets a weekly rhythm, and runs your linear algebra grade math at the end. All 23 dated items come from the two syllabi; the two finals carry TBC dates because both are registrar-scheduled in finals week.

    Course requirements

    Linear algebra (3 lectures plus 1 recitation per week), from the syllabus grading section:

    ComponentWeightNotes
    Problem sets15%10 sets per the course calendar, due roughly every third session
    Three one-hour exams45%Per-exam split unstated; 15% each assumed for math
    Final exam40%Calendar lists the final at session 40; registrar date TBC

    Intro algorithms (2 lectures plus 2 recitations per week), from the syllabus grading section:

    ComponentWeightNotes
    Problem sets30%Seven sets, each a Python programming part plus a theory part
    Quiz 1 and Quiz 220% eachTwo-hour evening quizzes
    Final exam30%Finals week, date TBC

    Master deadline calendar

    Mapping assumptions: linear algebra sessions run MWF from Feb 3, skipping break week; algorithms lectures run Tue-Thu from Feb 4, same skip. Quiz dates are as you supplied.

    DateCourseItemType
    Feb 11AlgorithmsProblem set 1 dueproblem set
    Feb 12Linear algebraProblem set 1 dueproblem set
    Feb 19Linear algebraProblem set 2 dueproblem set
    Feb 20AlgorithmsProblem set 2 dueproblem set
    Feb 26Linear algebraProblem set 3 dueproblem set
    Feb 28Linear algebraExam 1, chapters 1 to 3.4exam
    Mar 4AlgorithmsProblem set 3 dueproblem set
    Mar 5Linear algebraProblem set 4 dueproblem set
    Mar 6AlgorithmsProblem set 4 dueproblem set
    Mar 11AlgorithmsQuiz 1, eveningquiz
    Mar 12Linear algebraProblem set 5 dueproblem set
    Mar 19Linear algebraProblem set 6 dueproblem set
    Mar 20AlgorithmsProblem set 5 dueproblem set
    Apr 2Linear algebraProblem set 7 dueproblem set
    Apr 7Linear algebraExam 2, chapters 1-5, 6.1-6.2, 8.2exam
    Apr 10AlgorithmsProblem set 6 dueproblem set
    Apr 15AlgorithmsQuiz 2, eveningquiz
    Apr 16Linear algebraProblem set 8 dueproblem set
    Apr 21Linear algebraProblem set 9 dueproblem set
    Apr 24AlgorithmsProblem set 7 dueproblem set
    Apr 28Linear algebraProblem set 10 dueproblem set
    May 2Linear algebraCourse review sessionmilestone
    May 5Linear algebraExam 3, chapters 1 to 8exam
    TBC finals weekLinear algebraFinal exam (registrar date governs; calendar places a final at session 40, May 12)final
    TBC finals weekAlgorithmsFinal exam (registrar date governs)final

    Pattern note: linear algebra sets land on Wednesdays except where an exam shifts the week; algorithms set dates cluster irregularly, with problem set 3 and problem set 4 due 48 hours apart.

    Crunch-week heat map

    Week ofLoadWhat lands
    Feb 3LightTerm start, both courses begin
    Feb 10MediumTwo problem sets due back to back (Feb 11, Feb 12)
    Feb 17LightProblem set 2 due Feb 19
    Feb 24HIGHProblem set 3 due Feb 26, Exam 1 Feb 28; prep starts Mon Feb 24
    Mar 3HIGHThree deadlines in 72 hours: Algorithms PS3 Mar 4, Linear algebra PS4 Mar 5, Algorithms PS4 Mar 6
    Mar 10HIGHQuiz 1 Mar 11 evening, then Linear algebra PS5 due Mar 12; quiz prep starts Mar 4
    Mar 17MediumLinear algebra PS6 due Mar 19, Algorithms PS5 due Mar 20
    Mar 24BreakNo classes
    Mar 31HIGH prep weekPS7 due Apr 2; Exam 2 prep starts Mon Mar 31
    Apr 7HIGHExam 2 Apr 7; Quiz 2 prep starts Apr 8
    Apr 14HIGHQuiz 2 Apr 15 evening, Linear algebra PS8 due Apr 16
    Apr 21MediumPS9 due Apr 21, Algorithms PS7 due Apr 24; Exam 3 prep starts Apr 28
    Apr 28MediumPS10 due Apr 28, review session May 2; finals prep window opens
    May 5HIGHExam 3 May 5, then finals
    May 12HIGHFinals: both registrar-scheduled final dates TBC

    Weekly operating rhythm

    You did not give a weekly study-hours figure, so blocks are sized at defaults; say the word and I re-cut them.

    • Mon, Wed, Fri after each linear algebra lecture: 30-minute same-day block. Notes consolidation plus two worked examples.
    • Tue, Thu after each algorithms lecture: 45-minute same-day block. Lecture notes plus opening the current problem set.
    • Wed evening: linear algebra problem set session. The MWF pattern lands sets on Wednesdays; start each set two sessions before it is due.
    • Thu evening: algorithms problem set session, same start rule.
    • Wed evening, 20 minutes: recitation prep for both courses. The algorithms syllabus ties recitation attendance to quiz performance, so this block protects the quiz weeks.
    • Sun: 60-minute weekly review, 30 minutes per course, heavier on whichever course has a HIGH week next.
    • Exam prep windows (Feb 24, Mar 4, Mar 31, Apr 8, Apr 28, finals) override the standing rhythm.

    Policy flags

    • Algorithms late policy: 1 percent off per six minutes past the deadline, no credit after ten hours. It is the sharpest deadline of your term; every algorithms set gets submitted the day before.
    • Algorithms sets: collaboration allowed, write-ups written alone, collaborators listed. Proofs go into the grading tool in LaTeX, with your critique of the posted solution due by the next lecture.
    • Linear algebra homework: talking with other students encouraged, solutions written by you. Some problems require MATLAB.
    • Linear algebra exams: calculators and notes are both prohibited.

    Grade math: linear algebra

    Target 90, problem set average 85 so far, problem sets worth 15 percent.

    • Points earned toward target: 0.15 x 85 = 12.75
    • Remaining weight: exams 45 + final 40 = 85 percent
    • Needed average on remaining work: (90 - 12.75) / 0.85 = 90.9 percent

    Assumption on record: the three exams are worth 15 percent each, split from the stated 45 total. In plain terms, an 85 problem-set average leaves almost no cushion: you need to average 90.9 percent on every exam and the final to finish at 90.

    Delivery report

    23 dated deadlines plus 2 TBC finals are on the calendar; the per-exam split is the one assumed number, flagged in both the requirements table and the math. Crunch weeks: Feb 24, Mar 3, Mar 10, Apr 7, Apr 14, May 5, and the finals stretch. First action this week: start both problem set 1s now and submit each by the day before its due date.

    Next steps: confirm both registrar final dates and I will replace the TBC rows; send scores as they arrive and I will re-run the standing math; when an exam is a week out, hand me the lecture notes and I can build the study kit against the crunch schedule.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    What it does

    Semester OS turns a stack of syllabi into one operating plan for the term. It reads every syllabus you hand it, extracts the deadlines, grade weights, and course policies, and builds a single semester dashboard:

    • Master deadline calendar. Every dated item across every course in one chronological table, so nothing lands as a surprise.
    • Crunch-week heat map. Week-by-week load ratings that flag the heavy weeks while there is still time to prepare.
    • Weekly operating rhythm. Study blocks anchored to your real class days and the courses that meet them.
    • Per-course requirements tables. Components, weights, and notes, with every number traced to the syllabus section it came from.
    • Grade math on request. Weighted standing plus the average you need on remaining work to reach a target grade.

    How it works

    1. Intake. You supply the syllabi (pasted text or files), term dates, each course meeting pattern, and any known exam dates. Optional: weekly study hours, grade goals, scores earned so far.
    2. Extraction with receipts. Deadlines, weights, and policies are pulled with the syllabus section each came from. A date the sources do not state is marked TBC with the place to confirm it, never guessed.
    3. Schedule mapping. Session-numbered schedules are mapped onto real dates from your meeting pattern, with the mapping assumptions stated in the plan.
    4. Assembly. Requirements tables, master calendar, heat map, weekly rhythm, policy flags, and grade math, delivered as a markdown file with the full text pasted in the reply.
    5. Updates. Report a changed exam date or a new score and the affected sections rebuild. The plan is a living document for the term.

    Why this beats prompting it yourself

    A one-off prompt loses track of weights between messages, misses deadlines buried in a policy paragraph, and fills gaps in the syllabus with plausible invented dates. Semester OS enforces extraction honesty: TBC flags carry a confirmation source, mapping assumptions are stated in the plan, the grade math shows its arithmetic, and a delivery report counts the deadlines and names the crunch weeks so you can verify the plan against your own syllabi.

    Pair it with Lecture Notes Architect for lecture notes and Exam Cram Study Kit for exam-week study kits.

    Known limitations: works from the syllabi you supply; registrar-scheduled finals stay TBC until you confirm their dates; output is plain ASCII text in markdown.

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scanned

    Verified clean today

    • Passed all security checks, Safe to install

    Listedtoday

    What's inside

    Frequently Asked Questions