YouTube Channel API Skill

📖 Introduction

This skill provides users with a one-stop channel data extraction service through BrowserAct's YouTube Channel API template. It can directly extract structured channel results from YouTube search. By simply entering search keywords and optional upload date filters, you can get clean, usable channel data directly.

✨ Features

1. No hallucinations, ensuring stable and accurate data extraction: Pre-set workflows to avoid AI generative hallucinations.
2. No CAPTCHA issues: No need to handle reCAPTCHA or other verification challenges.
3. No IP restrictions or geo-blocking: No need to handle regional IP restrictions.
4. Faster execution: Faster task execution compared to purely AI-driven browser automation solutions.
5. High cost-effectiveness: Significantly reduces data acquisition costs compared to AI solutions that consume a large number of tokens.

🔑 API Key Guide

Before running, you must first check the BROWSERACT_API_KEY environment variable. If it is not set, do not take any other actions; you should request and wait for the user to provide it. The Agent must inform the user at this point:

"Since you have not configured the BrowserAct API Key yet, please go to the BrowserAct Console to get your Key."

🛠️ Input Parameters

Agent should flexibly configure the following parameters according to user needs when calling the script:

1. KeyWords

   • Type: string
   • Description: Search keywords used to find YouTube channels.
   • Example: AI, automation, tech reviews

2. Upload_date

   • Type: string
   • Description: Filter channels that have published content within a defined time window.
   • Optional Values: This week, Any time, etc.
   • Default: Any time

🚀 Usage

Agent should execute the following standalone script to achieve "one command gets results":

# Example call
python -u ./scripts/youtube_channel_api.py "Search Keywords" "Upload date"

⏳ Running Status Monitoring

Since this task involves automated browser operations, it may take a long time (several minutes). The script will continuously output status logs with timestamps (e.g., [14:30:05] Task Status: running) while running. Agent Notes:

• While waiting for the script to return results, please keep an eye on the terminal output.
• As long as the terminal continues to output new status logs, it means the task is running normally. Do not misjudge it as a deadlock or unresponsiveness.
• If the status remains unchanged for a long time or the script stops outputting without returning a result, then consider triggering the retry mechanism.