Go through a feedback list (Notion, Google Doc, Linear, GitHub issue, pasted notes) and fix the real bugs, propose small UX changes, and flag the rest. Use when someone shares a feedback link or paste and says "address this feedback", "fix the bugs in this doc", or runs /address-feedback. For Slack feedback channels use review-latest-feedback; for specific Slack threads use address-feedback-with-replies.
96%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Take a pile of feedback, fix what is objectively broken, verify it, and report
back briefly. Lean toward fixing, but don't agree with every suggestion or
bundle unrelated cleanups. If no link or text was given, ask for it. Use the
matching connector (Notion, Drive, Linear, gh, Slack) rather than scraping
authenticated pages. Slack reactions and replies follow review-latest-feedback.
Read the whole source, including comments, screenshots, and linked recordings. The error text in a screenshot is often the diagnosis.
Then check whether it was reported before; the same defect gets filed weeks apart by different people, and one came back fifteen times. Search three months back: the source, Sentry, Analytics errors, and merged PR titles, using the feature name, error text, and surface separately.
Checklist each item: symptom, expected behavior, evidence, owning surface.
:upvote:) is a request to
build the smallest version.For data, permissions, or lifecycle feedback, check the whole capability before calling it UX: does the action exist when a control is missing, and do owner, shared, and non-owner access behave? Use safe fixtures, never another user's production data. Possible cross-user exposure is a security bug.
Before asking the reporter anything, read the full thread and every accessible attachment, and list what is already known: surface, repro, exact error, run IDs. Never ask for something already there. If someone in the thread already named the cause, fixed it, or is fixing it, verify that and continue instead of asking again. If a run ID is given, inspect that run first.
When one specific detail still blocks the fix, ask one plain question, and only one pending question per thread. Don't ask a subjective question just to choose between plausible designs.
When it smells like an error, search Sentry (org builder-io) and Analytics
list-error-issues / get-error-issue by route, stack symbol, and error text.
Cite the match and its source. An unreadable source is "unavailable", never
"no match"; don't invent matches or repro steps.
Name the smallest invariant that explains the report and the boundary that owns it.
Never turn one data point into a global agent rule.
Reproduce first where you can, keep each fix narrow and mapped to an item, and
add a focused test when the risk warrants it. Verify as verifying-changes describes: a test that fails before and passes
after, or the flow working in the running app. For UI, look at the real screen
with a browser tool you already have; don't script browser automation for a
small fix. Reading the code is not verification.
For approved UX work, make the smallest change that clarifies the current state
or next step: remove competing elements before adding controls or text, and put
secondary actions in a menu or popover. Read frontend-design.
Reply with a status, not an implementation report: one plain line per item, no file paths, PR numbers, or test counts unless asked:
## Feedback Status
- <item> - Fixed. It will be on beta shortly after it merges.
- <item> - Needs a person: <what's needed, from whom>.
- <item> - Needs your answer: <one question>.
- <item> - Not planned.Don't say Fixed until it's verified.
BuilderIO/agent-native
cf9ff10
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.