Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/robius-event-action
CRITICAL:
Passed 21 of 22 test cases with the skill, and 13 of 22 without it.
and 11 more in the full report
9 fixed12 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
When processing a list of incoming actions inside `handle_actions`, what control flow pattern should be used after successfully matching and handling an action?
| Checked | Without skill | With skill |
|---|---|---|
| Uses the continue statement after handling an action inside the loop | Missed | Passed |
The instructions your model reads when the skill loads.
Best practices for event handling and action patterns in Makepad applications based on Robrix and Moly codebases.
Source codebases:
Use this skill when:
use makepad_widgets::*;
/// Actions emitted by the Message widget
#[derive(Clone, DefaultNone, Debug)]
pub enum MessageAction {
/// User wants to react to a message
React { details: MessageDetails, reaction: String },
/// User wants to reply to a message
Reply(MessageDetails),
/// User wants to edit a message
Edit(MessageDetails),
/// User wants to delete a message
Delete(MessageDetails),
/// User requested to open context menu
OpenContextMenu { details: MessageDetails, abs_pos: DVec2 },
/// Required default variant
None,
}
test cases passed, vs 13 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.