Introduction

This is an original TokRepo prompt for teachers, trainers and instructional staff who completed, or are partway through, a short AI professional-development badge or course. It converts your own notes into a single Markdown record: what the badge covered, what you can now do, evidence of practice, working vocabulary, open questions, a 30-day next-step plan, and a short shareable summary.

It is useful because badge completions often leave nothing durable behind. The prompt works only from what you supply and does not assume account access, provider rules or catalog details.

Prerequisites

• A completed or in-progress badge or short AI course, described in your own words.
• Your rough notes: takeaways, one classroom moment, your learner group.
• An ordinary AI chat that accepts text. No terminal, API key or account connection is needed.

Permissions and limitations

This is a writing and planning aid. It does not enrol you in anything, submit a badge claim, log in anywhere, or contact any organisation. Do not paste course materials, transcripts, slides or student data. It does not give legal, employment-contract or licensing advice about credential use. Whether an employer or licensure body accepts a specific badge depends on that body's rules, and you should check directly.

If you supply only the badge name, the assistant returns a short intake checklist and stops rather than filling gaps itself.

How to check the output

The prompt ends with a six-item review checklist you run yourself. Use it, plus these checks: does every capability statement trace to your notes; are tool and platform names accurate or removed; does the evidence section separate what you tested from what you only plan to test; does the shareable summary avoid numbers and titles you cannot support.

The record is capped at roughly 1,200 words unless you ask for more depth in one section. A manual alternative is included for readers working without an AI assistant.

FAQ

Do I need platform access or an API key? No. You paste text notes into an ordinary chat and read the Markdown document back.

Will it claim I earned a badge? No. It does not claim you earned, claimed or can claim a badge unless you explicitly say so, and it never states you are certified or endorsed.

Can I share the result publicly? The prompt marks inferences and gaps so you can review before reuse, and it never guesses a provider's display rules. Confirm those rules yourself.

Complete reusable prompt

Turn an AI Training Badge Into a Reusable Teaching Portfolio Record

You are helping an educator convert a completed or in-progress professional-development badge or short AI course into a concrete, reusable record they can keep, share, and build on. Work only from the information the user provides. Do not assume anything about a platform, badge provider, course catalog, or account. Do not claim the user earned, claimed, or can claim a badge unless the user explicitly says so.

Step 0 — Ask for inputs before writing

Ask the user to paste or list the following in their own words. If any item is missing, say explicitly that it is missing and write around it rather than inventing it.

1. Badge or session name, and the provider or organization as the user states it.
2. When they completed it (month/year is enough) and how long it took, if known.
3. The three to seven biggest takeaways in the user's own words. Rough notes are fine.
4. At least one specific classroom or training moment where they tried, plan to try, or would try the idea.
5. The grade level, subject, or learner group they work with.
6. Any tool, feature, or workflow they used, described in plain language. If they are unsure what a tool is called, they should describe what they did instead of naming a product.
7. What they still feel shaky about.
8. Where they want to go next (another badge, a unit redesign, a peer workshop, a department pilot, or 'not sure yet').

If the user gives only the badge name and nothing else, produce a short intake checklist and stop. Do not fill the gaps yourself.

Step 1 — Build the skill record

Produce a single Markdown document with these sections. Use the user's wording wherever possible. Keep quotes from the user's notes clearly attached to the user as their own words.

1. Badge at a glance

One short paragraph: what the badge covered, drawn only from the user's takeaways. No promotional language.

2. What I can now do

A bulleted list of four to eight capability statements. Each bullet must follow this shape: an action verb, the specific task, and the learner context. Example shape only: 'Design a short ___ activity that lets ___ students practice ___ before I grade it.' Do not reuse that example's content; derive each bullet from the user's material.

3. Evidence of practice

For each classroom or training moment the user described, write a short block with: the situation, what was tried or planned, what the user hoped would happen, and what would count as evidence it worked. If the user has not tried anything yet, label the block 'planned, not yet tested.'

4. My working vocabulary

A glossary of the terms the user actually mentioned, each defined in one plain sentence and connected to their subject or learner group. If the user is unsure about a term, mark it 'needs checking' rather than defining it confidently.

5. Open questions

A list of what the user said they feel shaky about, restated as answerable questions. For each, suggest one concrete way to find out: ask a colleague, test it with one class, read a specific type of guide, or bring it to a department meeting.

6. Thirty-day next step plan

Three to five steps, each with: what to do, roughly how long it will take, what to have in hand when done, and who else could be involved. Keep every step within the user's own control. Do not include steps that require posting publicly, emailing anyone, or registering anywhere.

7. Shareable summary

A 60 to 90 word paragraph the user could paste into a resume, a professional profile, or a staff update. It must be accurate to the inputs, contain no numbers that were not supplied, and contain no claim of certification unless the user stated it.

Step 2 — Handle uncertainty and missing information

• Mark every statement that rests on an inference with 'assumption' in brackets.
• Mark every gap with 'missing information' in brackets, and say what the user would need to add.
• Never guess a provider's rules, a badge's requirements, or whether a badge can be displayed publicly.
• Never state or imply that the user is certified, accredited, or endorsed by any organization.

Step 3 — Review checklist before the user reuses this record

Present this as a short checklist the user runs themselves:

1. Does every capability statement trace back to something in my notes?
2. Is any tool, feature, or platform name accurate to what I actually used, or should it be removed?
3. Does the evidence section separate what I tested from what I only plan to test?
4. Does the shareable summary avoid numbers and titles I cannot support?
5. Would I be comfortable if a colleague or supervisor read this and asked me to explain any line?
6. Is anything in the plan something I can start this week without waiting on anyone?

Boundaries

• This is a writing and planning aid. It does not enroll the user in anything, does not submit a badge claim, does not log in anywhere, and does not contact any organization.
• Do not reproduce course materials, transcripts, or slides. Work from the user's own summary.
• Do not give legal, employment-contract, or licensing advice about credential use.
• If the user asks whether a specific badge will be accepted by an employer or licensure body, tell them that depends on that organization's rules and they should check directly.

Output format

Return one Markdown document with the seven sections from Step 1, then the uncertainty notes from Step 2, then the checklist from Step 3. Keep the whole thing under roughly 1,200 words unless the user asks for more depth in one section. Use plain headings and bullets, no tables, no code blocks before the document begins, no preamble about what you are about to do.

Manual alternative if no AI assistant is available

Open a blank document and create headings 1 through 7 above. Fill section 2 by rereading your session notes and circling every verb that describes something you can do. Fill section 3 by writing one paragraph per classroom moment. Fill section 6 with three steps you could start before the end of the week. Then read section 7 aloud and delete any sentence you could not defend to a colleague.

References and reuse

• 1,400 educators joined our Badge-a-thon: Day of AI Learning. · Thu, 01 Oct 2026 16:00:00 +0000

Original TokRepo prompt · CC BY 4.0. Reference documents retain their own rights.