Stats
Actions
Tags
From slack-forge
Guidance for extracting actionable tasks from local Slack transcript files.
How this skill is triggered — by the user, by Claude, or both
Slash command
/slack-forge:task-harvesterThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when analyzing local transcript snapshots to identify actionable tasks.
Use this skill when analyzing local transcript snapshots to identify actionable tasks.
slack-forge/transcripts/*.md.high: explicit ask with owner/deadlinemedium: implied action, weaker assignmentlow: speculative or unclear ownershipFor each extracted task, preserve:
Content must answer four questions: What? (the action), Who? (requester and owner), Why? (business trigger), When? (deadline or urgency).
Minimum output: 2-3 sentences of narrative context per task. A one-liner is never sufficient.
Action items must be specific and assignable: verb + responsible person + deliverable. Bad: "Fix the bug." Good: "David Madsen to investigate and fix the product price display issue after substitution (VMS-14759)."
Source context must reference the conversation (channel, participants, date) — not just paste a bare timestamp.
Merge duplicate mentions of the same task across transcript files/windows when core action is identical.
npx claudepluginhub jeremybrice/the-forge --plugin slack-forgeExtracts action items, commitments, assignments, and follow-ups from Fireflies meeting transcripts for all attendees (default) or a specific person using parallel subagents and MCP tools.
Extracts action items from meeting notes, transcripts, or brain dumps and creates owned, dated tasks in Astravue. Useful for turning unstructured discussion into structured tasks.
Extracts key decisions, takeaways, action items with DRIs, and open questions from meeting transcripts, notes, or Slack threads. Handles single meetings or weekly batches.