Skill Tracer
Skills › Compound Engineering › ce-riffrec-feedback-analysis

ce-riffrec-feedback-analysis

skill · 33 lines · MIT · skills/ce-riffrec-feedback-analysis/SKILL.md

The facts

Its description

Analyze recorded product feedback into evidence for bugs and requirements. Use when a Riffrec capture or other screen, voice, or notes artifact needs interpretation. Use for Riffrec setup, capture, or sharing help when no recording exists yet.

The description the agent reads to decide when to use it.

From its settingsline 3

When it starts

The agent reaches for this skill when someone brings a recorded feedback artifact — a Riffrec zip, a screen/voice capture, video, audio, or meeting notes — and wants it interpreted into bug evidence or requirements, or when they ask how to install Riffrec and capture feedback because no recording exists yet.

Things a person might say (the model's guesses)

  • “Here's the riffrec zip from my session, can you pull the bugs out of it?”
  • “How do I install Riffrec so I can start recording feedback in our app?”
  • “I recorded a two-minute walkthrough of the checkout flow — turn it into requirements.”

A model's summary of when it is used.

A model's reading

Files it mentions

references/install-riffrec.md, references/analyzer.md, references/quick-bug-report.md, references/extensive-analysis.md, references/compound-engineering-feedback-format.md

Files the text names, such as ones to read or write. Found by matching words, so treat them as pointers.

Found by matching wordsline 21 line 22 line 23 line 33

Stops for a person

1 line stops to ask a person

Lines that stop and wait for a person before going on. Found by matching words, so treat them as pointers.

Found by matching wordsline 25

What it leads to

Other skills this one hands off to, calls, requires or offers instead, as a model read them.

A model's reading

Licence

MIT, from LICENSE

The terms its author shares it under, which let it be shown here.

From the repositorylicence text
Other files in this skill (6) Close

The text

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1---
2name: ce-riffrec-feedback-analysis
3description: "Analyze recorded product feedback into evidence for bugs and requirements. Use when a Riffrec capture or other screen, voice, or notes artifact needs interpretation. Use for Riffrec setup, capture, or sharing help when no recording exists yet."
4---
5
6# Riffrec Feedback Analysis
7
8Turn raw product feedback into structured evidence for downstream agents. 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 `riffrec-*.zip` bundle.
9
10**Done:**
12- Setup ends with a current capture/share path.
13- Quick analysis ends with one evidence-backed bug report and no durable artifact unless requested.
14- Extensive analysis ends with the complete evidence set and a `ce-brainstorm` handoff unless the user asked for extraction only.
15- A missing input, analyzer failure, or unresolved route ends with an actionable blocker rather than a partial success claim.

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.

Done:

  • Setup ends with a current capture/share path.
  • Quick analysis ends with one evidence-backed bug report and no durable artifact unless requested.
  • Extensive analysis ends with the complete evidence set and a ce-brainstorm handoff unless the user asked for extraction only.
  • A missing input, analyzer failure, or unresolved route ends with an actionable blocker rather than a partial success claim.
Raw lines 1 to 16
Names a skill ce-brainstorm :14
17## Choose the path
19Route from the input. Read only the references named for that route; do not load the other path references.
21- **Setup** — user has no recording yet and asks how to install Riffrec, capture a session, or share feedback. Read `references/install-riffrec.md`.
22- **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/analyzer.md`, then `references/quick-bug-report.md`.
23- **Extensive analysis** — input is longer, contains multiple issues, requirements, or a workflow walkthrough, or the user wants requirements material. Read `references/analyzer.md`, then `references/extensive-analysis.md`. Continue into `ce-brainstorm` unless the user explicitly asked only to extract or analyze artifacts.
25When 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.

Choose the path

Route from the input. Read only the references named for that route; do not load the other path references.

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.

Raw lines 17 to 26
Reads a file references/install-riffrec.md :21
Reads a file references/analyzer.md :22
Reads a file references/quick-bug-report.md :22
Reads a file references/extensive-analysis.md :23
Names a skill ce-brainstorm :23
Involves a person ask the user :25
27## Common rules
29- 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.
30- Text/metadata artifacts (requirements kickoff material, analysis summaries, problem analyses, source manifests) may be committed when they are needed for traceability and contain no sensitive data.
31- Use repo-relative screenshot paths in any committed doc so later agents can open the evidence without absolute local paths.
33The Compound Engineering output format used by the extensive path is documented in `references/compound-engineering-feedback-format.md`.

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 kickoff material, 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.

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

Raw lines 27 to 33
Reads a file references/compound-engineering-feedback-format.md :33

From EveryInc/compound-engineering-plugin at 3449230, 2026-10-31. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.