- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add 917Dhj/DeepPaperNote --skill research-memory -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add 917Dhj/DeepPaperNote --skill research-memory -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add 917Dhj/DeepPaperNote --skill research-memory -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add 917Dhj/DeepPaperNote --skill research-memory -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/917Dhj/DeepPaperNote/tree/HEAD/skills/research-memoryDe l'éditeur
Keep <vault>/DeepPaperNote/research-memory.md true to the user's research by interviewing them. The user never writes the memory alone: you propose, with evidence from what they have read; they confirm, correct, or add. Only confirmed answers reach the file, and only through scripts/write_research_memory.py. This skill writes that one file and never touches paper notes.
references/file-contract.md defines the file format and the JSON both scripts read and write. Read it before step 4.
Run python3 scripts/aggregate_reading.py --output <tmp>/aggregate.json. It finds the vault through DeepPaperNote's configuration. On needs_vault or not_a_vault, ask the user once for their Obsidian vault folder and rerun with --vault <path>.
Keep memory.sha256 from this run; step 4 passes it to the writer.
Done when the aggregate reports status: ok.
memory.exists picks the mode. Build the list of open candidates, each a statement you will ask the user to confirm, with its evidence: counts and up to five notes by title from the aggregate.
Building (no memory file yet):
enough_reading true, propose candidate directions from clusters across aggregates.methods, datasets, tasks, domains, and the recent window. The user's own words weigh most: papers[].my_notes and papers[].judgments.enough_reading false, propose no direction from reading; ask for directions directly.Updating (the file exists):
recent_90_days, asking whether to keep each; the new reading observations.In both modes:
legacy_count above zero, the first round states how many notes lack structured fields and that the counts may be incomplete.Done when every candidate is on the list.
Ask in rounds of at most four numbered questions, in the user's language. Each question asks one thing and ends with your proposed answer and its evidence, worded so "yes" accepts it. The user may answer tersely ("1 是,2 不是,3 改成……").
❓ **Q1** - 你读过的 23 篇里有 9 篇关于指令数据合成(Self-Instruct、Alpaca、……),其中 3 篇的"我的笔记"提到心理咨询。
➡️ 建议写成研究方向:用大模型合成心理咨询对话数据。
Done when no candidate is open and nothing is left to ask.
Turn the confirmed answers into the JSON from references/file-contract.md:
--create <content.json> --expected-sha256 absent --language <aggregate language> --dry-run, and show the user text in full.--update <changes.json> --expected-sha256 <memory.sha256> --dry-run, and show the user diff. Point out any hand-written text the new reading observations replace.Reading observations state facts about what the user read, each with at most five evidence targets copied from papers[].target. With enough_reading false, pass an empty list.
After the user confirms, run the same command without --dry-run. A refusal names its cause:
Done when the writer reports written: true, or the user declined the preview.
Give the file path and what changed. Say that DeepPaperNote reads My Research Directions to shape each note's transferable ideas whenever a request names no direction, and that the user can edit the first two sections in Obsidian at any time.
Use when the user wants to build, update, or review their research memory (研究记忆), the Obsidian note of their research directions that DeepPaperNote reads to tailor each paper's takeaways.
---name: research-memorydescription: Use when the user wants to build, update, or review their research memory (研究记忆), the Obsidian note of their…---# skills/research-memory/SKILL.mdFAQ
Téléchargez skills/research-memory/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/917Dhj/DeepPaperNote.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.