Write your first reusable skill (no coding)
Goal: Ship a one-screen skill with a golden test and no hidden secrets before you share it.
Best for: Absolute beginners who want something useful before learning file formats.
One screen, one golden test, no secrets in the pack.
Why beginners skip this
Writing the first skill as a universal helper feels ambitious—boundaries scatter and teammates won’t use it. One job + fixture.
Step 1 — Fill this skeleton (keep it one screen)
Keep the skeleton to one screen; fill it with a scenario you will really use—no fake task titles.
Skill name: [short, verb-like]
When to use: [one sentence trigger]
Do not use when: [two bullets]
Steps the AI must follow:
1)
2)
3)
Output format:
Quality bar: [how I will reject a bad draft]
Examples: [one tiny input → output pair]
Step 2 — Worked example (meeting notes → decisions)
Example
Filled prompt
Skill name: Notes-to-decisions
When to use: User pastes raw meeting notes and asks for decisions.
Do not use when: Notes are empty; or user asks for legal advice.
Steps:
1) List decisions only if the notes say they were decided.
2) List open questions separately.
3) Mark unclear items as Unclear — do not invent owners.
Output format: ## Decisions / ## Open questions / ## Unclear
Quality bar: Any invented deadline = fail.
Example input: “Leave with a one-page skill draft you can paste”
Example output: Decisions: (none explicit). Open questions: new ship date? Unclear: whether Friday confirm is a decision.
What good output looks like
- Skill purpose is one job for “Write your first reusable skill” — not a company brain
- Done + golden example present and tested
- Never-send / never-delete honored
- Pass/fail: fail-case run once (skills-write-your-first-skill #1)
Step 3 — Put it to work today (clicks)
- Easiest path: open or create a Project → paste the skeleton into Instructions → attach one sample file → start a new chat inside the Project.
- Say: “Use the Notes-to-decisions rules on the text I paste next.”
- When your product supports Skills, copy the same text into a new skill — the content stays, only the container changes.
Step 4 — Run one live test
Run one live test in a Project; pass only with a done bar plus a filled example.
Here are raw notes:
[paste]
Follow Notes-to-decisions. If a decision is not explicit, put it under Unclear.
Pass only if you would forward the lists without rewriting the facts. Fail → tighten “Do not invent…” and retest.
Example
Filled prompt
Draft a first skill card for “customer apology email”.
Purpose: one-screen rules for delay apologies.
Done boxes: (1) names the delay cause only from my notes (2) offers one concrete next step (3) no refund promise unless I typed it (4) ends with draft-only—never send.
Never-do: invent root cause; invent compensation; CC people I did not name.
Filled example input: “Order #4821 delayed 4 days; warehouse backlog; offer 10% next-order code CODE-WAIT already approved.”
Example output shape: subject + 5-sentence body using only those facts + CODE-WAIT.
Draft only—no send.
What good output looks like
- Purpose fits one screen
- Done boxes are testable (esp. no invented refund)
- Never-do blocks silent send and invented cause
- Example uses Order #4821 + CODE-WAIT only—no extra coupons
Close the loop
Write one line: next time my first skill is a universal helper, I refuse share.
Example
Filled prompt
Draft skill card "notes-to-decisions": when/when-not, 3 steps, quality bar, golden example.
Run golden twice before share. No secrets in pack.
What good output looks like
- Done + golden example present and tested
- Never-send / never-delete honored
- Pass/fail: fail-case run once (skills-write-your-first-skill #2)
- Skill purpose is one job for “Write your first reusable skill” — not a company brain
Red flag
Sharing without a golden test; secrets in the skill body—strip and test privately first.
Save this card
Card: one-screen skeleton · one golden test · no hidden secrets. Run the test before anyone else sees it.
Before you start
Open the skill card (or blank one-pager). Purpose must be one job for “Leave with a one-page skill draft you can paste.” Golden example slot cannot stay empty. Guide: skills-write-your-first-skill. Keep the real job visible the whole time; a blank box means stop and fetch the artifact first.
How to use this week
This week write your first real skill: one job, three boundary lines, one fixture; no share until it passes.
Pitfalls
| Pitfall | Fix |
|---|---|
| Writing a novel skill on day one | One screen + one golden test |
| Skipping the test conversation | Run golden example twice |
| Hard-coding secrets into the skill | Placeholders only |
Example
Filled prompt
Temptation: skip the habit for skills-write-your-first-skill to save five minutes.
Job still: Leave with a one-page skill draft you can
Smallest correct pass: Done visible · checkable artifact · Unknowns [?].
Boundaries: draft only; no silent send; no invented metrics.
Return: artifact + refuse-line said aloud.
What good output looks like
- Names the shortcut refused (specific to skills-write-your-first-skill)
- Still delivers checkable output for “Write your first reusable skill”
- Unknowns labeled; draft-only
- Pass/fail: refuse-line dated (skills-write-your-first-skill #4)
Practice now
Hello refuse: first skill must refuse one unsafe ask in tests (Asia/Shanghai).
Tiny trigger: trigger phrase ≤6 words (Asia/Shanghai).
Stub-first drill: ship refuse + trigger only; add cleverness tomorrow (Asia/Shanghai).
First-skill drill: ship a stub skill with refuse-line before adding cleverness (Asia/Shanghai).
Thin-spot drill: rewrite the Save card with real nouns from your work (repo, doc, inbox). Generic placeholders fail the drill.
Tonight fill a one-screen skeleton from a real repeat job, attach one example, run it on a real task in a Project; do not share until the done standard passes.
One sentence takeaway
One job + three boundary lines + one fixture; no share until pass.
Next
写你的第一个可复用技能(不用写代码)
目标: 写出第一张能跑的 skill 卡:什么时候触发、不要用于什么、步骤、输出格式,以及一条能判失败的质量线。
适合: 想把「记录变决定」或「客户道歉邮件」收成可复用流程的人。
先写「不要用于」和「只出草稿」,再写步骤。质量线要硬到能判失败:比方说:任何编造的截止日期,都算失败。
为什么新手跳过
第一份 skill 写成万能助手像有野心;边界一散,队友不敢用。一件活 + 夹具。
步骤 1——填这张骨架(控制在一屏内)
骨架控制在一屏内;用你手头真实会用到的场景来填,别写假任务标题。
技能名:[短,最好像动词]
何时使用:[一句话触发条件]
不要用于:[两条]
AI 必须遵循的步骤:
1)
2)
3)
输出格式:
质量线:[怎样算不合格,我会打回]
例子:[一对很小的输入 → 输出]
步骤 2——完整例子(会议记录 → 决定)
实例
填好的提示词
技能名:记录变决定
何时使用:用户粘贴原始会议记录,并要求整理决定。
不要用于:记录是空的,或用户要法律意见。
步骤:
1) 只有记录里写明「已决定」的才进决定列表。
2) 未决问题单独列出。
3) 不清楚的标「不明确」:不要编造负责人。
输出格式:## 决定 / ## 未决问题 / ## 不明确
质量线:任何编造的截止日期 = 不合格。
示例输入:「发版日推迟了;Maya 周五确认。」
示例输出:决定:(无明确)。未决:新的发版日?不明确:周五确认算不算已决定。
像样的输出大概长这样
- 触发条件具体:粘贴原始会议记录并要求整理决定
- 写清不适用范围:空记录 / 要法律意见
- 质量线可检验:任何编造的截止日期都算失败
- 输出三级标题固定:决定 / 未决 / 不明确
- 像第一张能跑的 skill 卡
步骤 3——今天就用起来(怎么点)
最省事的路径:打开或新建 Project,把骨架贴进 Instructions,附一个样例文件,再在该 Project 里新开对话。
- 对模型说:「下一段文字请按「记录变决定」规则处理。」
- 等你的产品支持 Skills,把同一段文字拷进新技能:内容不变,只是容器变了。
步骤 4——做一次真实验收
在 Project 里跑一次真任务:有完成标准 + 填例才算过。
原始记录如下:
[粘贴]
按「记录变决定」执行。如果决定写得不明确,放进「不明确」。
只有当你愿意几乎不改事实就转发列表时,才算通过。失败 → 收紧「禁止编造…」再测。
实例
填好的提示词
请起草第一张 skill 卡「客户道歉邮件」:用途、完成标准(4 格)、绝不、一个填例。只出草稿:不发送。
骨架一屏内;填例具体到能金测试。
边界:不编造;未知标 [?];发送前停下。
像样的输出大概长这样
- 「客户道歉邮件」卡含:用途、完成 4 格、绝不、一个填例
- 明确只草稿、不发送
- 填例具体到能试跑
- 绝不列表挡住常见翻车
- 新手照着能写出第一版
- 金测试用真实客户草稿跑一遍才算过
- 未知标出;不编造负责人、日期或指标
闭环
写下一行:下次第一份 skill 写成万能助手,我拒绝分享。
红旗
第一份 skill 写成万能助手,边界一散,队友不敢用;一件活 + 夹具。
保存这张卡
记下:skill 名 + 版本号 + 红线夹具是否测过。标上日期。
开始前
信任该 skill 前,先确认已有完成标准 + 一个实例。
本周怎么用
本周写第一个真 skill:一件活、边界三行、夹具一条;不过关不分享。
常见坑
| 坑 | 改法 |
|---|---|
| 没有「不要用于」 | 空记录/要法律意见等写明 |
| 质量线不可检验 | 「任何编造截止日期=失败」 |
| 道歉邮件 skill 直接发送 | 只草稿,人来点发送 |
现在就练一次
今晚就练:写第一个真 skill:一件活、边界三行、夹具一条;不过关不分享。
一句话带走
一件活 + 边界三行 + 夹具一条;不过关不分享。
下一步
← Back to home · Learn · Tools · Compare · Start