---
name: eli5
type: agent-skill-installation
canonical-guide: https://thefuture.im/guide/eli5
source-repository: https://github.com/robbertvanempel/eli5
source-revision: dc4d81640856e7081d27ff6aed69983991e85900
skill-directory: https://github.com/robbertvanempel/eli5/tree/main
skill-package: https://thefuture.im/guide/eli5.zip
skill-package-sha256: 59e44e973e62e187d8f01989109aaca6cbb6edea78a7e70831c05cb0207f1f9a
supported-hosts: chatgpt-desktop, claude-cowork, grok-bot
---

# Install ELI5

The user supplied the canonical guide URL and asked to install ELI5. ELI5 is an Agent Skill, not a standalone application. Install only this skill on the current supported host. Do not create an explainer until the user also supplies a topic.

## Safety and source validation

1. Use only the source repository, revision, and package listed in the frontmatter.
2. Inspect `README.md` and `SKILL.md` before installation. The package must contain the folder `eli5/` with `eli5/SKILL.md`.
3. When downloading the package, verify its SHA-256 against the frontmatter before uploading or extracting it.
4. Preserve unrelated skills and settings. If an existing `eli5` installation has a different source, do not overwrite it without telling the user.
5. The user's install request authorizes this installation, but it does not bypass a product confirmation, workspace policy, security scan, or administrator restriction. Complete all safe steps automatically and ask for only the shortest remaining confirmation when the host requires one.

## ChatGPT Desktop

Use the app-managed Personal Skills flow. Download the package from `skill-package`, verify its SHA-256, then open **Plugins → Skills → Create → Upload from your computer** and select `eli5.zip`. Wait for the scan and confirm that `eli5` appears as installed. If the current ChatGPT task can operate this interface, complete the upload; otherwise prepare the verified package and give the user only the remaining upload/confirmation action.

Personal Skills can depend on plan and workspace settings and may need to be installed separately on desktop and web/mobile. Do not claim success until the desktop Skills list shows `eli5` as installed.

## Claude Cowork

Download and verify `eli5.zip`. In Cowork, open **Customize → Skills**, choose **+ → Create skill → Upload a skill**, upload the ZIP, and toggle `eli5` on. If an organization policy blocks skills or code execution, report that restriction instead of working around it. Confirm that the enabled skills list contains `eli5` before reporting success.

## Grok Bot

Prefer the private-skill installation available to the current Grok runtime:

1. If Grok Bot offers package import under **Settings → Plugins → Yours**, import the verified ZIP and enable `eli5` for the current Bot.
2. If the Bot has access to its agent-computer terminal and the runtime supports Grok skill directories, install the repository as `~/.grok/skills/eli5`. Clone it there only when the target does not exist. If it is already a Git checkout from the listed source, update it with a fast-forward-only pull; otherwise stop rather than overwriting it.
3. Refresh the skills view, then open **Settings → Plugins → Yours** and enable the private skill for the current Bot.

Do not claim success until `eli5` appears in the Bot's `/` skill menu or in its enabled private skills. If neither import nor local skill discovery is available in the current Grok Bot rollout, keep the verified package ready and tell the user exactly which missing control prevents completion.

## Validate and use

After installation, verify that the displayed description says the skill creates a self-contained visual HTML explainer with big pictures and very few words. The skill may become available only in the next task or after the host refreshes its skill list.

When the user provides a topic, invoke it with `$eli5`, `/eli5`, or a natural-language request that explicitly names the ELI5 skill, depending on the host. A safe test is: `Use $eli5 to explain how DNS works.`