Test Orchestrator

Automated testing framework for ClaudeKit Marketing workflows.

When to Use

• Testing new commands after implementation
• Validating agent orchestration flows
• Verifying skill integrations work correctly
• Regression testing after changes
• End-to-end workflow validation

Workflow

1. Scan Components

# Generate fresh catalogs
python .claude/scripts/generate_catalogs.py --all

# Or scan specific type
python .claude/skills/test-orchestrator/scripts/scan-components.py

2. Select Test Scope

3. Execute Tests

Each test step pauses for manual verification:

[STEP 1/5] Executing: /youtube:social "https://youtube.com/..."
─────────────────────────────────────────────────
[OUTPUT]
...generated content...
─────────────────────────────────────────────────
[VERIFY] Check output matches expected format
[PASS/FAIL?] > _

Test Case Format

name: youtube-to-social-flow
description: Convert YouTube video to multi-platform social posts
type: integration

steps:
  - name: Extract video data
    action: vidcap summary
    input: "https://youtube.com/watch?v=dQw4w9WgXcQ"
    verify:
      - Response contains video title
      - Response contains summary content

  - name: Generate social posts
    action: /youtube:social
    input: "{video_url}"
    verify:
      - Twitter post under 280 chars
      - LinkedIn post has professional tone
      - No anti-pattern hooks used

  - name: Apply writing style
    action: copywriting skill
    input: Apply casual style to Twitter post
    verify:
      - Contains contractions
      - Uses first-person

Pre-Built Test Scenarios

1. YouTube Pipeline

2. Content Creation

3. Email Automation

4. Brand Consistency

Happy Case Prompts

Pre-validated inputs that should always succeed:

youtube_url: "https://www.youtube.com/watch?v=dQw4w9WgXcQ"
blog_topic: "10 productivity tips for remote workers"
email_flow: "welcome"
brand_preset: "ocean-professional"
social_platform: "twitter"
writing_style: "casual"

Manual Verification Checklist

At each step, verify:

• Output format matches expected structure
• No error messages in response
• Content quality acceptable
• Anti-patterns avoided (for hooks)
• Brand voice consistent (if applicable)
• File saved to correct path (if applicable)

Integration

Use with:

• /test command to launch test runner
• debugging skill for failure analysis
• code-review skill for output validation