ce-riffrec-feedback-analysis

Converts Riffrec session recordings into transcripts, screenshots, and structured requirements artifacts.

Updated May 11, 2026
One-click install
npx skills add https://github.com/mmnavarr/harness --skill ce-riffrec-feedback-analysis-mmnavarr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-riffrec-feedback-analysis
Source: https://github.com/mmnavarr/harness/tree/main/skills/ce-riffrec-feedback-analysis
Command: npx skills add https://github.com/mmnavarr/harness --skill ce-riffrec-feedback-analysis-mmnavarr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Raw product feedback recordings (screen capture, voice, and event logs) are hard to turn into actionable engineering input. This Skill analyzes Riffrec zip bundles, standalone video/audio, or meeting notes and produces structured evidence: transcripts, high-signal screenshots, candidate findings, and requirements-kickoff documents. ## Core Features & Use Cases - Three routing paths: setup guidance for installing Riffrec, a quick bug report path for short single-issue recordings, and an extensive analysis path producing a full Compound Engineering artifact set. - Automated evidence extraction: transcribes media via the OpenAI transcription API (with chunked fallback for long files), selects high-signal moments from click/network/console events, and extracts screenshots with ffmpeg. - Requirements handoff: generates analysis.md, problem-analysis.md, source-materials.md, and requirements-kickoff.md, then hands off to the ce-brainstorm skill for requirement confirmation. - Use Case: A user drops a riffrec-*.zip containing a 5-minute session where they verbalize a broken button. The Skill transcribes the voice track, extracts frames near the failed clicks, and produces a requirements document with timestamped evidence ready for brainstorming. ## Quick Start Analyze the attached riffrec-abc123.zip recording and turn it into structured product feedback.

Frequently Asked Questions about ce-riffrec-feedback-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a Riffrec zip recording for product feedback?▼

Run python scripts/analyze_riffrec_zip.py with the path to your riffrec-*.zip file. The script extracts the bundle, transcribes the voice track, selects high-signal moments from events, and writes analysis.md plus requirements artifacts to an output directory.

What input formats does the Riffrec analyzer support?▼

The analyzer accepts Riffrec zip bundles, standalone video files (.webm, .mp4, .mov, .mkv, .avi), audio files (.mp3, .m4a, .wav, .ogg, .flac), and meeting notes in .txt or .md format. It classifies the source automatically and adjusts extraction accordingly.

Why is the transcript missing from my Riffrec analysis output?▼

Transcription requires the OPENAI_API_KEY environment variable and curl installed. Without the key, the script marks transcription as skipped and continues with event and frame analysis only. Long files that exceed API limits are retried in ffmpeg-split chunks.

When should I use the quick bug report path instead of extensive analysis?▼

Use the quick path for recordings under about 60 seconds describing a single issue, or when the user asks for a quick transcription. It writes to a temp directory and emits one concise bug report, skipping the requirements-kickoff and brainstorm handoff.

Does the analyzer commit extracted screenshots and raw recordings to the repo?▼

No. Raw zip contents, audio chunks, and extracted frames stay local-only by default and should not be committed unless the user explicitly requests it. Only text artifacts like analysis summaries and requirements docs may be committed when they contain no sensitive data.