feedback

Collect and structure user feedback into redacted reports via product_feedback.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cirne/brain-app --skill feedback-cirne
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feedback
Source: https://github.com/cirne/brain-app/tree/main/assets/user-skills/feedback
Command: npx skills add https://github.com/cirne/brain-app --skill feedback-cirne

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams struggle to capture, redact, and file user feedback consistently, leading to scattered reports and inconsistent data.

Core Features & Use Cases

  • Structured Feedback Drafting: Use the product_feedback tool to create a well-formed, redacted report ready for review.
  • Safe Redaction & Review: Automatically redact sensitive details and present a reviewable draft to the user before submission.
  • Persistent Archiving: Save a copy of the submitted report to the wiki path wiki/feedback/issue-<id> for future reference.
  • Operational Guidance: Invoke the /wiki skill to assist users in browsing the vault wiki if needed.

Quick Start

Draft a new bug report for the feature request you discussed with the user, then review and submit the redacted draft.

Frequently Asked Questions about feedback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I draft and submit structured product feedback automatically?▼

Yes, redacted feedback reports are saved directly to the wiki path wiki/feedback/issue-<id> for persistent archiving. This ensures all submitted product feedback remains accessible for future reference and team review.

Can I review a feedback report before it gets submitted?▼

This Skill supports capturing bug reports, feature requests, and general product ideas. It structures all feedback types into a formal report using the product_feedback tool before saving a copy to the wiki vault.

Does the feedback filing process require any dependencies or prior setup?▼

The feedback filing process requires no dependencies or prior setup. It operates independently to collect, redact, and submit structured feedback, though it can invoke the /wiki skill to help browse the vault wiki if needed.

What is the best way to capture and redact user feedback consistently?▼

The best way to capture and redact user feedback consistently is using a structured reporting tool that enforces a formal draft and review workflow. This prevents scattered reports and inconsistent data by archiving redacted copies to a wiki.