Competition GraphQL RPC Drift is a downstream skill of the CTF Sandbox Orchestrator. It covers challenges where the decisive behavior comes from a gap between what a schema, manifest or generated client declares and what the live handler accepts.
The agent collects the declared contract, captures real request and response pairs, and compares them side by side. It then reduces the result to one accepted operation and one drifted or hidden operation with the smallest difference between them.
What You Get
- A three-stage workflow: map the declared contract, prove live handler behavior, reduce to the decisive drift path
- A checklist of contract, request and effect evidence to keep together
- Guidance to state whether drift lives in the client, persisted query map, schema version or handler
- A pairing of one accepted request with one drifted request
- Hand-off rules for when the task turns into JWT, OAuth or queue behavior
Common Use Cases
- Finding a GraphQL operation that the generated client never calls but the server still runs
- Explaining a version mismatch between an OpenAPI document and the live service
- Tracing a persisted query identifier back to the operation it maps to
- Documenting an RPC method that exists only on the handler side
What Makes It Unique
The skill is centered on the difference between contract and behavior across several API styles at once. It treats a generated client as evidence of intent only, and asks for captured requests before any claim about a hidden operation, which sets it apart from skills that focus on a single API style.
Under The Hood
The skill is instruction text only: the SKILL.md body, one reference checklist and a small agent config file that disables implicit invocation. It ships no scripts. The instructions tell the agent to capture and compare requests against services in the sandbox the user supplies, to reply in Simplified Chinese unless asked for English, and to run only after the orchestrator skill is active.