skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
hyperb1iss/hyperskills615 installs

brainstorm

Use this skill when exploring an open product or architecture question before choosing an approach. Activates on mentions of brainstorm, ideate, design session, explore options, what should we build, how should we approach, let's think about, new project, architecture decision, or design exploration. Skip it for a clear implementation request.

How do I install this agent skill?

npx skills add https://github.com/hyperb1iss/hyperskills --skill brainstorm
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill provides a structured framework for brainstorming and architecture exploration. It includes instructions that prioritize user input over established safety or approval gates, which is identified as a minor prompt injection concern. It also references external resources from trusted technology organizations.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerpass

    1 file scanned · No issues

  • ZeroLeakspass

    Score: 93/100 · 2 sections analyzed

What does this agent skill do?

Collaborative Brainstorming

Turn uncertainty into a useful choice or a focused experiment.

The user's instructions take precedence over this skill; carry existing authorization forward and do not add approval gates.

Choose the Work Shape

SituationUseful output
The user wants open explorationDistinct directions, concrete tradeoffs, open questions
The user holds a picture they cannot articulateAn interview, or rendered directions with their styles named
The user says they do not know the domainA blind-spot pass: the questions they did not ask, by consequence
The problem is clear, the mechanism is notA recommendation and the evidence that would overturn it
One assumption determines feasibilityA small test of that assumption before any design
Approach chosen, implementation authorizedContinue into implementation
The user asks why something happensDiagnose the cause before designing a fix

Ground the Question

Recall prior decisions through the installed Sibyl skill when configured (sibyl context "<decision>" --intent plan), and recheck any volatile claim it returns. Find the nearest existing instance and the prior work before generating alternatives.

Translate taste into examples and observations. For "smooth," identify the interaction and visible delay. For "gorgeous," inspect the reference and name the composition, motion, or typography worth preserving. Quantification helps where a metric represents the experience; a proxy metric does not replace the experience itself. A reference the user supplies is the specification: match it before reinterpreting it, and when a concept could move, show it moving.

Treat the user's hunch as a hypothesis: a decisive check can confirm part of it and reject the rest, so report both. Do not downgrade an explicit "use X" to a preference because it was written casually; if it conflicts with feasibility, say so before designing around it.

Elicit what the user knows but did not write. A prompt is a map of the problem, and the user holds constraints, taste, and context they treat as obvious; a wrong guess at those costs a rebuilt slice. When the user signals ambiguity or a picture they cannot describe, interview them: a chain of specific, answerable questions through the host's question tool, or a rendered artifact that puts each question beside the diagram, snippet, or option it concerns. Stop when answers stop changing the design. For taste-driven work, distinct rendered directions are the interview: name the style of each so the user gains the vocabulary to steer, and treat the first pass as a probe. When the user says they do not know the domain, open with the questions they did not ask, ranked by consequence, before any recommendation.

Compare the Alternatives That Matter

Add an unconventional option only when the obvious ones share an untested assumption.

ApproachWhat improvesCarrying costMain uncertaintyDecisive check
[Mechanism][User or system outcome][Maintenance, runtime, migration][What could invalidate it][Experiment or evidence]

Test the Uncertainty Before Polishing

Pick the next move by its power to change the decision; a rough prototype often settles more than another design paragraph.

Evidence gapNext move
An API or model capability may have changedRead current primary docs and inspect the installed version
Performance determines feasibilityTest a representative workload against a baseline and resource caps
Several independent domains affect the choiceDelegate bounded research when permitted, or batch the reads
Stakeholders value different outcomesSurface the value tradeoff to the user
A favored approach has weak supportSeek a concrete counterexample or failure condition

Reviewer agreement is not proof, since reviewers may share training, sources, or framing. Settle consequential disagreements with code, sources, or an experiment, and say when evidence stays inconclusive.

Decide and Preserve the Reason

Recommend the best-supported direction with its main tradeoff and next action, or keep exploration open when that is the deliverable.

For a durable decision, record the choice, rationale, rejected alternative worth remembering, evidence, and reconsideration trigger in configured project memory. Preserve deliberately open decisions and user corrections verbatim when paraphrase would narrow them.

Route unresolved factual questions to research, complex execution to plan, and a clear bounded change to implement; these are optional compositions, not a mandatory pipeline.

Evidence

Reviewed 2026-09-04 and 2026-10-27; sources and their limits are in references/evidence.md.

Anti-Patterns

Anti-patternBetter move
Brainstorm before every code editExplore only unresolved direction
Ask the user to reconfirm known constraintsCarry prior authorization and decisions forward
Offer options that differ only cosmeticallyCompare different mechanisms or tradeoffs
Polish an approach with an untested premiseRun the feasibility check first
Turn an anecdote into a universal ruleRetain the mechanism and state its conditions

What This Skill is NOT

  • A prerequisite for implementation, debugging, or routine fixes.
  • A requirement to produce a spec, a fixed option count, or a final approval question.
  • A substitute for the user's product judgment or current technical evidence.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/hyperb1iss/hyperskills/brainstorm">View brainstorm on skillZs</a>