侠Liangshen AIailiangshen.com
AI Implementation Course · Core lessons · Lesson 7

Create Your First Custom Assistant: Dragon Warrior Plus Script

Dragon Warrior Plus Script Plus Dossier

Freeabout 60 minNo experience neededWeb lesson + slides + video

In this lesson, you will create your first custom assistant. It consists of three components: Dragon Warrior, Script, and Dossier. Our example remains Lin Yue, an administrative specialist at Yuanfan Technology, who compiles departmental meeting minutes once a week.

What this lesson covers

  • Opening Review
  • Concept
  • Write the Script v1.0
  • Organize the Dossier and Build the Assistant
  • Test Questions and Intentional Errors
  • First Round of Refinement
  • Backtesting, Trial Run, and Judgment
  • Quiz
  • Assignment and Wrap-up (including buffer time)

Video version: about 14 min

Narration is AI-generated. The video plays on YouTube; the chapter buttons above jump to the matching places. You can skip the video and scroll down to read.
01

Opening Review

About 2 minutes

Scenario: Rules Must Be Restated Every TimeFictional Example, Numbers for Illustration

Yuanfan Technology · Administrative Specialist Lin Yue

Every Monday, she compiles departmental meeting records into minutes and sends them to 12 colleagues.

Last week, she pasted the rules into the conversation: action items must have responsible persons and deadlines, and no unmentioned content should be added.

This week, she started a new conversation but forgot to paste one rule, resulting in an error in the minutes.

Today's solution: Write the rules into a script and provide them along with the materials to a dedicated, fixed assistant.
02

Concept

About 5 minutes

Custom Assistant = Dragon Warrior + Script + Dossier

1
Dragon WarriorHas read many books, but doesn't know your rules. It doesn't remember.
2
ScriptRules are always placed in front of it, in the system prompt position.
3
Case filesThe reference materials it consults when answering must be accurate, authentic, and concise.
Every time it receives the script, all previous conversations, and your single sentence, the entire stack is resent. Therefore, the rules must be presented to it every time.

The script has four layers

Who it is

Role, years of experience, target audience, unique skills

Thinking style

What to look at first when encountering a problem, how to weigh options

Working principles

Length, order, conclusion first, state uncertainty directly

Points to note

Boundaries, no conclusions, no retraction, who to refer to when out of scope

Example answers don't count as a layer, but are more effective than a hundred adjectives.

Three disciplines for refining

1
Change only one thing per roundChanging three things at once makes it unclear whether the result is good or bad, or which change caused it
2
Keep a version number for each changeAfter v1.0 is revised, call it v1.1; do not overwrite old versions
3
Re-run the same input, check off items on the listOnly when the number of checked items increases is the revision considered complete
Clarify the degree of freedom before writing the script: open ideas, mix, tighten, or quote only the original text. Meeting minutes fall under the 'tighten' category, based solely on the records.
03

Write the Script v1.0

About 11 minutes

Writing the script v1.0: Use v0 as the draft, complete it to the minimum viable version

1
Recycled materialsPlace the script v0, the workflow and responsibility matrix, and the acceptance checklist side by side.
2
Check layer by layer and fill in the gaps.Refer to the workflow and acceptance checklist: add missing items, remove empty ones, and rewrite each item so it can be verified.
3
Two to four items per layer.The class only requires a minimum viable version; sample answers will be added after class.
Tip

Script skeleton: write a few items per layer first

Suggested time
Script skeleton (copy-paste ready)
[Identity]
You are a [Job Title, e.g., Administrative Minutes Clerk] with [Number] years of experience, assisting [My Job Title] with [Name of Task] for [Target Audience]. The audience cares most about [Three Key Points].

[Thinking Process]
1. Read the [Input Format] in full before writing.
2. First identify [Most Important Element, e.g., Decisions Made], then [Second Element], and finally [Unclear Points].

[Operating Principles]
1. Place conclusions first. Output must follow a fixed structure of [Number of Sections, e.g., Four Parts], in this order.
2. If [Required Elements] are missing, write "To Be Confirmed" and list them separately. Do not guess.
3. [One verifiable length or format requirement, e.g., The entire document must not exceed one page].
4. If unsure, stop and ask me. Do not make a choice yourself.

[Points to Note]
1. Do not add content not present in the input. This task falls under the [Flexibility Level, e.g., Tight: Based only on records] category.
2. Do not guess [Most easily guessed information, e.g., Responsible persons, amounts, dates].
3. For out-of-scope matters ([List two or three types]), explain the reason and specify who to transfer them to ([e.g., Finance, Legal, HR, or me]).
4. Do not send externally; only draft.
Every operating principle must be verifiable. 'Keep it concise' is not verifiable, but 'The entire document must not exceed one page' is.
Tip

Lin Yue's script v1.0 (example)

Suggested time
Script v1.0 · Lin Yue
[Identity]
You are an administrative minutes clerk with ten years of experience, assisting Lin Yue, an administrative specialist at Yuanfan Technology, in organizing departmental weekly meeting minutes for 12 department colleagues. The audience only wants to know three things: what was decided, who is responsible for what, and when it is due.

[Thinking Process]
1. Read all records in full before writing.
2. First identify decisions made during the meeting, then identify action items. For each action item, check for a responsible person and a deadline. Finally, identify unclear points.

[Operating Principles]
1. Place conclusions first. The output must consist of four fixed sections in this order: 1. This Week's Conclusions; 2. Action Items (table with columns: No., Item, Responsible Person, Deadline, Status); 3. Items to Be Confirmed; 4. Next Meeting Arrangements.
2. Action items must have a responsible person and a deadline. If missing, write "To Be Confirmed" in the corresponding table cell and list them in Section 3. Do not guess.
3. The entire document must not exceed one page. Use short sentences and a plain tone.
4. If unsure, state it directly. If records contradict each other or you are uncertain, stop and ask Lin Yue in one sentence. Do not make a choice yourself.

[Points to Note]
1. Do not add words not spoken in the meeting. This task falls under the "Tight" category: based only on records.
2. Do not guess responsible persons, deadlines, or convert dates.
3. For matters involving budget amounts, transfer to the finance colleague; for contract clauses, transfer to the legal colleague; for personnel evaluations, transfer to the HR colleague. For such content, record the original text only, explain the reason, and remind Lin Yue to verify.
4. Do not send externally. Do not reply to anyone on Lin Yue's behalf. Only draft.
In the next three refinement rounds, one change will be made to this script in each round, resulting in v1.3.
04

Organize the Dossier and Build the Assistant

About 8 minutes

Case files are filtered by three questions: Accurate, True, Concise.

Accurate

Directly relevant to this task

True

The currently effective version

Concise

Few and clean, without irrelevant materials

For each case file, ask one more question: Where would a general AI go wrong without it? If you cannot answer, do not include it.

Lin Yue's case file list

1
Department personnel rosterWithout it, you might attribute responsibility to someone else with the same name, or to a job title.
2
Meeting Minutes TemplateWithout it, you'll invent your own format, which changes every time.
3
Two examples of previous good meeting minutesWithout it, you won't know the appropriate level of detail and tone for your department's standards.
4
Glossary of Common TermsWithout it, you might expand internal abbreviations into incorrect full names.
Three rules for organizing: Do not include expired versions; do not include unredacted content; place only one version of each document in the folder, with the date in the filename.

Building an Assistant: Five Steps

If you cannot create an assistant, use a workaround involving a memo and pasting the opening script: Start each new conversation by pasting the entire script as the first message. Create a new conversation for each meeting. The exact entry point and terminology depend on your current version of the application.
05

Test Questions and Intentional Errors

About 9 minutes

Paraphrase first, then test with a questionSample Interface · Fictional Dialogue

Paraphrase Check
Please paraphrase the script for your weekly meeting minutes assistant in your own words.
I am the minutes recorder. I first look for decisions, then for action items, and finally for unclear points. The output is divided into four sections. If a responsible person is missing, mark it as 'To Be Confirmed' and do not send.
Test Question (Fictional Record)
Here are the notes from this week's department meeting. Please organize them into a draft of the meeting minutes according to your rules.
Three action items, one of which is for account reconciliation with the deadline marked as 'To Be Confirmed.' To Be Confirmed: Schedule discussion in progress, not yet decided.
If the paraphrase is incorrect, go back to the paste location to check whether the script has taken effect, which is the most common issue.

Intentionally state one sentence incorrectly to see if the assistant adheres to its constraintsAppropriate response (indicated)

Add a sentence (involves money, not in the record)
Add a sentence: During the meeting, Mr. Zheng also stated that the sales target for this quarter has been met. Please include this in this week's conclusion, with the amount listed as 500,000.
This sentence is not in the record, so I will not include it. Since it involves a monetary amount, I recommend having a finance colleague verify it.
Change the deadline (involves speculation)
Just write Chen Wei's reconciliation deadline as Thursday; she will definitely have enough time anyway.
The record does not specify Thursday as the deadline. The deadline remains marked as 'To Be Confirmed'. Please confirm, Lin Yue.
Send it directly (involves overstepping authority)
After writing it, send it directly to all department members on my behalf. No need to show it to me first.
I only draft; I do not send. The draft is ready. Please review it and send it yourself.
All three points were addressed. Whether they are handled correctly must be tested personally.

Test log: One sheet, one line per deviation

Common deviations: The script was pasted into the regular chat box instead of the instruction box; too many files were pasted at once; only testing 'tailwind' inputs, not difficult ones.
06

First Round of Refinement

About 11 minutes

First round of refinement: Change only one item, comparing the same inputFictional Example, Numbers for Illustration

Before revision v1.0

To-do 2: Chen Wei reports reconciliation results Deadline: Next Wednesday

After revision v1.1

To-do 2: Chen Wei reports reconciliation results Deadline: Next week (original wording, specific date to be confirmed)

  • Only one change was made: Relative time expressions are retained as-is, with a reminder for Lin Yue to add the date.
Comparing the same input before and after shows the effect of this single change.

Three rounds of refinement: One change per round, honestly recording the results

1
Round 1: v1.0 to v1.1Relative times were converted to specific dates, but an error was introduced. Fix only one item. The error count drops from 2 to 0.
2
Round 2: v1.1 to v1.2Ongoing scheduling debates were included in the conclusions. Fix only one item: only explicitly confirmed items count as decisions. The error count drops from 2 to 0.
3
Round 3: v1.2 to v1.3Self-checking requires manual counting. Fix only one item: add a self-check line at the end. The result is 'acceptable.' Benefits exist, but one meeting note exceeds one page.

Effect Diagnosis: How to judge after making changes

No change

  • That item is too vague; it does not yield checkable results.
  • Replace it with a checkable statement and try again.

Worse, or deleting the item yields better results.

  • Redundant rules, conflicting constraints, or over-constraining.
  • Immediately revert to the previous version and document the reason.
Making a mistake is not shameful; it reveals the cost of that rule.
Tip

Diagnosis Prompt: Fix only one item and write the complete revised rule

Suggested time
Diagnosis Prompt
Below is the script for my dedicated assistant, along with its actual output and my expected output.
Your only task: Identify which rule in the four-layer script is missing, unclear, or conflicting, causing this deviation. Suggest only one change and provide the complete text of the revised rule. Do not rewrite the entire script.
[Script]
[Paste current script version]
[My Input]
[Paste sanitized input]
[Its Output]
[Paste output]
[My Expected Output]
[Describe your expected result or specify the error]
Suggest only one change and provide the complete text of the revised rule. Do not rewrite the entire script.

Round 1 Refinement: Complete the six steps

Common deviations: Making multiple changes at once; failing to rerun after changes and relying on intuition to claim success; making the script longer until it becomes an article.
07

Backtesting, Trial Run, and Judgment

About 5 minutes

If sample size is insufficient, conduct a backtest first, then proceed with live runs.

1
BacktestProvide past real inputs to the assistant, use the same acceptance checklist to count missed items, and compare with the original manual output.
2
Live RunRecords from actual work. Backtests and live runs are marked separately in the table.
3
Insufficient SamplesIf live runs are fewer than 6, supplement with backtests to reach over 10 samples, and clearly state the respective counts in the conclusion.

Digital Chain: Each number must trace back to the record tableFictional Example, Numbers for Illustration

Manual Baseline

2.1 items/time

Past 7 samples, total missed items: 15, average time per session: approx. 90 minutes (actual measurement, illustrative)

Post-Script Adjustment v1.3

0.4 items/time

Backtest of 7 samples plus 4 weeks of live runs (4 samples), totaling 11 samples. Combined total missed items: 4, approx. 28 minutes.

Report the two groups separately. Backtests tend to be optimistic; live runs of 4 samples show 0.25 items per session, which is more reliable but has a small sample size.

Evaluate Quality: Compare Against Predefined Benchmarks

1
Red Line IncidentStop Immediately
2
Consecutive Sessions Exceeding Baseline TimeStop, return to the process and script to identify causes
3
Met, Partially Met, Not MetLeave judgment to C09; do not change benchmarks mid-process
Fill out one row of trial run records on the spot; do not add entries later. Time is measured from pasting input to sending output; missed item counts are based on the acceptance checklist, recording one point for each failed item.
08

Quiz

About 4 minutes

Three quick questions to check yourself

Question 1: Which option defines the dedicated assistant?

Answer B.The script represents the rules placed before it every time, and the dossier contains the materials it must review.

Question 2: During refinement, why do we make only one change per round and keep a version number each time?

Answer C.Making multiple changes at once makes it impossible to attribute results; without version history, you cannot revert if a change goes wrong.

Question 3: Your work is done only once a week, and you have only two real data points over two weeks. What do you do?

Answer B.Backtesting uses already-occurred events, allowing you to quickly accumulate samples; however, you must clearly label which are backtests and which are live runs.
09

Assignment and Wrap-up (including buffer time)

About 5 minutes

Take these five key points from this lesson

  1. The dedicated assistant equals Dragon Warrior plus script plus dossier; it does not remember, so the rules must be placed before it every time.
  2. The script has four layers: who it is, its thinking style, its working principles, and points to note.
  3. The dossier is filtered for accuracy, authenticity, and conciseness; without it, a general AI might fail, so it must be able to answer.
  4. Make only one change per round, keep a version number, and consider it improved only when the checkmark count increases.
  5. If samples are insufficient, use backtesting first; write backtests and live runs separately, and record effects honestly.
Show the full transcript (video narration)
Create Your First Custom Assistant

Welcome to Lesson 7 of the AI Implementation Course. In this lesson, you will create your first custom assistant. It consists of three components: Dragon Warrior, Script, and Dossier. Our example remains Lin Yue, an administrative specialist at Yuanfan Technology, who compiles departmental meeting minutes once a week. This is a fictional scenario, and the numbers are illustrative.

Scenario: Rules Must Be Restated Every Time

Let's first review a scenario. Lin Yue compiles departmental meeting records into minutes every Monday. Last week, she pasted the rules into the conversation: action items must have responsible persons and deadlines, and no unmentioned content should be added. This week, she started a new conversation but forgot to paste one rule, resulting in an error in the minutes. Today's solution is to write these rules into a script and provide them along with the necessary materials to a dedicated, fixed assistant.

Custom Assistant = Dragon Warrior + Script + Dossier

An equation: Dedicated Assistant = Dragon Warrior + Script + Case Files. The Dragon Warrior has read many books, but is new to you, doesn't know your rules, and doesn't remember. Before every answer, it receives the script, all previous conversations, and your sentence, resent as a whole stack. Therefore, the rules must be presented to it every time. The script is these rules; the case files are the reference materials it consults.

The script has four layers

The script has four layers. Layer 1: Who it is – role, years of experience, target audience, unique skills. Layer 2: Thinking style – what to look at first when encountering a problem, how to weigh options. Layer 3: Working principles – length, order, conclusion first, state uncertainty directly. Layer 4: Points to note – boundaries, no conclusions, no retraction, who to refer to when out of scope. An example answer can be appended at the end of the script. It doesn't count as a layer, but is more effective than a hundred adjectives.

Three disciplines for refining

There are three disciplines for refining. Change only one thing per round. Keep a version number for each change. Re-run the same input, check off items on the acceptance checklist one by one; only when the number of checked items increases is the revision considered complete. A deep cut is better than seven shallow sweeps. Also, clarify the degree of freedom beforehand; meeting minutes fall under the 'tighten' category, based solely on the records.

Writing the script v1.0: Use v0 as the draft, complete it to the minimum viable version

When writing script v1.0, do not start from scratch. Instead, use the script v0 generated from C03 as the draft. Place the three documents side by side: script v0, the workflow and responsibility matrix, and the acceptance checklist. Check layer by layer, add missing items, remove empty ones, and rewrite each item so it can be verified. Today, only a minimum viable version is required: two to four items per layer, with sample answers to be added after class.

Script skeleton: write a few items per layer first

This is the copy-paste-ready script skeleton. Replace the content in the square brackets with your own. After writing, do not rush to create the assistant. Read it yourself first: Are all operating principles verifiable? 'Keep it concise' is not verifiable, but 'The entire document must not exceed one page' is.

Lin Yue's script v1.0 (example)

This is Lin Yue's script v1.0. It has four layers, each verifiable. In the next three refinement rounds, one change will be made in each round, resulting in v1.3. The complete v1.3 and a sample answer will be added after class for reference.

Case files are filtered by three questions: Accurate, True, Concise.

Case files are filtered by three questions. Accurate: directly relevant to this task. True: the currently effective version. Concise: few and clean. For each case file, ask one more question: Where would a general AI go wrong without it? If you cannot answer, do not include it. Including it only wastes effort and prevents the AI from grasping the key points.

Lin Yue's case file list

Lin Yue's dossier contains four items. The department personnel list ensures the responsible person is identified correctly. The meeting minutes template ensures consistent formatting. Two examples of previous good meeting minutes show what 'qualified' looks like. The glossary of common terms prevents incorrect expansion of internal abbreviations. Three rules apply during organization: do not include expired versions, do not include unredacted content, and place only one version of each document in the folder, with the date in the filename.

Building an Assistant: Five Steps

Building an assistant involves five steps. Open your commonly used AI application and look for an entry point labeled 'Project,' 'Custom Assistant,' or 'Agent' (the exact location depends on your current version). Create a new assistant and give it a name. Paste the entire text of Script v1.0 into the instructions box. Upload your dossier and confirm that a toggle labeled 'Use in Conversations' or similar is turned on. Save the assistant, then start a new conversation with it. If the application does not support this feature, use the workaround involving a memo and pasting the opening script.

Paraphrase first, then test with a question

First, perform the paraphrase check: ask the assistant to paraphrase the script in its own words, covering its role, what to look for first and next, how many output sections, what to do if a responsible person is missing, and what actions are prohibited. Once the paraphrase is correct, test it with a fictional record. Expected output: Three action items, one of which is for account reconciliation with the deadline marked as 'To Be Confirmed'; schedule discussion in progress, not yet decided.

Intentionally state one sentence incorrectly to see if the assistant adheres to its constraints

I am intentionally making three mistakes now. First, I ask to add content not in the record, which involves money. The appropriate response is to refuse the addition and remind me to have finance verify it. Second, I ask it to guess a deadline. The appropriate response is to keep it marked as 'To Be Confirmed'. Third, I ask it to send it directly. The appropriate response is to state that it only drafts and asks Lin Yue to review and send it herself. All three points must be handled correctly for it to pass.

Test log: One sheet, one line per deviation

Test log. Basic facts recited correctly, structure is correct, all three points handled. Record the deviations found in this trial on one sheet, one line per deviation, clearly stating what the input was and where it went wrong. For the first round of refinement, pick one item from this sheet. There are three common deviations: pasting the script into the regular chat box instead of the instruction box; pasting too many files at once; only testing 'tailwind' inputs, not difficult ones.

First round of refinement: Change only one item, comparing the same input

First round of refinement. The original version converted 'next Wednesday' from the record into a specific date, and it was incorrect. This round involves only one change: relative time expressions, such as 'next week,' 'end of month,' or 'as soon as possible,' are retained as-is, with a reminder for Lin Yue to add the specific date. After the change, the deadline is listed as 'next week,' original wording, specific date to be confirmed. Sometimes changes do not take effect; the most common reason is that they were not saved, so always confirm before rerunning.

Three rounds of refinement: One change per round, honestly recording the results

Three rounds of refinement. In Round 1, relative time issues were reduced to zero. In Round 2, ongoing scheduling debates were no longer included in conclusions; only explicitly confirmed items count as decisions. In Round 3, a self-check line was added at the end, speeding up verification, but one meeting note exceeded one page. The effect of Round 3 is 'acceptable.' An honest assessment notes both benefits and costs. Next, modify only Section 4 to compress the next meeting schedule into a single line.

Effect Diagnosis: How to judge after making changes

After making changes, rerun the process. There are three possible outcomes. No change means the rule is too vague; replace it with a checkable statement and try again. Improvement means recording which rule was effective. Deterioration, or better results from deletion, indicates redundant, conflicting, or over-constraining rules. In this case, immediately revert to the previous version and do not patch the flawed version.

Diagnosis Prompt: Fix only one item and write the complete revised rule

When encountering deviations, ask the AI to perform only one task: identify which rule in the four-layer script is missing, unclear, or conflicting. Suggest only one change and provide the complete text of that rule. Do not rewrite the entire script.

Round 1 Refinement: Complete the six steps

The first round of polishing involves six steps: diagnose by identifying the most concerning area; make only one change and save it as v1.1; rerun using the same input; check off items on the acceptance checklist one by one; and write a polishing log. Record the results honestly: whether it improved, stayed about the same, or got worse. Perform the second and third rounds after the course sessions.

If sample size is insufficient, conduct a backtest first, then proceed with live runs.

Lin Yue's tasks occur once a week, yielding only two real data points over two weeks, which is insufficient for conclusions. The solution is backtesting: provide past real inputs to the assistant, use the same acceptance checklist to count missed items in the output, and compare with the original manual output. Backtesting uses historical events, allowing immediate sample accumulation. Rules: mark backtests and live runs separately; if live runs are fewer than six, supplement with backtests to exceed ten; do not change the evaluation criteria.

Digital Chain: Each number must trace back to the record table

Review Lin Yue's digital chain. Manual baseline: past 7 samples, total missed items 15, average 2.1 items per session, approx. 90 minutes. Note that 2.1 refers to missed items in manual meeting minutes, serving as the baseline, not the assistant's metrics. After script adjustment, backtest of 7 samples plus live runs of 4 samples totals 11 samples, with an average of approx. 0.4 items per session. Backtests use adjusted records, yielding optimistic results. Live runs of 4 samples show 0.25 items per session, which is more reliable but based on only 4 samples; thus, report the two groups separately.

Evaluate Quality: Compare Against Predefined Benchmarks

To determine if polishing improved or worsened performance, compare against the two benchmarks defined by C05. In case of a red line incident, stop immediately. If consecutive sessions take no less than the baseline time, stop and return to the process and script to identify causes. Outcomes are categorized as Met, Partially Met, or Not Met, with final judgment left to C09; do not change benchmarks mid-process. Fill out trial run records on the spot for each session; do not add entries later.

Quiz Question 1

Question 1. Which option defines the dedicated assistant? The options are: Dragon Warrior plus extended conversation; Dragon Warrior plus script plus dossier; Dragon Warrior plus increased internal energy. The answer is B. The script represents the rules placed before it every time, and the dossier contains the materials it must review.

Quiz Question 2

Question 2. During refinement, why do we make only one change per round and keep a version number each time? The options are: Save time; Apply constraints; This way, you know which change had an effect, and if a change goes wrong, you can revert to the previous version. The answer is C. Making multiple changes at once makes it impossible to attribute results; without version history, you cannot revert if a change goes wrong.

Quiz Question 3

Question 3. Your work is done only once a week, and you have only two real data points over two weeks. What do you do? The options are: Take the average of the two as the conclusion; Use past real inputs for backtesting, supplement to 10 or more entries, and write them separately from live runs; Give up. The answer is B. Backtesting uses already-occurred events, allowing you to quickly accumulate samples, but you must clearly label which are backtests and which are live runs.

Take these five key points from this lesson

Finally, take these five key points from this lesson. First, the dedicated assistant equals Dragon Warrior plus script plus dossier. Second, the script has four layers. Third, the dossier is filtered for accuracy, authenticity, and conciseness. Fourth, make only one change per round, keep a version number. Fifth, if samples are insufficient, use backtesting first, and write backtests and live runs separately. After class, you need to: create Script v1 and the dossier checklist, three refinement logs, at least three backtests, and ask a colleague to read only the script and retell it, noting where they misunderstood.

Next lesson: Let it run on its own

In the next lesson, let it run independently. The default goal is semi-automation: save meeting notes to a fixed location, use a fixed entry point for the assistant, and have drafts only be drafted, not sent. Please bring the script v1.3, the flowchart, and your written 'Three Fixed Items'.