Lesson · AI literacy · Writing and procedures
Build an agent skill
An agent skill is a set of written instructions an AI agent follows for one kind of job. This page has two parts: a skill builder for your own planning, and a 45-minute lesson in which students write a skill on paper and a partner tests it by acting as the agent.
The big idea
An agent follows the instructions you wrote, even where they differ from what you meant. Clear writing becomes a working tool.
Students will be able to, without AI:
- Write a skill with a name, a description that says when to use it, steps and rules
- Test written instructions by having a partner follow them literally
- Revise instructions using evidence from a test
- Explain which rules must be enforced by code rather than requested in writing
Part 1 · For you
The teacher skill builder
Turn a job you repeat every week into a skill. It works in your browser, needs no account and saves nothing. Use “Classroom lesson” mode to show students a worked example on the projector.
Builder
Write, check and print a skill
Pick a starting point, change it to fit your class, write a short test plan, then download the file or print it as a card.
Test plan · not part of the file
Quality and privacy checks
The interactive builder needs JavaScript. A skill is a folder containing a file named SKILL.md. Copy this example and change it for your class:
--- name: exit-tickets description: Writes three exit-ticket questions, with expected answers and a likely misconception, from a lesson objective. Use when a teacher shares a lesson objective, plan or notes and asks for exit tickets, a quick check or end-of-class questions. --- # Exit tickets from a lesson objective ## Steps 1. Restate the objective in one plain sentence. If no grade level is given, ask for it. 2. Write three questions: one to recall, one to apply, one that asks students to explain their thinking. 3. Under each question, give a short expected answer and one likely misconception. 4. Keep the reading level at or below the grade given. ## Rules - Short-answer questions unless multiple choice is asked for. - Never include student names, grades or any student information. - If the objective is too broad for three questions, say so and suggest how to narrow it.
Use your skill
Three ways to try it
- Press Download .zip.
- In Claude on the web or desktop, turn on code execution in Settings (under Capabilities). Skills need it.
- Open Customize → Skills, press +, choose Upload a skill and pick the .zip.
- Start a new chat and try the four requests from your test plan.
Menu names have moved before; if you cannot find them, search the Claude help center for “use skills in Claude.” On a school account, your district may control which skills are allowed.
- Unzip the download.
- Put the folder in ~/.claude/skills/, or in .claude/skills/ inside a project to share it with colleagues.
- Start Claude Code and try your test requests.
Agent Skills is an open format (agentskills.io), so other tools that support it read the same folder.
- In Claude, describe the job: “Help me make a skill that turns my lesson objectives into exit tickets.”
- Claude has a built-in skill for making skills. It asks about your steps and rules, then writes the folder.
- Read it, then run your four test requests before you rely on it.
Before you use one
Three ground rules
- No student data in a skill. Names, grades, IEP or 504 details, health information and contact details never belong in the file. The privacy check above flags common ones, but it cannot catch everything.
- Follow your school’s AI policy. Use the tools and accounts your district has approved, and do not paste student work into a tool that is not approved for it.
- Read before you install. Skills can contain scripts. Only install skills you wrote or that come from people you trust, and read every file first.
Part 2 · Lesson flow · the 5 P’s
Write it. Test it on a person.
No student uses an AI tool in this lesson. Partners play the agent, which makes every unclear step visible. Claude’s apps are for adults 18 and over, and most AI tools set age limits, so the optional demo runs on the teacher’s screen. How the 5 P’s work →
Ponder
8 min○ Screens off · paper onlyRead one vague instruction aloud: “Make a study guide.” Ask two volunteers to describe, without talking to each other, exactly what they would make.
- Compare the two answers. How long? What goes in? What stays out? What if the notes are messy?
- Explain that an AI agent faces the same problem. A skill is a reusable instruction card for one job, with a label that tells the agent when to pull it out.
- Show the four parts on the board: name, description (what it does and when to use it), steps, rules.
Plan
12 min○ Screens off · paper onlyEach student chooses a job from the worksheet (study guide, lab report check, science news summary, or one of their own) and writes the skill.
- Name and description, including “Use when …”.
- Three to five steps someone could follow without asking questions.
- Two rules. One must say when to ask instead of guessing.
- A test plan: three requests that should use the skill and one that should not.
Partner
10 min● Optional AI demo · teacher screenPartners swap worksheets and play the agent. They must follow the card literally.
- Choose or skip: reading only the name and description, decide for each of the four test requests whether you would open this skill. Record yes or no in the test log.
- Follow the steps: talk through each step out loud as if doing the job. Put a ? next to any step where you had to guess.
- Optional demo: with a volunteer’s permission, type their skill into the builder on your projector, upload it to your own AI account, and run their four test requests live. Compare what the AI did with what the partner did.
Probe
10 min○ Screens off · paper onlyPartners return the sheets. Each student revises using the evidence in their test log.
- Fix the description for every request that was wrongly opened or wrongly skipped.
- Rewrite every step marked ? so nobody would have to guess.
- In the revision box, write what you changed and which test result made you change it.
- Whole class, two minutes: name a job that should never be given to an agent skill, and say why.
Prove
5 min○ Screens off · paper onlyExit ticket, on the worksheet, without help.
- Why does a skill’s description matter more than any other line?
- Name one rule from your skill that should be enforced by code (a hook) rather than just written as an instruction, and explain why.
- Teacher key: (1) The agent always sees the description and uses it to decide whether to open the skill; the rest is read only if it does. (2) Any rule that must never be broken, such as never sending student information outside the school. Written instructions can be misread, forgotten in a long job or overridden by planted text; a hook runs the same way every time.
Printable
Student worksheet
Two pages, one per student. Everything students hand in is handwritten, and the test log is filled in by a partner, so the thinking is visible.
Write a skill for an AI agent
An agent follows your card exactly. Make it impossible to misunderstand.
| Request | Should use it? | Partner opened it? | Why |
|---|---|---|---|
| Yes | |||
| Yes | |||
| Yes | |||
| No |
Assessment
Grade the instructions and the testing
Every row scores something students did themselves, in class. An AI could draft a skill; it cannot produce a partner’s test log or a revision based on it.
| Criteria | 4 · Excellent | 3 · Solid | 2 · Developing | 1 · Beginning |
|---|---|---|---|---|
| Description | Says what it does and exactly when to use it; the partner chose correctly on all four requests | Says what and when; one wrong choice | Says what but not when | Missing or vague |
| Steps | A partner could follow every step without guessing | One step needed a guess | Several steps needed guesses | Steps missing or out of order |
| Rules and judgment | Clear limits, an “ask instead of guessing” rule, and no private information | Two useful rules | One vague rule | No rules |
| Testing and revision | Every change is tied to a specific test result | Changes made, mostly linked to results | Changes made without evidence | No revision |
| Explanation (exit ticket) | Explains the description’s role and picks a rule that truly needs a hook, with a reason | Both answers correct, reasons thin | One answer correct | Missing |
Why this is hard to cheat
The skill, the test log and the revision are written by hand in class. The test log comes from a classmate reading the card, so the revision has to answer real evidence. An AI-written skill would still have to survive a partner’s literal reading.
Adjust it
Grades 7–8: Give students one of the starter skills from the builder with two steps left blank, and test with two requests instead of four.
Grades 11–12: Add a column to the test log: “Which rule should be a hook?” Or compare a student skill with one Claude drafts on the teacher’s screen.
No devices at all? Already device-free. Skip the optional demo.
Devices available? Students may type their card into the builder in “Classroom lesson” mode and print it. It runs in the browser, needs no account and saves nothing.
Discussion questions
- Which jobs should never be handed to an agent, however good the instructions? Who decides?
- If an agent follows a badly written skill and something goes wrong, who is responsible?
- How is writing a skill like writing a recipe, a lab procedure or a substitute-teacher plan?
- Why test with a request that should not use the skill?
Extensions & connections
- Background for you or older students: How AI agents are built, especially Lab 5 (skill, connector or helpers?) and Lab 6 (be the hook).
- Words to know: agent skill, hook, prompt injection.
- Careers: technical writers, process designers and safety engineers write instructions that others must follow exactly.
Put curiosity to work
Read it. Try it. Question it.
Every ARQIV lesson keeps the thinking on paper and puts AI in its place.
Written by ARQIV, October 2026. Initial edition, not yet classroom-piloted; tell us how it goes.