← Back to Skills Marketplace
therohitdas

transcriptapi

by Rohit Das · GitHub ↗ · v1.5.0 · MIT-0
cross-platform ⚠ suspicious
6859
Downloads
3
Stars
0
Active Installs
13
Versions
Install in OpenClaw
/install transcriptapi
Description
Use when YouTube is or could be relevant — even if not mentioned: pasted video/channel/playlist links, video IDs, @handles, creator lookups, video summaries,...
Usage Guidance
Install only if you are comfortable with a third-party TranscriptAPI service receiving YouTube-related requests and with the agent using a TranscriptAPI credential. Prefer creating the account yourself, providing the key through an approved secret manager, and avoiding persistent shell-profile storage or temporary-file redaction workarounds.
Capability Analysis
Type: OpenClaw Skill Name: transcriptapi Version: 1.5.0 The transcriptapi skill provides a toolkit for interacting with YouTube data via transcriptapi.com, covering transcripts, search, and channel metadata. It includes a detailed authentication setup guide (references/auth-setup.md) that helps users register for an API key directly through the agent. While the setup instructions include techniques to bypass agent-level redaction of secrets (e.g., writing API keys to temporary files to ensure the agent can read them), these are explicitly documented as functional workarounds for specific agent environments like Hermes or Claude Code. The code logic and instructions are consistent with the stated purpose of providing a managed YouTube data service and do not exhibit signs of data exfiltration or unauthorized execution.
Capability Assessment
Purpose & Capability
The core API use is read-only and aligned with YouTube transcripts, search, channels, and playlists, but the trigger wording is broad enough to use YouTube and transcriptapi.com even when YouTube was not explicitly requested.
Instruction Scope
The setup guide goes beyond transcript/search use by directing the agent to create accounts, collect an email address and OTP, exchange them for an API key, and handle sensitive auth responses.
Install Mechanism
There is no executable installer or bundled runtime code; the risk is from agent instructions in markdown, not automatic install-time execution.
Credentials
Internet access and an API key are proportionate to the service, but user queries, YouTube identifiers, email, OTP, and auth tokens may be sent to transcriptapi.com without a strong confirmation or privacy checkpoint.
Persistence & Privilege
The guide instructs persistent storage of TRANSCRIPT_API_KEY across future and non-interactive sessions using whatever environment mechanism the agent finds, and recommends temporary-file handling to work around redaction of tokens and keys.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install transcriptapi
  3. After installation, invoke the skill by name or use /transcriptapi
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.5.0
Replace auth.js with agent-native auth-setup.md; fix YAML frontmatter (quote descriptions); add version field; move homepage into metadata.openclaw.
v1.4.1
ClawHub variant: minimal tapi-auth.js v3.0.0, only writes to ~/.openclaw/openclaw.json
v1.4.0
- Adds detailed File Writes section: explains exactly which config files and environments the API key is saved to, including cross-shell and agent setups. - Documents automatic file backup: existing config files are now backed up to `<file>.bak` before modification for safer persistence. - Updates metadata to explicitly include all config file write locations for the skill. - Clarifies the autonomous/background authentication approach, ensuring the API key is available across shells and agent sessions with no extra manual steps.
v1.3.4
- Minor formatting fix in SKILL.md: metadata YAML condensed for consistency. - No changes to API endpoints, usage, or skill features.
v1.3.3
- Simplified and modernized API authentication flow; user no longer needs to set or remember a password. - Updated setup instructions: registration now requires only an email, verification uses a token and OTP. - Added "user-invocable: true" and updated metadata for compatibility. - Channel and playlist endpoints now directly accept @handle, URL, or ID (no need to resolve first). - Clarified documentation, removed redundant environment variable password steps, and linked the OpenAPI specification for complete reference.
v1.3.2
Fix: markdown formatting + blank line between password warning and Step 2
v1.3.1
Fix: register response now echoes password + pre-filled next_command to prevent agents losing the password between register and verify steps
v1.3.0
Bundled auth script for agent-driven signup flow
v1.2.2
Fixed code block widths for proper rendering
v1.2.1
Removed separators
v1.2.0
Cleaned docs — removed internal implementation details
v1.1.0
Full v2 API support: search, channels, playlists. Accurate schemas, validation, cache TTLs.
v1.0.0
Initial release — YouTube transcripts via TranscriptAPI.com
Metadata
Slug transcriptapi
Version 1.5.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 13
Frequently Asked Questions

What is transcriptapi?

Use when YouTube is or could be relevant — even if not mentioned: pasted video/channel/playlist links, video IDs, @handles, creator lookups, video summaries,... It is an AI Agent Skill for Claude Code / OpenClaw, with 6859 downloads so far.

How do I install transcriptapi?

Run "/install transcriptapi" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is transcriptapi free?

Yes, transcriptapi is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does transcriptapi support?

transcriptapi is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created transcriptapi?

It is built and maintained by Rohit Das (@therohitdas); the current version is v1.5.0.

💬 Comments