agentsclimarketplace

Slack summary

Skill alectivism/organization-ai-skills/org-meetings/skills/slack-summary

Claude Code / claude.ai Agent Skills for organizational knowledge work — marketing, comms, research, ops. Install: npx skills add alectivism/organization-ai-skills

Install
npx -y skills add alectivism/organization-ai-skills --skill slack-summary

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Summarize Slack channel activity — decisions, action items, key discussions. Use for "summarize Slack", "Slack recap", "catch me up on [channel]", or "what did I miss in Slack".

SKILL.md

1.8 KB, 381 tokens by cl100k_base, as published. Nobody here has run it

Template skill. Fill in the [BRACKETED] placeholders with your organization's details — or paste your org context and ask Claude to populate them for you.

Slack Channel Summary

Key Channels to Monitor

Populate this table with your organization's Slack channels and what matters in each:

ChannelWhat to Watch For
#generalCompany-wide announcements, policy changes
#[leadership-channel]Executive directives, strategic decisions
#[team-1-channel][e.g., Project updates, roadmap changes]
#[team-2-channel][e.g., Client issues, deal progress]
#[team-3-channel][e.g., Event planning, logistics]
#[ops/pmo-channel]Project status, resource allocation
[Add your key channels]

Summary Structure

Channel: #[channel-name]

Period: [date range]

Decisions Made

  • [Decision] — by [who], [date]

Action Items

  • [Task] — assigned to [who], due [date]

Key Discussions

  • [Topic]: [1-2 sentence summary of the discussion and outcome]

Flagged Items

  • [Anything that needs attention, is escalating, or is blocked]

Process

  1. Ask which channel(s) and time period to summarize
  2. Read recent messages from the channel(s)
  3. Extract decisions, action items, and key discussions
  4. Flag anything that needs the user's attention
  5. Present structured summary

Guidelines

  • Focus on decisions and actions, not chatter
  • Attribute decisions to the person who made them
  • Note any unresolved debates or open questions
  • Flag direct mentions of the user by name
  • Keep summaries under 500 words per channel

Gives 0 of the 12 instructions most note taking skills give in 381 tokens

Counted across 686 of the 876 authors here whose files we hold, read 2026-08-06

  • include a visual element on every slidein 44 of 686, across 13 files
  • use wikilinks for internal vault linksin 35 of 686, across 11 files
  • commit to a single visual motif across every slidein 34 of 686, across 9 files
  • read pptxgenjs guide before creating presentations from scratchin 30 of 686, across 6 files
  • keep 0.5 inch minimum marginsin 30 of 686, across 7 files
  • use subagents to visually inspect rendered slidesin 30 of 686, across 6 files
  • re-verify affected slides after every fixin 27 of 686, across 5 files
  • run content QA checks before declaring successin 26 of 686, across 3 files
  • Use Markdown links for external URLs onlyin 26 of 686, across 10 files
  • pick a bold topic specific color palettein 24 of 686, across 2 files
  • read editing guide before editing existing presentationsin 23 of 686, across 1 file
  • use one dominant color across all slidesin 23 of 686, across 1 file

Said here and by no other author read

  • ask which channels and time period to summarize
  • read recent messages from the channel
  • flag anything needing user attention
  • present a structured summary
  • focus on decisions and actions
  • attribute decisions to the person

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.