explain
Skill0 starsChanged 4 months agoMITView on GitHub
방금 받은 AI의 보고·설명이 어렵거나 길 때, 비개발자도 이해할 수 있게 풀어서 다시 설명합니다. Triggers: explain, 쉽게 설명, 무슨 말이야, 이해가 안 돼, 방금 뭐 한 거야, 풀어서 말해줘, 요약해줘.
130 other projects use a version of this.
Adopted by
Most recently taken up by
- tekumara/skillstheir own version, first seen Nov 16, 2026
- abdallahkht/arabic-motion-kittheir own version, first seen Nov 16, 2026
- nicodiansk/draw-it-outtheir own version, first seen Nov 16, 2026
- samsam007b/claude-code-standards-kittheir own version, first seen Nov 16, 2026
- librosdeia/builder-method-claude-plugintheir own version, first seen Nov 15, 2026
- dafto1/skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use debug-fix, root-cause and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
zebbernSkilldebug-fix
Find and fix a bug or issue — from any source (GitHub issue, error message, user report, or observed behavior)
Also in 3 projects that use this
Ingramradical235Skillroot-cause
Structured root cause analysis using WHERE (MECE decomposition) then WHY (causal structure diagrams) pipeline. Includes coin-flip detection, logical-leap detection, and vicious cycle intervention. Use when buffer enters YELLOW/RED, when metrics stall, or when Actions execute but don't produce results.
Also in 5 projects that use this
ralphkraussSkillresolve-conflicts
Resolve git merge conflicts or re-apply changes from a stale branch onto current main. Use when user says "resolve conflicts", "merge conflicts", "rebase branch", "branch is behind", "re-apply changes", "port branch", or a branch is too far behind main to merge cleanly.
Also in 4 projects that use this
neurofooSkillsocratic
Socratic questioning to examine beliefs, uncover assumptions, and develop deeper understanding. Use to challenge thinking, evaluate proposals, or teach without lecturing.
Also in 4 projects that use this
AntaresYuanSkilliterate
Meta-skill for skill self-improvement. After another skill finishes a run, /iterate analyzes the run's logs (friction events, retries, sub-agent rejections, pacing mismatches, bugs), produces a structured retrospective report, accumulates per-class friction counts, and — when a class crosses the configured threshold — opens a PR to that skill's open-source repo with a proposed SKILL.md diff. NEVER auto-merges; the human always reviews. Target skills opt in by declaring an `iteration:` block in their frontmatter. Invoke when the user says "iterate this skill", "iterate /devloop", "run a retro on the last skill run", "/iterate <skill-name>", or when a target skill auto-hands-off at end of its run.
Also in 3 projects that use this
anombyte93Skilldiscover
Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.
Also in 6 projects that use this
Other versions130 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 130
- Z3Prover/z3★ 13ksame name
- crbnos/carbon★ 2.8ksame name
- poshan0126/dotclaude★ 871same name
- VinkyDev/vibestart★ 295same name
- hsantanna88/clo-author★ 262same name
- hugosantanna/clo-author★ 262same name
- entireio/skills★ 240same name
- sammcj/agentic-coding★ 172same name
- SerhiiKorniienko/bullshit-detector★ 151same name
- kv0906/pm-kit★ 138same name
120 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- promptsSkill
- save-promptSkill
- score-docSkill
- score-reportSkill
- score-sessionSkill
- scoreSkill
The file
Files
쉬운 말로 다시 설명
AI가 작업을 끝내고 낸 보고가 너무 길거나 어려울 때, 다른 AI에게 물으러 가지 않고 그 자리에서 바로 이해할 수 있게 풀어줍니다. 작업 흐름이 끊기지 않는 것이 목적입니다.
Language / 언어
Respond in the language the user writes in, not the language of the report you are explaining. Someone writing Korean gets a Korean explanation even if the original report was in English — translating the hard parts is the whole point of this skill.
The output format shown below is written in Korean. When responding in English, translate the labels and headings but keep the structure identical.
절차
- 설명 대상 확보
- 인자로 특정 부분을 지목했으면 그 부분을 중심으로 설명합니다.
- 비어 있으면 직전 어시스턴트 응답(이 명령어 바로 앞의 보고·설명)을 대상으로 합니다.
- 직전 응답이 없으면 "어떤 내용을 풀어드릴까요?"라고 한 줄로 묻고 멈춥니다.
- 눈높이 설정 — 읽는 사람은 개발 지식이 없는 대표(경영자)입니다.
- 기술 용어는 쓰지 않거나, 쓰는 즉시 일상 비유로 풀어줍니다.
- 코드·파일 경로·명령어의 나열은 "무엇이 어떻게 됐다"는 결과 중심 문장으로 바꿉니다.
- 원래 보고에 없는 내용을 지어내지 않습니다. 원 보고가 모호한 부분은 모호하다고 말합니다.
- 출력 — 아래 형식을 그대로 씁니다.
출력 형식
한 줄로 말하면
○○을 만들어서 이제 △△이 됩니다.
무슨 일이 있었나
· (한 것 1 — 일상 언어로, 왜 필요했는지 포함)
· (한 것 2)
· (한 것 3 — 최대 5개, 사소한 건 묶어서)
지금 상태
끝난 것: …
남은 것: …
대표님이 정하실 것 / 하실 일
· (결정이 필요한 것. 없으면 "지금은 없습니다 — 그냥 쓰시면 됩니다")
용어 한 줄 풀이 (원 보고에 어려운 용어가 있었을 때만)
· 훅(hook): 특정 상황이 되면 자동으로 실행되는 장치. 알림 설정 같은 것.규칙
- 비유는 회사 업무에서 가져옵니다. 서버는 "창고", 배포는 "매장에 진열", 커밋은 "중간 저장", 버그는 "불량", 테스트는 "검수" — 이커머스를 운영하는 사람이 바로 그려지는 그림으로.
- 결정이 필요한 것을 반드시 분리해서 보여줍니다. 대표가 보고에서 진짜 알고 싶은 건 "그래서 내가 뭘 해야 하는데?"입니다. 없으면 없다고 명시합니다.
- 원 보고보다 짧아야 합니다. 풀어 쓴다고 길어지면 실패입니다. 절반 이하를 목표로.
- 숫자와 상태는 그대로 보존합니다. "테스트 45개 통과" 같은 사실을 뭉개지 않습니다. 실패·미완료가 원 보고에 있으면 숨기지 말고 "남은 것"에 그대로 적습니다.
- 설명 후 "더 궁금한 부분을 짚어주시면 그 부분만 더 풀어드릴게요" 한 줄로 마칩니다.
- 존댓말, 간결하게. 가르치려 들지 않습니다.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

