AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Transcribe

skill-jftuga-transcript-critic-transcript-critic · by jftuga

Transcribe and critically analyze audio/video content. Accepts a .vtt file, an audio file (.m4a, .mp3, .wav, etc.), or a URL (YouTube or other yt-dlp-supported sites). Generates a structured markdown analysis.

No reviews yet
0 installs
28 views
0.0% view→install

Install

$ agentstack add skill-jftuga-transcript-critic-transcript-critic

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No 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.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-jftuga-transcript-critic-transcript-critic)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
4mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

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 →
Are you the author of Transcribe? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

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 .vtt file with the same base name.
  • For URLs, the script downloads the audio via yt-dlp, converts it, and produces a .vtt file. Find the most recently created .vtt file in the current directory.
  • Proceed to the Analysis step.

Analysis

Once you have the .vtt file:

  1. Infer the title from the .vtt filename. Convert it to a natural, human-readable title (e.g., My_Cool_Video.vtt might become "My Cool Video"). Use your best judgment.
  1. Read the prompt template from:

`` ~/github.com/jftuga/transcript-critic/ANALYSIS_PROMPT.md ``

  1. Replace [TITLE] in the prompt with the inferred title. Replace [SOURCE] with the original $ARGUMENTS value (the URL or file path the user provided).
  1. Read the entire .vtt file 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.
  1. Check if the output file already exists. The output filename is the same as the .vtt file but with a .md extension. If the .md file already exists, ask the user:
  • Overwrite the existing file
  • Rename (prompt the user for a new filename)
  1. Generate the analysis following all instructions from the prompt template. Write the result to the .md output 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 .md output file should be created in the same directory as the .vtt file.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.