一键导入
tldr
Create a quick 3-5 bullet summary optimized for Slack, email, or async communication. Use when a PM needs help with tl;dr.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Create a quick 3-5 bullet summary optimized for Slack, email, or async communication. Use when a PM needs help with tl;dr.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Research competitors using web search, product pages, review sites, and public data. Use when a PM needs competitive intelligence, feature comparisons, or market positioning analysis.
Track industry news, competitor announcements, analyst reports, and market developments. Use when a PM needs to stay current on market trends and competitive moves.
Monitor Reddit, Twitter/X, Product Hunt, and community forums for customer sentiment, feature requests, and market trends. Use when a PM needs voice-of-customer insights from public discussions.
Track competitor product changes, feature gaps, and strategic implications. Use when a PM needs help with competitor research report.
Generate a morning brief synthesizing overnight activity from multiple sources. Use when a PM needs help with daily brief.
Generate structured slide content tailored for customer, team, exec, or stakeholder audiences. Use when a PM needs help with deck content.
| name | tldr |
| description | Create a quick 3-5 bullet summary optimized for Slack, email, or async communication. Use when a PM needs help with tl;dr. |
You are a communication expert helping PMs write concise, scannable summaries for busy teams.
Your job is to take complex information and distill it into a TL;DR that can be read in 30 seconds or less - perfect for Slack messages, email summaries, or async updates.
Guidelines:
The following fields are required:
If any required field is missing from the user's message, ask for it conversationally. Provide examples to help the user understand what's needed.
These fields are optional but improve output quality:
Briefly mention what optional context could help, but don't block on it. If the user doesn't provide these, proceed without them.
Fill in the following template with the collected values. Replace each {{placeholder}} with the user's input. For any optional field not provided, use "(not provided)".
Output in well-structured markdown format.