一份 Readiness 结论——Ready to submit,或 Not ready 并点名缺失的资产与缺口
一份 Listing Kit:一套事实与长度合规的文案,各目录通用
每个已出现目录类型一条定位文案——Startup 讲结果、SaaS 讲替代、AI 目录讲 AI 优先,等等
一份提交顺序——先免费目录、再未知费用、最后付费——加一张跟踪表记录每条结果
所有缺口、输入错误与警告都在报告中点名
适合人群
产品已上线、准备投 startup、SaaS、AI、dev、agent 或 review 类目录
预算为零、清单很长时,决定先投哪一个
上线前检查缺什么——没有定价页或截图的 listing 会被拒收,而不是被排后
不适合
替你提交——Kit 只做提交计划,每条 listing 仍须手工提交
编造目录数据——它只用你列出的目录与费用;没写费用就保持 unknown
承诺收录——就绪只是清单计数,不是目录一定会收录的保证
示例输出
此 Skill 产出的示例。示例内容,仅供说明。
Directory Submission Kit — sample
Product: BeanLoop | Directories: 6 (Free 5 · Paid 1 · Unknown 0) | Readiness: 5/5 | Variants: 5 | Gaps: 0 | Errors: 0 | Warnings: 0
Ready to submit — every required asset is present and six directories are listed.
First to submit: 1. Product Hunt (startup, free) — use the startup variant. Last: 6. There's An AI For That (ai, paid) — use the ai variant.
SaaS variant: "The Otter.ai alternative for small product teams: Turn scattered meeting notes into decisions, owners, and next steps in minutes."
A kit is a plan, not a submission — each listing is still filed by hand.