Skip to main content
skill CX Codex

competition-graphql-rpc-drift — Claude Code skill: contract analysis

competition-graphql-rpc-drift — a Claude Code skill compares GraphQL and RPC contracts with live handler behavior. It joins a CTF workflow after the main orchestrator sets up the sandbox.

MIT 110 installs ★ 45,047 updated 2026-09-22

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add zhaoxuya520/reverse-skill --skill competition-graphql-rpc-drift -a claude-code
Open on GitHub

What competition-graphql-rpc-drift does

The skill checks GraphQL schemas, RPC manifests, OpenAPI documents, and generated clients against real requests and live handlers. It looks for hidden operations, stale fields, and mismatches between declared contracts and handler behavior.

It starts by gathering contract artifacts and request details, including variables, headers, cookies, and response status. Then it reduces a mismatch to the shortest sequence that demonstrates the decisive branch. Further checklists and evidence guidance live in references/graphql-rpc-drift.md.

This skill runs only after $ctf-sandbox-orchestrator has set the sandbox assumptions and routed the task. If the work shifts to JWT, OAuth, or queue behavior, it hands off to a narrower skill.

What it helps with

  • compare a GraphQL schema with real requests and handlers
  • find hidden or stale operations
  • trace generated-client behavior
  • show a mismatch between an RPC contract and its handler

Example prompts for the agent

  • Compare the GraphQL schema with real requests and find hidden operations.
  • Trace where the RPC manifest differs from handler behavior.
  • Reduce the contract-to-handler mismatch to the shortest sequence that proves it.

How to install competition-graphql-rpc-drift

1Skills CLI (Vercel)

npx skills add zhaoxuya520/reverse-skill --skill competition-graphql-rpc-drift -a claude-code

2Manually: put the files in place

~/.claude/skills/competition-graphql-rpc-drift/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/competition-graphql-rpc-drift/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about competition-graphql-rpc-drift

How do I install competition-graphql-rpc-drift in Claude Code?

Run npx skills add zhaoxuya520/reverse-skill --skill competition-graphql-rpc-drift -a claude-code. The skill file is at ~/.claude/skills/competition-graphql-rpc-drift/SKILL.md.

What does competition-graphql-rpc-drift do?

It compares GraphQL and RPC contracts with actual requests and live handlers. The workflow can expose hidden operations and reduce a mismatch to the path that demonstrates its effect.

When does competition-graphql-rpc-drift run?

Only after $ctf-sandbox-orchestrator establishes the sandbox assumptions and routes the task to it.

Source text

SKILL.md · MIT
---
name: competition-graphql-rpc-drift
description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for GraphQL schemas, persisted queries, RPC manifests, generated clients, OpenAPI drift, hidden operations, and contract-to-handler mismatches. Use when the user asks to inspect GraphQL or RPC requests, compare client contracts to live handlers, recover hidden operations, trace generated clients, or explain how schema or contract drift produces the decisive behavior. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
---

# Competition Graphql Rpc Drift

Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first.

Use this skill when the hard part is matching declared contracts with live handlers to find hidden, stale, or privileged operations.

Reply in Simplified Chinese unless the user explicitly requests English.

## Quick Start

1. Collect the declared contract surface first: schema, manifest, generated client, persisted query map, or OpenAPI spec.
2. Record actual request shapes, operation names, variables, method, path, and auth context before mutating anything.
3. Compare declared contract, generated client behavior, and live handler behavior side by side.
4. Preserve one accepted operation and one drifted or hidden operation with the smallest delta.
5. Reproduce the smallest contract-to-handler mismatch that proves the decisive branch.

## Workflow

### 1. Map The Declared Contract Surface

- Record GraphQL schema, introspection output, persisted query ids, RPC manifests, generated clients, or OpenAPI documents that define the intended surface.
- Note versioned endpoints, client-only guards, hidden enums, optional fields, and operation naming conventions.
- Keep document source and generation path tied to the observed requests.

### 2. Prove Live Handler Behavior

- Capture the real request and response pairs, including operation name, variables, headers, cookies, and status.
- Compare client-side validation, schema expectations, and live handler normalization or fallback behavior.
- Record hidden operations, stale fields, undocumented methods, or handler-only branches that still execute.

### 3. Reduce To The Decisive Drift Path

- Compress the result to the smallest sequence: declared contract -> actual request -> handler branch -> resulting capability.
- State clearly whether the decisive drift lives in generated client assumptions, persisted query mapping, schema version skew, RPC manifest mismatch, or handler-side hidden logic.
- If the task shifts into generic JWT, OAuth, or queue behavior after acceptance, hand off to the tighter specialized skill.

## Read This Reference

- Load `references/graphql-rpc-drift.md` for the contract checklist, live-handler checklist, and evidence packaging.

## What To Preserve

- Schemas, manifests, generated clients, persisted query ids, operation names, and version markers
- One accepted and one drifted request pair that proves the mismatch
- One minimal contract-to-handler sequence that reaches the decisive effect

© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill

Similar skills

All skills for Backend and APIs →

From the same set36

The whole set →
competition-bundle-sourcemap-recovery The competition-bundle-sourcemap-recovery Claude Code skill reconstructs JavaScript structure from served assets and source maps. It runs after ctf-sandbox-orchestrator routes a task involving chunk loading or hidden routes. CX Codex +1 110installs competition-websocket-runtime competition-websocket-runtime is a Claude Code skill that inspects WebSocket and SSE handshakes, subscriptions, and frames after the orchestrator runs. CX Codex +1 110installs competition-stego-media The competition-stego-media Claude Code skill searches media files for hidden payloads in CTF tasks. It runs after ctf-sandbox-orchestrator routes an image, audio, video, or document for steganography analysis. CX Codex +1 110installs competition-ios-runtime competition-ios-runtime — a skill for Claude Code that automates iOS runtime analysis and hooking. It runs as a downstream module after $ctf-sandbox-orchestrator is active. CX Codex +1 110installs competition-identity-windows competition-identity-windows — a skill for Claude Code and Codex that examines Active Directory attacks, Windows host artifacts, and CTF pivot chains. It runs after routing by $ctf-sandbox-orchestrator. CX Codex +1 109installs competition-agent-cloud The competition-agent-cloud Claude Code skill investigates agent and cloud paths in CTF sandboxes. It is routed in after the orchestrator sets the sandbox assumptions, for tracing input-to-tool actions or deployment behavior. CX Codex +1 109installs competition-browser-persistence competition-browser-persistence — a skill for Claude Code that investigates browser persistence surfaces in CTF sandboxes. It activates when stored client state alters request flows, rendering, or access rules. CX Codex +1 109installs competition-ad-certificate-abuse The competition-ad-certificate-abuse Claude Code skill traces certificate-based abuse in AD CS CTF sandboxes. It is triggered by questions about templates, enrollment rights, PKINIT, and privilege paths through certificates. CX Codex +1 109installs

Project sponsors

Companies that keep this analytics open