Token导航 LogoToken导航TokenDH.com
研究检索需要联网clawhub未标认证来源可访问clear审计通过

eli5eli5 搜索

Agent Skill

eli5 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

2,571

周安装

104

GitHub Stars

1

下载量

807
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:eli5(eli5 搜索)
来源仓库:https://github.com/coghost/eli5
安装命令:
openclaw skills install eli5
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install eli5

简介

用最简单的语言解释复杂的话题——就像和一个 5 岁的孩子说话一样。使用类比,没有行话,日常用语。

SKILL.md

name
eli5
version
1.0.0
description
Explain complex topics in the simplest possible words — like talking to a 5-year-old. Uses analogies, no jargon, everyday language.

ELI5 — Explain Like I'm 5

Turn any complex topic into something a child could understand.


Why it exists

Most explanations are written for people who already halfway know the answer. They hand-wave the hard parts, use words that need the explanation itself to make sense, and leave you more lost than before.

ELI5 is different. It forces a clean picture — one familiar analogy, a few short steps, and one concrete example.

How ELI5 works (technical)

ELI5 works by loading SKILL.md into the conversation context. When you type /eli5 <concept>, OpenClaw matches the description and injects the skill's rules into the model.

The model reads the rules and examples, then generates an explanation following the same pattern.

Switching models: Works as long as the model can follow contextual instructions. If a model ignores rules in context, results may vary.


Quick start

/eli5 schrödinger's cat   # explain any concept
/eli5 help                 # show all commands
/eli5 lang <lang>          # switch language (en/zh/es/kr/...)
/eli5 bonus on             # enable bonus explanations
/eli5 steps 5              # adjust max steps (default: 3, max: 5)
/eli5 fetch on             # enable auto-fetch from web

Default language: Controlled by ELI5_DEFAULT_LANG env var (read-only). If not set, fallback to English.


The Rules

  1. Language priority:

- ELI5_DEFAULT_LANG env var (read-only) — set once, use forever - /eli5 lang <lang> — switch and hold until next switch - Fallback: English

  1. Be conversational, not formulaic — sound like a smart friend explaining, not a textbook. Skip the formula if it feels stiff.
  2. Assume nothing — the user knows zero technical terms
  3. Bridge: unknown → known — pick one familiar thing (toy, friend, magic box) and stick with it
  4. Max n steps — short sentences, one action each. Default is 3, configurable via /eli5 steps <n>
  5. Concrete example — one real thing the reader can picture. REQUIRED unless already perfectly clear.
  6. Have personality — vary your explanations. A good comparison, a touch of humor, or a memorable contrast beats dry lists every time.
  7. Bonus (default: off) — only show when bonus on or genuinely needed
  8. Freshness indicator (always shown, in current language):

- After the explanation, add a brief note: - Format: [Data: ~2024] [Freshness: ██████░░░░ 65%] [→ --fetch] - Visual bar: filled = fresh, empty = outdated - Scoring guidelines (subjective, use as reference): - Stable fields (philosophy, math, proven theories): 85-100 - Technology that evolves slowly (OS, hardware): 70-85 - Active tech fields (AI, frameworks, libraries): 50-70 - Fast-moving topics (startups, trends, new releases): 30-50 - Score 80-100: "Stable" → no action needed - Score 50-79: "Evolving" → consider --fetch - Score 0-49: "Outdated" → recommend --fetch strongly - If --fetch succeeded but data itself is old: use actual date + score based on how old the data is - If --fetch succeeded and data is latest: show actual date + high score - Example: [Data: 2024.03] [Freshness: ██████░░░░ 60%] [v1.2.0 — older]

  1. Fresh fetch (default: off):

- /eli5 fetch on → enable auto-fetch from web (GitHub, official docs, etc.) - /eli5 fetch off → disable - /eli5 <concept> --fetch → one-time fetch for this concept - If fetch succeeds → use latest content from web - If fetch fails → fall back to training data knowledge - Note: Fetch relies on OpenClaw's web search capability. If unavailable, falls back to training data.


Word Rules

Banned Words — Core Principle

Grandmother Test: Would my 80-year-old grandmother know this word? If NO → replace it or explain it immediately.

Happy Openings — Core Principle

Paint a picture. Make them visualize. Start with: "Imagine...", "Think of it as...", "Picture this..."

Forbidden Phrases — Core Principle

Never sound condescending, technical, or dismissive. Avoid: "Obviously...", "As you already know...", "Technically...", "In simple terms..."


Commands

/eli5 <concept>              # explain anything
/eli5 help                 # show this help (in current language)
/eli5 lang <lang>        # switch and hold language (en/zh/es/kr/...)
/eli5 bonus on|off          # toggle bonus (default: off)
/eli5 steps <n>             # set max steps (default: 3, max: 5)
/eli5 fetch on|off          # toggle auto-fetch from web (default: off)
/eli5 <concept> steps 5    # override steps for one answer
/eli5 <concept> in ZH      # override language for one answer
/eli5 <concept> --fetch   # fetch latest content for one answer

Env var (read-only): Set ELI5_DEFAULT_LANG in your environment. Skill reads it, does not write it.


Examples

Schrödinger's cat A cat that is both alive AND dead — until you open the box. Try it: /eli5 what is schrödinger's cat

The Chinese Room A person who pretends to understand Chinese but follows a rulebook instead. Try it: /eli5 what is the chinese room

The Ship of Theseus If you replace every plank of a ship, is it still the same ship? Try it: /eli5 what is the ship of theseus

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

80.33%
按下载量换算648

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills