deep-validation

---

name: deep-validation description: Validation patterns beyond HTTP 200. Use when building validation logic, testing Twilio integrations, or understanding status progression, Voice Insights, and debugger alert patterns.

Deep Validation Patterns for Twilio

This skill covers validation patterns that go beyond simple API response checking. Load this skill when testing Twilio integrations or building validation into workflows.

Why Deep Validation Matters

A 200 OK from Twilio API doesn't guarantee success. The operation may be queued but:

• TwiML validation could fail later
• Carrier could reject the message
• Webhook could return errors
• Call could fail to connect
• Voice quality could be degraded

Tests that only check for 200 OK give false confidence.

The Deep Validation Pattern

For each operation type, check multiple signals after API operations:

SMS/MMS Validation

interface MessageValidation {
  // Primary: Check message status progression
  resourceStatus: {
    passed: boolean;
    status: 'queued' | 'sending' | 'sent' | 'delivered' | 'undelivered' | 'failed';
  };

  // Secondary: Check for debugger alerts
  debuggerAlerts: {
    passed: boolean;
    alerts: Alert[];  // Error codes 30003, 30004, etc.
  };

  // Optional: Check callback data (if callbacks configured)
  callbackReceived: {
    passed: boolean;
    data: object;
  };
}

Status progression: queued → sending → sent → delivered

Common failure codes:

Code	Meaning
30003	Unreachable destination
30004	Message blocked
30005	Unknown destination
30006	Landline or unreachable
30007	Carrier violation

Voice Call Validation

interface CallValidation {
  // Primary: Check call status
  resourceStatus: {
    passed: boolean;
    status: 'queued' | 'ringing' | 'in-progress' | 'completed' | 'busy' | 'no-answer' | 'failed';
  };

  // Secondary: Check call events for HTTP errors
  callEvents: {
    passed: boolean;
    events: Event[];  // HTTP requests/responses during call
  };

  // Secondary: Check debugger for TwiML errors
  debuggerAlerts: {
    passed: boolean;
    alerts: Alert[];
  };

  // Quality: Voice Insights call summary
  voiceInsights: {
    passed: boolean;
    summary: {
      callQuality: string;
      disposition: string;
      jitter: number;
      packetLoss: number;
    };
  };
}
// The enhanced Voice Insights check now interprets specific quality tags
// (high_jitter, high_packet_loss, silence, etc.), SIP response codes
// (range-based + 20 specific codes), and edge-specific quality metrics
// against thresholds. See [Voice Insights skill](/skills/voice-insights/SKILL.md)
// for full diagnostic workflows.