一份 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.