CtrlK
BlogDocsLog inGet started
Tessl Logo

competition-graphql-rpc-drift

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.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, lean instruction skill with clear sequencing and proper progressive disclosure via a single real reference. Main improvement area is reducing Quick Start/Workflow overlap and adding an explicit verification feedback loop.

Suggestions

Dedupe the Quick Start and Workflow sections so each carries distinct content — e.g., keep Quick Start as the terse sequence and let Workflow hold the per-phase detail.

Add an explicit validate/reproduce checkpoint with a fix-and-retry loop, e.g., 'If the reproduced mismatch does not prove the decisive branch, re-capture the request pair and retry.'

Consider one concrete command or snippet (e.g., a sample introspection or request-capture incantation) to lift actionability from actionable methodology toward executable guidance.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence without explaining known concepts, but the Quick Start and Workflow sections overlap in content, leaving minor redundancy that could be tightened.

4 / 5

Actionability

Provides concrete, specific collection targets ('schema, manifest, generated client, persisted query map, or OpenAPI spec') and a clear comparison procedure; guidance is actionable though methodology-only with no executable code.

4 / 5

Workflow Clarity

Clear five-step Quick Start and three-phase Workflow with a reproduction step serving as verification, but no explicit validate-fix-retry feedback loop is articulated.

4 / 5

Progressive Disclosure

Well-organized short body with clearly signaled one-level-deep reference to references/graphql-rpc-drift.md (a real file), with content appropriately split between overview and checklist detail.

5 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly defines a niche domain and provides explicit trigger guidance with multiple concrete actions. Minor room for broader synonym coverage in trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'inspect GraphQL or RPC requests', 'compare client contracts to live handlers', 'recover hidden operations', 'trace generated clients', 'explain how schema or contract drift produces the decisive behavior' — with comprehensive domain coverage.

5 / 5

Completeness

Explicitly answers both 'what' (CTF-sandbox workflow for GraphQL schemas, persisted queries, RPC manifests, etc.) and 'when' with a concrete 'Use when...' clause listing multiple trigger conditions.

5 / 5

Trigger Term Quality

Good natural keyword coverage with phrases like 'inspect GraphQL or RPC requests' and 'recover hidden operations', but lacks synonym-level breadth and file-extension variants, stopping short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (CTF-sandbox GraphQL/RPC contract drift) with distinct triggers and explicit downstream scoping to a single orchestrator, minimizing conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
zhaoxuya520/reverse-skill
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.