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

Premium
Premium
Free
Premium此 Skill 產出的範例。範例內容,僅供說明。
Research Brief Compiler report — sample Claims: 3 | Supported: 1 | Single-source: 1 | Unsupported: 1 | Open questions: 2 | Notes: 4 | Gaps: 1 | Errors: 0 | Warnings: 0 Supported: small teams merge PRs faster with AI coding agents — N1 (Blog — blog.example.com/ai-agents-shipping) and N2 (Interview — Priya, Nov 2026). Single-source: a human review step is still required before merge — N3 (Docs — docs.example.com/agents). Unsupported: AI agents cut total engineering headcount — no notes cited, listed not treated as a finding. Open: do the gains hold for large codebases, and what does “faster” cost in review quality? Gaps: 1 claim cites no notes.
把這些收集的筆記整理成一份研究簡報——筆記到底支撐了什麼、什麼只有單一來源、還有什麼沒解決?Read https://skillu.dev/install/agent.md, then install the Research Brief Compiler skill (research-brief-compiler)./research-brief-compiler,然後用大白話描述你想要什麼。只看你引用的筆記,別無其他:有依據是 2 條以上不同筆記、單一來源是恰好 1 條、無依據是 0 條。兩條筆記說法相同,會讓主張在這份簡報裡算有依據,但不等於它正確——筆記本身可能錯、可能過時、可能同出一源,這個判斷在你手裡。
會被丟棄,並在輸入錯誤裡點名——腳本絕不會為一條主張編造來源。補上缺失的 Note 行(帶來源指向)再跑一次,主張就會按你實際收集的筆記重新分級。