Saltar al contenido
Marketplace

ce-riffrec-feedback-analysis

de everyinc

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.

Esta skill incluye scripts que tu agente puede ejecutar. Ver qué archivos

Resumen

SKILL.mdLeída en cef001f

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.

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, then references/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, then references/extensive-analysis.md. Continue into ce-brainstorm unless 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/ 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.

Archivos 7 archivos

Instálala a mano

Deska ejecuta esto por ti, para cada agente que elijas. Para ejecutarlo tú en una terminal:

npx skills add everyinc/compound-engineering-plugin --skill ce-riffrec-feedback-analysis

Más de everyinc

  • ce-brainstormeveryincExplore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm or scope what to build. Not for executing already-specified work. Use ce-pov for a verdict on adopting a named external technology.3,800 instalaciones en skills.sh0
  • ce-planeveryincCreate structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan; prefer ce-brainstorm for exploratory framing.3,600 instalaciones en skills.sh0
  • ce-code-revieweveryincReview a named diff or PR for bugs, regressions, tests, and standards. Use when asked to review code or when a shipping skill needs a review receipt. Use when asked to apply this review's findings locally. Use ce-resolve-pr-feedback for feedback already left on a PR.3,500 instalaciones en skills.sh0
  • ce-compoundeveryincDocument a solved problem as a durable repo learning. Use when verified work produced non-obvious reasoning absent from its final code, tests, or existing docs; avoid routine fixes whose artifacts already explain the lesson.3,500 instalaciones en skills.sh0
  • ce-doc-revieweveryincReview requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.3,500 instalaciones en skills.sh0
Todas las skills de everyinc