book-highlights-processor
Skill1 starsChanged 3 months agoMITView on GitHub
Экспорт хайлайтов книг из iBooks/Zotero → Obsidian callouts с claim-заголовками и ==выделением== ключевых фраз. Триггеры — «обработай цитаты/хайлайты», «разбери экспорт из книги», «обработай импорт из iBooks/Zotero».
In this repository47 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agentops-brevitySkill
- agentops-canarySkill
- agentops-compressSkill
- agentops-delegateSkill
- analysis-kitSkill
- bear-doctorSkill
- bear-helpSkill
- bear-new-skillSkill
- bear-statsSkill
- code-grillSkill
- code-last-mileSkill
- code-review-lineSkill
- code-senior-reviewSkill
- content-article-draftSkill
- content-humanizerSkill
- content-tg-postSkill
- content-tutorial-structureSkill
- git-backlog-triageSkill
- git-conventional-commitSkill
- git-monorepo-releaseSkill
- git-pr-descriptionSkill
- git-release-tagSkill
- knowledge-structuresSkill
- note-templatesSkill
- obsidian-add-summarySkill
- obsidian-daily-appendSkill
- obsidian-emotion-logSkill
- obsidian-enrich-noteSkill
- obsidian-inbox-reviewSkill
- obsidian-ingestSkill
- obsidian-journal-reviewSkill
- obsidian-note-criticSkill
- obsidian-refactor-inboxSkill
- obsidian-refactor-lectureSkill
- obsidian-split-noteSkill
- obsidian-untangle-knotSkill
- sre-k8s-triageSkill
- srekit-postmortemSkill
- srekit-runbookSkill
- srekitSkill
- teach-ruSkill
- telegram-chat-digestSkill
- vault-archivingSkill
- vault-mermaidSkill
- vault-statsSkill
- vault-tasksSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 54
If the quote has no ✍️ note, omit the last line.
- Distinctive: line 56
Never add commentary of your own — no summary line before the quote, no takeaway after it.
- Very specific: line 72
Add ==highlight== to 2–4 phrases per quote.
- Distinctive: line 77
Avoid highlighting entire sentences — pick the densest, most meaningful fragments.
- Very specific: line 81
Keep the frontmatter and the header block (book title, author, link) as-is, with two additions (see policies in …
- Very specific: line 84
if summary is missing or empty, fill it after processing all quotes: 1–3 sentences in Russian — the book's central claim as seen through …
- Distinctive: line 86
If a field already exists with the same value, leave it.
- Distinctive: line 120
Read the full file first — understand the domain and vocabulary before generating titles.
- Distinctive: line 123
If the file is very long (20+ quotes), process and write in one pass — don't ask the user to confirm each quote.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
<!-- СГЕНЕРИРОВАНО bin/mirror.js. Не редактировать: правки затрёт следующая генерация.
Источник правды — domains/<домен>/. -->Book Highlights Processor
Transform exported book highlight files into enriched Obsidian callouts with AI-generated titles and highlighted key phrases.
Input format
The markdown file from iBooks or Zotero looks like this:
---
book: Book Title
author: Author Name
language: ru
tags:
- ibook/imported
- literature
---
## 📔 Книга: Book Title
**Автор**:: Author Name
...
---
# 🔍 How I Discovered IT
- 📚
- 🎯Quote text here, possibly several sentences or paragraphs
- ✍️Reader's own note or commentary (optional)
- 🎯Another quote
- ✍️Another noteWhat to produce
For each 🎯 quote, output an Obsidian callout:
> [!quote] Generated Title
> Quote text with ==key phrase== and ==another key phrase== highlighted.
>
> ✍️ Reader's note textIf the quote has no ✍️ note, omit the last line.
Never add commentary of your own — no summary line before the quote, no takeaway after it. The callout carries the source's words, the reader's note and nothing else; anything explaining the quote back to the reader is the filler ../../rules/note-density.md forbids.
How to generate the title
The title goes into the callout header and will likely become the filename of a future Obsidian atomic note. Naming style (claim-based, 4–8 words, language rules) — see ../../rules/file-naming.md.
Draw on the ✍️ reader note as a signal of what the reader found important — that's the insight to encode in the title, not just a paraphrase of the raw quote.
Examples from SRE context:
- "Мониторинг min/max ловит сбои, которые среднее скрывает"
- "Fallback должен существовать даже в виде тетриса"
- "Graceful Degradation требует нескольких уровней готовности"
- "Ретраи без backoff превращают деградацию в катастрофу"
How to add highlights
Add ==highlight== to 2–4 phrases per quote. Choose phrases that:
- Carry the core claim or mechanism
- Help a reader scanning the quote instantly grasp the main point
- Are short (3–8 words each)
Avoid highlighting entire sentences — pick the densest, most meaningful fragments.
Output structure
Keep the frontmatter and the header block (book title, author, link) as-is, with two additions (see policies in ../../rules/note-types-frontmatter.md):
- append
ai_generated: true, because titles and highlights in the body are agent-generated; - if
summaryis missing or empty, fill it after processing all quotes: 1–3 sentences in Russian — the book's central claim as seen through its highlights. Plain text, no wikilinks or markdown. If a non-emptysummaryalready exists, leave it untouched.
If a field already exists with the same value, leave it; do not duplicate.
Replace the entire - 📚 list block with sequential callouts — no list bullets, no 📚 wrapper, just callouts separated by a blank line.
The final file should look like:
---
(frontmatter unchanged)
---
## 📔 Книга: ...
(header block unchanged)
---
# 🔍 How I Discovered IT
> [!quote] First Title
> Quote one with ==highlights==.
>
> ✍️ Note one
> [!quote] Second Title
> Quote two with ==highlights==.
> [!quote] Third Title
> Long quote three with ==important phrase== somewhere in the middle.
>
> ✍️ Note threeWorkflow
- Read the full file first — understand the domain and vocabulary before generating titles.
- Process all quotes sequentially.
- Rewrite the file with
EditorWrite, preserving frontmatter and header section. - If the file is very long (20+ quotes), process and write in one pass — don't ask the user to confirm each quote.
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.

