agentleFS
WALKERKILLERWALKERKILLER/Look-Tongji-Notes/skills/note/SKILL.md

note

Skill53 starsChanged 5 months agoMITView on GitHub

Generate study notes from a lecture transcript and slides. Runs transcript + slide download in parallel, then writes a Markdown note with timeline outline.

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use update, resume and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    update

    Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.

    Also in 4 projects that use this

  • genomewalkerSkill

    resume

    Resume a thread by loading its ~800-token context capsule

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 4 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 5 projects that use this

  • GoogleSkill

    tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

    Also in 3 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. 0 are common, 12 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 12

    Distinctive

    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
  1. Distinctive:

    After transcribing a lecture, the user wants a structured Markdown study note.

    line 17
  2. Very specific:

    Run slide to download slides (if not already done)

    line 42
  3. Distinctive:

    Write the note manually using the existing SRT/TXT + slides

    line 43
  4. Distinctive:

    When scripting or working non-interactively:

    line 49
  5. Distinctive:

    After the CLI finishes, the agent must:

    line 67
  6. Distinctive:

    Use SRT subtitles to produce a concise timeline in Simplified Chinese.

    line 70
  7. Distinctive:

    After the CLI finishes, ask the user for their preferred note style (unless they already stated one).

    line 77
  8. Distinctive:

    Write notes into the session raw-data folder:

    line 81
  9. Distinctive:

    CRITICAL: Notes must be PURE knowledge content: No task-oriented meta descriptions.

    line 88
  10. Distinctive:

    Self-check: After writing notes, the agent MUST re-read the output and remove any sentence that describes HOW the notes were made rather …

    line 97
  11. Very specific:

    Read transcript TXT (not JSON) and slide images directly.

    line 99
  12. Very specific:

    Use LaTeX $...$ / $$...$$ for formulas.

    line 100
  13. Distinctive:

    If slides and transcript conflict, prefer slide text.

    line 101
  14. Distinctive:

    Use the appropriate note prompt based on the chosen style:

    line 107
  15. Distinctive:

    After notes are written, run:

    line 146

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Note

Generate detailed study notes from lecture transcript and slides.

When to Use

  • User says /note or "write notes for this lecture".
  • After transcribing a lecture, the user wants a structured Markdown study note.

Workflow

  1. Default combined command:
python "<SKILL_DIR>/../../scripts/look_tongji.py" note --course-id "<ID>" --sub-id "<ID>"
  1. With supplementary materials:
python "<SKILL_DIR>/../../scripts/look_tongji.py" note \
  --course-id "<ID>" --sub-id "<ID>" \
  --material "slides-from-teacher=/path/to/file.pdf"
  1. The CLI runs transcript + slide in parallel, then the agent writes notes.

Important: note Re-Runs Transcription

note always re-downloads the video and re-runs ASR, even if the lecture was already transcribed. This is by design — note = transcribe + slide + note in one combined operation.

If you already ran transcribe separately, do NOT run note. Instead:

  1. Run slide to download slides (if not already done)
  2. Write the note manually using the existing SRT/TXT + slides

This saves ~4 minutes of re-downloading and re-transcribing per lecture.

Non-Interactive / Batch Flags

When scripting or working non-interactively:

FlagDescription
--no-slideSkip slide download (transcript only)
--no-material-promptSkip "any supplementary materials?" prompt

For --no-material-prompt, use with --material to supply materials non-interactively:

python "<SKILL_DIR>/../../scripts/look_tongji.py" note \
  --course-id "<ID>" --sub-id "<ID>" \
  --no-material-prompt \
  --material "slides=/path/to/file.pdf"

Agent Responsibilities

After the CLI finishes, the agent must:

A. Generate Timeline Outline

  • Use SRT subtitles to produce a concise timeline in Simplified Chinese.
  • Format: MM:SS-MM:SS:课程阶段内容
  • 10-20 segments for a typical 60-120 min lecture.
  • Validate with: python "<SKILL_DIR>/../../scripts/timeline_tools.py" timeline-normalize

B. Write Study Notes (Markdown)

After the CLI finishes, ask the user for their preferred note style (unless they already stated one). Options:

  • standard (default): Traditional lecture notes with ### headings.
  • dialogue: Conversational Q&A between 老师和学生.

Write notes into the session raw-data folder:

  • standard style → <course_id>_<sub_id>_notes.md
  • dialogue style → <course_id>_<sub_id>_dialogue.md

Also read supplementary material conversions when available:

  • materials/<name>/converted.md

CRITICAL: Notes must be PURE knowledge content. No task-oriented meta descriptions.

FORBIDDEN phrases and patterns:

  • "本节课将学习..."、"以下是笔记内容..."、"这里我使用了..."
  • "本笔记基于..."、"根据ASR转录..."、"从幻灯片中可以看到..."
  • Any meta-commentary about the note-taking process itself
  • "接下来"、"首先"、"然后" as standalone paragraph openers (task-oriented sequencing)
  • Sentences starting with "注意:" or "提示:" that are about the note-taking process rather than course content

Self-check: After writing notes, the agent MUST re-read the output and remove any sentence that describes HOW the notes were made rather than WHAT was learned.

Read transcript TXT (not JSON) and slide images directly. Use LaTeX $...$ / $$...$$ for formulas. If slides and transcript conflict, prefer slide text.

Important responsibility boundary

  • The CLI only fetches/transcribes/downloads artifacts; it does not generate study-note Markdown content.
  • The current AI agent must organize transcript + slides and write the final Markdown notes.

Use the appropriate note prompt based on the chosen style:

If standard style (default):

You are a professional course TA. Based on the provided ASR transcript and lecture slide snapshots, write detailed study notes in Markdown (notes content in Simplified Chinese).
Requirements:
1) Output notes directly. No polite preface. No "here is the summary" opener.
2) Make the text fluent and logically structured. Fix obvious ASR errors and repetitions, but do not fabricate content not present in transcript/slides.
3) Markdown formatting: only use headings starting from ### (allow ###/####/#####). Do not use # or ##. Use bold/lists/tables when appropriate; avoid overly fragmented bullet-only output.
4) If the lecture mentions assignments/exams/attendance/grouping, put a short "### Course Reminders" section at the very top.
5) Use LaTeX for variables and formulas: inline $...$, block $$...$$. Do not put non-ASCII characters inside LaTeX.
6) Be faithful to transcript/slides and include enough details so that a student can learn from the notes (not just an outline).
7) If transcript and slides conflict, prefer slide text for terminology/spelling and briefly note uncertainty.
Now write the notes from transcript + slides:

If dialogue style:

You are a professional course TA. Based on the provided ASR transcript and lecture slide snapshots, write study notes in **dialogue format** in Simplified Chinese.

CRITICAL OUTPUT RULES:
1) Output notes directly. No polite preface. No "here is the summary" opener.
2) Write in a natural Q&A conversation between "**老师**" (teacher) and "**学生**" (student):
   - "学生" raises questions that a real learner would have at each stage
   - "老师" answers using the lecture content and slides
   - Switch roles naturally as the lecture progresses through topics
3) Strict format for each exchange (one blank line between turns):
   **学生**:[学生提出的问题或疑惑]

   **老师**:[老师的解答和讲解,包含知识点、公式、示例]
4) Cover ALL major topics from the lecture in order. Do not skip sections.
5) Use LaTeX for variables and formulas: inline $...$, block $$...$$. Do not put non-ASCII characters inside LaTeX.
6) Be faithful to transcript/slides. Fix obvious ASR errors and repetitions, but do not fabricate content not present in transcript/slides.
7) If transcript and slides conflict, prefer slide text for terminology/spelling and briefly note uncertainty.
8) If the lecture mentions assignments/exams/attendance/grouping, include it naturally in the dialogue.
Now write the dialogue notes from transcript + slides:

C. Rebuild Wiki

  • After notes are written, run:
python "<SKILL_DIR>/../../scripts/look_tongji.py" index
python "<SKILL_DIR>/../../scripts/look_tongji.py" build

Artifacts

  • <course_id>_<sub_id>_timeline.txt — timeline outline
  • <course_id>_<sub_id>_notes.md — study notes (standard style)
  • <course_id>_<sub_id>_dialogue.md — study notes (dialogue style)

Where <SKILL_DIR> Points

<SKILL_DIR> is the directory containing this SKILL.md. Shared scripts (look_tongji.py, timeline_tools.py, tongji_backend/) and references live two levels up in the repository root (<SKILL_DIR>/../../scripts/ and <SKILL_DIR>/../../references/).

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.