- name
SKILL.md
技能檔案保留在發布者的儲存庫中。
在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add dzhng/skills --skill eli5 -a cursor -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add dzhng/skills --skill eli5 -a claude-code -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add dzhng/skills --skill eli5 -a codex -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add dzhng/skills --skill eli5 -a grok -y在 Grok Bot 聊天中傳送複製的訊息。Bot 會從 GitHub 取得這個 SKILL.md,並加入你所有 Bot 共用的技能中。
Install this skill: https://github.com/dzhng/skills/tree/HEAD/skills/engineering/eli5來自發布者
Turn the referenced spec or change into an accurate mental model for a technical reader who does not live in the code. Plain language, full precision: simplify the telling, never the claims.
Other skills point here when their output must be readable by someone who didn't live the work. The reader is technical — pseudocode and precise claims land fine — but they have read none of the code and none of the session's messages: no diff, no transcript, no labels the work invented along the way. Writing ELI5 means:
Use these headings in order:
ProblemSolutionSchema changesEnd with one short sentence stating what users should notice after the change.
Explain a technical spec or proposed change in plain language: what problem it solves, how the solution works, and every schema change.
---name: eli5description: Explain a technical spec or proposed change in plain language: what problem it solves, how the solution works…---# skills/engineering/eli5/SKILL.md常見問題
從發布者下載 skills/engineering/eli5/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/dzhng/skills。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。