一键导入
brief-feedback
Process feedback on morning briefs and update quality rules. Use when the brief was wrong or needs improvement.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Process feedback on morning briefs and update quality rules. Use when the brief was wrong or needs improvement.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | brief-feedback |
| description | Process feedback on morning briefs and update quality rules. Use when the brief was wrong or needs improvement. |
Process feedback on morning briefs and update quality rules.
/brief-feedback followed by your feedback
Vault/Core Memory/Brief Feedback.md/brief-feedback The Alexei suggestion was bad - you shouldn't propose partnerships without checking their GitHub first. Also stop suggesting random apartment stuff as quick wins.
Atlas will:
When user invokes /brief-feedback [feedback]:
Vault/Core Memory/Brief Feedback.mdFrom feedback, extract:
| Feedback Pattern | Rule Type |
|---|---|
| "Don't suggest X" / "Stop doing Y" | Don't Do |
| "You should X first" / "Always Y before Z" | Do More |
| "X was bad, should have been Y" | Bad → Good Example |
| "I care about X" / "X is important" | Context That Matters |
| "X is higher priority than Y" | High-Priority Situations |
After processing feedback:
✅ Added to Brief Feedback:
**Don't Do:**
- [new rule]
**Bad → Good:**
| [bad pattern] | [good pattern] |
Updated: Vault/Core Memory/Brief Feedback.md
Browser automation for web scraping and testing. Use for form filling, screenshots, and web interactions.
Tactical advice on brand storytelling from 30 product leaders (50 insights). Use when working on story, storytelling, narrative, brand story. Category: Marketing.
Discover trending topics and content ideas from social feeds for post creation. Use when scanning Twitter timeline or finding content inspiration.
Debrief last call with next steps. Use after finishing a call, when asking what happened on a call, or when needing post-call action items.
Prepare for a call with research, context, and YC qualifying questions. Use before meetings or sales calls.
Interactive code review with opinionated recommendations. Use when reviewing code changes, PRs, or existing code quality.