每周粘贴同一段 prompt，就是 Skill 该出场的信号。这一章给你一份完整的 SKILL.md，从头写到尾、可以直接抄走：一个替你审周报的技能。写完再让内置 xlsx 交出一份真 Excel —— 你早就有这个能力，只是从没让它交文件。If you paste the same prompt every week, that's the signal a Skill should take over. This chapter hands you a complete SKILL.md, written end to end and ready to copy: a skill that reviews your weekly report. Then let the built-in xlsx skill hand back a real spreadsheet — you've had that all along and never asked for the file.
每周粘贴同一段 prompt —— 同样的开场、同样的格式要求、同样的「记得加上这几条」—— 就是一个 Skill 该出场的信号。Pasting the same prompt every week — the same opener, the same format demands, the same 'remember to include these' — is the signal a Skill should take over.上一章你把「这件事的背景」钉进了 Project。这一章搬走剩下那部分：「这类事怎么做」。写完之后，你不用再想起要交代什么 —— 一句话触发，它自己知道步骤、格式和验收标准。Last chapter you pinned 'the background of this thing' into a Project. This chapter moves out what's left: 'how this kind of thing is done.' Once it's written, you stop having to remember what to spell out — one sentence triggers it, and it already knows the steps, the format, and the bar.
— I
Skill 是按需加载的方法A Skill Is Method, Loaded on Demand.
Project 钉的是上下文，Skill 钉的是方法。Projects pin context; Skills pin method.一个 Skill 是个文件夹：一份用 Markdown 写的说明（这类事怎么做）、可选的脚本、可选的参考资源。2注 2Note 2Anthropic Engineering · Equipping agents for the real world with Agent Skills —— Skill 是指令、脚本与资源的文件夹，靠渐进式披露按需加载，只在用得上时才读进上下文；写好一个 Skill 的关键是把示例当指令用，并把 name 与 description 写清「做什么 + 什么时候用」。Anthropic Engineering · Equipping agents for the real world with Agent Skills — a Skill is a folder of instructions, scripts, and resources, loaded on demand via progressive disclosure and read into context only when relevant; writing a good one comes down to treating examples as instructions and writing the name and description to say what it does and when to use it.关键在「按需加载」：Claude 先扫一眼每个 Skill 的简介，判断这次用不用得上，只把相关那份读进来 —— 所以你可以攒几十个 Skill，而不会把上下文撑爆。2注 2Note 2Anthropic Engineering · Equipping agents for the real world with Agent Skills —— Skill 是指令、脚本与资源的文件夹，靠渐进式披露按需加载，只在用得上时才读进上下文；写好一个 Skill 的关键是把示例当指令用，并把 name 与 description 写清「做什么 + 什么时候用」。Anthropic Engineering · Equipping agents for the real world with Agent Skills — a Skill is a folder of instructions, scripts, and resources, loaded on demand via progressive disclosure and read into context only when relevant; writing a good one comes down to treating examples as instructions and writing the name and description to say what it does and when to use it.A Skill is a folder: an instruction written in Markdown (how this kind of thing is done), optional scripts, optional reference resources.2注 2Note 2Anthropic Engineering · Equipping agents for the real world with Agent Skills —— Skill 是指令、脚本与资源的文件夹，靠渐进式披露按需加载，只在用得上时才读进上下文；写好一个 Skill 的关键是把示例当指令用，并把 name 与 description 写清「做什么 + 什么时候用」。Anthropic Engineering · Equipping agents for the real world with Agent Skills — a Skill is a folder of instructions, scripts, and resources, loaded on demand via progressive disclosure and read into context only when relevant; writing a good one comes down to treating examples as instructions and writing the name and description to say what it does and when to use it. The point is on-demand loading: Claude scans each Skill's blurb, decides whether it's relevant this time, and reads in only the one that is — so you can stockpile dozens without blowing up the context.2注 2Note 2Anthropic Engineering · Equipping agents for the real world with Agent Skills —— Skill 是指令、脚本与资源的文件夹，靠渐进式披露按需加载，只在用得上时才读进上下文；写好一个 Skill 的关键是把示例当指令用，并把 name 与 description 写清「做什么 + 什么时候用」。Anthropic Engineering · Equipping agents for the real world with Agent Skills — a Skill is a folder of instructions, scripts, and resources, loaded on demand via progressive disclosure and read into context only when relevant; writing a good one comes down to treating examples as instructions and writing the name and description to say what it does and when to use it.一共四类，先认清你在跟哪一类打交道：Anthropic 内置的（Excel / Word / PowerPoint / PDF，相关任务自动触发）、你自建的（这一章要写的）、组织下发的（Team / Enterprise 的管理者推给全组织）、以及合作方技能（Notion、Figma、Atlassian 这些，从技能目录里装）。全档开放，连 Free 都有；运行需要 code execution 是打开的。1注 1Note 1Claude 帮助中心 · 什么是 Skills —— Skill 是 Claude 按需加载的指令/脚本/资源文件夹；对 Free / Pro / Max / Team / Enterprise 全档开放，另有 Claude Code beta 与开启了 code execution 的 API 用户；运行需要 code execution 打开。共四类：Anthropic 内置（Excel / Word / PowerPoint / PDF）、自建、组织下发、以及来自技能目录的合作方技能（Notion、Figma、Atlassian 等）。用 Markdown 写说明即可创建，简单的无需写代码。截至 2026-08。Claude Help Center · What are skills — a Skill is a folder of instructions, scripts, and resources Claude loads dynamically; available on Free / Pro / Max / Team / Enterprise, plus the Claude Code beta and API users with code execution enabled; it requires code execution to be turned on. Four types: Anthropic built-ins (Excel / Word / PowerPoint / PDF), custom, organization-provisioned, and partner skills from the Skills Directory (Notion, Figma, Atlassian, and others). Create one by writing Markdown; simple skills need no code. As of 2026-08.There are four kinds — know which one you're dealing with: Anthropic built-ins (Excel / Word / PowerPoint / PDF, auto-invoked on relevant tasks), ones you build (what this chapter writes), organization-provisioned (pushed org-wide by a Team / Enterprise owner), and partner skills (Notion, Figma, Atlassian and others, installed from the Skills Directory). Available on every plan, Free included; running them requires code execution to be on.1注 1Note 1Claude 帮助中心 · 什么是 Skills —— Skill 是 Claude 按需加载的指令/脚本/资源文件夹；对 Free / Pro / Max / Team / Enterprise 全档开放，另有 Claude Code beta 与开启了 code execution 的 API 用户；运行需要 code execution 打开。共四类：Anthropic 内置（Excel / Word / PowerPoint / PDF）、自建、组织下发、以及来自技能目录的合作方技能（Notion、Figma、Atlassian 等）。用 Markdown 写说明即可创建，简单的无需写代码。截至 2026-08。Claude Help Center · What are skills — a Skill is a folder of instructions, scripts, and resources Claude loads dynamically; available on Free / Pro / Max / Team / Enterprise, plus the Claude Code beta and API users with code execution enabled; it requires code execution to be turned on. Four types: Anthropic built-ins (Excel / Word / PowerPoint / PDF), custom, organization-provisioned, and partner skills from the Skills Directory (Notion, Figma, Atlassian, and others). Create one by writing Markdown; simple skills need no code. As of 2026-08.在哪管：账号设置里的技能一栏开关，或从输入框的 + 菜单浏览技能目录。先装你真用得上的两三个，别把目录里的全开了 —— Skill 太多，触发判断也会变迟钝。Where to manage them: the Skills section in your account settings, or browse the directory from the + menu in the input box. Install the two or three you'll actually use, not the whole directory — too many Skills and the matching itself gets sluggish.
— II
动手：写完一个 SKILL.mdDo It: Write a SKILL.md End to End.
做自己的 Skill 不用写代码 —— 用 Markdown 写一份说明就是一个 Skill。Building your own takes no code — write an instruction in Markdown and that's a Skill.官方就两条要诀。一，示例即指令：与其用形容词描述你想要什么，不如塞一两个「长这样」的成品例子进去 —— 它照着样例学，比照着描述读准得多。2注 2Note 2Anthropic Engineering · Equipping agents for the real world with Agent Skills —— Skill 是指令、脚本与资源的文件夹，靠渐进式披露按需加载，只在用得上时才读进上下文；写好一个 Skill 的关键是把示例当指令用，并把 name 与 description 写清「做什么 + 什么时候用」。Anthropic Engineering · Equipping agents for the real world with Agent Skills — a Skill is a folder of instructions, scripts, and resources, loaded on demand via progressive disclosure and read into context only when relevant; writing a good one comes down to treating examples as instructions and writing the name and description to say what it does and when to use it.二，把 name 和 description 写清「做什么 + 什么时候用」（用第三人称），因为 Claude 就靠这两行判断这次该不该触发它。2注 2Note 2Anthropic Engineering · Equipping agents for the real world with Agent Skills —— Skill 是指令、脚本与资源的文件夹，靠渐进式披露按需加载，只在用得上时才读进上下文；写好一个 Skill 的关键是把示例当指令用，并把 name 与 description 写清「做什么 + 什么时候用」。Anthropic Engineering · Equipping agents for the real world with Agent Skills — a Skill is a folder of instructions, scripts, and resources, loaded on demand via progressive disclosure and read into context only when relevant; writing a good one comes down to treating examples as instructions and writing the name and description to say what it does and when to use it.第二条被低估得最厉害：大部分「我写的 Skill 没生效」，是 description 写坏了，不是正文写坏了。Two official rules. One, examples are instructions: instead of describing what you want with adjectives, drop in one or two 'looks like this' finished samples — it learns far more reliably from a sample than from a description.2注 2Note 2Anthropic Engineering · Equipping agents for the real world with Agent Skills —— Skill 是指令、脚本与资源的文件夹，靠渐进式披露按需加载，只在用得上时才读进上下文；写好一个 Skill 的关键是把示例当指令用，并把 name 与 description 写清「做什么 + 什么时候用」。Anthropic Engineering · Equipping agents for the real world with Agent Skills — a Skill is a folder of instructions, scripts, and resources, loaded on demand via progressive disclosure and read into context only when relevant; writing a good one comes down to treating examples as instructions and writing the name and description to say what it does and when to use it. Two, write name and description to say what it does and when to use it (third person), because those two lines are what Claude reads to decide whether to trigger it at all.2注 2Note 2Anthropic Engineering · Equipping agents for the real world with Agent Skills —— Skill 是指令、脚本与资源的文件夹，靠渐进式披露按需加载，只在用得上时才读进上下文；写好一个 Skill 的关键是把示例当指令用，并把 name 与 description 写清「做什么 + 什么时候用」。Anthropic Engineering · Equipping agents for the real world with Agent Skills — a Skill is a folder of instructions, scripts, and resources, loaded on demand via progressive disclosure and read into context only when relevant; writing a good one comes down to treating examples as instructions and writing the name and description to say what it does and when to use it. The second is badly underrated: most 'my Skill never fires' is a broken description, not a broken body.下面这份是完整的、可以直接抄走的一个 Skill —— 一个替你审周报的技能。它不做花活，只做一件你每周都要做的事：Below is one complete Skill, ready to copy as-is — a skill that reviews your weekly report. It does nothing clever; it does one thing you do every week:
SKILL.md
---name: review-weekly-reportdescription: Reviews a draft weekly work report before the user sends it, checking for vague claims, missing numbers, and buried blockers. Use when the user shares a weekly update, status report, or standup summary and asks for a check, a review, or feedback before sending.---# Review a weekly reportYou are reviewing a draft, not rewriting it. The user is about to sendthis to their manager or their team.## Steps1. Sort every line into one of three buckets: Progress, Blocker, Next. A line that fits none of the three is filler — say so.2. For each Progress line, check it carries a number or a verifiable fact. "Improved onboarding" is not a claim; "onboarding drop-off 28% -> 19%" is.3. Find the blockers. Blockers hidden inside a Progress sentence are the single most common defect — pull them out and list them separately.4. Check the Next section is committed, not aspirational. "Look into X" is aspirational; "ship X behind a flag by Thursday" is committed.## OutputReturn exactly two things, in this order:1. A short list of specific problems, each quoting the offending line.2. The rewritten report.Do not add praise. Do not add a summary of what you did.## Like this<example>Draft line: "Made good progress on the search redesign, though we hitsome issues with the index."Problem: two defects in one line — an unmeasured claim, and a blockerburied inside a progress sentence.Rewrite:- Progress: search redesign 70% done; first-paint latency 1.2s -> 0.4s.- Blocker: index rebuild fails on records older than 2024; blocked since Tuesday, need a decision on backfill vs drop.</example>## When not to use thisIf the user asks you to *write* the report rather than review a draft,this skill does not apply. Say so and write it normally.
全文照抄即可。四段结构：frontmatter 决定它什么时候触发，步骤决定它怎么做，示例决定它做成什么样，最后一段决定它什么时候该闭嘴。Copy it verbatim. Four parts: the frontmatter decides when it fires, the steps decide how it works, the example decides what the output looks like, and the last section decides when it should shut up.
01
挑那段你粘到第三遍的 promptPick the prompt you've pasted a third time
翻历史，找出你至少每周粘一次、结构基本不变的那段。粘第三遍是分界线：一次两次是巧合，第三次是流程。Scroll back and find the one you paste at least weekly whose structure barely changes. The third paste is the line: once or twice is coincidence, the third time is a process.
02
先写 description，写「什么时候用」而不是「这是什么」Write the description first — 'when to use it', not 'what it is'
照上面那份的写法：一句话说它做什么，然后「Use when 用户……」列出触发场景，用你真会说的那些话（「帮我看看这份周报」「发之前给点意见」）。这一步花的十分钟，回报比正文高。Follow the shape above: one line on what it does, then 'Use when the user…' listing the triggers in the words you'd actually type ('take a look at this weekly update', 'any feedback before I send'). The ten minutes here return more than the body does.
03
正文写步骤，不写原则Write steps in the body, not principles
「保持专业」是原则，没用；「每条进展必须带一个数字或可核实的事实」是步骤，有用。原则它已经会了，步骤它不知道 —— 你的 Skill 的全部价值就在步骤里。'Be professional' is a principle and does nothing; 'every progress line must carry a number or a verifiable fact' is a step and does everything. It already has the principles; it doesn't have your steps — and your steps are the entire value of your Skill.
04
塞一个真例子，用你自己的烂句子Drop in a real example — use your own bad sentence
从你上一份周报里挑一句真的写得含糊的，连同你会怎么改，一起写进 example。虚构的例子会教出虚构的标准。Take one genuinely vague line from your last report, along with how you'd fix it, into the example. Invented examples teach invented standards.
05
装上，然后用一句自然话试触发Install it, then trigger it with one natural sentence
别说「用 review-weekly-report 技能」—— 那是作弊。就说你平时会说的那句。它没触发，回去改 description 的「Use when」，不要改正文。Don't say 'use the review-weekly-report skill' — that's cheating. Say what you'd normally say. If it doesn't fire, go fix the 'Use when' line in the description, not the body.
— III
动手：让内置技能交一份真文件Do It: Make a Built-in Skill Hand Over a Real File.
你要的常常不是一段文字表格，是一份真的 Excel。What you want is often not a text table but a real spreadsheet.Claude 内置了四个文档技能：Excel、Word、PowerPoint、PDF，相关任务会自动触发。4注 4Note 4Claude 帮助中心 · 什么是 Skills —— Anthropic 内置的文档技能覆盖 Excel、Word、PowerPoint 与 PDF，相关任务会自动触发，直接交出文件。截至 2026-08。Claude Help Center · What are skills — Anthropic's built-in document skills cover Excel, Word, PowerPoint, and PDF, are auto-invoked on relevant tasks, and hand back the file itself. As of 2026-08.让它做一份带公式的 Excel、一套 PPT、一份排好版的 Word，它直接给你文件，而不是一段你还得自己誊进表格的文本。这是网页用户最容易忽略、却最省事的一类能力 —— 你早就有这个技能，只是从没让它交文件。Claude ships four document skills: Excel, Word, PowerPoint, PDF, auto-invoked on relevant tasks.4注 4Note 4Claude 帮助中心 · 什么是 Skills —— Anthropic 内置的文档技能覆盖 Excel、Word、PowerPoint 与 PDF，相关任务会自动触发，直接交出文件。截至 2026-08。Claude Help Center · What are skills — Anthropic's built-in document skills cover Excel, Word, PowerPoint, and PDF, are auto-invoked on relevant tasks, and hand back the file itself. As of 2026-08. Ask for a spreadsheet with working formulas, a slide deck, a formatted Word doc, and it hands you the file — not text you'd have to transcribe into a table yourself. It's the capability web users most overlook and that saves the most: you've had this all along and never asked for the file.
提示词Prompt让它交一份能算的 ExcelAsk for a spreadsheet that computes
把下面这些数据做成一个 .xlsx 文件给我下载，不要在回答里画表格。
数据：<把你的原始数据贴这里，乱一点没关系>
结构：第一个 sheet 是明细，第二个 sheet 是按<某个维度>的汇总。
合计和占比用真的公式算（SUM / SUMIF 之类），别把结果硬写成数字 —— 我改一行明细，汇总要跟着变。
表头加粗冻结首行；金额列保留两位小数。
做完告诉我你用了哪些公式，我要抽查一格。Turn the data below into an .xlsx file for me to download. Don't draw a table in your reply.
Data: <paste your raw data here; messy is fine>
Structure: sheet one is the line items, sheet two is a summary by <some dimension>.
Compute totals and percentages with real formulas (SUM / SUMIF and friends) — don't hard-code the results. If I edit one line item, the summary must follow.
Bold the header and freeze the top row; money columns to two decimals.
When you're done, tell me which formulas you used — I want to spot-check one cell.
把下面这些数据做成一个 .xlsx 文件给我下载，不要在回答里画表格。
数据：（粘贴的 60 行报销明细，含日期、供应商、类别、金额、是否含税）
结构：第一个 sheet 是明细，第二个 sheet 是按供应商的汇总。
合计和占比用真的公式算（SUM / SUMIF 之类），别把结果硬写成数字 —— 我改一行明细，汇总要跟着变。
表头加粗冻结首行；金额列保留两位小数。
做完告诉我你用了哪些公式，我要抽查一格。Turn the data below into an .xlsx file for me to download. Don't draw a table in your reply.
Data: (60 pasted expense lines with date, vendor, category, amount, tax-inclusive flag)
Structure: sheet one is the line items, sheet two is a summary by vendor.
Compute totals and percentages with real formulas (SUM / SUMIF and friends) — don't hard-code the results. If I edit one line item, the summary must follow.
Bold the header and freeze the top row; money columns to two decimals.
When you're done, tell me which formulas you used — I want to spot-check one cell.
最后那句「我要抽查一格」不是客套 —— 打开文件，点一下汇总里的某个合计，看编辑栏里是公式还是一个死数字。是死数字的，回去说一句「用公式重做」。这一次抽查，会决定你以后信不信它交的表。That last line — 'I want to spot-check one cell' — isn't politeness. Open the file, click a total in the summary sheet, and look at the formula bar: a formula, or a dead number? If it's dead, send back one line: 'redo it with formulas.' That single spot-check decides whether you'll trust its spreadsheets from now on.
— IV
换个域，写哪个 SkillWhich Skill to Write, by Field.
写一个「出题官」：给它一段你刚学完的材料，它按固定难度梯度出五道题（两道回忆、两道应用、一道反例），并且不给答案，等你答完再批。description 的触发场景写成「用户贴了一段学习材料并说想自测 / 检验掌握程度」。这个 Skill 的价值全在「不给答案」那一句 —— 没有它，它每次都会好心地把答案一起给你。Write an examiner: give it material you just finished and it produces five questions on a fixed difficulty gradient (two recall, two application, one counterexample), withholding the answers until you've attempted them. Write the trigger as 'the user pasted study material and wants to self-test or check their grasp.' The entire value of this Skill is the 'withhold the answers' line — without it, it will helpfully hand you the answers every time.
写一个「引用体检」：给它一段带引用的草稿，它逐条检查每个引述是否真的支持它挂着的那句话、日期够不够新、有没有把二手转述当一手源。输出固定成一张三列表（结论 / 引用 / 判定：支持 / 部分支持 / 不支持）。这个 Skill 和第 9 章的核对清单是同一件事的两种形态 —— 那边是手动过一遍，这边是把它固化。Write a citation health check: give it a draft with citations and it goes claim by claim, checking whether each source actually supports the sentence it's attached to, whether the date is recent enough, and whether a secondary retelling has been passed off as a primary source. Fix the output as a three-column table (claim / citation / verdict: supports / partly / doesn't). This Skill and Chapter 9's checklist are the same thing in two forms — there you run it by hand, here you pin it.
写一个「改稿」：把口语化草稿改成能发出去的文案。步骤写死三条（删客套与重复、被动改主动、长句拆短），example 里放一组你真的改过的前后对照。这一类最适合固化，因为标准最稳定 —— 你的品牌词表半年不会变，而你每周都要改三五段稿。Write a polisher: turn a chatty draft into publishable copy. Fix three steps (cut pleasantries and repetition, passive to active, split long sentences), and put one genuine before/after pair of your own in the example. This field suits pinning best because the bar is the most stable — your brand word list won't change in six months, and you polish three to five drafts every week.
本章给的那个「审周报」就是这一栏的样板。变体：一个「会议纪要转待办」的 Skill（每条待办必须有负责人和日期，没有的标出来问），或一个「复盘体检」（检查每条结论是否指向一个可改的动作，而不是一句感慨）。这一类 Skill 的共同价值：它替你做那件你最不想做的事 —— 挑同事写的东西的毛病。The weekly-report reviewer in this chapter is this field's template. Variants: a 'meeting notes to action items' Skill (every item must carry an owner and a date; flag the ones that don't and ask), or a retro health check (does each conclusion point at a changeable action, or is it a sigh?). What these share: the Skill does the thing you least want to do — find fault with what a colleague wrote.
四个能直接落成 SKILL.md 的候选。共同点：都是「审查 / 转换」类，不是「创作」类 —— 有明确验收标准的流程才值得固化，创作类固化了只会把你的风格冻在今天。Four candidates that drop straight into a SKILL.md. What they share: all are review-or-transform, none are create — only a process with a clear bar is worth pinning, and pinning a creative one just freezes your voice at today's version.
— V
边界：什么不该做成 SkillBoundaries: What Shouldn't Become a Skill.
一段重复的活值不值得做成 Skill，过一遍这五问 —— 三个「是」就动手：Whether a repeated task is worth turning into a Skill — run these five; three 'yes'es and do it:
这段流程你每周都要用一次以上。You use this process more than once a week.
步骤基本固定，不会每次大改。The steps are basically fixed, not reworked each time.
有明确的产出，和「做对了」长什么样。There's a clear output, and a sense of what 'done right' looks like.
你能塞进一两个「长这样」的成品例子。You can drop in one or two 'looks like this' finished samples.
它是「这类事怎么做」，不是「这件事的背景」—— 后者该进 Project。It's 'how this kind of thing is done,' not 'the background of this one thing' — that belongs in a Project.
还在频繁改的流程A process still changing often
别急着固化，否则你维护 Skill 的时间比省下的还多。等它连着三周没变，再写。Don't pin it yet or you'll spend more maintaining the Skill than it saves. Wait until it hasn't changed for three straight weeks.
创作类Creative work
「写一篇有洞见的文章」做不成 Skill —— 没有验收标准的流程，固化下来只是把今天的你冻住。审查类、转换类才是甜区。'Write an insightful essay' doesn't make a Skill — a process with no acceptance test, pinned, just freezes today's version of you. Review and transform are the sweet spot.
装太多Installing too many
Skill 太多，触发判断会变迟钝 —— 它每次都要扫一遍所有简介。先只留你真在用的两三个，用顺了再加。Too many and the matching gets sluggish — it scans every blurb each time. Keep only the two or three you actually use, and add more once those are smooth.
description 写成「这是什么」A description that says 'what it is'
最常见的失败。「一个专业的周报助手」永远不会被触发；「当用户分享周报草稿并要求 review 时用」才会。触发靠的是场景，不是名头。The most common failure. 'A professional weekly-report assistant' never fires; 'use when the user shares a draft weekly report and asks for a review' does. Triggering runs on scenarios, not on titles.
— VI
收束 · 本章验收Sign-off.
写完了一份 SKILL.md，含 frontmatter、步骤、输出格式、一个真例子。Finished one SKILL.md with frontmatter, steps, an output format, and one real example.
description 里的「什么时候用」用的是你真会打出来的话，不是产品名词。The 'when to use' line is written in words you'd actually type, not product nouns.
在新对话里用一句自然话触发成功了（没有报技能名）。Triggered it successfully in a fresh chat with one natural sentence, without naming the skill.
拿到了一个 .xlsx 文件，并且抽查了一格 —— 编辑栏里是公式，不是死数字。Got an .xlsx file back and spot-checked one cell — the formula bar shows a formula, not a dead number.
确认了这个 Skill 是「这类事怎么做」，没有把 Project 该管的背景写进去。Confirmed the Skill holds 'how this kind of thing is done' and hasn't absorbed background that belongs in the Project.
到这里，你有了三件资产：一段全局指令、一个 Project、一个 Skill。它们都在替你省「说明」的功夫。下一章换个方向 —— 省「搬运」的功夫。Three assets so far: a global instruction, a Project, a Skill. All three save you the work of explaining. The next chapter switches direction — it saves you the work of fetching.
粘第三遍同一段 prompt，
就该把它变成 Skill.
Paste the same prompt a third time,
and it should become a Skill.
Aklman Library
— 讨论Discussion
讨论Discussion.
评论区初始化中…Initializing comments…
01 / 01
没有匹配结果No matches.
换个关键词，或按 Esc 回到页面Try another keyword, or press Esc to return
