slack-daily-digest
Slack Daily Digest
Use this skill to produce a daily digest of today's important Slack activity from selected channels or topics.
Start Here
- If the user did not name channels or topics, ask first before making any Slack tool calls.
- Do not guess the user's main or starred channels.
Workflow
- Confirm channels or topic keywords.
- Resolve the user's timezone with
slack_read_user_profile. For "today," use local start-of-day through now and state that window in the digest. - Named channels: Resolve IDs through
slack_search_channels, then callslack_read_channelfor today's window withlimitat50per channel. - Named topics: Use
slack_search_public_and_privatefor each topic phrase. If channels were also provided, run one search per topic and channel withqueryset to<topic phrase> in:<#CHANNEL_ID>so the search stays inside the selected channels. If no channels were provided, setqueryto the topic phrase. Then read the returned channels withslack_read_channelor parent threads withslack_read_threadwhen a result looks important. - Prioritize decisions, blockers, incidents, asks, ownership changes, deadline changes, and status changes.
- When a named channel was resolved to a channel ID, render that channel in the final digest as a Slack channel mention like
<#CHANNEL_ID>instead of plain#channel-name, especially in Scope. - Read the full
## Formatting Rulessection below. - If the user asked to post or send the digest in Slack, use
../slack-outgoing-message/SKILL.mdand follow the user's explicit intent:
More from openai/plugins
plugin-creator
Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, and baseline placeholders you can edit before publishing or testing. Use when Codex needs to create a new personal plugin, add optional plugin structure, or generate or update personal or repo-root `.agents/plugins/marketplace.json` entries for plugin ordering and availability metadata.
71swiftui-liquid-glass
Implement, review, or improve SwiftUI features using the iOS 26+ Liquid Glass API. Use when asked to adopt Liquid Glass in new SwiftUI UI, refactor an existing feature to Liquid Glass, or review Liquid Glass usage for correctness, performance, and design alignment.
29swiftui-ui-patterns
Best practices and example-driven guidance for building SwiftUI views and components, including navigation hierarchies, custom view modifiers, and responsive layouts with stacks and grids. Use when creating or refactoring SwiftUI UI, designing tab architecture with TabView, composing screens with VStack/HStack, managing @State or @Binding, building declarative iOS interfaces, or needing component-specific patterns and examples.
27ios-debugger-agent
Use XcodeBuildMCP to build, run, launch, and debug the current iOS project on a booted simulator. Trigger when asked to run an iOS app, interact with the simulator UI, inspect on-screen state, capture logs/console output, or diagnose runtime behavior using XcodeBuildMCP tools.
27swiftui-view-refactor
Refactor and review SwiftUI view files with strong defaults for small dedicated subviews, MV-over-MVVM data flow, stable view trees, explicit dependency injection, and correct Observation usage. Use when cleaning up a SwiftUI view, splitting long bodies, removing inline actions or side effects, reducing computed `some View` helpers, or standardizing `@Observable` and view model initialization patterns.
27swiftui-performance-audit
Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.
27