# Prompt: Turn an AI Training Badge Into a Teaching Record > An original TokRepo prompt that helps educators convert a completed or in-progress AI badge into a structured, honest teaching record and 30-day plan. ## Install Copy the content below into your project: # Prompt: Turn an AI Training Badge Into a Teaching Record An original TokRepo prompt that helps educators convert a completed or in-progress AI badge into a structured, honest teaching record and 30-day plan. ## Quick Use Paste the full prompt below into an ordinary AI chat that accepts text. Before that, paste or type your own notes answering the eight input questions in the prompt: badge or session name and provider as you state it, when you finished it and how long it took, three to seven takeaways in your own words, at least one classroom or training moment, your grade level or learner group, any tool or workflow described in plain language, what still feels shaky, and where you want to go next. Check the result by reading each section against your own notes. Capability statements should trace back to something you wrote. Anything the assistant guessed should carry an `[assumption]` or `[missing information]` mark. Your own words should stay attributed to you. ## 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. ## Source and thanks Original TokRepo prompt, CC BY 4.0. Context reference: [1,400 educators joined our Badge-a-thon: Day of AI Learning]() (Google, 1 October 2026). External reference material retains its own rights. Source reviewed; runtime not tested. ## 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.](https://blog.google/products-and-platforms/products/education/ai-educator-series-badge-a-thon/) · Thu, 01 Oct 2026 16:00:00 +0000 Original TokRepo prompt · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Reference documents retain their own rights. --- # 提示词:把 AI 培训徽章整理成可复用的教学档案 一份 TokRepo 原创提示词,帮助教师把已完成或进行中的 AI 徽章培训整理成结构清晰、如实呈现的教学档案与 30 天行动清单。 ## 快速使用 把下方完整提示词粘贴进一个可以接受文本的普通 AI 对话中。在此之前,先粘贴或输入你自己的笔记,回答提示词中的八个输入问题:徽章或培训名称及你所述的主办方、完成时间与耗时、用你自己语言写的三到七条要点、至少一个课堂或培训场景、你面对的年级或学习者群体、用平实语言描述的任意工具或流程、你仍感不确定的内容,以及你接下来想做什么。 检查结果时,把每一节与你自己的笔记对照。能力陈述应当能追溯到你会写下的内容。助手猜测的部分应带有 `[assumption]` 或 `[missing information]` 标记。你自己的原话应仍归属于你。 ## 简介 这是 TokRepo 的原创提示词,面向已完成或正在参加短时 AI 专业发展徽章或课程的教师、培训师与教学人员。它把你自己的笔记整理成一份 Markdown 记录:徽章涵盖什么、你现在能做什么、实践证据、工作词汇、待解问题、30 天行动清单,以及一段简短的可分享简介。 它的价值在于:徽章完成后往往不留下任何可长期使用的东西。该提示词只依据你提供的信息工作,不假设账号访问、主办方规则或课程目录细节。 ## 前提条件 - 一个已完成或进行中的徽章或短时 AI 课程,能用自己的话描述。 - 你的粗略笔记:要点、一个课堂场景、你的学习者群体。 - 一个可接受文本的普通 AI 对话。不需要终端、API 密钥或账号连接。 ## 权限与限制 这是一个写作与规划辅助工具。它不会让你报名任何课程、不会提交徽章申领、不会登录任何地方、也不会联系任何组织。请勿粘贴课程材料、成绩单、幻灯片或学生数据。它不就凭证使用提供法律、雇佣合同或授权方面的建议。雇主或执照机构是否认可某个徽章取决于该机构的规则,你应直接核实。 如果你只提供徽章名称,助手会返回一份简短的资料清单然后停止,不会自行补齐空白。 ## 如何检查输出 提示词末尾有一份由你自己执行的六项检查清单。使用它,并加上这些检查:每条能力陈述是否可追溯到你的笔记;工具与平台名称是否准确,否则删除;证据一节是否区分了你已尝试和仅计划尝试的内容;可分享简介是否避免了无依据的数字与头衔。 记录控制在约 1,200 字以内,除非你要求某一节更深入。文中还包含一个供没有 AI 助手的读者使用的人工替代方案。 ## 常见问题 **需要平台访问权限或 API 密钥吗?** 不需要。你把文字笔记粘贴进普通对话,再读回 Markdown 文档。 **它会声称我获得了徽章吗?** 不会。除非你明确说明,它不会声称你已获得、已申领或可以申领徽章,也绝不会称你获得认证或被认可。 **我可以公开分享结果吗?** 提示词会标记推断与信息缺口,方便你在复用前审阅,并且从不猜测主办方的公开展示规则。这些规则请自行确认。 ## 来源与致谢 TokRepo 原创提示词,CC BY 4.0。背景参考:[1,400 educators joined our Badge-a-thon: Day of AI Learning]()(Google,2026 年 10 月 1 日)。外部参考材料保留其自身权利。已审阅来源;未进行运行时测试。 ## 完整可复制提示词 # 将 AI 培训徽章转化为可复用的教学作品集记录 你正在帮助一位教育工作者,把已完成或正在进行中的专业发展徽章或 AI 短期课程,转化为一份具体、可复用的记录,供其保存、分享并在此基础上继续发展。仅依据用户提供的信息来工作。不要对平台、徽章提供方、课程目录或账户做任何假设。除非用户明确说明,否则不要声称用户已获得、已申领或可以申领某枚徽章。 ## 第 0 步——写作前先索取输入 请用户用自己的话粘贴或列出以下内容。如果缺少任何一项,请明确说明该项缺失,并绕开它来写,而不是编造。 1. 徽章或课程的名称,以及用户所述提供方或机构。 2. 他们完成的时间(月份/年份即可)以及所花时长(如已知)。 3. 用用户自己的话列出三到七条最重要的收获。粗略笔记即可。 4. 至少一个具体的课堂或培训场景,说明他们曾尝试、计划尝试或会尝试该想法。 5. 他们所教的年级、学科或学习者群体。 6. 他们使用过的任何工具、功能或工作流程,用平实的语言描述。如果他们不确定某个工具叫什么,应描述自己做了什么,而不是说出某个产品名称。 7. 他们仍然觉得没把握的地方。 8. 他们接下来想去哪里(另一枚徽章、一个单元重新设计、一次同伴工作坊、一个部门试点,或“还不确定”)。 如果用户只给出徽章名称而别无其他,请生成一份简短的信息收集清单并停止。不要自行填补空白。 ## 第 1 步——构建技能记录 生成一份包含以下各部分的 Markdown 文档。尽可能使用用户的措辞。用户笔记中的引语要清楚标明是用户本人的原话。 ### 1. 徽章概览 用一段简短的文字说明:该徽章涵盖了哪些内容,仅依据用户的收获来写。不要使用宣传性语言。 ### 2. 我现在能做什么 一个由四到八条能力陈述组成的项目符号列表。每条都必须遵循这种形式:一个动作动词、具体任务,以及学习者情境。仅作形式示例:“设计一个简短的 ___ 活动,让 ___ 学生在评分前练习 ___。”不要沿用该示例的内容;每条都要从用户的材料中推导出来。 ### 3. 实践证据 针对用户描述的每一个课堂或培训场景,写一个简短段落,包含:情境、尝试或计划了什么、用户希望发生什么,以及什么可算作其奏效的证据。如果用户尚未尝试任何内容,请将该段标注为“已计划,尚未测试”。 ### 4. 我的工作词汇 一份术语表,收录用户实际提到的术语,每个术语用一句平实的话定义,并联系到他们的学科或学习者群体。如果用户对某个术语不确定,请标注“需要核实”,而不要自信地为其下定义。 ### 5. 待解问题 列出用户所说觉得没把握的内容,改写成可回答的问题。针对每个问题,建议一种具体的查明方式:询问同事、在一个班上测试、阅读某类特定指南,或提交到部门会议讨论。 ### 6. 三十天下一步计划 三到五个步骤,每一步都包含:做什么、大致需要多长时间、完成时手中应有什么,以及还可以让谁参与。每一步都要在用户自己可控的范围内。不要包含需要公开发布、给任何人发邮件或在任何地方注册的步骤。 ### 7. 可分享摘要 一段 60 到 90 词的文字,用户可以粘贴到简历、职业档案或员工动态中。它必须与输入信息一致,不包含未提供的数字,并且除非用户说明,否则不包含任何认证声明。 ## 第 2 步 — 处理不确定性和缺失信息 - 对每一条基于推断的陈述,用方括号标注"假设"。 - 对每一处信息空白,用方括号标注"缺失信息",并说明用户需要补充什么。 - 绝不要猜测提供方的规则、徽章的要求,或徽章是否可以公开展示。 - 绝不要声称或暗示用户已获得任何组织的认证、认可或背书。 ## 第 3 步 — 用户复用本记录前的检查清单 将此呈现为用户自行执行的简短检查清单: 1. 每一条能力陈述是否都能追溯到我的笔记中的内容? 2. 任何工具、功能或平台的名称是否与我实际使用的相符,还是应该删除? 3. 证据部分是否将我测试过的内容与我仅计划测试的内容区分开来? 4. 可分享的摘要是否避免了我无法支撑的数字和头衔? 5. 如果同事或主管读到这份内容并要求我解释任何一行,我会不会感到自在? 6. 计划中是否有任何事是我本周就能开始、无需等待他人的? ## 边界 - 这是一种写作和规划辅助工具。它不会让用户注册任何东西,不会提交徽章申请,不会在任何地方登录,也不会联系任何组织。 - 不要复制课程材料、成绩单或幻灯片。基于用户自己的摘要来工作。 - 不要就凭证使用提供法律、雇佣合同或许可方面的建议。 - 如果用户询问某个特定徽章是否会被雇主或执照颁发机构接受,告诉他们这取决于该组织的规则,他们应直接核实。 ## 输出格式 返回一份 Markdown 文档,包含第 1 步中的七个部分,然后是第 2 步的不确定性说明,再是第 3 步的检查清单。除非用户要求某个部分有更多深度,否则整份内容控制在约 1,200 词以内。使用简洁的标题和项目符号,不使用表格,文档开始前不使用代码块,不写关于你即将做什么的前言。 ## 没有 AI 助手时的手动替代方案 打开一个空白文档,创建上面的标题 1 到 7。填写第 2 部分时,重读你的会话笔记,圈出每一个描述你能做的事情的动词。填写第 3 部分时,为每个课堂时刻写一段话。填写第 6 部分时,写下你可以在本周末之前开始的三个步骤。然后大声朗读第 7 部分,删除任何你无法向同事辩护的句子。 ## 参考资料与复用 - [1,400 educators joined our Badge-a-thon: Day of AI Learning.](https://blog.google/products-and-platforms/products/education/ai-educator-series-badge-a-thon/) · Thu, 01 Oct 2026 16:00:00 +0000 TokRepo 原创提示词 · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)。参考资料保留各自原有权利。 --- Source: https://tokrepo.com/en/workflows/prompt-turn-ai-training-badge-into-teaching-record-93198355 Author: Prompt Lab