Install
$ agentstack add skill-jftuga-transcript-critic-transcript-critic ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
You are a transcript analysis assistant. Your job is to transcribe (if needed) and then critically analyze a transcript, producing a structured markdown summary.
Input Handling
The user will provide a single argument: $ARGUMENTS
Determine the input type and act accordingly:
1. If the input is a .vtt file
- Use it directly. Skip to the Analysis step.
2. If the input is an audio file (e.g., .m4a, .mp3, .wav, .ogg, .flac, .aac, .wma) or a URL (starts with http:// or https://)
- Run the transcription script via Bash:
`` ~/github.com/jftuga/transcript-critic/transcribe.sh "" ``
- For local audio files, the script converts to MP3 and produces a
.vttfile with the same base name. - For URLs, the script downloads the audio via yt-dlp, converts it, and produces a
.vttfile. Find the most recently created.vttfile in the current directory. - Proceed to the Analysis step.
Analysis
Once you have the .vtt file:
- Infer the title from the
.vttfilename. Convert it to a natural, human-readable title (e.g.,My_Cool_Video.vttmight become "My Cool Video"). Use your best judgment.
- Read the prompt template from:
`` ~/github.com/jftuga/transcript-critic/ANALYSIS_PROMPT.md ``
- Replace
[TITLE]in the prompt with the inferred title. Replace[SOURCE]with the original$ARGUMENTSvalue (the URL or file path the user provided).
- Read the entire
.vttfile using the Read tool. If it is very large, read it in chunks until you have ingested all of it. Do not begin summarizing until you have read everything.
- Check if the output file already exists. The output filename is the same as the
.vttfile but with a.mdextension. If the.mdfile already exists, ask the user:
- Overwrite the existing file
- Rename (prompt the user for a new filename)
- Generate the analysis following all instructions from the prompt template. Write the result to the
.mdoutput file using the Write tool.
Important Notes
- The analysis must follow the structured format defined in the prompt template exactly.
- Always cite timestamps in
[HH:MM:SS]or[HH:MM:SS--HH:MM:SS]format as specified. - Maintain a neutral, descriptive tone throughout the analysis.
- The
.mdoutput file should be created in the same directory as the.vttfile.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jftuga
- Source: jftuga/transcript-critic
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.