eval-integration

Specialized integration evaluator for the Evaluate-Loop. Use this for evaluating tracks that integrate external services — Supabase auth/DB, Stripe payments, Gemini API, third-party APIs. Checks API contracts, auth flows, data persistence, error recovery, environment config, and end-to-end flow integrity. Dispatched by loop-execution-evaluator when track type is 'integration', 'auth', 'payments', or 'api'. Triggered by: 'evaluate integration', 'test auth flow', 'check API', 'verify payments'.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "eval-integration" with this command: npx skills add ibrahim-3d/conductor-orchestrator-superpowers/ibrahim-3d-conductor-orchestrator-superpowers-eval-integration

Integration Evaluator Agent

Specialized evaluator for tracks that integrate external services — Supabase, Stripe, Gemini, or any third-party API.

When This Evaluator Is Used

Dispatched by loop-execution-evaluator when the track involves:

  • Authentication or database integration
  • Payment processing integration
  • AI/ML API integration
  • Any external API connection

Inputs Required

  1. Track's spec.md and plan.md
  2. Environment config (.env.example, env variable documentation)
  3. API client code (src/lib/)
  4. Database schema (if Supabase)
  5. Webhook handlers (if Stripe)

Evaluation Passes (6 checks)

Pass 1: API Contract Verification

CheckWhat to Look For
Request shapesAPI calls send correct payload structure
Response handlingResponses parsed with correct types
Error responses4xx/5xx errors handled with user-friendly messaging
Rate limitsRate limit handling present (retry, backoff, queue)
TimeoutReasonable timeout set on API calls
Auth headersBearer token / API key sent correctly
### API Contracts: PASS ✅ / FAIL ❌
- Endpoints verified: [count]
- Missing error handling: [list]
- Type mismatches: [list]

Pass 2: Authentication Flow

CheckWhat to Look For
Sign upCreates user, stores token, redirects to dashboard
Sign inValidates credentials, stores token, redirects
Sign outClears token, redirects to home
Token refreshHandles expired tokens (refresh or re-auth)
Protected routesUnauthenticated users redirected to login
OAuthThird-party login flow (if applicable)
### Auth Flow: PASS ✅ / FAIL ❌
- Flows tested: [sign up / sign in / sign out / token refresh]
- Broken flows: [list]
- Token handling: [correct / issues]

Pass 3: Data Persistence & Schema Hygiene

CRUD Operations:

CheckWhat to Look For
CreateData saved correctly to database/storage
read_fileData retrieved and rendered correctly
UpdateChanges persisted on save
DeleteRecords removed, UI reflects deletion
RelationshipsForeign keys / joins working correctly
StorageFile uploads stored and retrievable (if applicable)

Database Schema Quality (MANDATORY for all new tables/migrations):

CheckRequirementWhy
Timestampscreated_at, updated_at on ALL mutable tablesDebugging, audit trail, cache invalidation
Primary keysUUID with default OR auto-incrementData uniqueness
Foreign keysExplicit cascade rules (on delete cascade)Prevent orphaned data
IndexesIndex ALL foreign keysQuery performance
Null constraintsNew columns nullable OR have defaultsBackward compatibility
Unique constraintsComposite uniques where neededData integrity
Version historyJSONB column for flexible historySchema evolution

Schema Anti-Patterns to Flag:

-- ❌ BAD: No timestamps
create table brands (
  id uuid primary key,
  name text
);

-- ✅ GOOD: Complete schema
create table brands (
  id uuid primary key default gen_random_uuid(),
  name text not null,
  created_at timestamptz default now() not null,
  updated_at timestamptz default now() not null
);

-- ❌ BAD: Foreign key without cascade
brand_id uuid references brands(id)

-- ✅ GOOD: Explicit cascade
brand_id uuid references brands(id) on delete cascade not null

-- ❌ BAD: New required column (breaks existing data)
alter table assets add column image_url text not null;

-- ✅ GOOD: Nullable or has default
alter table assets add column locked boolean default false;
### Data Persistence & Schema: PASS ✅ / FAIL ❌
- CRUD operations: [which work / which fail]
- Data integrity: [any corruption or loss]
- Storage: [files accessible / issues]
- **Tables missing timestamps: [count] — [list]**
- **Foreign keys without indexes: [count] — [list]**
- **Migrations without defaults: [count] — [list]**
- **Orphaned data risk: [YES/NO — describe]**

Pass 4: Error Recovery

CheckWhat to Look For
Network failureOffline/timeout → user sees error, can retry
Invalid dataMalformed responses → graceful fallback
Auth failureExpired token → redirect to login, not crash
Payment failureDeclined card → clear message, can retry
API downService unavailable → error state, not blank screen
Partial failureOne API fails, others still work
### Error Recovery: PASS ✅ / FAIL ❌
- Scenarios tested: [list]
- Unhandled failures: [list]
- User messaging: [clear / missing]

Pass 5: Environment Configuration

CheckWhat to Look For
.env.exampleAll required variables documented
No secrets in codeNo API keys, tokens, or passwords in source files
Environment switchingDev/staging/prod configs separate
Missing varsApp handles missing env vars gracefully (error, not crash)
### Environment: PASS ✅ / FAIL ❌
- Variables documented: [YES/NO]
- Secrets in code: [NONE / list files with exposed secrets]
- Missing var handling: [graceful / crashes]

Pass 6: End-to-End Flow

Walk through the complete user journey that involves this integration:

FlowSteps to Verify
Auth flowLanding → Sign Up → Verify → Dashboard
Payment flowSelect plan → Checkout → Payment → Confirmation
Generation flowForm → Generate → View → Download
### E2E Flow: PASS ✅ / FAIL ❌
- Flow tested: [describe]
- Steps completed: [X]/[Y]
- Broken at step: [which step, if any]

Verdict Template

## Integration Evaluation Report

**Track**: [track-id]
**Evaluator**: eval-integration
**Date**: [YYYY-MM-DD]
**Service**: [Supabase/Stripe/Gemini/etc.]

### Results
| Pass | Status | Issues |
|------|--------|--------|
| 1. API Contracts | PASS/FAIL | [details] |
| 2. Auth Flow | PASS/FAIL | [details] |
| 3. Data Persistence | PASS/FAIL | [details] |
| 4. Error Recovery | PASS/FAIL | [details] |
| 5. Environment | PASS/FAIL | [details] |
| 6. E2E Flow | PASS/FAIL | [details] |

### Verdict: PASS ✅ / FAIL ❌
[If FAIL, list specific fix actions for loop-fixer]

Handoff

  • PASS → Return to loop-execution-evaluator → Conductor marks complete
  • FAIL → Return to loop-execution-evaluator → Conductor dispatches loop-fixer

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

writing-plans

No summary provided by upstream source.

Repository SourceNeeds Review
General

loop-planner

No summary provided by upstream source.

Repository SourceNeeds Review
General

plan-critiquer

No summary provided by upstream source.

Repository SourceNeeds Review
General

using-git-worktrees

No summary provided by upstream source.

Repository SourceNeeds Review