スキル一覧に戻る
DBS-Dev2000

generate-briefing-summary

by DBS-Dev2000

Version-controlled repository for Claude Code and Claude Desktop agents and skills

0🍴 0📅 2026年1月24日
GitHubで見るManusで実行

SKILL.md


name: generate-briefing-summary description: Final step in briefing pipeline. Consolidates action items from emails/Teams/Wrike, identifies system alerts, calculates quick stats, generates timestamp, and transitions Status from Collecting to Ready. Triggers on "Generate summary for briefing entry [id]", "Finalize the briefing". Called by briefing-generator after get-wrike-tasks. Requires Phase=5-Summary to proceed.

Generate Briefing Summary

Consolidates all briefing data and generates the final summary sections.

Input Parameters

ParameterRequiredFormatDescription
entry_idYesUUIDNotion page ID of briefing entry
dateYesYYYY-MM-DDBriefing date

Prerequisites

Phase must be "5-Summary" - all data collection skills must have completed.

Execution Workflow

Step 1: Fetch Current Briefing

Tool: notion_retrieve_page

{ "id": "entry_id" }

Step 2: Verify Phase

if (page.properties.Phase !== '5-Summary') {
  return {
    error: true,
    code: 'PHASE001',
    message: `Not ready. Current: ${phase}, Expected: 5-Summary`
  };
}

Step 3: Extract Action Items

Parse content from all sections:

From Emails: Look for "Action Required:" bullets From Teams: All items in "Teams Chat Action Items" section From Wrike: All "In Progress" tasks

Priority scoring:

  • Priority 1 (Urgent): Contains "urgent", "asap", "⚠️", overdue
  • Priority 2 (High): Email action items, Teams items, Wrike In Progress
  • Priority 3 (Medium): Wrike Review/Awaiting Feedback

Step 4: Extract System Alerts

Look for "System Alerts:" sections in emails:

  • Flag as critical if contains "critical", "failed", "error"

Step 5: Format Action Items Section

Sort by priority, then format as checklist (limit 10):

## ✅ Action Items

- [ ] **Shaeem** - Review PromoStandards PR before EOD ⚠️
- [ ] **Michael** - Test AccuZIP integration with sample data
- [ ] Kraken Mailing Phase 3 (Due: 2026-01-20)
- [ ] **Sarah** - Approve Kraken Phase 3 budget by Friday

Step 6: Format System Alerts Section

## ⚠️ System Alerts Requiring Attention

1. ⚠️ **CRITICAL**: **Azure DevOps** - Build Failed: Main Branch
2. • **Monitoring** - High CPU usage on Kraken service
3. • **GitHub Actions** - Test suite failing on PR #847

If no alerts: "No system alerts detected"

Step 7: Format Quick Stats

## 📊 Quick Stats

- **Meetings Today:** 6
- **Unread Emails:** 23 (5 high priority)
- **Active Wrike Tasks:** 23 (2 overdue)
- **Deep Work Available:** 3.5 hours
- **Financial Notices:** 2

Step 8: Generate Timestamp

Format: "Wednesday, January 14, 2026, 11:05 AM EST" Timezone: America/New_York

Step 9: Update Notion

Tool: notion_update_page_properties (multiple calls)

Update properties:

{
  "page_id": "entry_id",
  "command": "update_properties",
  "properties": {
    "Status": "Ready",
    "Action Item Count": 8,
    "Urgent Action Count": 2,
    "System Alert Count": 3
  }
}

Update content sections:

  • Replace "Generated:" line with timestamp
  • Replace Action Items section
  • Replace System Alerts section
  • Replace Quick Stats section

Output Format

{
  "success": true,
  "entry_id": "...",
  "date": "2026-01-14",
  "status": "Ready",
  "summary": {
    "action_items_count": 8,
    "urgent_count": 2,
    "system_alerts_count": 3,
    "critical_alerts": 1
  },
  "generated_at": "2026-01-14T11:05:00-05:00"
}

Error Handling

CodeDescriptionSeverityAction
PHASE001Wrong phase (not 5-Summary)CriticalFail - prerequisites not met
NOTION001Entry not foundCriticalFail with error
PARSE001Content parse errorWarningUse defaults, continue

Configuration

const CONFIG = {
  action_item_limit: 10,
  priority_weights: { urgent: 1, high: 2, medium: 3 },
  source_order: ['email', 'teams', 'wrike'],
  critical_keywords: ['critical', 'failed', 'error', 'exception', 'down'],
  timestamp: {
    timezone: 'America/New_York',
    format: 'long' // "Wednesday, January 14, 2026, 11:05 AM EST"
  }
};

⛔ MANDATORY: SAVE BEFORE COMPLETING

This skill is NOT complete until Status is changed to "Ready" in Notion.
DO NOT return success until notion_update_page_properties succeeds.
Unsaved summary WILL BE LOST on context compaction.

Integration

  • Called by: briefing-generator orchestrator after get-wrike-tasks
  • Final skill: No skills follow - briefing complete
  • API calls: 6 (fetch, 5 updates)
  • Expected time: 5-10 seconds
  • ⛔ MUST SAVE: Final summary and Status="Ready" BEFORE returning

Result

After completion:

  • Status: "Ready" (was "Collecting")
  • Phase: "5-Summary" (unchanged)
  • All summary sections populated
  • Timestamp generated
  • Briefing ready for user review

スコア

総合スコア

45/100

リポジトリの品質指標に基づく評価

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

0/10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

0/5
タグ

1つ以上のタグが設定されている

0/5

レビュー

💬

レビュー機能は近日公開予定です