메뉴
USE WHEN the user pastes long text (article, paper, transcript, doc) and wants a summary. Picks the right summary shape (TL;DR / key points / structured / actionable) for the source type and length. Preserves numbers, names, dates verbatim.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
USE WHEN the user asks to format references for an academic paper or research note. Converts messy DOIs, URLs, or pasted text into APA / IEEE / GB/T 7714 / BibTeX consistently. Verifies the cite key matches the work.
USE WHEN the user pastes code or asks for review of a file/diff. Reads the code, identifies real issues (bugs, security, perf, correctness, readability) in priority order, suggests concrete fixes. Skips style nitpicks unless asked.
USE WHEN a user shares or references a CSV file and wants it summarized, analyzed, or visualized — produces data overview, summary statistics, missing-data report, and relevant charts using built-in tools (Read + Bash running Python/pandas).
USE WHEN the user asks to clean up, reformat, or polish a markdown document. Normalizes headings, lists, tables, code fences, math delimiters, and Chinese punctuation. Returns the rewritten doc, not a description of changes.
USE WHEN turning raw meeting notes, transcripts, or discussion logs into structured minutes — extracting summary, decisions, action items (with owners and due dates), and next steps using ready-made templates for standups, project reviews, and client calls.
USE WHEN the user wants to draw an architecture diagram, sequence diagram, flowchart, ER diagram, or state machine. Picks the right mermaid type, writes correct syntax, validates before returning.
| name | summary-distiller |
| description | USE WHEN the user pastes long text (article, paper, transcript, doc) and wants a summary. Picks the right summary shape (TL;DR / key points / structured / actionable) for the source type and length. Preserves numbers, names, dates verbatim. |
| Source | Shape |
|---|---|
| News article | TL;DR + 3-5 key facts + "why it matters" |
| Academic paper | Background / Method / Results / Limitations |
| Meeting transcript | Decisions / Action items (with owner+due) / Open questions |
| Tutorial / how-to | Numbered steps, preserving every command verbatim |
| Long thread / comments | Stance map: "X argued A, Y countered B" |
| Strategy doc | Goals / Constraints / Decisions / Open issues |
Don't impose one shape on all sources. If unsure, ask: "What are you using this for?" — that tells you the shape.
These must be quoted exactly, never paraphrased:
**TL;DR**: {one sentence}
**Key facts**:
- {bullet with verbatim number/name}
- ...
**Why it matters**: {one sentence on consequence or context}
**Source**: {title}, {publication}, {date}, [link]