ce-riffrec-feedback-analysis
Analyze Riffrec feedback captures from bundles or standalone recordings. Always load for `riffrec-*.zip`, `session.json` + `events.json` + `recording.webm` + `voice.webm` bundles, `.mp4`/`.mov`/`.webm` videos, `.m4a`/`.mp3`/`.wav` audio, or capture/share requests.
Security Assessment
About ce-riffrec-feedback-analysis
A consumption-side skill for turning raw product feedback captured with Riffrec into structured evidence for downstream agents. Riffrec is a capture tool that records synchronized screen, voice, and event sessions and emits a riffrec-*.zip bundle; this skill always loads for those bundles, for session.json + events.json + recording.webm + voice.webm sets, for standalone video (.mp4/.mov/.webm) or audio (.m4a/.mp3/.wav) files, and for capture or share requests. The goal is to convert unstructured recordings into requirements and bug reports that later agents can act on.
It routes input to one of three paths, reading only the matching reference. Setup is for users who have no recording yet and need to install Riffrec, capture a session, or share feedback. Quick bug report is for short recordings (under about 60 seconds), a single specific issue, or requests for something quick or just a transcription; it emits one concise bug report and skips the full artifact set. Extensive analysis is for longer recordings, multiple issues or requirements, or workflow walkthroughs, and always continues into the ce-brainstorm skill. When input is ambiguous, it inspects recording length and event count before choosing, and asks the user if still unclear.
All non-setup paths share one analyzer that ships in the skill's scripts/ directory and must be invoked by absolute path (setting SKILL_DIR in the same command, since the Bash working directory is the user's project and shell state does not persist). The analyzer accepts a Riffrec zip, a video, an audio file, or a meeting-notes markdown file, with an --output-dir option. Privacy rules keep raw recordings, audio chunks, and extracted frames local-only by default, committing only non-sensitive text and metadata artifacts with repo-relative screenshot paths. The Compound Engineering output format used by the extensive path is documented in a dedicated reference.
FAQ
What inputs does the skill accept?
Riffrec .zip bundles, session.json + events.json + recording.webm + voice.webm sets, standalone .mp4/.mov/.webm video, .m4a/.mp3/.wav audio, and meeting-notes markdown, as well as capture or share requests.
How does it decide between a quick and an extensive analysis?
Short recordings (under about 60 seconds), a single specific issue, or requests for quick or just-transcribe take the quick bug-report path; longer recordings, multiple issues, or workflow walkthroughs take the extensive path, which continues into ce-brainstorm.
How do I run the analyzer script?
Invoke it by absolute path, setting SKILL_DIR to the directory containing the SKILL.md in the same command, e.g. python "$SKILL_DIR/scripts/analyze_riffrec_zip.py" /path/to/input, because the Bash working directory is the user's project and shell state does not persist between calls.
What does the skill keep private?
By default it keeps raw recordings, audio chunks, zip contents, session dumps, and extracted frames local-only, and does not commit raw/ or frames/ directories unless the user explicitly asks and privacy is acceptable.
What is Riffrec?
Riffrec is a capture tool that records synchronized screen, voice, and event sessions and emits a riffrec-*.zip bundle; this skill is the consumption side that analyzes those captures.
Install ce-riffrec-feedback-analysis
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
everyinc/compound-engineering-plugin