Menu
NEW AGENT
MY AGENTS
ASSISTANTS
Step 1:
YouTube Audio Sample Generator
1️⃣
Perfect output
- scan ALL
2️⃣ Add
output numbers
, then...
3️⃣ Add
Subagent Numbers
(work backwards
from output number!
)
4️⃣ Add
ACTUAL Skills
to subagent
✅ DONE..Copy x4 to Step 3...
SETTINGS
LOGOUT
What Shall We Build Next?
1
Describe
Describe your task
2
Refine
Refine the plan
3
SubAgents
Review all agents
4
Deploy
Deploy your agent
Sub Agent 1
Sub Agent 2
Sub Agent 3
Sub Agent 4
Sub Agent 5
Sub Agent 6
Sub Agent 7
Sub Agent 8
Let me break down the MEDIAAGENT subagent in detail: A) SUBAGENT SUMMARY: Downloads a YouTube video and converts it to high-quality WAV format for audio processing, ensuring the audio is in the correct format for subsequent stem separation and beat analysis. B) FINAL TASK OUTPUT: A single high-quality WAV file (44.1kHz, 16-bit) containing the full audio from the YouTube video, saved to the server with a standardized filename format (e.g., "source_full_audio.wav") C) SUBAGENT INPUT: - YouTube video URL - (Optional) Desired output filename D) SUBAGENT TASK SUMMARY: YouTube URL > #193 Download Entire YouTube Video As MP3 > #178 Convert 1-20 MP3s to wav > raw WAV file E) DETAILED WORKFLOW: 1. Initial Input Processing: - Accept YouTube URL - Validate URL format - Generate standardized filename 2. Download Phase: - Use Skill #193 (Download Entire YouTube Video As MP3) - Input: YouTube URL - Output: MP3 URL on server 3. Conversion Phase: - Use Skill #178 (Convert 1-20 MP3s to wav) - Input: MP3 URL from previous step - Output: WAV URL on server - Format: 44.1kHz, 16-bit WAV F) SILOS: This subagent is simple enough that it doesn't require multiple silos - it operates in a linear fashion with each step feeding directly into the next. NOTES: 1. This subagent is intentionally straightforward with minimal complexity, as its role is purely to prepare audio for the more complex processing that follows in other subagents. 2. The output quality is crucial as it affects all downstream processing. 3. No additional filtering or processing is done at this stage - that's handled by subsequent subagents. 4. Error handling should be implemented for both the download and conversion steps.
SubAgent #1 - Diagram
Expand Diagram
Let me break down SUBAGENT 2: ANALYSISAGENT in detail. A) SUBAGENT SUMMARY: A specialized audio processing agent that analyzes an MP3 file to extract tempo information and separate it into vocal and instrumental stems, converting all outputs to WAV format for further processing. B) FINAL TASK OUTPUT: - 2x WAV files (vocal and instrumental stems) - 1x JSON/text file containing: * Detected tempo (BPM) * Beat positions (in seconds) * Downbeat positions (in seconds) All WAV files at 44.1kHz, 16-bit quality C) SUBAGENT INPUT: - 1x MP3 URL (from MEDIAAGENT) - 3x timestamp positions (in seconds) for sample extraction D) SUBAGENT TASK SUMMARY: MP3 input > #180 Extract Beatpoints & Tempo > #197 Extract Instrumental & Vocal > #178 Convert MP3 stems to WAV > Final Output E) SILOS: The agent operates in three distinct silos: SILO 1: TEMPO ANALYSIS Input: MP3 URL - Skill #180: Extract Beatpoints & Tempo of MP3 Output: Tempo data (BPM, beat positions, downbeat positions) SILO 2: STEM SEPARATION Input: MP3 URL - Skill #197: Extract Instrumental & Vocal From MP3 Output: 2x MP3 URLs (vocal and instrumental) SILO 3: FORMAT CONVERSION Input: 2x MP3 URLs from Silo 2 - Skill #178: Convert MP3s to WAV Output: 2x WAV URLs The entire process flows: 1. Input MP3 is processed simultaneously through Silo 1 and Silo 2 2. Output from Silo 2 feeds into Silo 3 3. Final output combines tempo data from Silo 1 with WAV files from Silo 3 This structured approach ensures parallel processing where possible (tempo analysis can happen simultaneously with stem separation) and maintains clear data flow between components.
SubAgent #2 - Diagram
Expand Diagram
Let me break down SUBAGENT 3 (SAMPLEAGENT) in detail: A) SUBAGENT SUMMARY: A specialized audio processing agent that takes vocal and instrumental stems and generates beat-aligned samples of varying lengths (1, 2, 4, and 8 beats) from three specified timestamp positions. B) FINAL TASK OUTPUT: Two collections of beat-aligned WAV audio samples (one for vocals, one for instrumentals): - 3 timestamp positions × 4 sample lengths = 12 samples per stem type - Each WAV file: 44.1kHz, 16-bit - Named format: "[timestamp]sec_[stem-type]_[beat-length]beat.wav" - Total output: 24 WAV files (12 vocal + 12 instrumental) C) SUBAGENT INPUT: - Two WAV files (vocal stem and instrumental stem) - Three specific timestamps (in seconds) - BPM/tempo data - Beat position data (from previous agent) E) SUBAGENT TASK SUMMARY: For each stem type (vocal/instrumental): 1. Input WAV > #219 Cut WAV (at timestamp 1) > 4 samples (1,2,4,8 beats) 2. Input WAV > #219 Cut WAV (at timestamp 2) > 4 samples (1,2,4,8 beats) 3. Input WAV > #219 Cut WAV (at timestamp 3) > 4 samples (1,2,4,8 beats) F) SILOS: SILO 1: VOCAL STEM PROCESSING - Input: vocal.wav + timestamps + tempo data - Process: 3 rounds of #219 (one per timestamp) - Output: 12 vocal samples (3 positions × 4 lengths) SILO 2: INSTRUMENTAL STEM PROCESSING - Input: instrumental.wav + timestamps + tempo data - Process: 3 rounds of #219 (one per timestamp) - Output: 12 instrumental samples (3 positions × 4 lengths) Each silo runs independently but identically, using the same timestamps and beat calculations. The #219 skill is used repeatedly but with different parameters each time to generate the various beat-length samples. The agent automatically names and saves each file according to the specified naming convention.
SubAgent #3 - Diagram
Expand Flow
Let me break down SUBAGENT 4: PACKAGEAGENT in detail. A) SUBAGENT SUMMARY: A packaging agent that organizes processed audio samples, generates metadata, and creates a structured zip archive of the final sample pack. B) FINAL TASK OUTPUT: A single .zip file containing: - 24-48 .wav files (44.1kHz, 16-bit) - Organized in folders (vocals/instrumentals) - Named systematically (e.g., "130sec_vocal_4beat_1.wav") - metadata.json file containing: - Original YouTube URL - Detected BPM - Sample timings - Number of samples - File organization structure C) SUBAGENT INPUT: - Collection of .wav files from SUBAGENT 3 (both vocal and instrumental) - Original YouTube URL - BPM/tempo data - Original timestamp positions - Beat lengths used for samples E) SUBAGENT TASK SUMMARY: 1. Generate metadata (#223 Powerful LLM Prompt-to-Text Response) - Input: Collection of data points - Output: Structured JSON text 2. File organization and naming - Using built-in file organization function - Create folder structure - Rename files systematically 3. Create zip archive - Built-in zip function to package all files - Return final zip URL F) SILOS: SILO 1: METADATA GENERATION - Purpose: Create structured metadata file - Input: All technical data about samples - Skills: #223 - Output: metadata.json file SILO 2: FILE ORGANIZATION - Purpose: Structure and rename files - Input: All .wav files - Skills: Built-in file organization function - Output: Organized file structure with renamed files SILO 3: ARCHIVE CREATION - Purpose: Create final zip package - Input: Organized files + metadata - Skills: Built-in zip function - Output: Final .zip file The key insight here is that this subagent is primarily focused on organization and packaging, rather than audio processing. It needs to create clear, systematic organization of the files while preserving all technical metadata for future reference. The agent works in three distinct silos: metadata creation, file organization, and final packaging.
4 Template & Links
Expand Flow
I notice that you've asked me to analyze "subagent 5", but in the original agent breakdown, there were only 4 subagents listed (MediaAgent, AnalysisAgent, SampleAgent, and PackageAgent). There was no subagent 5 defined. Would you like me to: 1. Analyze one of the existing 4 subagents in detail 2. Propose a new subagent 5 that might enhance the workflow 3. Clarify which specific subagent you'd like me to focus on Please let me know which option you'd prefer, and I'll provide a detailed breakdown following the format you've specified.
5 Template & Links
Expand Flow
I notice that you've asked me to analyze "subagent 6" but in the original agent breakdown there were only 4 subagents listed (MediaAgent, AnalysisAgent, SampleAgent, and PackageAgent). There was no subagent 6 defined in the original workflow. Would you like me to: 1. Analyze one of the existing 4 subagents in detail 2. Propose a new subagent (subagent 6) that might add value to the workflow 3. Clarify which specific subagent you'd like me to focus on Please let me know which option you'd prefer, and I'll provide a detailed breakdown following the format you've specified.
6 Template & Links
Expand Flow
Templates & Links Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.
7 Template & Links
Expand Flow
Questions & Research Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.
8 Template & Links
Expand Flow
Templates & Links Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.
9 Template & Links
Expand Flow
Templates & Links Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.
10 Template & Links
Expand Flow
Questions & Research Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.
11 Template & Links
Expand Flow
Templates & Links Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.
12 Template & Links
Expand Flow
Need To Start Afresh?
BACK TO REFINE
Tweaked & Good To Go?
PROCEED TO DEPLOY