Skill Go-To-Market技能出海工具箱
Five steps. Every pitfall marked. Turn your methodology into a SKILL.md pack and get it listed — with CN-friendly payout routes included.五步走。每一步的坑都标好。把你的方法论做成 SKILL.md 技能包并成功上架——内置大陆友好收款路径。
Safety安全性
- Read-only: analyzes your document, never runs generated code只读：分析你的文档，绝不运行生成的代码
- 0 risky commands, 0 secrets detected by default默认检测：0 危险命令、0 硬编码密钥
- Everything stays in plain markdown一切保持纯文本 markdown
From a methodology file to a sellable package.从一个方法论文件到一个可售安装包。
The skill reads your doc, generates a SKILL.md, and hands you a listing checklist.技能包读取你的文档、生成 SKILL.md，并给你一份上架清单。
Five steps. Every pitfall marked.五步走。每一步的坑都标好。
The exact order that works — and the mistakes that silently kill a listing if you skip them.经过验证的正确顺序——以及跳过就会悄悄毁掉上架的坑。
- 1
Package打包
Turn your methodology into a SKILL.md following the writing rules — imperative voice, dense, progressive disclosure.按写作规则把你的方法论转成 SKILL.md——命令式语气、高密度、渐进式披露。
Pitfall:坑： zip must contain a SKILL.md file — not a folder that hides it. Many marketplaces reject a zip without the file at root.zip 里必须直接含 SKILL.md 文件——不能是包了一层文件夹把它藏住。很多市场会拒绝根目录没有 SKILL.md 的 zip。 - 2
Push to GitHub引流 GitHub
Free traffic, social proof, and a place for the free version — buyers check your repo before they trust you.免费流量、社交证明、放免费版的去处——买家下单前都会先看你的仓库。
Pitfall:坑： A README that shows real output builds trust. Screenshots of made-up results destroy it instantly.README 里放真实输出能建立信任；放编造的截图会瞬间毁掉信任。 - 3
List on marketplaces上架市场
The listing checklist — name, description, tags, demo — so your pack ranks and converts.上架清单——名称、描述、标签、演示——让你的包能被搜到、能成交。
Pitfall:坑： Description must carry all three elements: what it does, when to use it, what you get. Vague copy ranks and converts worse.描述必须包含三要素：它做什么、什么时候用、你会得到什么。含糊文案在搜索和转化上都吃亏。 - 4
Get paid收款
Configure payouts — with CN-friendly routes so mainland developers aren't stuck at the Stripe dead-end.配置收款——含大陆友好通道，让大陆开发者不被 Stripe 卡死。
Pitfall:坑： Test a $1 transaction end-to-end before listing. A payout that fails after your first sale is a support nightmare.上架前先端到端跑通一笔 $1 测试单。第一单卖出后收款失败，就是售后噩梦。 - 5
Validate & iterate验证迭代
Watch installs and feedback, update the SKILL.md, push new versions. A living skill sells again.盯安装量和反馈，更新 SKILL.md，推新版本。活着的技能包才会持续卖。
Pitfall:坑： Keep time-sensitive claims out of SKILL.md — "as of 2026" ages badly and hurts credibility.SKILL.md 里别放时效性内容——"截至 2026" 会快速过期并伤害可信度。
SKILL.md writing rules that make a pack sell.让技能包卖得动的 SKILL.md 写作规则。
These aren't stylistic preferences — they're what separates a usable skill from a paperweight.这些不是风格偏好——它们是"能用"和"吃灰"的分界线。
Write in the imperative用命令式语气
Tell the agent what to do, don't describe what it could do.直接告诉智能体去做什么，而不是描述它"可以"做什么。
Stay dense保持高密度
Target under ~500 lines / ~5k tokens. Every line must earn its place.目标控制在 500 行以内 / 约 5k tokens。每一行都要有存在的价值。
Progressive disclosure渐进式披露
Start with the core trigger, open up detail as the task advances.先给核心触发条件，随任务推进再展开细节。
Description carries 3 elements描述含三要素
What it does, when to use it, what you get. This is what the agent reads to decide.它做什么、什么时候用、你会得到什么。智能体靠它判断何时调用。
Name it lowercase + hyphen命名用小写+连字符
One word or hyphenated, lowercase. This is the command the agent invokes.单词或连字符，小写。这就是智能体调用的命令名。
No time-sensitive claims不放时效性内容
SKILL.md lives for years. "As of 2026" ages badly and kills credibility.SKILL.md 要用好几年。"截至 2026" 会快速过时并毁掉可信度。
Three ways to package. One is usually right.三种打包形态。通常只有一种是对的。
SKILL.md only仅 SKILL.md
Best for a single, well-scoped workflow. Smallest surface, easiest to maintain.最适合单一、边界清晰的流程。面积最小、最好维护。
Most common最常见SKILL.md + scriptsSKILL.md + 脚本
When a step needs real automation — a search, a check, a transform. Keep scripts read-only.当某一步需要真正的自动化——搜索、检查、转换。保持脚本只读。
SKILL.md + dataSKILL.md + 数据
When the skill is better with a pre-measured reference — a density map, a checklist, a template.当技能包配上一份预测量参考会更好——密度图、清单、模板。
Before you buy.购买前想问的。
Does it write the SKILL.md for me?它会帮我写 SKILL.md 吗？
Yes. You give it your methodology doc, it generates a dense, imperative SKILL.md following the writing rules, then checks it for safety.会。你给它方法论文档，它按写作规则生成高密度、命令式的 SKILL.md，然后做安全扫描。
What does 'CN-friendly payout' mean?「大陆友好收款」指什么？
It walks you through payout routes that mainland developers can actually use, so you're not stuck at the Stripe dead-end.它带你配置大陆开发者真正用得上的收款路径，不让你卡在 Stripe 的死胡同。
Do I need to be technical?需要技术背景吗？
No. The skill handles the SKILL.md structure and packaging. You only provide your methodology and follow the checklist.不需要。技能包负责 SKILL.md 的结构和打包。你只需提供方法论并按清单操作。
Your methodology is already worth something. Ship it.你的方法论本来就值钱。把它卖出去。
Five steps from a doc to a listed, sellable skill — with every pitfall marked along the way.五步，从一份文档到一个已上架、可售卖的技能包——每一步的坑都已标好。