CtrlK
BlogDocsLog inGet started
Tessl Logo

security-audit

Audit the game for security vulnerabilities: save tampering, cheat vectors, network exploits, data exposure, and input validation gaps. Produces a prioritised security report with remediation guidance. Run before any public release or multiplayer launch.

73

Quality

92%

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

100%

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

The content is exemplary: concise, highly actionable with specific grep patterns and a complete report template, and structured as a clear phased workflow with explicit validation and re-audit checkpoints. It assumes Claude's competence throughout and wastes no tokens on background explanation.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it lists checks and grep patterns without explaining what save tampering or path traversal are, and every section earns its place.

3 / 3

Actionability

Provides concrete, copy-paste-ready guidance: per-category grep patterns, a full report template, a severity table, an exact output path, and a dependency glob list — the agent knows exactly what to search and what to produce.

3 / 3

Workflow Clarity

A clear 7-phase sequence with explicit validation checkpoints (Phase 4 classification, Phase 6 write-after-approval, Phase 7 re-audit trigger and release-gate feedback), including a remediation feedback loop.

3 / 3

Progressive Disclosure

No bundle files exist and the skill needs none; the body is well-organized into distinct phases, categories, tables, and a template, satisfying the 'well-organized sections' criterion for reference-free skills.

3 / 3

Total

12

/

12

Passed

Description

85%

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 states both its purpose and when to run it, scoped tightly to game security. The main weakness is trigger-term coverage, which leans on scheduling language rather than the natural phrases a user would say when they need a security audit.

Suggestions

Add an explicit 'Use when...' clause with natural user phrases (e.g., 'Use when shipping a game, adding multiplayer, or when the user asks for a security review / cheat check').

Include common trigger variations such as 'security review', 'cheat detection', and 'is my game safe to release' alongside 'security vulnerabilities'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across five named vulnerability categories (save tampering, cheat vectors, network exploits, data exposure, input validation) plus a concrete output artifact, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (audits categories and produces a prioritised remediation report) and when ('Run before any public release or multiplayer launch'), matching the clear both-what-and-when anchor.

3 / 3

Trigger Term Quality

Relevant terms like 'security vulnerabilities', 'public release', and 'multiplayer launch' are present, but common natural variations a user would say ('security review', 'cheat detection', 'is my game safe to ship') are missing.

2 / 3

Distinctiveness Conflict Risk

Game-scoped security auditing with five enumerated categories is a clear niche unlikely to conflict with other skills, matching the distinct-triggers anchor.

3 / 3

Total

11

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository
Donchitos/Claude-Code-Game-Studios
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.