菜单
Writes clear, appropriately-toned internal communications including project status updates, company newsletters, all-hands summaries, incident reports, FAQs, onboarding docs, and team announcements. Use when writing anything meant for a colleague, team, or company-wide audience.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | internal-comms |
| description | Writes clear, appropriately-toned internal communications including project status updates, company newsletters, all-hands summaries, incident reports, FAQs, onboarding docs, and team announcements. Use when writing anything meant for a colleague, team, or company-wide audience. |
A framework for writing internal communications that get read, understood, and acted on. Different formats for different audiences and purposes.
Structure: RAG status → progress → blockers → next steps
## [Project Name] — [Date]
Status: 🟢 On track / 🟡 At risk / 🔴 Blocked
**This week**
- [What was completed]
**Next week**
- [What's planned]
**Blockers / Decisions needed**
- [Specific ask, tagged to a person if applicable]
**ETA to milestone**: [Date or "TBD — see blockers"]
Structure: What happened → Impact → Timeline → Root cause → Actions
## Incident Report: [Brief title]
**Date**: [Date]
**Severity**: [P0/P1/P2]
**Duration**: [Start → Resolution]
**What happened**
[2-3 sentences. Plain language. No jargon.]
**Impact**
- Affected: [users, services, data]
- Scale: [how many, how long]
**Timeline**
- [HH:MM] Event
- [HH:MM] Detection
- [HH:MM] Mitigation started
- [HH:MM] Resolution
**Root cause**
[Single sentence. Blame systems, not people.]
**Actions to prevent recurrence**
| Action | Owner | Due |
|--------|-------|-----|
Structure: What's changing → Why it matters to you → What to do
Keep it short. 150-250 words. No corporate filler.
Structure: Headline moment → Team spotlights → Key metrics → What's coming
Aim for scannable. People read newsletters at 30% attention. Put the most important thing first and make it possible to skim.
Structure: Most important questions first → Questions grouped by topic → Links to more detail
Write questions the way people actually ask them, not the way you wish they would. "How do I get reimbursed?" not "Expense Reimbursement Policy."
Structure: Key announcements → Decisions made → Q&A highlights → Action items
Before writing, choose the tone:
| Tone | Use when | Example signal words |
|---|---|---|
| Warm + direct | Good news, milestones, team wins | "Excited to share", "proud of", "thank you" |
| Clear + neutral | Process updates, policy changes | "Starting [date]", "going forward", "to clarify" |
| Serious + calm | Incidents, difficult decisions | "I want to be transparent", "this is significant" |
| Urgent | Blockers, time-sensitive requests | "Needs your input by [time]", "action required" |
Avoid: passive voice, hedge words ("hopefully", "kind of", "sort of"), unnecessary preamble ("I wanted to reach out to let you know that…")
Before sending:
Extracts full article text and metadata from web pages, then produces a clean structured summary with key claims, supporting evidence, author stance, and original source link. Use when researching a topic, fact-checking a claim, saving content for reference, or comparing coverage across multiple sources.
Guides you through building new Claude skills with a structured Q&A process. Use when you want to create a new skill from scratch, improve an existing one, or turn a repeated workflow into a reusable skill. Produces a ready-to-upload SKILL.md file.
Identifies and qualifies high-quality leads by analyzing your product or service, searching for target companies and contacts, and providing actionable outreach strategies. Use when building a prospect list, preparing for outbound sales, researching a target account before a call, or building an ICP (Ideal Customer Profile).
Implements and evaluates software design patterns including Clean Architecture, SOLID principles, domain-driven design, and system design best practices. Use when designing new systems, refactoring existing code, evaluating architectural trade-offs, or learning design patterns through concrete examples.
Analyzes meeting transcripts to surface behavioral patterns, extract decisions, flag unresolved issues, and identify follow-up actions. Use after any meeting where you have a transcript or detailed notes — especially useful for 1:1s, team syncs, retrospectives, and customer calls.
Transforms rough ideas into fully-formed concepts through structured questioning, lateral thinking, and alternative exploration. Use when you're stuck, exploring a new idea, trying to break out of conventional thinking, or need to generate multiple strong options before committing to one.