doc-briefing
2
总安装量
2
周安装量
#69075
全站排名
安装命令
npx skills add https://github.com/wangc94/my-vibing-skills --skill doc-briefing
Agent 安装分布
opencode
2
gemini-cli
2
claude-code
2
github-copilot
2
codex
2
kimi-cli
2
Skill 文档
Document Briefing Skill
Overview
This skill creates structured, comprehensive document briefings from various input types. Core principle: Summary as translation, not compression. Retain sufficient detailâit’s better to err on the side of including more information than over-condensing.
When to Use
Use this skill when the user wants to:
- Summarize a URL/webpage into a briefing
- Extract and summarize content from PDF files
- Summarize Word documents (.docx)
- Create briefings from Markdown or text files
- Convert any document into a structured briefing format
Input Types
| Type | Handler |
|---|---|
| URLs | Use WebFetch to get content |
| PDF (.pdf) | Use pdf skill to extract text |
| Word (.docx) | Use docx skill to extract text |
| Markdown (.md) | Read file directly |
| Text (.txt) | Read file directly |
Output Format
The briefing follows this structure:
# [Document Title]
## ð åºæ¬ä¿¡æ¯
- æ¥æºç±»åï¼
- è·åæ¶é´ï¼
- ææ¡£é¡µæ°/åæ°ï¼
## ð¯ æ ¸å¿è§ç¹
ï¼ç¨ 1-3 å¥è¯æ¦æ¬ææ¡£æ ¸å¿ä¸»å¼ ï¼
## ð å
³é®åç°
1. åç°ä¸
2. åç°äº
3. ...
## ð è¯¦ç»æè¦
### èæ¯/å¼è¨
...
### 主ä½å
容
ï¼æåæç»æå段æ»ç»ï¼ä¿çè¶³å¤ç»èï¼
### ç»è®º
...
## ð¡ åæä¸æ´å¯
ï¼å¯éï¼æè½çç¬ç«åæè§è§ï¼
## ð å¾
å¤çäºé¡¹
- [ ] å¾
确认çç¹ 1
- [ ] å¾
确认çç¹ 2
## ð ç¸å
³èµæº
ï¼ä»ææ¡£ä¸æåç龿¥ãå¼ç¨çï¼
Processing Workflow
Step 1: Identify Input Type
- If URL â fetch with WebFetch
- If PDF â use pdf skill to extract text
- If Word â use docx skill to extract text
- If Markdown/Text â read file directly
Step 2: Extract Content
- Get full text content from the document
- Note metadata (title, page count if available, source URL)
Step 3: Create Briefing
- Title: Extract or infer from content
- åºæ¬ä¿¡æ¯: Document source type, fetch time, approximate length
- æ ¸å¿è§ç¹: 1-3 sentence summary of main argument
- å ³é®åç°: Numbered list of key findings (3-7 items)
- è¯¦ç»æè¦: Full summary with background, body, conclusion
- åæä¸æ´å¯: Optional – your analysis as an expert reader
- å¾ å¤çäºé¡¹: Points that need verification or follow-up
- ç¸å ³èµæº: Extract URLs, citations, references from source
Step 4: Quality Check
Before delivering, verify:
- All sections are present
- Key information is retained (not over-condensed)
- Original structure is reflected in summary
- Links and resources are captured
- Markdown formatting is correct
Quality Guidelines
Do:
- Preserve specific numbers, names, dates, and technical details
- Maintain the original document’s logical structure
- Include relevant quotes when they add value
- Note any ambiguities or unclear points for follow-up
- Extract all relevant URLs and references
Don’t:
- Over-condense to the point of losing important detail
- Omit negative findings or contradictions
- Add information not in the source
- Use vague summaries like “discusses various topics”
Tips
- For long documents, process each section/chapter recursively but output as ONE unified briefing
- When unsure about detail level, include more rather than less
- Always preserve technical terms, acronyms, and specific data
- Note the document’s tone and intended audience if apparent
Document Type Adaptation
Different document types require different emphasis:
| Document Type | Emphasis |
|---|---|
| 论æ/ç ç©¶æ¥å | æ¹æ³è®ºãæ°æ®æ¥æºãç»è®ºãç ç©¶ä»·å¼ |
| æ°é»æ¥é | 5W1Hãæ¶é´çº¿ãå ³é®äºå® |
| å䏿¥å | å ³é®æ°æ®ã建议ãè¡å¨é¡¹ãROI |
| ææ¯ææ¡£ | æ¶æãAPIãä½¿ç¨æ¹æ³ãéå¶ |
| æ¿çæä»¶ | éç¨èå´ãæå©ä¹å¡ãçææ¶é´ |
Handling Long Documents
For documents >20 pages or with clearç« èç»æ:
- Internal recursive processing: éç« /éèæååå¤çå 容ï¼è®°å½æ¯ä¸ªç« èçæ ¸å¿è§ç¹åå ³é®åç°
- Single unified output: æç»æ´åæä¸ä»½å®æ´çç®æ¥ï¼ä¸æ¯å¤ä»½
- ç« èæ å°: å¨”è¯¦ç»æè¦”é¨åæåææ¡£ç« èç»æç»ç»å 容
- å¤çè®°å½ (å¯é): å¯å¨”ð åºæ¬ä¿¡æ¯”䏿·»å å¤ç深度说æ
å¤ççç¥ï¼éå½å¤çå
¨ææ¡£ X ç« /èï¼æ´å为åä»½ç®æ¥