schema-drift-detector

Monitor API endpoints for schema drift and generate Payload field definitions.

Updated Aug 23, 2026

Search Tags:#api #integration #code generation #drift detection #synchronization #schema #payload cms

One-click install

npx skills add https://github.com/ComparePower/payload-cms-cloudflare-baseline --skill schema-drift-detector

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: schema-drift-detector
Source: https://github.com/ComparePower/payload-cms-cloudflare-baseline/tree/main/.claude/skills/schema-drift-detector
Command: npx skills add https://github.com/ComparePower/payload-cms-cloudflare-baseline --skill schema-drift-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node-fetch, pnpm, and includes scripts (resource) components.

What problem does it solve?

External API schemas can change without warning, leading to broken integrations and outdated data models in your CMS. This skill automatically monitors API endpoints for schema drift, identifies changes, and generates the necessary Payload field definitions to keep your collections synchronized.

Core Features & Use Cases

Automated Schema Monitoring: Fetches current API responses and compares them against a defined expected schema to detect additions, removals, or changes in fields and types.
Payload Field Generation: Automatically generates TypeScript Payload field definitions for new or changed fields, streamlining the process of updating your CMS schema.
Use Case: Your Providers collection in Payload CMS relies on data from the ComparePower API. Use this skill to regularly check the API for schema changes, and if a new field like email is added, it will generate the corresponding Payload email field definition and a migration script for you.

Quick Start

Check for schema drift on the ComparePower API endpoint 'https://api.comparepower.com/v1/providers/4change-energy' against the 'providers' collection.