菜单
Rewrite supplied text or Markdown in plain language while preserving facts, technical artifacts, structure, and the source language. Use when a user asks for a simpler explanation, document, or agent response without a meaning change.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/wcygan/agent-skills --skill plain-language-rewrite命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use PromptKit’s official docs, machine-readable indexes, registry items, blocks, primitives, and source code to answer, debug, or implement React AI UI requests involving prompt-kit or prompt-kit.com. Trigger when a request names PromptKit, a PromptKit component, block, primitive, or registry URL. Verify current APIs, dependencies, shadcn setup, React/Next.js/Tailwind compatibility, and AI SDK assumptions. Change project files only when implementation is explicitly requested.
Coordinate a bounded multi-agent software task from decomposition through verified integration. Use for concurrent workers, dependent tasks, or shared integration ownership.
Create a beginner-friendly visual explainer with big pictures and few words as one self-contained HTML document. Use for ELI5 explanations of modules, tradeoffs, incidents, and unfamiliar topics.
正在显示 SKILL.md
| name | plain-language-rewrite |
| description | Rewrite supplied text or Markdown in plain language while preserving facts, technical artifacts, structure, and the source language. Use when a user asks for a simpler explanation, document, or agent response without a meaning change. |
| license | MIT |
| metadata | {"author":"William Cygan","inspiration-url":"https://github.com/gvzdv/claudish-to-english","inspiration-revision":"e109e224acbfcc49016f383cc0d178c0b69b4954"} |
Rewrite prose so a reader can understand it more easily. Preserve meaning and technical detail.
Use the input language unless the user asks for translation. Use the requested
style. Default to plain.
plain: Use common words and short, direct sentences.summary: Keep the main points and remove nonessential detail.beginner: Explain necessary terms in simple language. Preserve technical
details that the reader needs to act.Ask one question only when the audience or intended meaning is unclear.
Keep these items unchanged unless the user explicitly asks to change them:
Use code formatting for inline technical literals. Keep a statement uncertain when the source is uncertain.
Use active voice, concrete verbs, and short sentences. Replace unexplained jargon with common language. Define a necessary technical term once, near its first use.
Keep the original Markdown structure unless a different structure makes the request clearer. Do not add facts, advice, or examples that the source does not support.
Before you return the rewrite, compare its technical literals and factual claims with the source. Correct a difference or return the original text with a short explanation when preservation is not possible.
Return only the rewrite unless the user asks for a comparison or explanation.
When the user asks for a file artifact, create a sibling file named
NAME.plain.md by default. Overwrite a source file only with direct user
approval. Report the saved path.