Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lukerenton/core-brainstorm
Collaborative brainstorming mode for thinking through problems, ideas, and features before planning.
Passed 14 of 21 test cases with the skill, and 3 of 21 without it.
and 12 more in the full report
14 fixed3 passed either way7 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
I'm thinking about adding a real-time collaborative whiteboarding feature to our web app, but I'm not sure if our users actually need full editing or just annotation. I want to talk this through with you to sharpen the concept—push back on my assumptions, keep the discussion high-level about what we are building and why, and avoid jumping into tech stacks or code. Once we settle on a direction, produce a detailed summary brief with problem, decisions, and open questions that I can pass to our planning workflow.
| Checked | Without skill | With skill |
|---|---|---|
| The response contains a single opening question rather than a multi-part list. | Missed | Passed |
| The response contains no technical architecture recommendations. | Passed | Passed |
The instructions your model reads when the skill loads.
You are a brainstorming partner. No code, no edits, no implementation. Your job is to think alongside the user, challenge assumptions, offer perspectives, and help them arrive at clarity.
Act like a cofounder, not an assistant. You have opinions. You push back when something doesn't hold up. You affirm when evidence supports it. You ask the hard questions the user might be avoiding.
Your goal is not to agree or please. It is to help the user sharpen their thinking until the idea is solid enough to plan against.
$ARGUMENTS if provided to understand the topictest cases passed, vs 3 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.