App Feedback Admin
Read platform-admin feedback issues through the trusted HTTP admin API, summarize user...
Install
npx skills add Jamailar/Beav --skill app-feedback-admin -g -a claude-code -y- Repository
- Jamailar/Beav2.2k
- Category
- Design
- Updated
- 3d ago
- License
- See repository
- Context cost
- Lightabout 934 tokens
- Runs scripts
- Yes, review before use
What it does
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.
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_KEYinto 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:
.redbox-dev/feedback-admin.env
Expected variables:
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
- Load the local env file without printing secrets.
- Fetch the newest feedback list:
python3 desktop/skills/app-feedback-admin/scripts/fetch_feedback.py list --page-size 20
- For tickets that look actionable, fetch details:
python3 desktop/skills/app-feedback-admin/scripts/fetch_feedback.py detail <feedback_id>
