competition-graphql-rpc-drift

Compare declared GraphQL/RPC contracts against live handler behavior to identify drift.

4|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/xjtu-wang/DigAgent --skill competition-graphql-rpc-drift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: competition-graphql-rpc-drift
Source: https://github.com/xjtu-wang/DigAgent/tree/main/.agents/skills/competition-graphql-rpc-drift
Command: npx skills add https://github.com/xjtu-wang/DigAgent --skill competition-graphql-rpc-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Identify and surface drift between declared GraphQL/RPC contracts and live handlers to reveal hidden or stale operations.

Core Features & Use Cases

  • Contract-to-handler drift analysis: compare declared contracts (schema, manifests, persisted queries) with live handler behavior to reveal drift or hidden operations.
  • Evidence-driven investigation: collect request shapes, variables, and responses to reproduce decisive drift paths.
  • Guided workflow after sandbox activation: ensures proper sandbox assumptions and routing before running drift analyses.

Quick Start

Analyze a deployed GraphQL/RPC surface by collecting contract surface and live request data, then contrast outcomes to identify drift and produce actionable evidence.

Frequently Asked Questions about competition-graphql-rpc-drift

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect drift between a declared GraphQL schema and live handlers?

Contract drift occurs when declared GraphQL schemas or RPC manifests mismatch live server behavior. Compare declared surfaces against actual request shapes to reveal hidden or stale operations.

How do I compare RPC manifests against live handler behavior?

Compare RPC manifests against live handler behavior by recording real request shapes and responses. Contrast live recordings with the declared contract surface to produce evidence-based drift results.

What is the best way to find hidden or stale GraphQL operations?

The best way to find hidden GraphQL operations is to compare client expectations in persisted query maps against actual server behavior. Collecting live request shapes provides evidence-based drift detection.

What contract formats can I use for GraphQL and RPC drift analysis?

You can use GraphQL schemas, persisted query maps, RPC manifests, generated clients, or OpenAPI specs as declared contract surfaces. These formats are contrasted with live requests to identify drift.

Do I need a sandbox environment to run contract-to-handler drift analysis?

Yes, a sandbox environment is required to run contract-to-handler drift analysis. The guided workflow ensures proper sandbox activation, routing assumptions, and data collection before analyzing drift.

Why does my OpenAPI spec show different responses than my live RPC handlers?

Your OpenAPI spec shows different responses than live RPC handlers due to contract drift. Analyze the declared spec against recorded live request shapes and responses to reveal the decisive drift path.