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 行(带来源指向)再跑一次,主张就会按你实际收集的笔记重新分级。