looplia build
The build command uses AI to generate a workflow definition from a natural language description.
looplia build [description] [options]Arguments
Section titled “Arguments”| Argument | Description |
|---|---|
description | Natural language description of the workflow (optional) |
Options
Section titled “Options”| Option | Description |
|---|---|
--name <name> | Workflow name (auto-generated if not provided) |
Examples
Section titled “Examples”Interactive Mode
Section titled “Interactive Mode”# Start the interactive build wizardlooplia buildThe wizard guides you through:
- Describing what you want to accomplish
- Answering clarifying questions
- Reviewing the generated workflow
- Saving to
~/.looplia/workflows/
Direct Mode
Section titled “Direct Mode”# Generate workflow from descriptionlooplia build "analyze videos and create blog outlines"
# With explicit namelooplia build --name video-to-blog "analyze YouTube video transcripts and generate blog post outlines with key points"How It Works
Section titled “How It Works”The build command uses three skills in sequence:
-
plugin-registry-scanner
Discovers all available skills from installed plugins.
Found 8 skills:- media-reviewer (content analysis)- idea-synthesis (creative generation)- writing-kit-assembler (document assembly)... -
skill-capability-matcher
Matches your requirements to available skills.
Requirement: "analyze videos"→ Matched: media-reviewer (content analysis, supports video transcripts)Requirement: "create blog outlines"→ Matched: writing-kit-assembler (structured output generation) -
workflow-schema-composer
Generates a valid workflow YAML/Markdown definition.
---name: video-to-blogsteps:- id: analyzeskill: media-reviewermission: Analyze video transcript for key themes...---
Interactive Build Wizard
Section titled “Interactive Build Wizard”The interactive wizard provides a multi-step TUI:
┌─────────────────────────────────────────────────────┐│ Looplia Build Wizard │└─────────────────────────────────────────────────────┘
Step 1/3: Describe Your Workflow┌─────────────────────────────────────────────────────┐│ What do you want to accomplish? ││ ││ > analyze podcast transcripts and create ││ newsletter content with key takeaways │└─────────────────────────────────────────────────────┘
Step 2/3: Clarifying Questions┌─────────────────────────────────────────────────────┐│ How long should the newsletter content be? ││ ○ Brief (200-300 words) ││ ● Standard (500-800 words) ││ ○ Detailed (1000+ words) │└─────────────────────────────────────────────────────┘
Step 3/3: Review & Save┌─────────────────────────────────────────────────────┐│ Generated workflow: podcast-newsletter ││ ││ Steps: ││ 1. media-reviewer → Analyze transcript ││ 2. idea-synthesis → Generate newsletter ideas ││ 3. writing-kit-assembler → Create newsletter ││ ││ [Save] [Edit] [Cancel] │└─────────────────────────────────────────────────────┘Generated Workflow
Section titled “Generated Workflow”The output is a standard workflow markdown file:
---name: podcast-newsletterversion: 1.0.0description: Transform podcast transcripts into newsletter content
steps: - id: analyze skill: media-reviewer mission: | Analyze the podcast transcript to extract: - Main topics and themes discussed - Key quotes from speakers - Actionable insights for listeners input: ${{ sandbox }}/inputs/content.md output: ${{ sandbox }}/outputs/analysis.json
- id: ideas skill: idea-synthesis mission: | Generate newsletter content ideas including: - Compelling subject lines - Key takeaways (3-5 bullet points) - Call-to-action suggestions needs: [analyze] input: ${{ steps.analyze.output }} output: ${{ sandbox }}/outputs/ideas.json
- id: newsletter skill: writing-kit-assembler mission: | Assemble a complete newsletter draft (500-800 words) with introduction, key points, and conclusion. needs: [analyze, ideas] input: - ${{ steps.analyze.output }} - ${{ steps.ideas.output }} output: ${{ sandbox }}/outputs/newsletter.json final: true---
# Podcast Newsletter Workflow
Transforms podcast transcripts into engaging newsletter content.Tips for Good Descriptions
Section titled “Tips for Good Descriptions”Good descriptions:
- “Analyze YouTube video transcripts and create Twitter thread drafts with key insights”
- “Transform research papers into accessible blog posts with simplified explanations”
- “Extract action items and key decisions from meeting transcripts”
Vague descriptions (will prompt for clarification):
- “Process content” (what kind? what output?)
- “Write something” (based on what? in what format?)
See Also
Section titled “See Also”- Understanding Workflows — Workflow schema reference
- Building Custom Workflows — Manual workflow creation
- run — Execute your new workflow