This skill produces worksheets as
packages. Follow the
k2f skill for authoring: unpack or init a workspace, edit the semantic tree, run pack/verify, then export. K2F keeps agents on
meaning (sections, items, response types)—not pixel coordinates—while the engine compiles layout, typography, and theme.
Before you build, install the core skill:
npx skills add suzheng/k2f --skill k2f
.
-
Route & clarify — Infer subject, grade band, duration, and worksheet type (drill, scaffolded practice, lab/data, reflection, organizer, gap-closure). Ask at most two high-leverage questions (e.g., target standard, with/without answer key); default item count and difficulty from context.
-
Learning frame — Title, optional standard or skill gist (≤10 words), and what success looks like in one sentence. State prerequisites or materials the sheet assumes (textbook page, prior lesson, calculator)—not repeated per item.
-
Information architecture — Layer top to bottom:
- Orientation (brief): purpose and how to use the sheet; no teaching lecture.
- Optional anchor (one block max): stimulus—passage excerpt, diagram description, data table, scenario—only if items depend on it.
- Sections: grouped by sub-skill or cognitive step; each section has a short heading and 3–12 items unless the user specifies otherwise.
- Response contract: per item, declare response type (blank line, checkbox, table cell, short paragraph box, label-on-diagram) and approximate space needed.
- Answer key (if requested): separate outline keyed by item ID; do not interleave solutions with student items on the same page role.
-
Item design — One measurable prompt per item; split compound questions. Order easy → hard within a section unless spiral review demands otherwise. For gap-style sheets, group by category; omit empty categories. Each gap row: short source snippet (or “not stated”), one specific question, blank answer field. Prioritize scope, core skill, and blocking ambiguities before nice-to-haves.
-
Shared registry — Numbers, names, vocabulary, dataset values, and scenario facts live once under
; items reference stable keys so edits cannot fork.
-
Design intent — For the engine, not coordinates:
- Tone: calm, classroom-credible; friendly for younger grades without clip-art clutter.
- Hierarchy: title and learning frame strongest; section heads scannable; item numbers or letters consistent.
- Density: instructions tight; generous workspace where handwriting or drawing is expected; avoid paragraph walls.
- Consistency: parallel wording across items; same label scheme for sections and response types.
- Palette: print-safe B&W; at most one accent for section headers or the learning frame.