research-note-wrap
Skill18 starsChanged 8 months agoMITView on GitHub
Use when the user wants to summarize research or analysis into a readable Obsidian markdown note, such as 总结调研, 输出结论, 总结分析, 输出笔记, 调研纪要, 分析纪要, 会话结论, or when asking to summarize today's sessions about a topic. Use for current-session summaries by default, and for cross-session topic summaries when the user mentions 今天会话 or gives a topic scope.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- borgesme/fastapi-general-templateword for word, first seen Apr 9, 2026
Other versions1 project uses a version of this.
Word for word · 1
- borgesme/fastapi-general-template★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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.
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. About 0 are common, 21 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈21
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Write in Simplified Chinese by default.
- Distinctive: line 16
Do not produce a chronological 流水账.
- Distinctive: line 17
Use tables first when comparing multiple problems, hypotheses, conclusions, impacts, or next actions.
- Very specific: line 18
After the tables, provide a short 关键结论 section.
- Distinctive: line 19
Only include code-level details when they are truly necessary to support the conclusion.
- Distinctive: line 20
If you mention a file, function, method, or code path, explain in Chinese:
- Distinctive: line 24
Default to writing the note file after confirmation.
- Distinctive: line 30
If the user says things like:
- Very specific: line 50
If the user explicitly provides another time range, follow that range.
- Distinctive: line 54
Before writing the file:
- Distinctive: line 56
Check whether the current project's AGENTS.md explicitly defines a default output directory for research / analysis summary notes.
- Distinctive: line 57
If AGENTS.md already defines it, follow that path directly.
- Distinctive: line 58
If it does not define a path, ask the user for the output directory the first time.
- Distinctive: line 63
Do not write the file immediately after the first draft.
- Distinctive: line 80
After the user confirms the problem framing, present the conclusions.
- Distinctive: line 98
Only after both confirmations:
- Distinctive: line 101
write the markdown file
- Distinctive: line 106
Use this structure by default.
- Very specific: line 158
If the topic is unclear, use a short neutral fallback such as session-research.
- Distinctive: line 169
Add a new section such as:
- Distinctive: line 175
Only create a new file if the user explicitly asks for a separate note.
- Distinctive: line 181
Prefer contrast and synthesis.
- Distinctive: line 182
Keep wording human-readable and Chinese-first.
- Distinctive: line 194
Before writing the file, verify:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
research-note-wrap
Overview
Summarize the current session, or today's related sessions for a given topic, into an Obsidian Markdown note that is easy to review later. Prioritize core problems, comparative analysis, and clear conclusions over code detail or process narration.
Core Rules
- Write in Simplified Chinese by default.
- Prioritize logical conclusions over coding details.
- Do not produce a chronological 流水账.
- Use tables first when comparing multiple problems, hypotheses, conclusions, impacts, or next actions.
- After the tables, provide a short
关键结论section. - Only include code-level details when they are truly necessary to support the conclusion.
- If you mention a file, function, method, or code path, explain in Chinese:
- what it does
- why it matters
- how it supports the conclusion
- Default to writing the note file after confirmation; do not stop at chat-only output unless the user explicitly asks not to write a file.
Scope Decision
Default scope
If the user says things like:
- 总结调研
- 输出结论
- 总结分析
- 输出笔记
- 调研纪要
- 分析纪要
- 会话结论
Then summarize the current session only.
Cross-session scope
If the user says things like:
- 总结今天会话关于 xx 的分析
- 汇总今天关于 xx 的调研
- 总结今天相关会话中的 xx 问题
Then collect today's related sessions about the given topic and synthesize them into one note.
If the user explicitly provides another time range, follow that range. Otherwise, 近期 defaults to 当天.
Output Location Decision
Before writing the file:
- Check whether the current project's
AGENTS.mdexplicitly defines a default output directory for research / analysis summary notes. - If
AGENTS.mdalready defines it, follow that path directly. - If it does not define a path, ask the user for the output directory the first time.
- Once the user gives a path, use it for the current task. Suggest adding it to
AGENTS.mdif this is a recurring workflow.
Confirmation Workflow
Do not write the file immediately after the first draft. Use this confirmation sequence:
Step 1: Draft the main problems
Extract and compress the discussion into a high-density problem summary. Prefer a table like this:
## 问题对比表
| 问题 | 现象/信号 | 核心判断 | 当前结论 | 影响 |
|---|---|---|---|---|
| 问题 A | ... | ... | ... | ... |Then ask the user to confirm whether these are the right 主要问题.
Step 2: Draft the conclusions
After the user confirms the problem framing, present the conclusions. Prefer a compact table first, then a short conclusion block:
## 结论对比表
| 主题 | 结论 | 依据 | 风险/边界 |
|---|---|---|---|
| xx | ... | ... | ... |
## 关键结论
1. ...
2. ...
3. ...Then ask the user to confirm whether these are the right 结论.
Step 3: Write the note file
Only after both confirmations:
- finalize title
- finalize file path
- write the markdown file
- report the saved path back to the user
Output Structure
Use this structure by default. Keep it concise and dense.
---
title: <标题>
date: <YYYY-MM-DD>
project: <项目名或路径>
tags: [research, summary]
source: <current-session | today-topic-synthesis>
---
# <标题>
## 问题对比表
| 问题 | 现象/信号 | 核心判断 | 当前结论 | 影响 |
|---|---|---|---|---|
| ... | ... | ... | ... | ... |
## 结论对比表
| 主题 | 结论 | 依据 | 风险/边界 |
|---|---|---|---|
| ... | ... | ... | ... |
## 关键结论
1. ...
2. ...
3. ...
## 必要实现位点(仅在真的重要时)
| 位点 | 逻辑/作用 | 为什么关键 |
|---|---|---|
| `path:line` / `symbol` | 它负责什么 | 它如何支撑结论 |
## 未决项 / 后续建议
| 项目 | 说明 |
|---|---|
| ... | ... |File Naming
Default filename format:
YYYY-MM-DD-<topic>.mdExamples:
2026-03-30-dsa-sidecar-pinned-ref.md2026-03-30-hqchart-data-contract.md2026-03-30-session-research.md
If the topic is unclear, use a short neutral fallback such as session-research.
Follow-up Research After Initial Output
If the user says things like:
- 再调研 xx 输出到文件中去
- 补充分析 xx 并写入笔记
Then:
- Reuse the current note file by default.
- Add a new section such as:
## 追加专题:xx- Only create a new file if the user explicitly asks for a separate note.
Writing Guidance
Good
- Compress repeated discussion into one row or one conclusion.
- Prefer contrast and synthesis.
- Keep wording human-readable and Chinese-first.
- Explain technical references in plain Chinese.
Avoid
- Long process transcripts
- Tool chatter
- Repeating the same conclusion in multiple bullets
- Dumping file paths or function names without explanation
- Overusing multi-level bullet lists when a table is clearer
Final Checklist
Before writing the file, verify:
- The scope is correct: current session or today's related sessions.
- The output path follows
AGENTS.md, or has been explicitly confirmed with the user. - The user has confirmed both:
- 主要问题
- 核心结论
- Tables carry the dense comparison content.
关键结论appears after the tables.- Code-level references, if any, are explained in Chinese.
- The filename matches
YYYY-MM-DD-topic.md.
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.

