返回提示词目录第 1184 页

定制助手指令与配置编写

根据用途与受众编写可粘贴的助手指令,并配套知识文件规划、开场问题及测试用例。

完整提示词

<context>
Builder tools for custom assistants (custom GPTs, Gems, project assistants and similar) all take the same ingredients: an instructions field, optional knowledge files, conversation starters, and switches for capabilities such as web search, code or image generation. Most custom assistants disappoint for the same reasons: the instructions describe a personality instead of the jobs, nobody told it when to use the knowledge files versus general knowledge, the scope is so broad it is generic, and it was never tested with the questions real users ask. Anyone who can use the assistant may also be able to coax out its instructions and knowledge files, so nothing confidential belongs in them.

<purpose>
{{purpose}}
</purpose>
Audience: {{audience}}
</context>

<task>
1. If the purpose is too vague to define the main jobs, ask up to three questions and stop. Otherwise list your assumptions.
2. Write a setup summary: name suggestion, one-line description for the builder's description field, the two to four jobs it does, and what it deliberately does not do.
3. Write the instructions field:
   - Role and audience in two sentences, including what users typically know.
   - How to handle each main job: what to ask first if information is missing, the steps, and the format of a good answer.
   - Knowledge use: which questions to answer from the knowledge files, to quote or name the file it used, to say when the files do not cover something, and when general knowledge is acceptable.
   - Tone, length and formatting for this audience.
   - Boundaries: out-of-scope requests and what to do instead, with reasons; honesty that it is an AI and can be wrong; protecting personal data users paste.
   Keep it within about 6,000 characters so it fits common builder limits, and tell the user to check their tool's current limit.
4. Plan the knowledge files: which documents to include, the format and naming, what to remove first (personal data, confidential material, outdated versions), and one sentence per file on what it answers.
5. Write four conversation starters that show the main jobs.
6. List settings to check: capabilities to turn on or off for this purpose and who it is shared with, phrased generically because menus differ by tool.
7. Write eight test prompts: each main job, a question the files answer, a question they do not, an out-of-scope request, an attempt to extract the instructions, and a vague request.
</task>

<constraints>
- Never put secrets, passwords, API keys, client data or anything confidential in the instructions or knowledge files; say so explicitly in the output when the purpose suggests it.
- Do not invent facts about the user's organisation, course or products; use placeholders such as [RETURN POLICY].
- Do not claim exact menu names or limits for a specific builder as current fact.
- For an audience of children, keep the assistant within the platform's age rules and recommend adult supervision.
</constraints>

<output_format>
## Setup summary
## Instructions
One fenced block, ready to paste.
## Knowledge files
Table: File | Format and name | What it answers | Clean-up before upload.
## Conversation starters
## Settings to check
## Test prompts
Table: Prompt | What it tests | Good behaviour.
</output_format>

可替换内容

  • {{purpose}}
  • {{audience}}
  • [RETURN POLICY]

分类与标签

办公效率、定制助手、助手指令、知识库配置、测试用例

前往 AI 图片创作