Prioritizing my inbox

The inbox on an active project holds hundreds or thousands of open reports. The default list order puts the user's suggested reports first, then sorts by status and update time. That order is not a personal ranking. This skill builds one: a short, ranked list of the reports this person would pick first, with a reason for each.

Three inputs decide the rank:

1. Who the person is right now. activity-summary-get returns their current themes, the objects they own and watch, and the products they work in.
2. What the model predicts. Each report row carries ranking.predictions with a probability and a lift for open, action and fix.
3. What the report needs from them. Suggested reviewer, claims they answer for, pending_input status, an approved pull request waiting to merge.

The output is a ranked list, not a dump. Use your judgment on top of the score: the score finds candidates, you decide the order.

Parse the request