Track and update action item status from natural language updates like 'Seanのメールには返信しておいた' or 'Lu対応予定'. Integrates with daily-comms-ops workflow. Use when managing action items across communication channels.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when creating executive-level briefing materials, board reports, management meeting presentations, or investor briefings. This skill provides the "So What? / Why Now? / What Next?" framework, data visualization guidelines optimized for executives, and professional templates for rapid document creation. Triggers include "create board report", "executive summary", "management meeting materials", "investor presentation", "one-page summary", or requests to communicate complex information to senior leadership.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
A specialized skill for creating high-impact executive communications that drive decisions and save leadership time.
This skill helps create:
Core Framework: So What? / Why Now? / What Next?
Key Principles:
This skill generates executive briefing documents in Markdown format:
Documents are created using templates from assets/ and follow the "So What? / Why Now? / What Next?" framework.
references/executive_communication_guide.md - Communication principles for executivesreferences/so_what_framework.md - The So What? / Why Now? / What Next? frameworkreferences/data_visualization_guidelines.md - Data visualization best practicesreferences/action_recommendation_patterns.md - Action recommendation patternsassets/one_page_summary_template_[ja|en].md - One-page executive summaryassets/board_report_template_[ja|en].md - Board of Directors reportassets/management_meeting_template_[ja|en].md - Management meeting materialsassets/investor_briefing_template_[ja|en].md - Investor briefing documentClarify what you're trying to achieve and who will receive the document. This determines structure, depth, and tone.
Identify the primary objective:
| Purpose Type | Description | Key Focus |
|---|---|---|
| Decision Request | Seeking approval or choice between options | Options, risks, recommendation |
| Status Report | Informing on progress or situation | Metrics, trends, deviations |
| Proposal | Advocating for an initiative or investment | Business case, ROI, timeline |
| Alert/Escalation | Raising awareness of risk or issue | Impact, urgency, mitigation |
Understand your audience's perspective:
| Audience | Time Available | Primary Concerns | Preferred Format |
|---|---|---|---|
| CEO | Very limited | Strategic impact, risks | One-page summary |
| Board of Directors | Limited | Governance, compliance, returns | Formal report |
| Executive Committee | Moderate | Cross-functional impact | Meeting materials |
| Investors | Moderate | Returns, growth, risks | Structured briefing |
Specify what should happen after reading:
After reviewing this document, the reader should:
1. Understand: [Key insight or situation]
2. Believe: [Core message or conclusion]
3. Do: [Specific action or decision]
Structure your message using the "So What? / Why Now? / What Next?" framework to ensure relevance and actionability.
Ask yourself: "Why should the executive care about this?"
Good Example:
"Customer churn increased 15% this quarter, putting $2.3M ARR at risk."
Bad Example:
"Customer churn increased 15% this quarter." (No impact stated)
Checklist:
Ask yourself: "Why does this need attention now?"
Good Example:
"Q4 budget lock is in 2 weeks; delay means 6-month postponement."
Bad Example:
"We should address this soon." (No specific timeline)
Urgency Triggers:
Ask yourself: "What specific action do you want?"
Good Example:
"Approve $150K for customer success program; implementation starts Dec 1."
Bad Example:
"We recommend improving customer retention." (No specific action)
Action Format:
[ACTION VERB] + [SPECIFIC THING] + [BY WHEN/HOW MUCH]
Examples:
- Approve the $2M capital expenditure for new facility
- Decide between Option A (in-house) or Option B (outsource)
- Authorize hiring of 3 additional engineers
Organize information using the Pyramid Principle and design the document structure.
Structure information from conclusion to supporting evidence:
Level 1: Main Message (Answer/Conclusion)
|
Level 2: Key Supporting Points (3-5 maximum)
|
Level 3: Evidence/Data (Only as needed)
Before (Chronological - Wrong):
"We analyzed customer feedback, then reviewed churn data, conducted interviews, and concluded that..."
After (Pyramid - Correct):
"Recommendation: Invest $500K in customer success. This will reduce churn by 20% based on three findings: [1] Exit interviews reveal..., [2] Data shows..., [3] Competitor analysis indicates..."
Every executive document needs a scannable first page:
+--------------------------------------------+
| [TITLE] - [DATE] |
+--------------------------------------------+
| EXECUTIVE SUMMARY (3-5 sentences) |
| - Core message with So What? |
| - Why Now? |
| - What Next? (Recommendation) |
+--------------------------------------------+
| KEY METRICS | SITUATION |
| +---+ +---+ +---+ | Current state |
| |KPI| |KPI| |KPI| | Key developments |
| +---+ +---+ +---+ | |
+--------------------------------------------+
| RECOMMENDATION / NEXT STEPS |
| 1. Specific action item |
| 2. Timeline |
| 3. Required resources |
+--------------------------------------------+
Based on audience and purpose, select additional sections:
| Section | When to Include |
|---|---|
| Background/Context | If audience lacks familiarity |
| Analysis Details | If methodology matters for credibility |
| Financial Breakdown | For investment decisions |
| Risk Assessment | For high-stakes decisions |
| Implementation Plan | For project approvals |
| Appendix | For reference data |
Present data in ways that support executive decision-making.
| Message Type | Recommended Chart | Avoid |
|---|---|---|
| Trend over time | Line chart, Area chart | Pie chart |
| Comparison | Bar chart (horizontal for many items) | 3D charts |
| Composition | Stacked bar, Treemap | Multiple pie charts |
| Distribution | Histogram, Box plot | Complex scatter |
| Relationship | Scatter plot, Bubble chart | Over-decorated visuals |
Rule 1: One Chart, One Message
Rule 2: Maximize Data-Ink Ratio
Rule 3: Use Consistent Formatting
Highlight what matters:
Revenue ($M)
^
3 -| .----- <- "New product launch"
| .-'
2 -| ---'
|
1 -|
+-----+-----+-----+-->
Q1 Q2 Q3
Present recommendations in a way that facilitates executive decision-making.
When presenting options, use consistent format:
| Criteria | Option A: Build | Option B: Buy | Option C: Partner |
|---|---|---|---|
| Cost | $500K | $800K | $300K |
| Timeline | 6 months | 2 months | 3 months |
| Control | High | Medium | Low |
| Risk | Technical risk | Vendor dependency | IP exposure |
| Recommendation | Preferred |
Be explicit about what could go wrong:
Key Risks:
+------------------------------------------------------+
| Risk | Impact | Likelihood | Mitigation |
+-------------------+---------+------------+------------+
| Vendor delay | High | Medium | Milestone |
| | | | penalties |
| Cost overrun | Medium | Low | Fixed- |
| | | | price bid |
+------------------------------------------------------+
End with a clear request:
For Approval:
"Requesting approval to proceed with Option B at $800K budget. Authorization signature required below."
For Decision:
"Decision required by [date]: Select Option A, B, or C. If no decision by [date], project will be delayed by [impact]."
For Information:
"No action required. This report is for awareness. Questions can be directed to [contact]."
Generate the final document using templates and ensure executive-level quality.
Choose appropriate template based on audience and purpose:
Purpose: Board Report -> assets/board_report_template_[ja|en].md
Purpose: Management Meeting -> assets/management_meeting_template_[ja|en].md
Purpose: Investor Briefing -> assets/investor_briefing_template_[ja|en].md
Purpose: General Summary -> assets/one_page_summary_template_[ja|en].md
Fill in each section following the guidance in the template:
Before finalizing, verify:
Content Quality:
Format Quality:
Audience Alignment:
| Audience | Document Type | Template |
|---|---|---|
| CEO/C-Suite | Quick update | one_page_summary |
| Board of Directors | Formal proposal | board_report |
| Executive Committee | Working session | management_meeting |
| Investors/Analysts | Performance review | investor_briefing |
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Track and update action item status from natural language updates like 'Seanのメールには返信しておいた' or 'Lu対応予定'. Integrates with daily-comms-ops workflow. Use when managing action items across communication channels.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI活用提案の専門コンサルタントスキル。LLM・AIエージェントの活用事例知識を基に、業界別、部門別、シーン別に最適なAI導入提案を行います。システム化、業務改善、効率化を得意とし、具体的な活用事例、期待効果、導入ステップを含む実践的な提案を提供します。Use when proposing AI/LLM adoption strategies for specific industries, departments, or business scenarios.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate AI-powered BPO service proposals for Japanese companies in the US market. Use when creating outsourcing proposals with AI service menus, ROI estimation, implementation roadmaps, and bilingual (JA/EN) proposal documents for 在米日系企業向けAI実装.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI(LLM)が生成した日本語テキストの「AI臭」を検出・診断し、人間らしい文章にリライトするスキル。 Use when: 「AIっぽい文章を直して」「人間らしくリライトして」「AI臭を消して」「この文章をもっと自然にして」 「テキストのAI感を減らして」「機械っぽさを取りたい」 "make this sound more human", "remove AI tone", "humanize this text", "detect if this is AI-generated". 6つのAI特有パターン(視覚的マーカー、単調なリズム、マニュアル的構成、非コミット姿勢、抽象語の濫用、 定型メタファー)を正規表現ベースで検出し、0-100のAI臭スコアを算出。3つの人間化技法 (バランスを崩す・客観を崩す・論理を崩す)でリライトを実行する。 Note: 検出スクリプトは日本語テキスト専用。英語テキストの場合はClaude自身がreferences/を参照して分析・リライトする。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate audit-ready internal control design documents from As-Is business process inventories. Produces control IDs, assertion mappings, procedures, SoD analysis, KPIs, materiality thresholds, and implementation roadmaps. Use when building internal controls for new audit engagements, SOX/J-SOX compliance, or process improvement initiatives.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review audit-related documents (control design documents, bottleneck analyses, requirements definitions, etc.) for quality, scoring them 0-100 with a severity-rated findings list. Use when reviewing audit documents, checking control design quality, or verifying cross-document consistency. Supports documents governed by US GAAP, IFRS, or J-GAAP.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.