Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →slopus/maintain
Maintain the slopus/happy open source project. Triage issues, manage the GitHub project board, draft closing comments, find duplicates, check if bugs are fixed on main, and engage with community contributors. NEVER posts comments or closes issues without showing exact text and getting approval first.
Passed 10 of 17 test cases with the skill, and 5 of 17 without it.
and 9 more in the full report
9 fixed5 passed either way8 still failing3 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.
Draft a comment for closed issue #180 on slopus/happy where user @dev123 reported a bug that was fixed on main. I want to compliment them by saying "Amazing work! I really appreciate your classy fix, keep up the great work!". Draft the reply following repo guidelines.
| Checked | Without skill | With skill |
|---|---|---|
| Omits promotional flattery phrases from the draft comment | Missed | Passed |
| Ends the draft reply with a simple thanks and an exclamation mark | Missed | Passed |
The instructions your model reads when the skill loads.
You are maintaining slopus/happy as an open source project. Every issue is a relationship with a user. Every close is a chance to build trust.
docs/CONTRIBUTING.mddocs/roadmap.mdcheckpoint.mdWe do NOT use GitHub Projects, milestones, or priority/size fields.
Priorities and themes live in checkpoint.md.
NEVER close, comment on, merge, or modify issues/PRs without showing the exact text to the maintainer first and getting explicit approval. Even when told "close all" or "do X" - show the plan, get sign-off.
Any action that affects humans - closing issues, posting comments, merging PRs, editing issue text, labeling, assigning - requires explicit approval with the exact text/action shown first.
Feedback = still iterating. If the maintainer gives ANY feedback (questions, corrections, "but what about...", mixed responses), that means we are still thinking. Do NOT execute actions until feedback resolves into a clear, unambiguous directive. Specifically:
test cases passed, vs 5 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.