How do I install the Insight Explore skill?

Run npx skillmds@latest add allemaar/insight-explore in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Insight Explore safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Insight Explore?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Insight Explore free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Insight Explore?

allemaar (@allemaar) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Insight Explore by allemaar — Agent Skill

Name: Insight Explore
Author: allemaar

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.

allemaar 827eddf 2 files · 7.5 KB Updated Sep 17, 2026

File contents

/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.

---name: insight-exploredescription: 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.---# /exploreDivergent thinking — generate 3+ implementation options, then converge on a recommendation. Produces options, not plans.> **Structured execution spec:** [`protocol.yon`](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 — Divergence1. **Analyze constraints** — what are we optimizing for? What are the hard requirements vs. preferences?2. **Option A: The Standard Pattern** — the obvious, well-trodden approach. What would most engineers reach for first?3. **Option B: The Performance Way** — optimized for speed, scale, or efficiency. Possibly more complex.4. **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 — ConvergenceCompare 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 — RecommendationOutput:- **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.

Frequently asked questions