cjl-plain
Cognitive atom: Plain (白). Rewrites any content so a smart 12-year-old groks it. Structure-free — form follows content. Use when user says '白话说', '说人话', '解释一下', 'plain', 'grok'.
Best use case
cjl-plain is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Cognitive atom: Plain (白). Rewrites any content so a smart 12-year-old groks it. Structure-free — form follows content. Use when user says '白话说', '说人话', '解释一下', 'plain', 'grok'.
Teams using cjl-plain should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/cjl-plain/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How cjl-plain Compares
| Feature / Agent | cjl-plain | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Cognitive atom: Plain (白). Rewrites any content so a smart 12-year-old groks it. Structure-free — form follows content. Use when user says '白话说', '说人话', '解释一下', 'plain', 'grok'.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
Best AI Agents for Marketing
A curated list of the best AI agents and skills for marketing teams focused on SEO, content systems, outreach, and campaign execution.
Best AI Skills for ChatGPT
Find the best AI skills to adapt into ChatGPT workflows for research, writing, summarization, planning, and repeatable assistant tasks.
SKILL.md Source
# cjl-plain: 白
让人 grok。
不规定怎么写。规定不能怎么写。下限锁死，上限放开。不同主题有不同的最佳写法——类比、故事、问答、递进的例子、一个长场景——由内容决定形式。
## 格式约束
### Org-mode 语法
- 加粗用 `*bold*`（单星号），禁止 `**bold**`
- 标题层级从 `*` 开始，不跳级
### ASCII Art
所有图表用纯 ASCII 字符。允许：`+ - | / \ > < v ^ * = ~ . : # [ ] ( ) _ , ; ! ' "` 和空格。禁止 Unicode 绘图符号。
### Denote 文件规范
- 时间戳：`date +%Y%m%dT%H%M%S`
- 可读时间：`date "+%Y-%m-%d %a %H:%M"`
- 文件名：`{时间戳}--plain-{简短标题}__plain.org`
- 输出目录：`~/Documents/notes/`
### Org 文件头
```
#+title: plain-{简短标题}
#+date: [{YYYY-MM-DD Day HH:MM}]
#+filetags: :plain:atom:
#+identifier: {YYYYMMDDTHHMMSS}
#+source: {URL 或来源描述}
```
文件写入后报告路径。
## 红线（每条必须过，顺序即优先级）
1. *口语检验* — 最高法则。读出声来，你会这样跟一个聪明的朋友说话吗？不会→改到会。连词不是敌人——"但是""所以"是思维转弯的声音，只砍机械连词（"此外""值得注意的是"）
2. *零术语* — 聪明的 12 岁孩子能复述。专业词必须出现时，先用大白话把意思落地，再顺带提术语名
3. *短词优先* — 能用两个字说的不用四个字。「进行分析」→「看」。大词不让你显得聪明，只让人读得累
4. *一句一事* — 每句只推进一步。长句拆短
5. *具体* — 名词看得见，动词有力气。「有人觉得情况不太好」→「张三说项目要黄了」。形容词能砍就砍
6. *开头给理由* — 第一句话让人想读下一句。不铺垫、不背景、不「自古以来」
7. *不填充* — 删开场白、拐杖词、夸大象征。每句都在干活
8. *信任读者* — 跳过软化、辩解、手把手引导。说一遍够了
9. *诚实* — 想不清楚就说想不清楚。"大概 70%" 比"可能"诚实
## 工具箱（选用，不必全用）
写的时候可以从这里拿工具，没有哪个是必须的：
- *类比* — 找结构对得上的日常经验。好类比承重（去掉它文章塌），多层（挖一层还像），自明（不需要解释类比本身）。动词延伸到新对象时检查中文动宾搭配是否自然
- *好问题* — 找读者的卡点，变成问题。读者被卡住，才想往下读
- *裂缝* — 模型/类比在哪里不够？那个点往往最值钱。不宣布它，让读者自己感到
- *画面* — 闭眼能看到的场景。硬造的画面比没有更糟
- *故事* — 一个具体的人遇到一个具体的问题。读者跟着走
- *反问入链* — 遇到隐含前提，用问题打开，然后回答它
- *骨架图* — 概念涉及空间关系时，嵌入 ASCII 图（`#+begin_example` 块）
## 执行
### 1. 获取内容
URL → WebFetch | 文本 → 直接用 | 文件路径 → Read | 概念 → 直接解释 | 书名/论文名 → WebSearch
### 2. 写
形式自由。从工具箱里选最适合这个主题的方式，也可以不选——如果有更好的写法，用它。
输出是一篇从第一行流到最后一行的连贯文章。全文只有文件标题，正文无子标题。
禁止：
- 结构标签（`* 类比` / `* 裂缝` 等）
- 指向写作过程的元评论（「打个比方」「接下来我们讨论」）
### 3. 过红线
逐条扫红线清单。额外检查：
- 破公式——否定式排比全文不超过两处，三段式改两项或四项
- 变节奏——长短句交替，段落结尾多样
- 杀金句——听起来像可引用的，重写
- 查跳跃——每步逻辑可追？前句说 A，后句跳到 B→补桥
- 查译感——动宾搭配中文天然吗？不自然→换动词或换句式
扫完列修改清单（哪句触发什么，改前→改后）。清单不写入文件。
### 4. 生成 Org 文件
按 Denote 规范获取时间戳，写出文件头 + 正文，存入 `~/Documents/notes/`。
## 验收
- *Grok*：读完能用自己的话复述核心
- *零术语*：12 岁孩子能跟上
- *记得住*：读完脑子里留下了什么——一个画面、一个问题、一个转折，什么都行
- *想读完*：从头到尾没有想跳过的段落Related Skills
explainer
Create explainer videos with narration and AI-generated visuals. Triggers on: "解说视频", "explainer video", "explain this as a video", "tutorial video", "introduce X (video)", "解释一下XX（视频形式）".
visual-explainer
Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data. Use when the user asks for a diagram, architecture overview, diff review, plan review, project recap, comparison table, or any visual explanation of technical concepts. Also use proactively when you are about to render a complex ASCII table (4+ rows or 3+ columns) — present it as a styled HTML page instead.
feynman-technique-explainer
Explain any concept using the Feynman Technique, plain language, a real-world analogy, a concrete example, and a comprehension quiz. No jargon from the concept allowed.
aws-guardduty-explainer
Translate GuardDuty findings into plain-English incident summaries with actionable response steps
aws-anomaly-explainer
Diagnose AWS cost anomalies and explain root cause in plain English when spend spikes unexpectedly
moa-explainer
Generate 3D animation scripts and lay explanations for drug mechanisms.
concept-explainer
Uses analogies to explain complex medical concepts in accessible terms.
sbom-explainer
把依赖清单或 SBOM 翻译成非技术可读的风险说明，按影响面排序。；use for sbom, dependencies, risk workflows；do not use for 伪造 CVE 状态, 替代专业漏洞扫描.
env-diff-explainer
比较 dev/staging/prod 配置差异，并把技术差异翻译成业务风险。；use for env, config, diff workflows；do not use for 输出敏感密钥值, 直接覆盖配置.
token-risk-explainer-skill
Explain crypto token risk in plain Chinese and English from Binance Web3 token audit and market metadata. Use this skill when users want a contract-level risk score, factor-by-factor explanation, comparison between tokens, watchlist triage, and ready-to-send community or Binance Square risk copy.
---
name: article-factory-wechat
humanizer
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.