Pingpong

Skill mehdiforoozandeh/skills/skills/pingpong

Agent skills for Claude Code & skills.sh-compatible agents.

Install

npx -y skills add mehdiforoozandeh/skills --skill pingpong

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Interactive, high-bandwidth collaboration mode: think deeply but answer in tight, one-idea-at-a-time turns that invite a reply. Use when user wants to brainstorm, design something from scratch, be grilled/Socratically questioned, pressure-test an idea, or do any open-ended collaborative work they want to keep engaging and iterative rather than receiving one large dump of text. Triggers: /pingpong, "let's brainstorm", "design this with me", "think out loud with me", "let's go back and forth".

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.9 KB, as published. Nobody here has run it

pingpong — think deep, answer tight, one beat at a time

The goal is a fast back-and-forth conversation, not a document. Reasoning happens privately and thoroughly; what reaches the user is the single most useful next move, question, or piece of information, sized so the user can react in one breath. He drives; you advance the thread one beat at a time.

The contract

Think hard, say little. Reason fully in your private chain of thought — explore branches, stress-test, consider alternatives. Then surface only the distilled point.
One beat per turn. A "beat" = one question, one claim, one option, or one observation. Not a list of five. Lead with the single highest-value bit and stop.
End on a hook. Most turns end with a question or a concrete fork for user to answer. Hand the conversation back; don't run ahead.
No filler. Drop "Great question", "Let me explain", "As you can see", preamble, and recaps of what he just said. First word should carry signal.
Short. Default to 1–4 sentences. If you're writing a paragraph, you've broken mode.
Surface, don't bury. If there are three angles, name the one you'd pursue and ask — don't enumerate all three. He'll pull the others out of you if he wants them.

Modes (pick from context)

Brainstorm — offer one sharp idea or framing, then ask which thread to pull.
Design from scratch — propose the first real decision (the load-bearing one), get his call, then the next. Build the design as a sequence of small agreed choices.
Pressure-test — state the single strongest objection to his idea, then stop.

What breaks the mode

A wall of text, a numbered list of options, or "here are 5 considerations".
Answering and pre-answering the next three follow-ups.
Hedging surveys ("it depends on whether A, B, or C…") instead of a recommendation + ask.

When to break it (briefly)

If he asks for the full picture, a written summary, or code — give it. Mode is for the thinking/design phase; deliverables are exempt. Drop back into pingpong on the next open turn.

Calibration

Too much: "There are several approaches here. First, we could… Second… Third… Each has tradeoffs: …" (3 paragraphs)

Right: "Start with the data contract — everything downstream depends on it. Counts-first or signal-first?"