hebrew-tech-lecture-summary

Summarizing texts and content in Hebrew

Creates a structured summary in Markdown from any content — a lecture, meeting, article, transcript, or any other text.

The output is always in Hebrew — even if the original material is in English.

Workflow

Receive the content to summarize — one of the options:
- Text the user pasted directly
- A transcript file (usually output/transcription_plain.txt)
- A link, article, or any other material provided
Analyze the content: identify topics, speakers, questions, and important quotes
Write the summary in Hebrew according to the structure intemplate.md
If it is a file — save according to the rules in"Saving the summary file" below
(Optional) Convert to Word — see the "Export to Word" step below

Strictly forbidden

Do not add any editorial note that does not come from the transcript.

Examples of forbidden notes:

"This is the summary for whoever wanted the content"
"Those who did not attend can listen to the recording"
"The summary was written based on the transcript only"
"For further details, one can contact the lecturer"
Any sentence that is not direct content from the transcript

Follow template.md only. Do not add, do not explain, do not respond — just write the summary.

Saving the summary file

Choosing a file name

Before saving, check whether output/lecture_summary.md already exists.

If the file does not exist — save asoutput/lecture_summary.md.

If the file already exists — create a more suitable name according to the formula:

output/summary_<נושא-בקצרה>.md

Rules for constructing the name:

Derive the topic from the main heading of the summary (# סיכום: [נושא])
Use 2–4 words from the topic (in English if the topic is technical, in transliterated Hebrew if not)
Replace spaces with_, remove special characters
Examples: summary_ci_cd_pipeline.md, summary_product_review.md, summary_agile_sprint.md

After saving under an alternative name, notify the user:

"output/lecture_summary.md already exists — the summary was saved under the name: output/summary_<שם>.md"

The same rule for a Word file

If during export to.docx a file with the same name already exists — use the same alternative-name logic and notify the user.

Writing rules

Language and terms

The summary always in Hebrew — regardless of the language of the original material (Hebrew, English, or any other language)
Tech and programming concepts remain in English
Examples: production, deploy, PR, build, MCP, workspace, branch, commit, Docker image, rollout, pipeline, CI/CD, code review, unit test, integration test, API, endpoint, repository
Tool and product names in English: Cursor, Jenkins, Argo, Splunk, Jira, GitHub

Step-by-step instructions

When there is a process or sequence of actions, use arrows:

git clone --> פתיחת workspace ב-Cursor --> הרצת build --> deploy ל-QA

Summary structure

The summary must be chronological -- in the order in which things were said in the lecture. See template.md for the full structure.

Content principles

Full value -- whoever missed the lecture should receive all the essential content
Concrete -- specific examples, not generalizations
Audience questions -- every question and answer, this is an important part of the value
Quotes -- strong and precise sentences that were said in the lecture
Do not invent content that was not said in the lecture
If part of the transcript is unclear -- skip it, do not guess

Export to Word (optional)

After saving the summary in Markdown, you can convert it to a Word file:

python "<skill_dir>/scripts/md_to_word.py" "<path_to_summary.md>"

The command saves the.docx next to the Markdown file, in the same folder.

Dependencies: The script requires python-docx (see requirements.txt).

Read the output and act accordingly:

Output	Action
`[DONE] /path/to/file.docx`	Report to the user about the file that was created
`[MISSING_DEP] python-docx is not installed.`	Show the user the following message andcontinue anyway (do not stop)
`[ERROR] ...`	Show the error to the user

When the library is missing, say to the user:

"To export to Word, you need to install python-docx:
pip install python-docx
The summary is saved in Markdown and is valid — you can export to Word at any time."

Then continue. Do not block the summarization process because of the missing library.

Important: no editorial notes

The summary is content only. Do not add:

Your own introductions or conclusions
References to the recording, the lecturer, or external sources
Explanations about how the summary was written
Anything that is not part of the structure intemplate.md