03_task6

Aggregate Slack messages into a board-level execution summary with reconciled metrics.

1|Updated May 20, 2026
One-click install
npx skills add https://github.com/Wanli-Lee/CUA-Claw-Harness --skill 03-task6-wanli-lee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 03_task6
Source: https://github.com/Wanli-Lee/CUA-Claw-Harness/tree/main/skills/03_task6
Command: npx skills add https://github.com/Wanli-Lee/CUA-Claw-Harness --skill 03-task6-wanli-lee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you consolidate multi-department Slack updates into a coherent, board-level execution summary by validating numbers against finance reconciliation and surfacing cross-team dependencies and risks.

Core Features & Use Cases

  • Cross-department Slack integration: Fetches, filters, and reads relevant messages across teams to assemble the project status narrative.
  • Data reconciliation and discrepancy detection: Compares conflicting metrics and treats finance reconciliation data as the source of truth.
  • Dependency and risk identification for executives: Highlights schedule/budget changes, inter-team dependencies, and HR/vendor risks, then packages them as a structured executive draft.
  • Communication guardrails: Ensures drafts are saved via the required Slack draft flow and confirms recipients through the contacts API before drafting to COO (no direct board contact).

Quick Start

Ask the assistant to generate a board-grade project execution status report by aggregating relevant Slack messages from the last 7 days, reconciling metrics with finance data, and saving the resulting draft for the COO.

Frequently Asked Questions about 03_task6

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an executive summary from Slack messages for board reporting?

To generate an executive summary from Slack messages, the Skill aggregates multi-department project updates, reconciles conflicting metrics against finance data, and identifies cross-team dependencies and risks to produce a board-ready draft.

What is the best way to reconcile project metrics from different teams for an execution summary?

The best way to reconcile project metrics is to treat finance reconciliation data as the source of truth, comparing it against conflicting departmental metrics to detect discrepancies before drafting the execution summary.

How does dependency mapping work when aggregating cross-department project status updates?

Dependency mapping works by analyzing integrated Slack messages to highlight inter-team dependencies, schedule changes, budget adjustments, and HR or vendor risks into a structured executive reporting format.

Can I use Slack data to track schedule and budget changes for executive reporting?

Yes, you can use Slack data to track schedule and budget changes by fetching and filtering relevant team messages, prioritizing finance reconciliation data to ensure accurate executive reporting.

Do I need a contacts API to verify recipients before drafting a board-level report?

Yes, you need a contacts API to verify recipients before drafting a board-level report, as the Skill confirms recipients through the contacts API and routes drafts to the COO instead of direct board contact.

Why does my report drafting workflow save to a local results file instead of sending directly to the board?

The report drafting workflow saves to a local results file to enforce communication guardrails, ensuring the draft is reviewed via the Slack draft flow and directed to the COO rather than sending directly to the board.