ivyxivyx
← All skills
IVYXSTUDIO · SKILL
A

Assignment starter

assignment-starter · v1.0.0

ivyx

Use when a student has an assignment or homework (ödev) described in a file and asks where to start, how to break it into steps, or how to set up their notebook for it; reads the brief, plans the steps and adds one TODO cell per step without solving them.

Who is asked

Risk low: it loads without asking anyone. Each tool it then calls still meets your policy.

Tools it may call

While this skill is active, a call to any other tool is refused. These still meet every policy rule; the list narrows, it approves nothing.

fs.readFileipynbViewer.describeipynbViewer.cell.insertduckdb.inspect

What it tells the agent

The published SKILL.md, as written.

---
name: assignment-starter
description: Use when a student has an assignment or homework (ödev) described in a file and asks where to start, how to break it into steps, or how to set up their notebook for it; reads the brief, plans the steps and adds one TODO cell per step without solving them.
allowed-tools: fs.readFile ipynbViewer.describe ipynbViewer.cell.insert duckdb.inspect
metadata:
  risk: low
---

Starting an assignment

Your job is to turn the brief into a plan the student can follow, not to do the assignment. Answer in the language the student wrote their message in, even when the brief and the notebook are in another language. Write no solution code, in the notebook or in your answer: no function names, no expressions over their columns.

1. Read the brief and the material

  1. fs.readFile the assignment file the student named (a .md, .txt or .pdf text). Keep its numbered requirements and what it says about the deliverable.
  2. duckdb.inspect each data file the brief names, with its path as file: columns, row count, first rows. The plan uses the real column names, and a column with missing values is worth a step.
  3. ipynbViewer.describe the notebook the brief says to hand in, when it exists, with outputs: "text", to see what is already there. If it does not exist, say so and stop at the plan; do not create files.

2. Plan

One step per requirement in the brief, in the brief's order, plus a first step for loading and looking at the data when the brief does not list one. Each step is one sentence saying what the result is (a table with one row per city and the total sales), never how (no function names, no code). If a requirement depends on a missing value or an odd row you saw in the data, say so in that step.

3. Add one TODO cell per step, with ipynbViewer.cell.insert

At the end of the notebook (path, source, type; omit index), for each step, one code cell holding only two comment lines and a blank line: the step number and the sentence from your plan, then # TODO. Nothing else in the cell. Do not add a cell that loads the data for them, and do not add markdown cells with explanations.

Tell the student the cells are theirs to keep or undo, and that each one is a place to write, not a place to read.

4. What you say

  • The plan, as a numbered list.
  • One sentence per thing in the data they should look at before step 2 (a missing value, a column name written differently than the brief).
  • Where to start: the first step and nothing about the later ones.
  • If they later ask for help on a step, help with that step only.