multiplayer

Multiplayer game development principles. Architecture, networking, synchronization.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/game-development/multiplayer/SKILL.md

Quality

Content

65%

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

The body is a compact, well-organized reference of multiplayer principles that respects token budget, but it stays at the conceptual level: no executable code, no sequenced workflow with validation, and no progressive disclosure into bundled files. It reads more as a knowledge cheatsheet than as actionable skill guidance.

Suggestions

Add at least one concrete, executable pattern (e.g. a server-authoritative validation snippet or a tick-based state-sync code skeleton) to lift actionability.

Provide a sequenced workflow with validation checkpoints for a representative task such as 'add a networked entity' or 'harden a client action against cheating'.

Move detailed sub-topics (anti-cheat catalog, matchmaking factors, update-rate tuning) into reference files linked one level deep from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean throughout — terse tables, a short decision tree, and a compact anti-patterns matrix with no padding or restated definitions; every section earns its tokens.	3 / 3
Actionability	It gives some concrete specifics (e.g. 'Position 20-60 Hz', 'Design for 100-200ms', dos/don'ts), but the code blocks are conceptual illustrations rather than executable code, and most sections describe principles instead of instructing concrete implementation steps.	2 / 3
Workflow Clarity	Sections are well-organized by topic and the decision tree offers a light flow, but there is no sequenced multi-step process and no validation checkpoints — it is a topical reference rather than a workflow.	2 / 3
Progressive Disclosure	The single file is cleanly sectioned and has no nested references, but at ~125 lines it is a monolithic inline reference with no progressive split of detailed sub-topics (e.g. anti-cheat, matchmaking) into separate files.	2 / 3
	Total	9 / 12 Passed

Description

57%

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

The description names a clear niche and a few relevant sub-areas in concise third-person voice, but it lacks any 'Use when...' trigger clause and uses topics rather than concrete actions. It is clearly distinguishable but only moderately complete.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building or debugging multiplayer/networked games, netcode, or real-time synchronization.'

Replace topic nouns with concrete actions the skill performs (e.g. 'Choose networking architectures, design synchronization and lag-compensation, harden against cheating').

Include natural user variations such as 'netcode', 'lag', 'client-server', and 'server-authoritative'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Multiplayer game development principles') and three concrete sub-areas ('Architecture, networking, synchronization'), but these are topics/nouns rather than concrete actions, and coverage is not comprehensive.	2 / 3
Completeness	It states what the skill covers, but provides no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Terms like 'multiplayer', 'networking', and 'synchronization' are ones users would naturally say, but common variations (e.g. 'netcode', 'lag', 'server-authoritative', 'real-time game') are missing.	2 / 3
Distinctiveness Conflict Risk	'Multiplayer game development' is a clear, narrow niche with distinct triggers that is unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: vudovn/ag-kit
Path: .agents/skills/game-development/multiplayer/SKILL.md
Commit: 04514f0

Reviewed: about 12 hours ago

Table of Contents

Discovery Implementation Validation

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.