Morning Meeting Bwm
WarnAudited by ClawScan on May 10, 2026.
Overview
This skill should be reviewed because it can turn Slack standup messages into automatically executed business tasks across many agents without clear approval or permission limits.
Before installing, confirm exactly which Slack channels, agents, and business systems this skill can access. Do not allow immediate execution of standup-derived tasks unless you add approval gates, least-privilege credentials, retention rules, and a clear way to disable any scheduled runs.
Findings (6)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A Slack message or AI-generated channel content could cause the agent to take actions that were not explicitly approved by the user.
The skill makes Slack conversation content, including AI conversation, a source of executable goals without specifying validation, trusted senders, or approval checks.
Read #morningmeeting Slack channel for human + AI conversation 3. Parse transcript for tasks and assignments 4. Delegate to appropriate AI agents 5. Execute any tasks agents can handle immediately
Require explicit user confirmation for task execution, define who can assign tasks, and treat channel messages as untrusted input rather than direct instructions.
The agent could make business changes immediately based on parsed meeting content, including changes affecting code, infrastructure, orders, marketing, or customer support.
This grants broad automatic execution authority without describing limits, rollback, approvals, or which tools/accounts may be used.
Execute any tasks agents can handle immediately
Add clear action classes, require confirmation for high-impact or external-facing changes, and log/preview planned actions before execution.
Users cannot tell which Slack identity or business permissions the agent will use, or how far its delegated authority extends.
The workflow implies delegated Slack workspace read/post authority, but the supplied requirements declare no primary credential, env vars, or scoped permission contract.
Read #morningmeeting Slack channel ... Send summary report back to #morningmeeting
Declare required credentials and scopes, use least-privilege Slack permissions, and document exactly what accounts/channels the skill may access.
Private meeting context or business tasks may be shared with multiple agents, and the user may not know which agent is responsible for each action.
The skill routes Slack-derived tasks to many named agents but does not define agent identity verification, permission boundaries, data-sharing limits, or failure handling.
Delegate to appropriate AI agents
Define trusted agent identities, per-agent permissions, data minimization rules, and approval gates before delegating work.
Meeting details and task instructions may remain available to future agent runs.
The skill stores meeting summaries and active task assignments in persistent memory, which is purpose-aligned but can preserve sensitive business context and task instructions for later reuse.
Meeting summaries: `memory/meetings/YYYY-MM-DD-morning-meeting.md` Task assignments: `memory/tasks/active-tasks.md`
Document retention, access controls, and cleanup behavior; avoid storing secrets or sensitive customer data in meeting/task memory.
If scheduled externally, the automation could run every weekday without the user manually invoking it each time.
The documented weekday cron schedule is expected for daily standup automation, but it represents recurring background operation that users should explicitly approve and be able to disable.
0 10 * * 1-5 # 10:00 AM weekdays
Make scheduling opt-in, document how to disable it, and require confirmation before any high-impact task execution during scheduled runs.