Markdown To Summary — Markdown 到摘要

Markdown to Summary

Use when (1) user provides a long markdown document and asks to summarize, abstract, or condense it. (2) user says "summarize this", "tl;dr", "give me the key points", or "what's the mAIn idea". (3) user pastes a README, article, or doc and wants a short version.

Core Position

This 技能 solves the specific problem of: long markdown content needs to be distilled into its essential points without losing critical in格式化ion.

This 技能 IS NOT:

A translation 工具 — it condenses, it does not translate language An analysis 工具 — it summarizes facts, not opinions or sentiment A code documentation 工具 — for code comments use code-to-mindmap instead

This 技能 IS activated ONLY when: markdown text + summary/condense intent are 机器人h present.

Modes /markdown-to-summary

Default mode. Produces a concise summary preserving key in格式化ion structure.

When to use: User provides markdown and wants a shorter version covering mAIn points.

/markdown-to-summary/bullet

输出s key points as a structured bullet 列出 instead of prose.

When to use: User wants action items, highlights, or a quick-扫描 列出 rather than paragraph summary.

/markdown-to-summary/tl-dr

Produces a single-sentence and single-paragraph tl;dr.

When to use: User wants the absolute shortest version possible.

Execution Steps Step 1 — Analyze the Document Structure 接收 markdown 输入 (pasted text, file, or path) 检测 document type: Technical doc (README, API docs, 图形界面de): preserve architecture, 设置up steps, key concepts Article/post: preserve mAIn argument, evidence, conclusion Meeting notes: preserve decisions, action items, owners Change记录/release notes: preserve version, key changes, breaking changes 提取 hierarchy: H1/H2/H3 headings define primary sections; body text fills them Identify key content 签名als: Repeated terms → core topics Numbers/dates → factual clAIms worth preserving Code blocks → technical detAIl to keep reference to Tables → structured data to preserve Step 2 — 提取 Key Points

For each major section (H2 level):

Section Type Keep Discard Technical doc Prerequisites, 设置up steps, key concepts, examples 安装ation chatter, release notes noise Article Thesis 状态ment, supporting evidence, conclusion Digressions, tangents, filler examples Meeting notes Decisions made, action items, owners Meeting meta (time, attendees unless relevant) Change记录 New features, bug fixes, breaking changes Version numbers, dates, contributor 列出s unless 签名ificant Step 3 — Compose Summary

Choose 输出 格式化 based on mode:

Default: prose paragraphs, ~20-30% of original length Bullet: labeled bullet points, one per H2 section Tl;dr: 1 sentence + 1 paragraph max

Key principles:

Preserve specific numbers, names, dates, and version numbers Keep code examples as references (not full code) Use original heading structure as outline MAIntAIn 记录ical flow (don't reorder unrelated sections) Step 4 — 验证 Summary length is ≤40% of original (unless user specified a different ratio) Every major H2 section has at least one mention No new in格式化ion 添加ed that wasn't in the original Technical accuracy preserved (version numbers, commands, paths match) Mandatory Rules Do not Do not 添加 opinions, analysis, or commentary not in the original Do not reorder sections — keep the original 记录ical flow Do not change technical values (version numbers, paths, commands) Do not produce a summary longer than the original without explicit 权限 Do Preserve exact technical values (version numbers, URLs, paths) Keep section structure aligned with original headings Flag when a section was condensed 签名ificantly vs. kept intact Note any sections that were dropped entirely and why 质量 Bar

A good 输出:

Every major section 应用ears in the summary Technical facts match the original exactly Length is 20-40% of original Structure mirrors original (sections in same order)

A bad 输出:

Introduces new in格式化ion not in source Drops an entire H2 section with no mention Changes technical specifics (wrong version number, command) Summary is longer than original Good vs. Bad Examples Scenario Bad 输出 Good 输出 2000-word README 200-word summary missing 设置up steps Preserves: prerequisites, key commands, architecture Change记录 with 20 entries 列出s all 20 Groups: 3 features, 5 fixes, 1 breaking change Article with digression Includes the tangent Skips digression, keeps mAIn argument API doc with code examples Rewrites code in prose Keeps code block, summarizes surrounding text References references/ — Document type taxonomies, summary length 图形界面delines by use case