agentleFS
alectivismalectivism/maven-template/.claude/skills/slack-summary/SKILL.md

slack-summary

Skill1 starsChanged 6 months agoMITView on GitHub

Summarize MMA Slack channel activity — decisions, action items, discussions. Use for "summarize Slack", "Slack recap", "catch me up on".

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask which channel(s) and time period to summarize

    line 42
  2. Distinctive:

    Read recent messages from the channel

    line 43
  3. Distinctive:

    Keep summaries under 500 words per channel

    line 53

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Slack Channel Summary

Key MMA Channels

ChannelWhat to Watch For
#generalCompany announcements, policy changes
#ceo-updatesGreg's directives, strategic decisions
#ai-upskillingTool rollouts, training updates, adoption metrics
#mma-ai-tiger-teamAI initiative decisions, cross-functional coordination
#thinktank-altt-aiALTT updates, lab progress, member engagement
#capCAP lab results, brand recruitment, experiment updates
#bapBrand as Performance study progress
#possible-staff-mmaEvent planning, logistics, deadlines
#membership-teamRenewals, onboarding, engagement issues
#sales-reviewPipeline updates, deal progress
#pmoProject status, resource allocation

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
  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 mentions of the user by name
  • Keep summaries under 500 words per channel

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.