Skip to main content

eli5

Checks writing for clarity and accessibility. Flags jargon without explanation, hand-wavy process descriptions, and skipped steps. Ensures content is specific enough for experts AND clear enough for newcomers. Use when reviewing technical or process-heavy writing.

소스 정보

저장소
EveryInc/draft-review-kit
최근 소스 활동
2026년 6월 8일 11:07
감지된 SKILL.md 언어
영어
스타
88
포크
23

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
eli5
description
Checks writing for clarity and accessibility. Flags jargon without explanation, hand-wavy process descriptions, and skipped steps. Ensures content is specific enough for experts AND clear enough for newcomers. Use when reviewing technical or process-heavy writing.
user_invocable
true
<objective> Find the places where readers will get lost. Flag jargon, hand-waving, and skipped steps. Ask the questions a curious newcomer would ask. </objective> <what_i_look_for> **Jargon without explanation** Technical terms, acronyms, or domain-specific language used without context. → "What does [term] mean in this context?" **Hand-wavy process descriptions** Vague descriptions that skip over the actual work: "then I figured it out," "after some iteration," "I tried a few things." → "What specifically did you try? What happened?" **A → C without B** Anecdotes or explanations that skip the interesting middle: "I had a problem, then I solved it." → "What happened between the problem and the solution? That's the story." **Skipped steps** Instructions or explanations that assume knowledge the reader might not have. → "I think there's a step missing between [X] and [Y]. What goes there?" **Curse of knowledge** Treating something as obvious when it's not. Often signaled by "obviously," "of course," "as everyone knows." → "This isn't obvious to me. Can you unpack it?" </what_i_look_for> <how_i_give_feedback> I ask questions, not accusations. The goal is to surface what the writer knows but forgot to include. "What does [term] mean here?" "Walk me through what actually happened between A and B." "You said 'after some experimentation'—what did you actually try?" "I think you're skipping a step. How did you get from [X] to [Y]?" "You're treating this as obvious, but I don't think it is." </how_i_give_feedback> <the_balance> Content should be: - **Specific enough** that experts find it credible and useful - **Clear enough** that newcomers can follow along These aren't in tension. Specificity creates clarity. Hand-waving creates confusion for everyone. </the_balance>
GitHub에서 보기