メニュー
Generates Slack messages in user's authentic voice: direct, concise, data-driven. Use when user needs to write, draft, compose, or rewrite Slack messages, DMs, or channel posts. Adapts style based on channel type (public vs DM) and message type.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | slack-writing |
| description | Generates Slack messages in user's authentic voice: direct, concise, data-driven. Use when user needs to write, draft, compose, or rewrite Slack messages, DMs, or channel posts. Adapts style based on channel type (public vs DM) and message type. |
Generate Slack messages in your authentic voice: direct, concise, data-driven, and confidently human. Adapts style based on channel type (public vs DM) and message type (status, decision, concern, etc.).
Quick update: [what happened in one line].
[Metrics if applicable:]
• [Metric 1]: [Value] ([context - above/below target])
• [Metric 2]: [Value]
Next steps:
• [Action 1] - [Owner] - [Deadline]
• [Action 2] - [Owner] - [Deadline]
Example:
Quick update: shipped landing page redesign yesterday.
Early metrics:
• Adoption: 15% (below 20% target)
• Page load: 1.2s (within goal)
Next steps:
• @sarah run user interviews by Friday
• @mike pull funnel analytics by EOD Thursday
Will synthesize findings and share action plan Monday.
Need input on [topic].
Context: [1-2 sentences of essential background]
Options:
• Option 1: [Brief description] - [Trade-off]
• Option 2: [Brief description] - [Trade-off]
[Your position]: Leaning toward [option] because [reason].
@[person] need your call by [deadline].
Example:
Need input on API approach.
Context: Building the integration layer. Two viable paths with different trade-offs.
Options:
• Option 1: REST - faster to ship (2 weeks), creates tech debt
• Option 2: GraphQL - cleaner long-term, delays launch by 2 weeks
My take: Leaning toward Option 1 given our Q1 timeline pressure.
@david need your call by EOD Wednesday.
Flagging a risk: [one-line summary].
Context: [Why this matters]
Impact: [What happens if not addressed]
Recommendation: [Proposed action]
[Confidence level if uncertain]: Medium confidence this is the right call.
Example:
Flagging a risk: Legal approval timeline is tight.
Context: Current plan assumes 5-day Legal review. Based on past reviews, that is optimistic.
Impact: Can slip launch by 2+ weeks if not addressed now.
Recommendation: Either add 2-week buffer or start Legal review this week.
High confidence this needs attention.
Different take: [your position in one line].
[Why you see it differently - 2-3 sentences max]
Trade-off to consider: [What your approach gains/loses]
Open to discussing if helpful.
Example:
Different take: we should prioritize mobile over desktop.
Usage data shows 65% of our users are on mobile during site visits. Desktop-first means we are optimizing for the minority. The mobile experience is also where we are losing users in the funnel.
Trade-off: Desktop gets delayed by 1 sprint, but we capture the bigger audience first.
Open to discussing if helpful.
[Impact statement]. Well done.
What this unlocks: [Customer/business value]
[Specific callout if applicable]: @[person] [specific contribution]
Example:
This unlocks real-time collaboration for our largest customer segment. Well done.
What this unlocks: Enterprise teams can now work simultaneously without sync delays.
@lisa your work on the conflict resolution logic made this possible.
Checking in on [topic].
Last status: [What was agreed/expected]
Need by: [Deadline]
Let me know if anything is blocking progress.
Example:
Checking in on the API documentation.
Last status: Draft was due yesterday per our sync.
Need by: Friday to unblock partner integration testing.
Let me know if anything is blocking progress.
FYI: [What is happening in one line].
Key details:
• [Detail 1]
• [Detail 2]
• [Detail 3]
What this means for you: [Specific impact/action needed]
Questions? Thread here or DM me.
Example:
FYI: Launching the new dashboard to all users next Monday.
Key details:
• Rollout: 10% Monday, 50% Wednesday, 100% Friday
• Training: Self-serve guide in Help Center
• Support: #dashboard-questions for issues
What this means for you: Review the guide before Monday. Flag concerns by Friday.
Questions? Thread here or DM me.
+1 on this. Adding: [your contribution]
You asked about [topic]. Here is my take:
[Your input in bullet format if multiple points]
On your question about [topic]:
[Direct answer]
[Context if needed - 1 sentence max]
Before sending, verify:
Use these when uncertain:
For product-specific context (product name, key terms, stakeholders), see CLAUDE.local.md.
When drafting Slack messages:
Reference/corporate-strategy/ for org contextBrains/*/CLAUDE.md for project contextinput/org/colleagues.json for name verificationMUST BE USED when analyzing meeting transcripts or notes. Classifies input type, attributes speakers, and verifies names against colleagues.json. Works with routing-brains and summarizing-meetings skills for complete workflow.
A framework for evaluating whether a product's success is mathematically possible based on its cost structure, acquisition assumptions, and unit economics. Use this when vetting a new job opportunity, evaluating a startup's viability, or determining if a failing product can be "iterated" to success.
A structured method for gathering high-signal, contextual feedback from a trusted network to validate ideas or navigate complex career decisions. Use this when facing a "fork in the road" career choice, prioritizing product features, or narrowing down topics for public speaking or content.
Create and maintain individual colleague communication profiles in Markdown. Use when the user wants to document a person's communication style, tone preferences, decision style, sensitivities, channels, response cadence, or examples of good vs bad communication, and store it as a per-person profile under input/org/profiles/.
Gather context through high-leverage eigenquestions when information is missing or ambiguous. ACTIVATE THIS SKILL when: (1) context is missing or unclear, (2) user asks something requiring unstated assumptions, (3) working within a brain without recent context, (4) starting new work or strategic decisions, (5) multiple valid approaches exist without clear direction, (6) user says "clarify", "help me think through", or "what should I consider". This skill asks ONE discriminating question at a time to unlock maximum downstream clarity.
Drafts concise, professional PM emails using the CRAFT method. Use when user needs to compose, draft, write, or rewrite professional email communication including follow-ups, status updates, escalations, and stakeholder messages.