ClawHub

Transcript

v1.4.1

Get transcripts from any YouTube video — for summarization, research, translation, quoting, or content analysis. Use when the user shares a video link or asks "what did they say", "get the transcript", "transcribe this video", "summarize this video", or wants to analyze spoken content.

⭐ 1· 4.3k·15 current·15 all-time
byRohit Das@therohitdas
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (fetch YouTube transcripts) match the declared requirements: node binary (the shipped CLI is Node) and TRANSCRIPT_API_KEY (the service's API key). The declared config path (~/.openclaw/openclaw.json) is used to persist the API key for the agent — this is consistent with the skill's purpose.
✓
Instruction Scope
SKILL.md instructs the user to register/verify via the included scripts/tapi-auth.js, then call transcriptapi.com (curl examples) using the API key. The instructions only reference the openclaw config file and the API key; they do not request unrelated system files or additional credentials. The script sends requests to transcriptapi.com and writes only to ~/.openclaw/openclaw.json (with a .bak backup) — which matches the documentation.
✓
Install Mechanism
No install spec (instruction-only) and the only runtime dependency is node. There are no downloads from arbitrary URLs or archive extraction steps. The included CLI is shipped as a local script, so no external install mechanism is required.
✓
Credentials
Only TRANSCRIPT_API_KEY is required (declared as primaryEnv). That single API credential is appropriate and necessary to interact with the third-party TranscriptAPI service. The script uses short-lived session tokens only during verification and does not request unrelated secrets.
✓
Persistence & Privilege
The skill writes its own API key into the agent's openclaw config (~/.openclaw/openclaw.json) and backs up the file before modification; this is proportional for enabling the skill. always:false and user-invocable:true are appropriate. The skill does not modify other skills' configs or system-wide settings beyond its mentioned config file.
Assessment
This skill appears internally consistent: it uses the included Node CLI to register/verify and obtain a TRANSCRIPT_API_KEY from transcriptapi.com, and then stores that key in ~/.openclaw/openclaw.json (backing up the file first). Before installing, confirm you trust transcriptapi.com (privacy, billing, and content policies) and are comfortable storing an API key in your OpenClaw config. The script will send your email/OTP to transcriptapi.com during signup and then save the returned API key locally; it explicitly blocks disposable emails. If you prefer not to have the agent write to your config, you can manually create an account via the homepage and export TRANSCRIPT_API_KEY into your shell instead. Finally, be aware that the agent may call this skill autonomously (default behavior), so consider whether you want automatic transcript requests enabled for your agent.

Like a lobster shell, security has layers — review code before you run it.

latestvk973q9tkxs1h7hftgs8swtts1n80zhfr

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

📝 Clawdis
Binsnode
EnvTRANSCRIPT_API_KEY
Config~/.openclaw/openclaw.json
Primary envTRANSCRIPT_API_KEY

Comments