Insight explore

Skill allemaar/open-skills/skills/insight-explore

Brainstorm 3+ possible implementations before committing. Trigger when the user runs /explore or asks to "brainstorm options", "what are the ways to do this", "explore approaches", "give me alternatives", or wants divergent thinking before planning or assessment. Use insight-assess to evaluate known options, insight-critique to review an existing output, and plan-create to turn a chosen direction into an implementation plan.From its SKILL.md

Install

npx -y skills add allemaar/open-skills --skill insight-explore

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

13 stars13 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.

SKILL.md

3.4 KB, 610 tokens by cl100k_base, as published. Nobody here has run it

/explore

Divergent thinking — generate 3+ implementation options, then converge on a recommendation. Produces options, not plans.

Structured execution spec: protocol.yon. Read it for the canonical rules and step sequence; this file is explanation. The two must stay in sync — if you edit one, update the other and refresh the @STAMP date.

Brainstorming Protocol — explore before committing. /insight-explore generates alternatives (divergent). /insight-assess evaluates them (convergent). /plan-create designs the chosen approach.

Phase 1 — Divergence

Analyze constraints — what are we optimizing for? What are the hard requirements vs. preferences?
Option A: The Standard Pattern — the obvious, well-trodden approach. What would most engineers reach for first?
Option B: The Performance Way — optimized for speed, scale, or efficiency. Possibly more complex.
Option C: The Minimalist — YAGNI. Smallest footprint that still solves the problem.

Additional options may be added if the problem space warrants them (e.g., event-driven, type-safe, or zero-dependency variants).

Phase 2 — Convergence

Compare all options across:

DX — developer experience, API ergonomics, debuggability
Robustness — error handling, edge case coverage, failure modes
Timeline fit — how long does each take to implement and validate?
Alignment — does it match existing patterns and coding standards in the repo?

Phase 3 — Recommendation

Output:

Winner — which option and why
Reason — 1–2 sentences, referencing the comparison
Next step — ask the user: "Shall I /plan-create this?"

Rules

MUST generate at least 2 distinct options (3 is the target).
MUST NOT write code or make changes — this is ideation only.

Next Steps

/insight-assess — evaluate the winner in depth before committing
/plan-create — design the chosen approach

Human output. This skill's handler-facing output obeys the human-output contract (human-output/SKILL.md).

Next skills. On completion, run the Next Skills protocol (next-skills/SKILL.md): surface the next-skills recommendations from front-matter for the caller to pick. Offer only — never auto-invoke.

Self-improvement. On completion, run the Self-Improvement Protocol (self-improve/SKILL.md): if this run surfaced a concrete, blocking-or-recurring weakness in this skill, propose a specific fix for the handler to approve. Conservative — silent otherwise. Never auto-apply.

What ships with it: 1 file

4.5 KB alongside SKILL.md

protocol.yon4.5 KB