# Turn One Task Into a Reusable AI Prompt

> A portable prompt that turns one recurring task and one past run into a reusable instruction block for any AI chat, flagging gaps and conflicts first.

## Install

Copy the content below into your project:

# Turn One Task Into a Reusable AI Prompt

A portable prompt that turns one recurring task and one past run into a reusable instruction block for any AI chat, flagging gaps and conflicts first.

## Start here

**What to paste:** one message containing this prompt text plus your own answers in the five `[INPUT]` slots — your repetitive task, what stays the same each time, what changes each time, one real past run (raw input and finished output), and your quality requirements and hard boundaries.

**Where to paste it:** the text box of an ordinary AI chat that accepts text. No terminal, account connection, API key or setup step is involved.

**How to check the output:** confirm you get all six parts in order, that the one-placeholder slot is a single marked line, that the walkthrough is labelled as a fictional-style example, and that anything you left blank is listed as UNRESOLVED instead of filled in.

## What this does

A recurring task — a weekly summary, a standard reply, a short report — is usually re-explained from scratch every time. This prompt converts one such task into a compact instruction block you can paste into any capable AI assistant whenever the task comes round again. It also runs your instruction block once on a real past run so you can see the shape of the result, and it lists gaps and rule conflicts before you rely on it.

It is a drafting and self-check exercise. It produces text you copy and use yourself.

## Prerequisites and permissions

There is nothing to install and nothing to connect. You supply text; you receive text. The prompt cannot access an account, file, calendar, mailbox or external service, and nothing it writes sends, schedules or saves anything. Keep the last field for anything sensitive that must not be reproduced.

## Working through the inputs

| Slot | What belongs there | If it is missing |
| --- | --- | --- |
| Repetitive task | Name, short description, frequency, audience | The block is stated as UNRESOLVED and cannot be finished |
| Stays the same | Templates, formats, lists, terminology, house rules | Constants are omitted and the draft is thin |
| Changes each time | The variable part you paste in later | The reusable slot stays generic |
| One past run | Raw input and your finished output, even if messy | The walkthrough is weak and flagged as such |
| Quality and boundaries | What the output must never do, and sensitive material | Boundaries cannot be enforced; do not reuse until added |

A weak past run is not fatal. Say it is thin, and the block is written to still produce a usable draft while flagging the weak spots rather than papering over them.

## How to read the result

The answer arrives in six parts: the instruction block, the single variable slot, a walkthrough, a self-check, a reuse checklist, and up to three fixes. The walkthrough carries the label FICTIONAL-EXAMPLE-STYLE WALKTHROUGH — NOT A LIVE RUN, and it is a shape demonstration only. The self-check marks invented additions as SPECULATIVE and states conflicts instead of quietly choosing a side.

Source reviewed; runtime not tested.

## FAQ

**Does this connect to my calendar, files or mailbox?** No. It only writes text back to you, and you paste the instruction block wherever you like yourself.

**What if I only have a rough idea of the task?** Give the rough version. The answer should list what is missing and what the smallest useful version of each missing piece looks like, then continue with only what you gave, marking the rest UNRESOLVED.

## Source and thanks

Original TokRepo prompt, CC BY 4.0. Context reference: [Let skills in Gemini tackle your most repetitive tasks](<https://blog.google/products-and-platforms/products/gemini/automate-tasks-with-skills/>) (a reference for the reusable-instructions idea, not proof of popularity or of any product capability). External reference material retains its own rights.

## Complete reusable prompt

You are helping me turn one repetitive task into a reusable instruction block I can paste into an AI assistant whenever I need it again. This is a drafting and self-check exercise: you produce text I will copy and use later myself. You cannot access any account, file, calendar, mailbox, or external service, and nothing you write here performs an action, sends anything, or saves anything automatically.

My repetitive task (name and short description, plus frequency and who the output is for):
[INPUT]

What I already have that stays the same each time (templates, formats, lists, terminology, style rules, house conventions):
[INPUT]

What changes each time I run it (the variable part I will paste in — e.g. raw notes, a new request, a new document section, a set of data):
[INPUT]

One real past run of this task, as I actually did it — raw input and my finished output, even if messy or imperfect:
[INPUT]

My quality requirements and hard boundaries (things the output must never do, include, or assume; anything sensitive that must not be reproduced):
[INPUT]

If any section above is empty or too vague to work from, do not invent the missing details. Instead, list what is missing and what the smallest useful version of it would look like, then continue with only what I gave. Mark anything you could not produce for that reason as UNRESOLVED rather than filling it in.

Produce the following, in this order.

1) INSTRUCTION BLOCK — the reusable part
Write a single, self-contained block of instructions that could be copied into any capable AI assistant. It must:
- State the task and the role the assistant should take.
- Define exactly what input the assistant will receive each run, and what it should do if that input is empty, incomplete, or off-topic.
- Specify the exact output format: sections, order, length guidance, tone, and what to do when a required piece of information is absent (leave a clearly labelled gap rather than guessing).
- Carry over every constant from my 'stays the same' list and never contradict my quality requirements or hard boundaries.
- Avoid any claim of tool access, browsing, sending, scheduling, or memory. Phrase everything as instructions for what the assistant should write, not actions it should take.
- Be written as instructions to the assistant, not as instructions to me.

2) ONE-PLACEHOLDER VARIABLE SLOT
Show, as a clearly marked line, the single slot where I paste my changing input each time, and describe in one sentence what belongs in it.

3) WORKED EXAMPLE
Run the instruction block once on the real past input I supplied. Show:
- A short label line: 'FICTIONAL-EXAMPLE-STYLE WALKTHROUGH — NOT A LIVE RUN.'
- The raw input used, quoted from mine, or a minimized version if it is too long.
- The output the block produces, in full, following your own format rules.
This is a worked example showing the shape of the result, not evidence that anything ran live.

4) SELF-CHECK AGAINST MY MATERIALS
Go through the worked example and report:
- Which parts are directly supported by what I supplied.
- Which parts are gaps, assumptions, or plausible-sounding additions I never provided. List each one as SPECULATIVE and either remove it or mark it.
- Any place where the block's own rules and my quality requirements conflict, or where two requirements cannot both be satisfied. State the conflict instead of silently picking a side.
- Any hard boundary that the worked example brushes against.

5) REUSE CHECK
State in one list what a future run must verify before I trust the output: input completeness, format compliance, unsupported claims, boundary compliance, and anything task-specific I insisted on. Keep each check short enough to actually perform.

6) WHAT TO FIX BEFORE I REUSE THIS
Give at most three concrete edits to the instruction block that would most reduce rework, based on the gaps and conflicts you found. If there is nothing meaningful to fix, say so instead of inventing improvements.

Rules for your whole answer:
- Do not add facts, deadlines, names, numbers, policies, or sources that are not in my input.
- Do not restate my hard boundaries as optional.
- Do not use phrases suggesting you accessed, changed, sent, or stored anything.
- Keep the instruction block compact enough to paste into a chat window in one go.
- If my past run is weak or incomplete, say what is weak and write the block so it will still produce a usable draft, flagging the weak spots rather than papering over them.

Labelled fictional mini example (style only, not real data): Input: recurring task = 'weekly summary of client call notes'; constants = plain tone, three bullets max, no client names; variable = this week's raw notes; past run = messy notes with two action items; boundaries = never invent deadlines. Expected output shape: an instruction block, one 'PASTE HERE' slot, a walkthrough summary with two bullets and a flagged missing deadline, a SPECULATIVE list for any invented owner, and a short reuse checklist. Pass/fail checks: fail if the block claims it can send or file anything; fail if the walkthrough invents a deadline or owner not in the notes; fail if the constants are dropped; pass only if gaps are labelled and each check can be tied to the supplied inputs.

## References and reuse

- [Let skills in Gemini tackle your most repetitive tasks](https://blog.google/products-and-platforms/products/gemini/automate-tasks-with-skills/) · Wed, 30 Sep 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.

---

<!-- ZH -->

# 把一项任务变成可复用的 AI 提示词

一个可直接使用的提示词：把一项重复性任务和一次真实的历史成果，转换成可粘贴到任意 AI 对话中的复用指令块，并先标出缺口与冲突。

## 开始使用

**粘贴什么：** 一条消息，包含本提示词正文，以及你在五个 `[INPUT]` 位置填写的答案——你的重复性任务、每次都不变的部分、每次都会变的部分、一次真实的历史执行（原始输入和你的成品输出）、以及你的质量要求和硬性边界。

**粘贴到哪里：** 普通 AI 对话的输入框（任何能接受文字的聊天窗口）。不需要终端、不需要连接账号、不需要 API 密钥或任何配置步骤。

**怎么检查输出：** 确认六个部分按顺序齐全；确认变量插槽是单独一行并明确标出；确认示例部分带有“虚构风格示例”的标注；确认你留空的内容被列为 UNRESOLVED，而不是被擅自补齐。

## 这个提示词做什么

重复性任务——每周小结、标准回复、简短报告——往往每次都要重新解释一遍。这个提示词把其中一项任务转化成一段紧凑的指令块，任务再次出现时，把它粘贴进任意有能力的 AI 助手即可。它还会用你提供的一次真实历史执行，把这段指令块试跑一遍，让你看到结果的形状，并在你依赖它之前列出缺口和规则冲突。

这是一次起草与自查练习，产出的是你自己复制使用的文字。

## 前提与权限

无需安装，无需连接。你提供文字，它返回文字。该提示词无法访问账号、文件、日历、邮箱或任何外部服务，它写出的内容也不会发送、排程或保存任何东西。把敏感内容放进最后一个字段，写明不得复现的部分。

## 五个输入项怎么填

| 位置 | 应填内容 | 缺失的后果 |
| --- | --- | --- |
| 重复性任务 | 名称、简短描述、频率、给谁看 | 指令块标为 UNRESOLVED，无法完成 |
| 每次不变的部分 | 模板、格式、清单、术语、内部惯例 | 常量被略去，草稿很单薄 |
| 每次变化的部分 | 你之后每次粘贴进来的变量 | 复用插槽只能保持泛泛而谈 |
| 一次历史执行 | 原始输入和你的成品输出，粗糙也可以 | 示例薄弱，并被明确标注为薄弱 |
| 质量与边界 | 输出绝不能做的事，以及敏感材料 | 边界无法落实；补齐前不要复用 |

历史执行薄弱不是致命问题。直接说明它薄弱，指令块会被写成仍能产出可用草稿的形式，并标注薄弱之处，而不是掩盖过去。

## 如何阅读结果

回答分为六部分：指令块、唯一的变量插槽、示例走查、自查、复用前检查清单，以及最多三条修改建议。示例走查带有标注 FICTIONAL-EXAMPLE-STYLE WALKTHROUGH — NOT A LIVE RUN，仅用于展示结果形状。自查会把凭空添加的内容标为 SPECULATIVE，遇到冲突会直接说明，而不是悄悄选一边。

来源已审核；未做运行时测试。

## 常见问题

**它会连接我的日历、文件或邮箱吗？** 不会。它只把文字写回给你，指令块由你自己粘贴到想用的地方。

**如果我对任务只有一个模糊的想法怎么办？** 就把模糊版本给它。回答应当列出缺失了什么、每一项缺失的最小可用版本长什么样，然后只基于你给出的内容继续，其余部分标为 UNRESOLVED。

## 来源与致谢

TokRepo 原创提示词，CC BY 4.0。背景参考：[Let skills in Gemini tackle your most repetitive tasks](<https://blog.google/products-and-platforms/products/gemini/automate-tasks-with-skills/>)（用于说明“可复用指令”这一思路的参考，不作为流行度或任何产品能力的证明）。外部参考资料保留其自身权利。

## 完整可复制提示词

你正在帮我把一项重复性任务转成一个可复用的指令块，以便我在需要时随时把它粘贴进 AI 助手。这是一个起草与自查练习：你产出的文本将由我复制并在之后自行使用。你无法访问任何账户、文件、日历、邮箱或外部服务，你在此写下的任何内容都不会执行操作、发送任何东西或自动保存任何东西。

我的重复性任务（名称与简短描述，外加频率以及输出是给谁的）：
[INPUT]

我已有的、每次都保持不变的内容（模板、格式、列表、术语、风格规则、内部惯例）：
[INPUT]

我每次运行时会变化的内容（我将粘贴进来的可变部分——例如原始笔记、一个新请求、一个新的文档章节、一组数据）：
[INPUT]

这项任务的一次真实过往运行，按我实际执行的方式——原始输入和我最终完成的输出，即使杂乱或不完美：
[INPUT]

我的质量要求和硬边界（输出绝不能做、包含或假定的内容；任何不得被复现的敏感信息）：
[INPUT]

如果以上任何部分为空或过于模糊而无法据此工作，不要编造缺失的细节。相反，列出缺失的内容，以及它最小可用的版本会是什么样，然后仅用我给出的内容继续。凡是因该原因而无法产出的内容，标记为 UNRESOLVED，而不是把它补上。

按此顺序产出以下内容。

1) INSTRUCTION BLOCK——可复用部分
写一个单一的、自包含的指令块，可以复制进任何有能力的 AI 助手。它必须：
- 说明任务，以及助手应扮演的角色。
- 准确界定助手每次运行将收到什么输入，以及如果该输入为空、不完整或离题时它应怎么做。
- 规定确切的输出格式：各章节、顺序、长度指引、语气，以及当某条必需信息缺失时该怎么做（留出清楚标注的空缺，而不是猜测）。
- 承接我“保持不变”清单中的每一个常量，绝不与我的质量要求或硬边界相矛盾。
- 避免任何关于工具访问、浏览、发送、排期或记忆的声称。把一切表述为助手应写什么的指令，而不是它应采取的动作。
- 写成给助手的指令，而不是给我的指令。

2) ONE-PLACEHOLDER VARIABLE SLOT
以一行清楚标注的形式，展示我每次粘贴变化输入的唯一槽位，并用一句话描述其中应放什么。

3) WORKED EXAMPLE
在我提供的真实过往输入上运行一次该指令块。展示：
- 一行简短标签：'FICTIONAL-EXAMPLE-STYLE WALKTHROUGH — NOT A LIVE RUN.'
- 所使用的原始输入，引用自我提供的内容；如果太长，则用最小化版本。
- 该指令块产出的输出，完整呈现，并遵循你自己的格式规则。
这是一个展示结果形态的示例推演，不是任何内容实际运行过的证据。

4) SELF-CHECK AGAINST MY MATERIALS
检查这个示例推演并报告：
- 哪些部分直接由我提供的内容支持。
- 哪些部分是空缺、假设，或我从未提供但听起来合理的添加。将每一项列为 SPECULATIVE，并删除它或标注它。
- 指令块自身规则与我的质量要求冲突的任何地方，或两项要求无法同时满足的任何地方。说明冲突，而不是悄悄选择一边。
- 示例推演擦边的任何硬边界。

5) REUSE CHECK
用一个列表说明，未来运行在我信任输出之前必须验证什么：输入完整性、格式合规、无根据的声称、边界合规，以及我坚持的任何任务特定事项。让每项检查都短到可以实际执行。

6) 在我复用此内容之前需要修复什么
基于你发现的缺口与冲突，给出至多三处对指令块的具体修改，这些修改最能减少返工。如果没有什么值得修改的，就直说，而不是凭空编造改进点。

你整个回答的规则：
- 不要添加我的输入中不存在的事实、截止日期、名称、数字、政策或来源。
- 不要把我的硬性边界重述为可选项。
- 不要使用暗示你访问、更改、发送或存储了任何内容的措辞。
- 让指令块足够紧凑，以便一次性粘贴进聊天窗口。
- 如果我过往的运行结果薄弱或不完整，就指出薄弱之处，并把指令块写得仍能产出一份可用的草稿，标明薄弱点，而不是掩盖它们。

标注为虚构的迷你示例（仅示范风格，非真实数据）：输入：重复性任务 = ‘客户通话记录的每周摘要’；常量 = 平实的语气、最多三条要点、不出现客户姓名；变量 = 本周的原始记录；过往运行 = 带有两个行动项的杂乱记录；边界 = 绝不编造截止日期。预期输出形态：一个指令块、一个‘此处粘贴’槽位、一段带两条要点并标出一个缺失截止日期的走查摘要、一个针对任何凭空捏造负责人的推测性列表，以及一份简短复用清单。通过/失败检查：如果指令块声称它能发送或归档任何内容，则失败；如果走查摘要编造了记录中不存在的截止日期或负责人，则失败；如果常量被丢弃，则失败；仅当缺口被标注，且每项检查都能与所提供输入对应时，才通过。

## 参考资料与复用

- [Let skills in Gemini tackle your most repetitive tasks](https://blog.google/products-and-platforms/products/gemini/automate-tasks-with-skills/) · Wed, 30 Sep 2026 16:00:00 +0000

TokRepo 原创提示词 · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)。参考资料保留各自原有权利。

---
Source: https://tokrepo.com/en/workflows/turn-one-task-into-reusable-ai-prompt-1f3a998e
Author: Prompt Lab