PremiumEmail Triage Automation
- 閱讀完整對話串
- 分入 3 個類別
- 以你的語氣起草
- 核准後發送
← 全部 Skills · 自動化 · CRO Audit

Premium
Premium
Free
Premium此 Skill 產出的範例。範例內容,僅供說明。
CRO Audit — sample Page: BeanLoop pricing page | Type: pricing | Goal: signup | Traffic: paid | Obstacles: 6 (High 3 · Medium 2 · Low 1) | Quick wins: 4 | Bigger changes: 2 | Test ideas: 3 | Gaps: 0 | Errors: 0 | Warnings: 0 Ready to act — every part is present and the input had no errors. Top obstacle: [High · Quick win] Value proposition — Headline states no specific benefit - no number, outcome, or time frame a visitor can check. Evidence: Headline: "The all-in-one platform for modern teams". Second: [High · Quick win] CTA copy — Button copy says the action, not the value. Third: [High · Bigger change] Friction — Form asks for 7 fields. Copy alternatives are patterns with bracketed placeholders — fill in your real numbers, never invent them; a fix is a change to make, not a result to expect.
我們的 BeanLoop 定價頁沒有把付費流量轉化掉——審計它,告訴我們先修什麼。Read https://skillu.dev/install/agent.md, then install the CRO Audit skill (cro-audit)./cro-audit,然後用大白話描述你想要什麼。不是。它只表示每個部分都齊了、輸入沒有錯誤——審計完整了,不代表頁面就好。一份 ready 的審計仍可能找出 6 個障礙(自帶樣本就是如此);沒有障礙的頁面也只是通過了本次審計的七個維度檢查。
不會。它只讀你寫的 cro.txt 檔案,只標記你在裡面描述的東西。輸入沒有描述的維度是缺口或缺失信號,絕不是猜出來的事實。
Fields 行不寫就行——它是可選的。只有表單類目標(signup、demo、contact、subscribe)在沒有 Fields 行時才會收到一條警告:表單長度未知。