47 lines
3.1 KiB
Markdown
47 lines
3.1 KiB
Markdown
---
|
|
name: read-trans
|
|
description: Reads a YouTube transcript (pasted text or a .txt/.srt/.vtt file) and explains it in simple Tanglish - Tamil written in English letters with technical words kept in English. Gives a 2-line short version, a medium explanation, and a "what do I do in my projects" takeaway with a ready-to-copy prompt. Use whenever the user types /read-trans, pastes a YouTube/video transcript, or says "transcript Tanglish la sollu", "intha video enna solluthu", "video explain pannu", even if they don't say "read-trans".
|
|
---
|
|
|
|
# Read Trans
|
|
|
|
Turn a YouTube transcript into a Tanglish explanation the user can read in two minutes and act on. The user is a developer who watches English tech videos and wants to know: what happened, and what should I do in my own projects.
|
|
|
|
## Input
|
|
|
|
- Transcript pasted after `/read-trans`, or a file path (`.txt`, `.srt`, `.vtt`). Read the file if a path is given.
|
|
- Only a YouTube link and no transcript: you can't watch the video. Ask the user to paste the transcript. Don't guess from the title.
|
|
- Strip timestamps (`0:07`, `1 minute, 4 seconds`), `Chapter N:` lines and caption numbering before reading.
|
|
|
|
## Output
|
|
|
|
Always these 4 sections, in this order, with these headings:
|
|
|
|
### 1. Video enna solluthu (short)
|
|
Exactly 2 lines. What the speaker did and what he found.
|
|
|
|
### 2. Medium explanation
|
|
Numbered points (4-6). Tell it as a sequence: what he set up, what he ran, what happened, what surprised him. Say it so a person who did not watch can picture it. Name the tools, models, numbers and prices he mentions (e.g. "Sonnet ~$22, Opus ~$137").
|
|
|
|
### 3. Final takeaway
|
|
3-5 bullets: only the lessons the speaker himself states or clearly shows. One bullet = one idea. No own arithmetic, no own conclusions here.
|
|
|
|
### 4. Unga projects-ku enna pannanum
|
|
This is the part the user cares about most. Concrete, numbered steps the user can do today, not the speaker's story. Steps that come from the video are plain. Steps that are your own idea end with "(En idea)" so the user knows the speaker didn't say it. End with one ready-to-copy prompt or command in a fenced block, if the video is about prompting or tooling. If the video gives nothing actionable, say so in one line instead of inventing steps.
|
|
|
|
## Language rules
|
|
|
|
- **Tanglish = spoken Tamil in English letters** ("idhu romba nalla irukku", "panna num"). Not Tamil script, unless the user asks for Tamil script.
|
|
- Keep technical words in English: prompt, API, model, session, code, test, feature, deploy.
|
|
- Short sentences. Simple words. No formal Tamil.
|
|
- Sections 1-3 carry only what the speaker said. Your own comments or ideas go only in section 4, marked "(En idea)".
|
|
- Copy qualifiers exactly: "did not work" is not "broke", "about $22" is not "$22 exactly".
|
|
- Skip sponsor plugs, "like and subscribe", and intros that carry no information.
|
|
- If the speaker's own claim looks doubtful (e.g. a number that doesn't add up), say so in one line.
|
|
|
|
## Don't
|
|
|
|
- Don't quote the transcript line by line. Explain it.
|
|
- Don't pad. If the transcript is short, the output is short.
|
|
- Don't write files unless the user asks. Reply in chat.
|