assumed-knowledge
/assumed-knowledge
Rules for the prerequisite boundary of a course - what learners can be assumed to know and have at each point, and how to tell a gap from a fair assumption. Use when writing or reviewing participant-facing instructions, tasks, setup steps or quizzes, and when a learner got stuck.
- Author
- steffen74 ↗
- Repository
- agentic-course-creation ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Rules for the prerequisite boundary of a course - what learners can be assumed to know and have at each point, and how to tell a gap from a fair assumption. Use when writing or reviewing participant-facing instructions, tasks, setup steps or quizzes, and when a learner got stuck.
Original author description
Rules for the prerequisite boundary of a course - what learners can be assumed to know and have at each point, and how to tell a gap from a fair assumption. Use when writing or reviewing participant-facing instructions, tasks, setup steps or quizzes, and when a learner got stuck.
How it works
- What the boundary covers
- Rules
- Typical gaps
- Red flags in class
SKILL.md preview
--- name: assumed-knowledge description: Rules for the prerequisite boundary of a course - what learners can be assumed to know and have at each point, and how to tell a gap from a fair assumption. Use when writing or reviewing participant-facing instructions, tasks, setup steps or quizzes, and when a learner got stuck. --- # Assumed knowledge The **boundary** is what a learner can be assumed to know, have and be able to do at a given point of the course. Canvas block 6 holds it for the course start; the material of each unit extends it. Every step a learner is asked to take must lie inside the boundary at that point. A step outside it is a **gap**: the learner gets stuck, guesses or asks. ## What the boundary covers Not only concepts. Gaps come at least as often from: - **Things they have**: accounts, subscriptions, installed software, admin rights, a laptop of their own, a repository of their own. - **Things they have done**: a clone, a fork, a `uv sync`, joining a chat room, accepting an invitation. - **Where things are**: which repository, which folder, which link. “Your clone of the template repository” assumes they made one. - **Conventions**: what a command prompt is, what “run” means in a notebook, that `/command` is typed into the agent. ## Rules - The boundary is the instructor’s decision. When it is unclear whether something can be assumed, ask; do not decide. - Something becomes known only when the material taught it **before** it is used, or asked learners to do it with instructions they could follow. Being in a video listed for the same unit counts only if the video comes before the task. - A tool doing it for the learner (an agent, a setup script) counts only if the learner is told to use it at that step, with the exact prompt or command. - Every artifact a step relies on needs an origin: a step that created it, or a link to where it lives. - Optional material never extends the boundary. - When two personas differ, the boundary follows the weaker one, unless block 6 explicitly excludes them. ## Typical gaps - An instruction refers to an object (repository, file, room, account) whose creation step is missing or only implied. - Two pages name different repositories or folders for the same step. - A command works only from a specific folder, and the page does not say which. - A tool the step depends on is free in one plan and paid in another; the page assumes the paid one. - A task needs a concept that is scheduled for a later unit. ## Red flags in class The same question from several learners; learners waiting for the instructor before they can start; a deliverable missing for a whole group. Treat each as a boundary violation until shown otherwise, and load `course-checks` to turn it into a check.
Versions
The database has no other skills named assumed-knowledge.
Database snapshot: 13.11.2026 · package version 989c5b2778b2 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90learner-instructions
Rules for writing participant-facing instructions, tasks and setup steps that a learner can follow alone. Use when writing or editing participant pages, task descriptions, setup guides, READMEs of templates, or announcements to learners. - 100knowledge-gap-detector
Diagnoses what a learner knows about a topic or syllabus: probing questions across sub-topics, then a gap map of solid, shaky and missing areas with what to study next and in what order. Use when a student preparing for an exam or a professional learning a new field needs to… - 100learning-artifact
Diagnoses a learner's existing knowledge with no-default multiple-choice rounds, teaches only the gaps using evidence-based methods, schedules spaced review from a per-gap memory model, then tests with applied problems and a Feynman essay scored on a five-axis rubric. Use when… - 90course-checks
Rules and a catalogue of checks that course material must pass before learners see it - alignment, boundary, workload, consistency, visibility, links and setup. Use when planning checks, reviewing a unit, or turning a classroom problem into a check. - 100learn
Entry point for learning anything. Finds out what the user wants (quick intro, deep understanding, a course, a conversation, testing themselves, or going through a source) and what they already know, then routes to the right mode. Use for "/learn X", "I want to learn X", "teach… - 100teaching-technical-concepts
Explain a technical idea by starting from what the learner knows, one concept at a time, with a concrete example before the abstraction. Use when teaching, mentoring, or writing an explanation.