Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
everyinc avatar

Ce Riffrec Feedback Analysis

  • 2.1k installs
  • 23.9k repo stars
  • Updated August 5, 2026
  • everyinc/compound-engineering-plugin

ce-riffrec-feedback-analysis is an agent skill that Riffrec product-feedback workflow. ALWAYS load when the user posts a `riffrec-*.zip`, a bundle with `session.json` + `events.json` + `recording.webm` + `voice.webm`, a

About

The ce-riffrec-feedback-analysis skill. Riffrec product-feedback workflow. ALWAYS load when the user posts a `riffrec-*.zip`, a bundle with `session.json` + `events.json` + `recording.webm` + `voice.webm`, a video/audio recording for product feedback, or asks how to capture and share Riffrec sessions. Routes between setup, quick bug report, and extensive analysis. This skill is the consumption side of [Riffrec](https://github.com/kieranklaassen/riffrec), a capture tool that records synchronized screen + voice + event sessions and emits a bundle. Read only that reference; do not load the others. - **Setup** - user has no recording yet and asks how to install Riffrec, capture a session, or share feedback. - **Quick bug report** - input is a short recording (under ~60 seconds), the user describes a single specific issue, or asks for "quick", "small", or "just transcribe". Emit one concise bug report; skip the full artifact set and brainstorm handoff. - **Extensive analysis** - input is a longer recording, contains multiple issues / requirements / workflow walkthroughs, or the user wants requirements or brainstorm material.

  • Setup - user has no recording yet and asks how to install Riffrec, capture a session, or share feedback. Read `referen
  • Use repo-relative screenshot paths in any committed doc so later agents can open the evidence without absolute local pat
  • Read only that reference; do not load the others.
  • - **Setup** - user has no recording yet and asks how to install Riffrec, capture a session, or share feedback.
  • Emit one concise bug report; skip the full artifact set and brainstorm handoff.

Ce Riffrec Feedback Analysis by the numbers

  • 2,086 all-time installs (skills.sh)
  • +69 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #234 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

ce-riffrec-feedback-analysis capabilities & compatibility

Capabilities
setup user has no recording yet and asks how t · use repo relative screenshot paths in any commit · read only that reference; do not load the others · **setup** user has no recording yet and asks · emit one concise bug report; skip the full artif
Use cases
documentation · planning · orchestration
From the docs

What ce-riffrec-feedback-analysis says it does

Read only that reference; do not load the others.
SKILL.md
npx skills add https://github.com/everyinc/compound-engineering-plugin --skill ce-riffrec-feedback-analysis

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs2.1k
repo stars23.9k
Security audit1 / 3 scanners passed
Last updatedAugust 5, 2026
Repositoryeveryinc/compound-engineering-plugin

How do I apply ce-riffrec-feedback-analysis correctly using the SKILL.md workflows and reference files?

Riffrec product-feedback workflow. ALWAYS load when the user posts a `riffrec-*.zip`, a bundle with `session.json` + `events.json` + `recording.webm` + `voice.webm`, a video/audio recording for produc

Who is it for?

Developers and software engineers working with ce-riffrec-feedback-analysis patterns from the skill documentation.

Skip if: Skip when cached docs are empty, boilerplate-only, or outside the skill documented scope.

When should I use this skill?

Riffrec product-feedback workflow. ALWAYS load when the user posts a `riffrec-*.zip`, a bundle with `session.json` + `events.json` + `recording.webm` + `voice.webm`, a video/audio recording for product feedback, or asks

What you get

Grounded ce-riffrec-feedback-analysis guidance with highlights, triggers, and evidence quotes from SKILL.md.

  • severity-tagged findings doc
  • Requirements Kickoff markdown
  • traceable requirement candidates

By the numbers

  • Uses P0 through P3 severity levels on structured findings

Files

SKILL.mdMarkdownGitHub ↗

Riffrec Feedback Analysis

Turn raw product feedback into structured evidence for downstream agents. This skill is the consumption side of Riffrec, a capture tool that records synchronized screen + voice + event sessions and emits a riffrec-*.zip bundle.

Choose the path

Route to the matching reference based on the input. Read only that reference; do not load the others.

  • Setup — user has no recording yet and asks how to install Riffrec, capture a session, or share feedback. Read references/install-riffrec.md.
  • Quick bug report — input is a short recording (under ~60 seconds), the user describes a single specific issue, or asks for "quick", "small", or "just transcribe". Read references/quick-bug-report.md. Emit one concise bug report; skip the full artifact set and brainstorm handoff.
  • Extensive analysis — input is a longer recording, contains multiple issues / requirements / workflow walkthroughs, or the user wants requirements or brainstorm material. Read references/extensive-analysis.md. Always continue into the ce-brainstorm skill.

When the input is ambiguous (e.g., a zip arrived without context), inspect the recording length and event count before choosing. If still unclear, ask the user which path applies before running anything heavy.

Common rules

  • Keep raw recordings, audio chunks, zip contents, session dumps, and extracted screenshots local-only by default. Do not commit raw/ or frames/ directories unless the user explicitly asks and privacy is acceptable.
  • Text/metadata artifacts (requirements docs, analysis summaries, problem analyses, source manifests) may be committed when they are needed for traceability and contain no sensitive data.
  • Use repo-relative screenshot paths in any committed doc so later agents can open the evidence without absolute local paths.

Analyzer entrypoint

All non-setup paths share the same analyzer:

python scripts/analyze_riffrec_zip.py /path/to/input

Accepted inputs: a Riffrec .zip, an .mp4 / .mov / .webm video, an .m4a / .mp3 / .wav audio file, or a meeting-notes .md. Use --output-dir <dir> to control where artifacts land. In repos with docs/brainstorms/, the default is docs/brainstorms/riffrec-feedback/. The quick path overrides the output dir to a temp location so nothing pollutes the repo.

The Compound Engineering output format used by the extensive path is documented in references/compound-engineering-feedback-format.md.

Related skills

How it compares

Use ce-riffrec-feedback-analysis when Riffrec evidence must become ranked requirements instead of manual transcript summarization.

FAQ

Who is ce-riffrec-feedback-analysis for?

Developers and software engineers working with ce-riffrec-feedback-analysis patterns from the skill documentation.

When should I use ce-riffrec-feedback-analysis?

Riffrec product-feedback workflow. ALWAYS load when the user posts a `riffrec-*.zip`, a bundle with `session.json` + `events.json` + `recording.webm` + `voice.webm`, a video/audio recording for product feedback, or asks how to capture and share Riffrec sessions. Routes between se

Is ce-riffrec-feedback-analysis safe to install?

Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.