slack-huddle-transcript/SKILL.md
Extract and format Slack huddle transcripts for analysis. Use this skill when processing Slack huddle transcript files (.vtt), when user mentions huddle transcript or Slack transcript, when user uploads a VTT file from Slack, or when user asks to summarize or analyze a Slack meeting/huddle. Handles VTT format transcripts with speaker identification, timestamps, and conversation merging.
npx skillsauth add stympy/skills slack-huddle-transcriptInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Parse and format Slack huddle transcripts into clean, readable output for analysis.
python scripts/parse_transcript.py <transcript.vtt> --format markdown
.vtt file# List recent files to find transcript
curl -H "Authorization: Bearer $SLACK_TOKEN" \
"https://slack.com/api/files.list?types=transcript"
# Download specific file
curl -H "Authorization: Bearer $SLACK_TOKEN" \
"https://slack.com/api/files.info?file=FILE_ID"
If user provides raw VTT content, save to file first:
cat > /tmp/transcript.vtt << 'EOF'
<paste VTT content here>
EOF
python scripts/parse_transcript.py transcript.vtt
# Markdown (default) - best for reading/sharing
python scripts/parse_transcript.py transcript.vtt --format markdown
# JSON - best for further processing
python scripts/parse_transcript.py transcript.vtt --format json
# Plain text - minimal formatting
python scripts/parse_transcript.py transcript.vtt --format plain
--no-merge: Keep all entries separate (default merges consecutive same-speaker entries)--title "Meeting Name": Custom title for markdown output--output file.md: Write to file instead of stdout--stdin: Read VTT content from stdinSlack huddle transcripts use WebVTT format:
WEBVTT
00:00:01.000 --> 00:00:05.000
Alice: Hey everyone, let's get started.
00:00:05.500 --> 00:00:08.000
Bob: Sounds good, I have a few updates.
The script automatically:
python scripts/parse_transcript.py meeting.vtt > meeting.md
# Then analyze meeting.md for key points, action items, decisions
Parse to JSON for programmatic extraction:
python scripts/parse_transcript.py meeting.vtt --format json | \
jq '.entries[] | select(.text | contains("action") or contains("TODO"))'
for f in huddle_*.vtt; do
python scripts/parse_transcript.py "$f" --format json > "${f%.vtt}.json"
done
development
Deep research before planning. Launches parallel agents to search docs, web, and codebase, then synthesizes findings into actionable context.
development
This skill will be invoked when the user wants to create a PRD. You should go through the steps below. You may skip steps if you don't consider them necessary. 1. Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions. 2. Explore the repo to verify their assertions and understand the current state of the codebase. 3. Interview the user relentlessly about every aspect of this plan until you reach a shared understanding. Walk down e
development
--- name: refactor-pass description: Perform a refactor pass focused on simplicity after recent changes. Use when the user asks for a refactor/cleanup pass, simplification, or dead-code removal and expects build/tests to verify behavior. --- # Refactor Pass ## Workflow 1. Review the changes just made and identify simplification opportunities. 2. Apply refactors to: - Remove dead code and dead paths. - Straighten logic flows. - Remove excessive parameters. - Remove premature optimizati
development
# PRD to Issues Break a PRD into independently-grabbable GitHub issues using vertical slices (tracer bullets). ## Process ### 1. Locate the PRD Ask the user for the PRD GitHub issue number (or URL). Fetch it with `gh issue view <number>`. Read and internalize the full PRD content (with all comments). ### 2. Explore the codebase Read the key modules and integration layers referenced in the PRD. Identify: - The distinct integration layers the feature touches (e.g. DB/schema, API/backend, UI