Ljg Learn
Deconstruct an unfamiliar term or idea into an eight-dimensional org-mode report ending in a one-line epiphany before you spec, ship, or write about it.
Overview
ljg-learn is a journey-wide agent skill that deconstructs any concept through eight exploration dimensions and compresses the result into an org-mode epiphany report—usable whenever a solo builder needs to understand a t
Install
npx skills add https://github.com/lijigang/ljg-skills --skill ljg-learnWhat is this skill?
- Five-step ritual: anchor definition, eight exploration cuts, first-person introspection, compress to formula and ASCII s
- Eight dimensions: history, dialectics, phenomenology, linguistics, formalization, existentialism, aesthetics, meta-philo
- Strict org-mode output only—*bold*, ~code~, no markdown fences or --- separators
- Triggers on 解剖概念, 概念解剖, explain concept, learn concept, and /ljg-learn
- Delivers #+title org document with concept formula and deepest one-sentence insight
- 8 exploration dimensions in the eight-cut phase
- 5-step workflow from anchor through org-mode write
Adoption & trust: 3.5k installs on skills.sh; 5.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You encounter a fuzzy concept in product, tech, or strategy and chat summaries hide misconceptions, history, and structure you need for real decisions.
Who is it for?
Solo builders researching domain language, philosophical product metaphors, or technical jargon before writing plans or public copy.
Skip if: Tasks that only need a quick dictionary definition, runnable code, or compliance checklists—skip when you already have an approved spec and just need implementation steps.
When should I use this skill?
User asks to explain, dissect, or deeply understand a concept, term, or idea; triggers include 解剖概念, 概念解剖, explain concept, learn concept, /ljg-learn.
What do I get? / Deliverables
You receive a structured org-mode anatomy with formula, ASCII skeleton, and one distilled sentence you can cite in specs, docs, or positioning work.
- Org-mode report with #+title 概念解剖：{概念名}
- Concept formula, one-sentence insight, and ASCII structure diagram
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Dissect “product-market fit” before choosing a niche to validate.
Anatomize pricing model vocabulary so your MVP scope matches what customers mean.
Clarify an architecture buzzword for internal docs agents will maintain.
Unpack user-facing concepts for lifecycle emails without diluting meaning.
How it compares
Use instead of one-shot “explain like I’m five” chat answers when you want repeatable depth and a durable org-mode artifact.
Common Questions / FAQ
Who is ljg-learn for?
Indie builders and agent users who keep org-mode notes and want rigorous concept breakdowns before product, technical, or content commitments.
When should I use ljg-learn?
During Idea research to scope a market term, in Validate when pricing or positioning hinges on precise language, in Build when naming architecture concepts, at Launch when SEO or thought-leadership needs clear definitions, and in Grow when educating users on unfamiliar ideas.
Is ljg-learn safe to install?
Review the Security Audits panel on this Prism page and treat the skill like any third-party procedural prompt—no special permissions are required beyond normal agent file output.
SKILL.md
READMESKILL.md - Ljg Learn
## Usage <example> User: /ljg-learn 熵 Assistant: [对"熵"进行八维解剖，生成 org-mode 报告] </example> ## Instructions 你是概念解剖师。拿到一个概念，从八个方向切开它，最后把所有切面压成一句顿悟。 ### 1. 定锚 1. 这个概念最通行的定义是什么？常见误解在哪？ 2. 概念里藏着哪几个核心词素？ ### 2. 八刀 八个方向各切一刀。每刀 2-3 句，只留筋骨，不带水分。 1. **历史**：最早从哪冒出来 → 怎么变的 → 哪一步拐成了今天的意思 2. **辩证**：它的反面是什么 → 正反碰撞后，更高一层的理解是什么 3. **现象**：扔掉所有预设，回到事情本身 → 用一个日常场景把它还原出来 4. **语言**：拆字源（中/英/希腊/拉丁）→ 画出相邻概念的语义网 → 这个词暗含什么隐喻 5. **形式**：写一个公式或形式化表达 → 公式在哪里失效 6. **存在**：这个概念改变了人怎么活着 7. **美感**：它美在哪？用一个具体意象呈现 8. **元反思**：我们在用什么隐喻理解它？这个隐喻挡住了什么？换一个会怎样 ### 3. 内观 1. 变成这个概念本身，用第一人称看世界。3-5 句。 2. 八刀之中，哪几刀指向同一个深层结构？把它提出来。 ### 4. 压缩 1. **公式**：`概念 = ...` 2. **一句话**：用最简单的话说出最深的理解 3. **结构图**：纯 ASCII 画出概念的骨架（只用 +-|/\<>*=_.,:;!'" 等基本符号，不用 Unicode 绘图字符） ### 5. 写入 **格式规则（零例外）：** - 输出必须是纯 org-mode 语法，禁止任何 markdown 语法 - 加粗用 `*bold*`（org-mode），不用 `**bold**`（markdown） - 分隔线用空行或 org 标题层级区分，不用 `---`（markdown 分隔符） - 列表用 `- item` 或 `1. item`，不用 markdown 的 `* item`（因为 `*` 在 org 中是标题） - 代码用 `~code~` 或 `=code=`，不用反引号 整合为 org-mode，结构： ```org #+title: 概念解剖：{概念名} #+filetags: :concept: #+date: [YYYY-MM-DD] * 定锚 * 八刀 ** 历史 ** 辩证 ** 现象 ** 语言 ** 形式 ** 存在 ** 美感 ** 元反思 * 内观 * 压缩 ``` 写入文件： 1. 运行 `date +%Y%m%dT%H%M%S` 获取时间戳。 2. 写入 `~/Documents/notes/{timestamp}--概念解剖-{概念名}__concept.org`。 3. 报告路径，完成。