User Personas
phuryn/pm-skills
Create refined user personas from research data — 3 personas with JTBD, pains, gains, and unexpected insights.
Turns Riffrec screen, voice and event recordings into evidence for bug reports and requirements, and helps set up Riffrec when no recording exists yet.
Install Riffrec Feedback Analysis
$ npx skills add EveryInc/compound-engineering-plugin --skill ce-riffrec-feedback-analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install EveryInc/compound-engineering-plugin ce-riffrec-feedback-analysis --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ce-riffrec-feedback-analysis .claude/skills/ce-riffrec-feedback-analysis && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ce-riffrec-feedback-analysis" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-riffrec-feedback-analysis into .claude/skills/ce-riffrec-feedback-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ce-riffrec-feedback-analysis", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-riffrec-feedback-analysisType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add EveryInc/compound-engineering-plugin --skill ce-riffrec-feedback-analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install EveryInc/compound-engineering-plugin ce-riffrec-feedback-analysis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ce-riffrec-feedback-analysis .agents/skills/ce-riffrec-feedback-analysis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ce-riffrec-feedback-analysis" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-riffrec-feedback-analysis into .agents/skills/ce-riffrec-feedback-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ce-riffrec-feedback-analysis", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add EveryInc/compound-engineering-plugin --skill ce-riffrec-feedback-analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install EveryInc/compound-engineering-plugin ce-riffrec-feedback-analysis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ce-riffrec-feedback-analysis .cursor/skills/ce-riffrec-feedback-analysis && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ce-riffrec-feedback-analysis" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-riffrec-feedback-analysis into .cursor/skills/ce-riffrec-feedback-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ce-riffrec-feedback-analysis", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/EveryInc/compound-engineering-plugin.git --path skills/ce-riffrec-feedback-analysis--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add EveryInc/compound-engineering-plugin --skill ce-riffrec-feedback-analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install EveryInc/compound-engineering-plugin ce-riffrec-feedback-analysis --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ce-riffrec-feedback-analysis .gemini/skills/ce-riffrec-feedback-analysis && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ce-riffrec-feedback-analysis" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-riffrec-feedback-analysis into .gemini/skills/ce-riffrec-feedback-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ce-riffrec-feedback-analysis", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install EveryInc/compound-engineering-plugin ce-riffrec-feedback-analysisInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add EveryInc/compound-engineering-plugin --skill ce-riffrec-feedback-analysis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ce-riffrec-feedback-analysis .github/skills/ce-riffrec-feedback-analysis && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ce-riffrec-feedback-analysis" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-riffrec-feedback-analysis into .github/skills/ce-riffrec-feedback-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ce-riffrec-feedback-analysis", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add EveryInc/compound-engineering-plugin --skill ce-riffrec-feedback-analysis -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install EveryInc/compound-engineering-plugin ce-riffrec-feedback-analysis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ce-riffrec-feedback-analysis .opencode/skills/ce-riffrec-feedback-analysis && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ce-riffrec-feedback-analysis" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-riffrec-feedback-analysis into .opencode/skills/ce-riffrec-feedback-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ce-riffrec-feedback-analysis", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ce-riffrec-feedback-analysis- GitHub stars
- 25k
- Token cost
- ~695 tokens
- SKILL.md length
- 329 words
- Files
- 7 (incl. scripts, references)
- Skills in repo
- 37
- Repo updated
- First seen
- Licence
- MIT
At a glance
Turns Riffrec screen, voice and event recordings into evidence for bug reports and requirements, and helps set up Riffrec when no recording exists yet.
- Turning a recorded product feedback session into a structured bug report
- SKILL.md covers Choose the path and Common rules
- Runs Python scripts from its folder
- Extracting requirements from a longer screen and voice walkthrough
What it does
Riffrec is a capture tool that records synchronized screen, voice and event sessions into a `riffrec-*.zip` bundle, and this skill reads those bundles. It routes by input. With no recording yet it helps you install Riffrec, capture a session and share it. A short recording (under about 60 seconds) or a single issue gets a quick bug report. Longer recordings with several issues, requirements or a workflow walkthrough get an extensive analysis that continues into ce-brainstorm unless you asked only for extraction.
Quick analysis ends with one evidence-backed bug report and no lasting file unless requested, and a missing input or analyzer failure ends with an actionable blocker rather than a claim of partial success. Raw recordings, audio chunks, zip contents and extracted frames stay local and are not committed by default. Text artifacts such as analysis summaries can be committed when free of sensitive data, using repo-relative screenshot paths. The analyzer is `analyze_riffrec_zip.py`.
When your agent uses it
- Turning a recorded product feedback session into a structured bug report
- Extracting requirements from a longer screen and voice walkthrough
- Getting started with Riffrec when you have no recording yet
Example prompts
- “Analyze this riffrec zip and write a bug report from it.”
- “Pull the requirements out of this customer walkthrough recording.”
- “How do I install Riffrec and share a capture of this checkout problem?”
Requirements
- A Riffrec capture bundle, or Riffrec installed to record one
- Python for `analyze_riffrec_zip.py`
What it can do on your machine
Read from SKILL.md and the folder at commit 67035e9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Riffrec Feedback Analysis loads about 695 tokens when it runs, and up to ~4.9k if it reads all its reference files. Until then it costs about 68 tokens; SKILL.md has 329 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from EveryInc/compound-engineering-plugin at commit 67035e9, republished under its MIT licence (© EveryInc). 329 words, ~695 tokens.
Download SKILL.mdSave it as
.claude/skills/ce-riffrec-feedback-analysis/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- ce-riffrec-feedback-analysis
- 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.
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-brainstormhandoff 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.
Choose the path
Route from the input. Read only the references named for that route; do not load the other path references.
- 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/analyzer.md, thenreferences/quick-bug-report.md. - Extensive analysis — input is longer, contains multiple issues, requirements, or a workflow walkthrough, or the user wants requirements material. Read
references/analyzer.md, thenreferences/extensive-analysis.md. Continue intoce-brainstormunless the user explicitly asked only to extract or analyze artifacts.
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/orframes/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.
© EveryInc, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 6 other files (scripts, references) in skills/ce-riffrec-feedback-analysis of EveryInc/compound-engineering-plugin.
- SKILL.md
- references/analyzer.md
- references/compound-engineering-feedback-format.md
- references/extensive-analysis.md
- references/install-riffrec.md
- references/quick-bug-report.md
- scripts/analyze_riffrec_zip.py
Open the folder on GitHubat commit 67035e9
Compare with similar skills
Riffrec Feedback Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Riffrec Feedback Analysis this skillEveryInc/compound-engineering-plugin | 25k | — | ~695 | Automated safety check: Pass | MIT | |
| User Personasphuryn/pm-skills | 27k | — | ~762 | Automated safety check: Pass | MIT | |
| Prd V09 Feedback Loop Setupmattgierhart/PRD-driven-context-engineering | 180 | — | ~3.9k | Automated safety check: Pass | MIT | |
| Mom Testwondelai/skills | 2.4k | — | ~4.2k | Automated safety check: Pass | MIT | |
| QAwp-media/wp-rocket | 767 | — | ~552 | Automated safety check: Pass | GPL-2.0 | |
| Issue Triage WorkflowHack23/cia | 239 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Prd V09 Feedback Loop Setup
mattgierhart/PRD-driven-context-engineering
Establish channels and processes for capturing and processing post-launch feedback during PRD v0.9 Go-to-Market.
Mom Test
wondelai/skills
Talk to customers without leading them using Mom Test rules: discuss their life not your idea, ask about specifics in the past, and talk less.
QA
wp-media/wp-rocket
Run QA validation on a pull request — boots the local environment, tests acceptance criteria, and optionally posts the report as a PR comment.
Issue Triage Workflow
Hack23/cia
Triage GitHub issues: labeling, prioritization, assignment, and resolution tracking
Customer Research
Nexus-JPF/note-companion
When the user wants to conduct, analyze, or synthesize customer research.
More from EveryInc/compound-engineering-plugin
All 37 skills in this repoCompound Learning Writer
EveryInc/compound-engineering-plugin
Records one solved and verified problem as a durable learning in the repository, but only when the reasoning is not already clear from the final code, tests or docs.
Compound Learnings Refresh
EveryInc/compound-engineering-plugin
Audits a repo's stored learnings against the current codebase, fixes stale, overlapping or superseded docs and reports on every document.
Compound Engineering Prototype
EveryInc/compound-engineering-plugin
Builds a throwaway prototype at just the fidelity needed to settle a specific how-it-should-work-or-feel question, before committing to an approach other work will treat as fixed.
Compound Engineering Setup
EveryInc/compound-engineering-plugin
Checks Compound Engineering plugin health and repo-local config, or scaffolds a Compound Pack when you ask for one by id.
PR Babysitter
EveryInc/compound-engineering-plugin
Watches an open GitHub pull request over time, routing review comments and CI failures to other skills until the PR is ready to merge.
CE Brainstorm
EveryInc/compound-engineering-plugin
Turns a vague or ambitious feature idea into a requirements-only plan through dialogue with you, sized to the work, before any code is written.
Related
Categories
Questions about Riffrec Feedback Analysis
What does Riffrec Feedback Analysis do?
Turns Riffrec screen, voice and event recordings into evidence for bug reports and requirements, and helps set up Riffrec when no recording exists yet. zip` bundle, and this skill reads those bundles. It routes by input.
When should I use Riffrec Feedback Analysis?
Riffrec Feedback Analysis fits situations like: turning a recorded product feedback session into a structured bug report; extracting requirements from a longer screen and voice walkthrough; getting started with Riffrec when you have no recording yet.
How do I install Riffrec Feedback Analysis in Claude Code?
Run `npx skills add EveryInc/compound-engineering-plugin --skill ce-riffrec-feedback-analysis -a claude-code`. Or copy the skill folder (skills/ce-riffrec-feedback-analysis in EveryInc/compound-engineering-plugin) into .claude/skills/ce-riffrec-feedback-analysis in your project. Claude Code loads it when a task matches its description.
How do I install Riffrec Feedback Analysis in Codex?
Run `npx skills add EveryInc/compound-engineering-plugin --skill ce-riffrec-feedback-analysis -a codex`. Or copy the skill folder (skills/ce-riffrec-feedback-analysis in EveryInc/compound-engineering-plugin) into .agents/skills/ce-riffrec-feedback-analysis in your project. Codex loads it when a task matches its description.
Can I use Riffrec Feedback Analysis in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add EveryInc/compound-engineering-plugin --skill ce-riffrec-feedback-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ce-riffrec-feedback-analysis, .gemini/skills/ce-riffrec-feedback-analysis, .github/skills/ce-riffrec-feedback-analysis and .opencode/skills/ce-riffrec-feedback-analysis in your project.
What does Riffrec Feedback Analysis need to run?
Going by SKILL.md and its folder, Riffrec Feedback Analysis needs Python for the scripts in its folder. Our summary lists: A Riffrec capture bundle, or Riffrec installed to record one; Python for `analyze_riffrec_zip.py`.
Does Riffrec Feedback Analysis access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Riffrec Feedback Analysis safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Riffrec Feedback Analysis use?
Riffrec Feedback Analysis is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Riffrec Feedback Analysis use?
About 695 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.2k tokens, read only when the agent opens those files.
What are the alternatives to Riffrec Feedback Analysis?
Skills that share tags, products or a category with Riffrec Feedback Analysis: User Personas (phuryn/pm-skills, 27k stars), Prd V09 Feedback Loop Setup (mattgierhart/PRD-driven-context-engineering, 180 stars), Mom Test (wondelai/skills, 2.4k stars) and QA (wp-media/wp-rocket, 767 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Riffrec Feedback Analysis?
EveryInc (a GitHub organization) maintains it in EveryInc/compound-engineering-plugin, which has 25,436 GitHub stars. The repository holds 37 skills in this directory. The repository was last updated on October 8, 2026.
Source: EveryInc/compound-engineering-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.