⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
course-design
Design and revise a course's goal, progression, prerequisites, and sources. Record depth and duration, validate and enroll course.json, then hand the current topic to lesson-design.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
What is GNOS?
GNOS is a teaching harness made of skills, scripts, and visual tools. Tell it what you want to learn. For a course, it asks how deep you want to go and how much time you have, uses course materials such as university syllabi, textbooks, and documentation to plan a route, then builds the first lesson. Subagents make its lesson blocks; GNOS reviews and joins them before asking if you want to see the course.
As you work, GNOS records what you tried, where your reasoning broke, and what you could do independently. It uses that evidence to adjust upcoming lessons and exercises. The course grows with you.
Star history
Study your course in a browser
Just ask GNOS to show your course in the browser. It routes the request to the course-viewer skill, which renders the curriculum and current lesson as a study page. Open a topic to read its lesson, work through exercises, and follow its sources and learning materials.
A true slideshow can't run inside a README, so here is the closest thing — click each frame to expand it:
Why does learning with AI still feel hard?
Frontier models know a great deal, but a good answer is only one part of teaching. Learning a large subject also takes a coherent route, a diagnosis of mistakes, and a way to make abstract ideas visible. GNOS gives a coding agent that structure.
| The problem | What GNOS does |
|---|---|
| The voice feels generic | Subject-specific teachers use SOUL.md files to guide their explanations and judgment. This builds on my earlier SOUL.md project. |
| Lessons lose the thread | A living course plan and learner records keep topics, prior attempts, and the next step together across sessions. |
| A correct answer gets mistaken for understanding | Learner tracking distinguishes seeing an explanation, solving with help, and solving independently; the next exercise responds to the evidence. |
| Everything becomes text | GNOS can choose diagrams, images, simulations, narrated animations, or PDF handouts when that format helps explain the idea. Visual tools and media dependencies vary by environment. |
Get started
Start with Git, Python 3, and your preferred coding agent installed. Codex, Claude Code, and other agents use a local checkout. Cursor adds the skills from Customize, in the section below.
Clone GNOS once and use this folder as your learning workspace:
git clone https://github.com/madhvantyagi/Gnos.git
cd Gnos
Codex
Install the plugin through the Codex CLI:
codex plugin marketplace add madhvantyagi/Gnos --ref main
codex plugin add gnos@gnos
Start a new Codex session in Gnos, or open the folder in the Codex app and start a new task. Ask:
Use GNOS. Read
skills/learning-orchestrator/SKILL.mdin this workspace and teach me [topic].
Claude Code
From Gnos, launch Claude Code with the plugin:
claude --plugin-dir .
Enter /gnos:learning-orchestrator Teach me [topic]. Repeat the launch command each session; --plugin-dir is session-only.
Cursor
-
Open Customize.
-
Add this repository:
https://github.com/madhvantyagi/Gnos -
Open a new agent chat and send:
Use GNOS. Read
skills/learning-orchestrator/SKILL.mdand teach me [topic].
That installs the teaching skills. These buttons install the diagram servers:
Excalidraw
Pinepaper
Approve Excalidraw and Pinepaper if Cursor asks. To keep a course in a local folder, clone the repository, open that folder, and send the same message. The folder loads the same skills.
OpenCode, Antigravity, and other agents
Open the Gnos folder as your workspace. For OpenCode, run opencode from that folder; for Antigravity, open it in the editor. Send:
Read AGENTS.md, then skills/learning-orchestrator/SKILL.md.
Use GNOS to teach me [topic]. Keep courses and progress in this workspace.
This uses GNOS directly from its files; your agent needs local file and terminal access. OpenCode also loads AGENTS.md automatically. Keep the repository together so its teachers, references, and scripts remain available.
Visual tools: Codex and Claude Code load the server definitions in .mcp.json. In Cursor, use the Add to Cursor buttons above, or open the folder so .cursor/mcp.json loads the same servers. For OpenCode or Antigravity, configure those servers using the host's MCP format. Pinepaper needs Node.js/npm; image generation uses your agent's available tools, while PDF and video lessons need their own dependencies.
For a course, share your goal, starting point, depth, and available time. To study the result, ask: “Show my course in the browser.”
Help it grow
GNOS grows through its users. If it helps you learn something hard, share what worked or broke and star the repo so others can find it.
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
skills/course-design/SKILL.md5.6 KBupstream ↗
--- name: course-design description: "Design and revise a course's goal, progression, prerequisites, and sources. Record depth and duration, validate and enroll course.json, then hand the current topic to lesson-design." --- # Course design Use this skill when a learning goal needs several sessions or a sequence of prerequisites. Answer a small local question directly in chat. For a course, design the progression from the learner's starting point to the agreed goal. Lesson design develops each topic into a complete lesson. ## Establish depth and duration Before designing, establish how deeply the learner wants to study and how much time they have. Ask for whichever information they have not already provided. Record both in `course.json`: - `depth`: `survey` for understanding the central ideas and connections, `working` for applying them independently, or `mastery` for justifying methods and examining their limits. - `length`: the learner's intended duration, such as one session, six weeks, or a term. Use these answers to choose the scope, pace, research, and useful media. A shorter course should cover fewer ideas well rather than abbreviating every explanation. ## Research and plan the course Read [course-research.md](references/course-research.md). Consult accessible books, course materials, or documentation to check prerequisites, definitions, and suitable exercises. Record what you actually opened and which sections the course will use. When a current topic or its blocking prerequisite might have a Khan Academy resource, send lesson design to check [the Khan Academy skill](../khan-academy/SKILL.md). Record the verified item as a course source, add its ID to that topic's `resource_ids`, add the Khan skill route to the topic's `skill_routes`, and use representation kind `khan` when the plan names one; leave clip selection and placement to lesson design. Do not expand the course around a broad Khan match when the learner needs one bridge. Read [course-contract.md](references/course-contract.md) and write `course.json`. Organize chapters and topics so their outcomes build toward the course goal. Identify the current topic and leave uncertain later topics provisional. Read the selected subject guide through `skills/subject/SKILL.md` and its assigned teacher's `SOUL.md` when one exists. Use its matching subfield to check the starting case, difficult distinction, and evidence the topic needs. Leave media, worked examples, and block order to lesson design using [representation choices](../lesson-design/references/representation-choices.md). Keep existing representation plans binding until explicitly revised; new plans need not prescribe media before the lesson's reasoning is developed. ## Validate and enroll Validate the plan and enroll it in the same turn: ```bash python3 skills/course-design/scripts/validate_course.py <course.json> python3 skills/learner-tracking/scripts/learner_state.py init <learner> python3 skills/learner-tracking/scripts/learner_state.py enroll <learner> --course <course.json> ``` Use the learner's name, or `learner` when no name was given. Confirm that the canonical workspace at `learners/<learner>/courses/<course-id>/course.json` exists before handing the topic to lesson design. Do not stop at saving a plan under `outputs/`; enroll it so lesson design can use the canonical course. Briefly explain the course goal, agreed depth and duration, and current topic. Describe what the current topic will help the learner understand. Use enough detail to make the plan understandable without reciting its fields. ## Hand the current topic to lesson design After enrollment, continue with [lesson-design](../lesson-design/SKILL.md). Read its [teaching reference](../lesson-design/references/lesson-design.md) and load the current topic, teacher, subject guidance, and learner evidence. When using the context loader, switch to lesson authoring explicitly: ```bash python3 skills/learning-orchestrator/scripts/assemble_context.py --subject <subject> \ --learner <learner> --course-id <course-id> --mode lesson ``` Lesson design must develop and review the explanation before publishing a ready lesson. Do not turn topic outcomes or representation purposes into short paragraphs and call that the lesson. Its finished content belongs in `lessons/<lesson-id>/lesson.json`. Course design stops authoring at the plan; the same host continues the work under lesson design's instructions. ## Show the finished lesson **Ask "Do you want to see the course now?" unless the learner already requested or approved it. This question controls opening the page, not whether lesson design runs. On yes, use [course-viewer](../course-viewer/SKILL.md) and render** ```bash python3 skills/course-viewer/scripts/render_viewer.py learners/<learner>/courses/<course-id> --require-current-lesson ``` Return the `portal/` link with the current lesson to open. An explicit request for only an outline may render before a lesson exists; identify that result as the course outline. For teaching, complete the lesson handoff before delivering the page. Re-render after changes to the lesson or its artifacts. If lesson design discovers a missing concept, source, or topic boundary, revise that part of the course. Record the reason in `revision_notes`, validate and enroll the revised plan, then return to lesson design. A media change stays with lesson design unless it changes a binding representation plan. Use learner evidence to revise future topics as the course progresses. Preserve stable IDs and record why the sequence, sources, or scope changed, following [course-contract.md](references/course-contract.md).README.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/madhvantyagi-gnos-skills-course-design.md