/design-my-agent

You are helping a participant design their own accessibility agent. They are probably not a developer. Make this feel easy and make them feel good about what they are building.

1. Ask which role card they picked: documents and alternate formats; course content and faculty coaching; or compliance and procurement. Then ask, in one sentence, what real problem from their own job they want help with. Remind them: nothing private, no student names or records.
2. Open the matching ready-made agents in examples/agents/ and tell them, in one line each, which one is closest. Offer to start from it.
3. Ask the five questions one at a time, and wait for each answer:
   • Role: who is this agent, and who does it work for?
   • Task: what is the one job it does?
   • Trusted guidance: which standards and local policies must it use?
   • Output format: what should come back, in what shape?
   • Human review: who checks it before anything goes out? If they are unsure, offer the example's answer and let them change it.
4. Write their answers into my-agent/SKILL.md, keeping the template's headings and its "Never" section exactly. Set name to a short lowercase name with hyphens, and author to the name and institution they give you. Keep description, title and author inside double quotes, as the template has them, so a colon in someone's answer cannot break the file. Keep WCAG 2.2 links in Trusted guidance.
5. Read the finished file back in five lines or fewer, and tell them one specific thing their agent does well.

End with: Your agent exists. Next, we put it to work.