CtrlK
BlogDocsLog inGet started
Tessl Logo

game-server-security

Review multiplayer authority and backend trust across RPCs, sessions, object authorization, inventory, economy, and purchases. Use when choosing or assessing KCP, GameNetworkingSockets, Steam networking interfaces, server frameworks, or token-validation resources; distinguish delivery reliability, transport identity, game permission, and durable state. Cover retries, provider contracts, clock domains, replication order, prediction, and replay, producing operation maps and evidence-based invariants.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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, information-dense instruction-only review skill that assumes expertise and provides concrete enumerated guidance plus named provider contracts. It scores consistently strong across conciseness, actionability, workflow clarity, and progressive disclosure, with the main limitation being the lengthy inlined Data Source section and fewer explicit feedback-loop checkpoints.

DimensionReasoningScore

Conciseness

Dense, technical prose that assumes Claude's competence throughout and avoids explaining basics; the inlined 'Data Source' section is somewhat long but operationally specific rather than padded, leaving only minor trims before the top anchor.

4 / 5

Actionability

Gives concrete, enumerable review directives — 'Record the initiating principal, authenticated identity, object owner, requested action, authoritative validator...' — and names specific provider contracts (PlayFab IdempotencyId vs ETags, Google Play pending-purchase state); mostly executable guidance with minor gaps and no copy-paste commands, which is appropriate for an instruction-only review skill.

4 / 5

Workflow Clarity

A clear review methodology sequences Map One Consequential Operation → threat model → auth/authz → economy/inventory/purchase → network failure → Review Output, with an explicit field list and an output ledger/checklist; this is analysis rather than destructive/batch execution so the validation cap does not apply, though explicit verify→fix→retry feedback loops are less emphasized.

4 / 5

Progressive Disclosure

Body signals one-level-deep references to real files (references/repository-resources.md, references/time-ordering-and-replay.md, both present) and organizes content under clear section headers; the long inlined 'Data Source' section is deliberately retained rather than split out, a minor organization gap below the top anchor.

4 / 5

Total

16

/

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, third-person description that names concrete review domains, named networking libraries, and explicit 'Use when' triggers. It is comprehensive on specificity and completeness with low conflict risk; trigger-term coverage is strong though a few natural synonyms would push it to the top anchor.

DimensionReasoningScore

Specificity

Lists many concrete review actions and domains — 'RPCs, sessions, object authorization, inventory, economy, and purchases' plus 'retries, provider contracts, clock domains, replication order, prediction, and replay, producing operation maps and evidence-based invariants' — comprehensive concrete coverage rather than abstract language.

5 / 5

Completeness

Explicitly answers both what ('Review multiplayer authority and backend trust across...') and when ('Use when choosing or assessing KCP, GameNetworkingSockets, Steam networking interfaces...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes named technologies a user would actually say ('KCP, GameNetworkingSockets, Steam networking interfaces, server frameworks, token-validation resources') plus natural domain nouns like 'multiplayer', 'purchases', 'economy'; strong coverage though a few common phrasings/synonyms are absent, keeping it just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (game-server/backend authority and trust review) with distinctive named-lib triggers and a narrow problem space, giving minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 8 suspicious

Warning

Total

15

/

16

Passed

Repository
gmh5225/awesome-game-security
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.