eli
Version: 1.2.0 (locally maintained edition).
Explain logically and interactively. Produce a self-contained HTML page that
helps a mature reader decide, not just understand. /eli5 stays the
dead-simple picture mode. This skill adds depth, evidence, and control.
Sources this skill builds on
Delegate by skill name. Do not restate their rules here.
- Prose quality: load
/unslop. It must always apply to the page copy and to
this skill's own text. It isn't bundled here. If it isn't installed, say so
once and run the plain-language self-check below instead.
- Visualization and evidence discipline: load
/teach-pro-max. Take its
honest-claims boundary. Report what was observed. Name remaining
uncertainty. Never infer mastery from completion.
- Claim sourcing: load
/deep-research. Every claim gets a source or an
explicit label. Separate fact from inference. Flag single-source claims as
unverified.
Artifact contract
One self-contained HTML file. No build step, no network requests at view
time, no CDN fonts or scripts, no analytics. System font stacks only. The
file must render correctly from file://.
Interactivity ladder
Native HTML first. JavaScript only enhances.
<details>/<summary> carries per-item depth. It works with JS off.
That is the static fallback and it is required, not optional.
- Enhanced controls behind small vanilla JS: search filter, category
chips, per-item selection checkboxes, a sticky selection bar that
renders the exact install commands, and a copy button.
- No persistence by default. Selection lives in page state and dies with
the reload. Durable state requires the user's explicit consent and a
stated storage location.
Content contract
Every item on the page carries the decision fields. An item missing a
field is incomplete, not minimalist.
- What it is. One concrete sentence, mechanism named.
- Why you care. Tied to the reader's actual stack, not generic benefits.
- Tradeoffs and risks. Including overlap with things the reader already
runs, maintenance staleness, trust level, and cost drivers.
- Verdict tier. Install now, consider, or skip. With a one-line reason.
- Install command. Exact and runnable, or the reason none exists.
- Evidence badge on every factual claim: verified (checked this session,
with the method), unverified (single source or vendor-claimed), or
unavailable (say so plainly).
Modes
Pick the lightest mode that serves the decision.
| Mode |
Deliverable |
quick |
One screen, hero claim, three supporting cards |
matrix |
Full item set, filters, tiers, selection bar. The default for "help me choose" |
compare |
Two to four items head to head on the decision fields |
Process
- Gather facts with real lookups (registry, docs, logs, files). Never
fill decision fields from memory.
- Write the page. Apply unslop to every sentence. Short declarative
sentences, active voice, sentence case headings, straight quotes, no
em dashes, no mid-sentence colons. Without unslop, reread every sentence
against this self-check before delivering: Is it plain words a newcomer
knows, or is each term defined where it first appears? Does it say one
thing, with a concrete subject and verb? Can a filler word, hedge or
stacked adjective go? Is any claim vaguer than the facts gathered in
step 1? Fix each sentence that fails.
- Validate. Open the file. Check that details expand with JS disabled,
filters work with JS on, commands copy cleanly, and no field is empty.
- Deliver. State the file path, what is interactive, and what remains
uncertain. Do not create extra files beyond the one artifact.
Closing
Report the artifact path, the decision tiers chosen and why, and the
top uncertainty a skeptic would probe next. Keep it under ten lines.
1---2name: eli3description: Explain any topic in a detailed, interactive, visual HTML explainer for a mature reader making a decision. Use when the user asks for an "eli" page, a decision-grade visual breakdown, or to regenerate an explainer with more depth. Extends /eli5 with evidence labels, tradeoffs, risks, costs, install commands, and interactive filtering and selection. Offline-safe, no CDN, no API keys, no telemetry.4metadata:5 source: https://skillmd.com/skills/praxstack/eli6---78# eli910Version: 1.2.0 (locally maintained edition).1112Explain logically and interactively. Produce a self-contained HTML page that13helps a mature reader decide, not just understand. `/eli5` stays the14dead-simple picture mode. This skill adds depth, evidence, and control.1516## Sources this skill builds on1718Delegate by skill name. Do not restate their rules here.1920- Prose quality: load `/unslop`. It must always apply to the page copy and to21 this skill's own text. It isn't bundled here. If it isn't installed, say so22 once and run the plain-language self-check below instead.23- Visualization and evidence discipline: load `/teach-pro-max`. Take its24 honest-claims boundary. Report what was observed. Name remaining25 uncertainty. Never infer mastery from completion.26- Claim sourcing: load `/deep-research`. Every claim gets a source or an27 explicit label. Separate fact from inference. Flag single-source claims as28 unverified.2930## Artifact contract3132One self-contained HTML file. No build step, no network requests at view33time, no CDN fonts or scripts, no analytics. System font stacks only. The34file must render correctly from `file://`.3536### Interactivity ladder3738Native HTML first. JavaScript only enhances.39401. `<details>`/`<summary>` carries per-item depth. It works with JS off.41 That is the static fallback and it is required, not optional.422. Enhanced controls behind small vanilla JS: search filter, category43 chips, per-item selection checkboxes, a sticky selection bar that44 renders the exact install commands, and a copy button.453. No persistence by default. Selection lives in page state and dies with46 the reload. Durable state requires the user's explicit consent and a47 stated storage location.4849### Content contract5051Every item on the page carries the decision fields. An item missing a52field is incomplete, not minimalist.5354- What it is. One concrete sentence, mechanism named.55- Why you care. Tied to the reader's actual stack, not generic benefits.56- Tradeoffs and risks. Including overlap with things the reader already57 runs, maintenance staleness, trust level, and cost drivers.58- Verdict tier. Install now, consider, or skip. With a one-line reason.59- Install command. Exact and runnable, or the reason none exists.60- Evidence badge on every factual claim: verified (checked this session,61 with the method), unverified (single source or vendor-claimed), or62 unavailable (say so plainly).6364### Modes6566Pick the lightest mode that serves the decision.6768| Mode | Deliverable |69|---|---|70| `quick` | One screen, hero claim, three supporting cards |71| `matrix` | Full item set, filters, tiers, selection bar. The default for "help me choose" |72| `compare` | Two to four items head to head on the decision fields |7374## Process75761. Gather facts with real lookups (registry, docs, logs, files). Never77 fill decision fields from memory.782. Write the page. Apply unslop to every sentence. Short declarative79 sentences, active voice, sentence case headings, straight quotes, no80 em dashes, no mid-sentence colons. Without unslop, reread every sentence81 against this self-check before delivering: Is it plain words a newcomer82 knows, or is each term defined where it first appears? Does it say one83 thing, with a concrete subject and verb? Can a filler word, hedge or84 stacked adjective go? Is any claim vaguer than the facts gathered in85 step 1? Fix each sentence that fails.863. Validate. Open the file. Check that details expand with JS disabled,87 filters work with JS on, commands copy cleanly, and no field is empty.884. Deliver. State the file path, what is interactive, and what remains89 uncertain. Do not create extra files beyond the one artifact.9091## Closing9293Report the artifact path, the decision tiers chosen and why, and the94top uncertainty a skeptic would probe next. Keep it under ten lines.