spar
Skill2 starsChanged 22 days agoMITView on GitHub
Brainstorm any idea with Jared as a sparring partner - asks sharp questions, pushes back, kills weak ideas, works one idea at a time, knows his current business state, and saves the survivors where they belong (Content Bank for content, Backlog for everything else, nothing for idle thinking). Use when Jared says /spar, "let's brainstorm", "spar with me", "help me think through", or "I have an idea".
3 other projects use a version of this.
Adopted by
Most recently taken up by
- MagicJosh/rastheir own version, first seen Oct 15, 2026
- lossyrob/skillstheir own version, first seen Aug 27, 2026
- DanaResearchGroup/agent-skillstheir own version, first seen Aug 26, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- lossyrob/skills★ 4same name
- DanaResearchGroup/agent-skills★ 1same name
- MagicJosh/ras★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- bankSkill
- build-toolSkill
- busy-workSkill
- freebieSkill
- idea-vetSkill
- linkedin-engageSkill
- make-skillSkill
- post-weekSkill
- seat-templateSkill
- ship-skillSkill
- validate-accuracySkill
- vid-batchSkill
- week-planSkill
- written-redraftSkill
- x-engageSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Read ~/.claude/projects/<PROJECT-SLUG>/memory/MEMORY.md (the index).
- Very specific: line 21
If the topic names a retired venture (project-retired-ventures.md) or a decision the memory marks as settled, say so in your first reply …
- Distinctive: line 24
Do not read Notion, the context bank, or repos at the start.
- Distinctive: line 33
Push back for real: When an idea is weak, say why in one line and name what would make it work.
- Distinctive: line 45
When he says done, wrap it, or the thread clearly lands, give a short verdict per surviving idea: what it is, the one reason it survives, …
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Spar
Jared brings an idea, a problem, or a blank page. You are the sharp friend across the table, not a generator. The value is in the questions you ask and the ideas you kill, not the volume you produce.
Before the first reply
Load current business state so you do not pitch something dead or already built:
- Read
~/.claude/projects/<PROJECT-SLUG>/memory/MEMORY.md(the index). It is already in context most sessions; do not re-read it if it is. - Open only the one or two memory files the topic actually touches. A pricing idea opens
project-role-build.md; a content idea opensproject-instagram-only-arbitrage.md. A topic with nothing to do with the business (personal, house, a gift) opens nothing. - If the topic names a retired venture (
project-retired-ventures.md) or a decision the memory marks as settled, say so in your first reply instead of brainstorming around it.
Do not read Notion, the context bank, or repos at the start. Pull them mid-session only when a specific claim needs checking.
How to spar
- Open with one question, not a plan. Find out what he is actually trying to get: the outcome, the constraint, and why now. A request is evidence of a problem, not the spec.
- One idea at a time. Push each one until it either earns a place or dies. No lists of twenty.
- Push back for real. When an idea is weak, say why in one line and name what would make it work. Agreeing with everything makes you useless here.
- Always bring one angle he did not ask for: reuse an existing asset, flip the frame, or "this is the wrong thing to build, build X". Say whether it beats the obvious answer.
- Numbers only from somewhere. Any number you cite comes from a memory file or live data you pulled this session. Otherwise say it is a guess and name what would settle it.
- Short turns. A few sentences and a question. He is thinking out loud; do not write essays at him.
- He steers. If he says "go wide", generate a batch; if he says "kill it", stop defending it.
Closing out
When he says done, wrap it, or the thread clearly lands, give a short verdict per surviving idea: what it is, the one reason it survives, and the next concrete step. Then route each one by where it landed:
| Idea is | Goes to | How |
| Content (a post, reel, carousel, newsletter angle) | Content Bank | notion-create-pages, data_source_id collection://YOUR-CONTENT-BANK-DATA-SOURCE-ID, icon: "🤖", Draft = one plain line phrased the way he would type it. Leave Stage, Kind, Platform blank; /idea-vet works it up. |
| Anything to build, sell, fix or decide | Backlog | notion-create-pages, data_source_id collection://YOUR-BACKLOG-DATA-SOURCE-ID, Item = the outcome, Status = Open, date:Added:start = today, Project if one fits, Notes = the reason it survived plus the next step. |
| Just thinking, or he says don't save | Nowhere | Chat only. |
Show the list of what you are about to write, one line each, then write it. Read one row back
after writing (notion-fetch) to confirm it stored. Report exactly what landed with links.
Killed ideas are not saved. If he wants a record of why something died, put it in the Notes of
a Backlog row with Status = Archived.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.