app-feedback-admin
/app-feedback-admin
Read platform-admin feedback issues through the trusted HTTP admin API, summarize user reports, and turn them into RedBox/RedConvert repair and iteration plans. Use when the user asks to read app feedback, triage feedback tickets, inspect remote feedback context, or prepare fix/iteration plans from feedback. This skill must keep FEEDBACK_ADMIN_API_KEY server-side/local only and must not place it in app UI, frontend code, desktop client code, logs, commits, or shared artifacts.
- Author
- jamailar ↗
- Repository
- beav ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/fetch_feedback.py
What it does and when to use it
Read platform-admin feedback issues through the trusted HTTP admin API, summarize user reports, and turn them into RedBox/RedConvert repair and iteration plans. Use when the user asks to read app feedback, triage feedback tickets, inspect remote feedback context, or prepare fix/iteration plans from feedback. This skill must keep FEEDBACK_ADMIN_API_KEY server-side/local only and must not place it in app UI, frontend code, desktop client code, logs, commits, or shared artifacts.
Original author description
Read platform-admin feedback issues through the trusted HTTP admin API, summarize user reports, and turn them into RedBox/RedConvert repair and iteration plans. Use when the user asks to read app feedback, triage feedback tickets, inspect remote feedback context, or prepare fix/iteration plans from feedback. This skill must keep FEEDBACK_ADMIN_API_KEY server-side/local only and must not place it in app UI, frontend code, desktop client code, logs, commits, or shared artifacts.
How it works
- Hard Boundaries
- Local Environment
- Read Workflow
- Output Shape
- Optional Write Actions
SKILL.md preview
--- name: app-feedback-admin description: Read platform-admin feedback issues through the trusted HTTP admin API, summarize user reports, and turn them into RedBox/RedConvert repair and iteration plans. Use when the user asks to read app feedback, triage feedback tickets, inspect remote feedback context, or prepare fix/iteration plans from feedback. This skill must keep FEEDBACK_ADMIN_API_KEY server-side/local only and must not place it in app UI, frontend code, desktop client code, logs, commits, or shared artifacts. allowed-tools: [bash, redbox_fs] --- # app-feedback-admin Use this skill to read remote feedback tickets and convert them into concrete RedBox/RedConvert repair and iteration work. Activate this skill when the user asks to read app feedback, process feedback tickets, inspect remote feedback context, or turn feedback into a repair or iteration plan. ## Hard Boundaries - Never put `FEEDBACK_ADMIN_API_KEY` into desktop app code, renderer UI, frontend bundles, committed docs, screenshots, transcripts, or generated plans. - Treat the feedback API as an operator-only channel. It is suitable for local scripts, CI/ops jobs, or trusted server automation only. - Default to read-only triage. Do not update ticket status, add comments, or review/reward feedback unless the user explicitly asks for a write action in the current turn. - Do not infer product root cause only from the ticket text. For bugs, cross-check RedBox code and local runtime evidence where relevant, especially `~/Library/Application Support/RedBox/session-transcripts/`, `session-bundles/`, and state DB/files. ## Local Environment Use the ignored env file at repo root: ```text .redbox-dev/feedback-admin.env ``` Expected variables: ```bash API_BASE="https://..." FEEDBACK_ADMIN_API_KEY="..." FEEDBACK_APP_SLUG="xitun" ``` If the env file is missing or incomplete, stop and ask the user for the missing local configuration. Do not invent an API base or app slug. ## Read Workflow 1. Load the local env file without printing secrets. 2. Fetch the newest feedback list: ```bash python3 desktop/skills/app-feedback-admin/scripts/fetch_feedback.py list --page-size 20 ``` 3. For tickets that look actionable, fetch details: ```bash python3 desktop/skills/app-feedback-admin/scripts/fetch_feedback.py detail <feedback_id> ``` 4. Classify each ticket into one of: - `bug`: reproducible product failure, crash, wrong result, data loss, broken workflow. - `ux`: confusing UI, missing affordance, excessive friction. - `feature`: new capability or workflow expansion. - `ops`: account, billing, deployment, API, notification, or backend process issue. - `invalid`: duplicate, unclear, spam, unsupported, or not enough evidence. 5. Map actionable items to RedBox modules: - desktop UI: `desktop/src/pages/*`, `desktop/src/components/*`, `desktop/src/bridge/ipcRenderer.ts` - Tauri host: `desktop/src-tauri/src/commands/*`, `runtime/*`, `persistence/*`, `events/*` - AI runtime: `desktop/src-tauri/src/agent/*`, `skills/*`, `tools/*`, `mcp/*`, `subagents/*` - media/video: `desktop/src-tauri/src/media*`, editor/runtime files - plugin intake: `Plugin/*` - website/release: `RedBoxweb/*`, `private/scripts/hybrid-release/*` 6. Produce a concrete plan, not loose advice. Include ticket ids, severity, evidence, suspected module, implementation target files, verification steps, and whether it is a fix or product iteration. ## Output Shape Use this shape unless the user asks for a different one: ```markdown **Feedback Triage** - <id>: <status/priority> <classification> - <one-line user problem> **Repair Plan** - <module>: <specific fix>, files: <paths>, verification: <checks> **Iteration Plan** - <module>: <specific product improvement>, files/docs: <paths>, risk: <risk> **Needs User Decision** - <question or tradeoff, only when blocked> ``` Keep user-facing wording concise. Prefer evidence and next actions over explanatory text. ## Optional Write Actions Only after explicit user approval, use the admin API to: - add internal comments for investigation notes, - add user-visible replies, - update status/priority/category, - review as `useless`, `thanks`, or `useful`. Write actions must include a short audit note and must not expose secrets.
Files in this package (3)
- SKILL.md 4 KB
- agents/openai.yaml 1 KB
- scripts/fetch_feedback.py 7 KB
Versions
The database has no other skills named app-feedback-admin.
Database snapshot: 13.11.2026 · package version 7ea0ee67357b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90feedback-triage
Turn a batch of user feedback (Discord threads, DMs, article comments, support tickets) into a triage checklist. Produces TWO artifacts — a full private one with attribution and tracker links, and a sanitized public one safe for docs/. Use when asked to triage feedback, build a… - 100user-feedback-synthesizer
Analyze collections of user feedback to identify patterns and themes. Use when you have user feedback from multiple sources that needs synthesis. - 100feedback
Triage and respond to the user-feedback queue — pull open feedback, detect items already fixed but never marked, route translation-requests and metadata-corrections, mark items resolved, and (on approval) email submitters. Use when asked to check/triage/answer/clear feedback,… - 90company-setup
Build the company memory every teammate reads, with an admin. Use only when an admin asks to set up (or refresh) company memory. - 100produck-feedback
Use when acting on real user feedback — you have a Produck feedback ticket or URL, or the user wants to fix something users complained about or build a feature users asked for. Pulls full feedback context through the Produck MCP and drives a feedback → aligned PRD → build loop.… - 96pm-iteration
Use when: 需要规划迭代内容、制定迭代排期、明确迭代优先级、从需求到排期的落地 Do NOT use when: 迭代已由团队自行规划、无需系统化管理