← ClaudeAtlas

concept-explainerlisted

Plain-language concept explainer and task knowledge-card generator. Use when a task contains tools, commands, files, configs, architecture layers, code mechanisms, business rules, or troubleshooting chains that a user may not understand. ⛔ Trigger on unfamiliar concepts, commands, or execution flows. If you skip it, the user may get an answer but still lack the mental model needed to act independently. Trigger words: do not understand, explain, what is this, why, how to use, CLI, command, npm, package.json, access credential, environment variable, API, architecture, workflow, error.
PhilRobinluo/ai-coevolution-skills · ★ 3 · AI & Automation · score 64
Install: claude install-skill PhilRobinluo/ai-coevolution-skills
<!-- workbuddy-install: pending; slug: concept-explainer --> ## 在 WorkBuddy 中找到并安装 **Skill slug:`concept-explainer`** 在 WorkBuddy 新会话粘贴: ```text 请按 https://skillhub.cn/install/skillhub.md 检查 SkillHub,搜索 `concept-explainer`;仅在 slug 完全一致时安装到 `~/.workbuddy/skills/`。安装后读取 `~/.workbuddy/skills/concept-explainer/SKILL.md`,核对 name、version 和实际路径,然后新开会话触发该 Skill。 ``` 也可以打开左侧「技能」→「添加技能 / 查找技能」,搜索 `concept-explainer` 后安装;界面文字可能随 WorkBuddy 版本变化。 # Concept Explainer Concept Explainer helps an AI assistant explain unfamiliar concepts while continuing the user's real task. It is not a standalone lecture mode. It turns important concepts encountered during work into short, memorable knowledge cards. ⛔ **Core rule: when a task includes a tool, command, file, config, architecture layer, code mechanism, business rule, or troubleshooting chain that a user may not understand, explain it in plain language and generate 1-5 knowledge cards while still moving the task forward.** --- ## When To Use Use this skill when any of these are true: 1. The task includes unfamiliar parts such as CLI, npm, package.json, API, access credential, environment variable, database, smart contract, build command, test command, deployment command, config file, working directory, logs, or network request. 2. The user needs to understand a workflow, not just copy a command. 3. The user says they do not understand, asks what something means, asks why something works, or says the explanation is not landing. 4. Th