Build or restructure a course syllabus from a topic list or reading list — course description + prerequisites, week-by-week schedule (topic → readings → deliverables), measurable learning objectives, an assessment scheme + rubric, standard policies (late work, AI use, academic integrity, accessibility), and a per-week work-list to hand to `/create-lecture`. Use when user says "build a syllabus", "structure my course", "turn this reading list into a schedule", "draft a course outline", "make a syllabus for Econ 7xx", or "map weeks to lectures". Economics-aware (PhD metrics/micro/macro sequences
A source-grounded starter task has not been verified for this skill yet.
SKILL.md
name: syllabusdescription: Build or restructure a course syllabus from a topic list or reading list — course description + prerequisites, week-by-week schedule (topic → readings → deliverables), measurable learning objectives, an assessment scheme + rubric, standard policies (late work, AI use, academic integrity, accessibility), and a per-week work-list to hand to `/create-lecture`. Use when user says "build a syllabus", "structure my course", "turn this reading list into a schedule", "draft a course outline", "make a syllabus for Econ 7xx", or "map weeks to lectures". Economics-aware (PhD metrics/micro/macro sequences, undergrad); generic enough for any field.
syllabus
This skill's instructions live in .claude/skills/syllabus/SKILL.md.
Read that file now and follow it, with the files it points to. Read AGENTS.md
first if you have not already.
It was written for Claude Code. Running it from Codex, Antigravity or another agent:
Arguments. Where it says $ARGUMENTS, use what the user asked for.
Claude Code agents. Where a step hands work to an agent in .claude/agents/ (through the
Agent or Task tool), do that step where it appears in the procedure: never later, and never
skip it. A step that gates what follows still gates it (/commit runs its verifier before it
commits). Read the agent's file for what the step checks.
Fresh context. If the step needs a context that has not seen your work, for example a claim
verifier that must never see the draft, run it in a separate session or worker that has not
seen the draft, if your tool can start one, and give it only what the step says to pass. If it
cannot, do the step yourself, mark every result it produced not independently verified, and
tell the user to repeat that check in Claude Code (/verify-claims for citations) before
relying on it.
Claude Code settings.allowed-tools, model, effort, argument-hint and
disable-model-invocation in the source's frontmatter configure Claude Code. Ignore them.
Guards. Claude Code's guard hooks do not run for you. Follow the rules in AGENTS.md
yourself; the git pre-commit gate and CI still apply to your commits.