メニュー
Use when the founder wants to configure Slack channels, extract actionable Slack intelligence, create a daily Slack digest, review Slack decisions and handoffs, or turn selected Slack context into task candidates for the daily operating workflow.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the founder needs a reusable business artifact from saved workspace context, especially investor/stakeholder updates or competitive snapshots. Combines recent context, tasks, research, closeouts, weekly plans, metrics supplied by the user, and competitor inputs into paste-ready drafts.
Fires when the user pastes a transcript or says they just finished a meeting. Provides: summary, what matters now, risks or blockers, tasks, and follow-up email. Output contract: every closeout leaves the user with a saved record and clear next actions.
Use when the founder needs to identify, connect, verify, or document email, calendar, Drive, CRM, call recording, Apollo, Slack, Teams, search/Tavily, or other operating connectors for SalesSidekick Lite.
Fires when the user wants to get ready for a meeting. Provides: account context, person point of view, talk track angles, questions to ask, watch-outs, and desired next step. Output contract: the user walks into the meeting with a clear point of view and practical talking points.
Use when the user wants to build an outbound SDR campaign, create a target account list, research a market from ICP, find buyers, build account/persona POVs, or draft a 3-5 step outbound sequence. Runs a staged campaign workflow: ICP/value prop/offer intake, 3x long-list, preliminary scan, top-50% deep account research, final prioritized list, top-20 company POVs, buyer persona research, persona POVs, offer mapping, then message sequence.
Fires during setup and daily briefing. Provides: seller identity, company/product context, competitor context, communication style, daily briefing preference, and setup-state logic. Output contract: the system always knows what has been captured and what is still missing.
| name | slack-intelligence |
| description | Use when the founder wants to configure Slack channels, extract actionable Slack intelligence, create a daily Slack digest, review Slack decisions and handoffs, or turn selected Slack context into task candidates for the daily operating workflow. |
| user-invocable | true |
Make Slack useful inside the founder operating system without turning it into a noisy transcript dump.
The skill should read only the Slack channels, threads, exports, or pasted snippets the founder chooses. It extracts operational intelligence that should affect the day: decisions, asks, customer/account mentions, blockers, handoffs, risks, product feedback, competitor mentions, useful links, and task candidates.
Use /slack-setup when Slack is first connected or when the founder wants to change which channels matter.
Capture:
Write:
data/slack/channel-map.mddata/setup-status.mddata/ops.logRead:
data/setup-status.mddata/connectors.mddata/slack/channel-map.mddata/tasks.mdviews/daily-briefing.mdviews/priority-plan.mddata/ops.logWrite:
data/slack/channel-map.mdviews/slack-digest.mddata/slack/digests/{{DATE}}.mddata/setup-status.md during setupdata/ops.logdata/slack/channel-map.md.Use /slack-digest daily, or let the morning briefing include it when Slack is configured.
Read:
data/slack/channel-map.mddata/tasks.mdviews/daily-briefing.mdviews/priority-plan.mddata/ops.logExtract:
Write:
views/slack-digest.mddata/slack/digests/{{DATE}}.mddata/ops.logKeep the digest short enough to use in a morning briefing. Do not summarize every message.
Every item should answer:
data/tasks.md.