CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

security-audit

Security audit — save tampering, cheat vectors, network exploits, data exposure, input validation. Before public or multiplayer release.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/security-audit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

An exceptionally actionable, well-sequenced audit workflow: copy-paste templates, exact patterns, explicit decision trees, and built-in guards against the audit's most dangerous failure mode (the false-clean report). Its one real weakness is repetition — the same safety rules are restated so often across phases that the file is noticeably longer than its content requires.

Suggestions

State each safety rule once in a canonical location and cross-reference it: the 'zero-hit scan renders the report clean' warning, the NOT ASSESSED rule, and the multiplayer HIGH→CRITICAL rule are each repeated 2–4 times across Phases 1, 3, 5, and 7.

Move the Unity/Unreal engine pattern lists (sourced from docs/engine-reference/) into a references/ file or rely directly on the pinned docs, keeping the Phase 3 table to just the per-engine sourceability verdicts.

Trim the Phase 1 blockquote on absent-not-false to its operative rule (ask the user; if unaskable, run Category 2 and mark NOT ASSESSED) — the surrounding justification repeats the same point several ways.

DimensionReasoningScore

Conciseness

Every section is task-specific instruction with no padding about concepts Claude already knows, but the same critical warnings are repeated across phases: 'zero hits … renders the report clean — the most dangerous possible failure for a security audit' appears nearly verbatim in the Phase 3 intro and the Category 1 note, the NOT ASSESSED rule is restated in Phases 1, 3 (twice), 5, and 7, and the multiplayer HIGH→CRITICAL rule appears in four places. Consolidating these to one canonical statement each would cut substantial length without losing clarity — more than the 'minor instances' of the anchor-4 example.

3 / 5

Actionability

Fully executable throughout: a copy-paste agent-brief template with clearly marked {…} slots, a complete markdown report template down to per-finding fields, exact grep pattern lists per category, a concrete output path convention (production/security/security-audit-[date]-[scope].md), and verbatim message templates for every Phase 7 recommendation branch. The common cases are covered end-to-end.

5 / 5

Workflow Clarity

Seven phases are clearly sequenced (scope → spawn → categories → classify → report → write → gate) with explicit validation checkpoints: a first-match-wins decision tree for the release recommendation, a write-only-after-approval gate in Phase 6, NOT ASSESSED rules that prevent a zero-hit scan reading as a pass, and a re-audit feedback loop (re-run /security-audit quick before /gate-check release) after remediation.

5 / 5

Progressive Disclosure

A single-file skill with no bundle files, organized into well-labeled phase sections and tables, with clearly signaled one-level-deep references to project docs (docs/engine-reference/<engine>/…, .claude/docs/automation-modes.md). The Unity/Unreal pattern sets inlined in the Phase 3 table are sourced from pinned repo references and could arguably live in a separate file, which keeps this just short of fully appropriate placement.

4 / 5

Total

17

/

20

Passed

Description

75%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 solid, terse description that names a clear niche (game security auditing) with an explicit timing trigger. It consistently lands just below top marks: concrete categories but no stated output artifact, good but not exhaustive trigger terms, and a single when-clause where the body itself lists four distinct run triggers.

Suggestions

State the output in the description (e.g., '…and produces a prioritised remediation report') so the 'what' includes the deliverable, not just the scan categories.

Broaden the when-clause to match the body's own triggers, e.g. 'Use before public or multiplayer release, before enabling online features, or when a security bug or cheat/exploit report comes in.'

Add one or two natural synonyms users would say — 'vulnerabilities' or 'is my game secure' — to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete audit areas ("save tampering, cheat vectors, network exploits, data exposure, input validation") rather than generic language, but never states what the audit produces (a prioritised report/remediation plan) and omits the dependency/supply-chain category — minor gaps in coverage, not a comprehensive action list.

4 / 5

Completeness

Both parts are present: what ("Security audit — save tampering, … input validation") and an explicit when ("Before public or multiplayer release."). The when is a single timing trigger and the what is a list of category nouns rather than actions, so it falls short of the anchor-5 example that answers both with multiple concrete trigger phrases.

4 / 5

Trigger Term Quality

Good natural keywords users would say — "security audit", "save tampering", "cheat vectors", "multiplayer release" — but common phrasings like "vulnerabilities", "exploits" as a standalone concern, or "when a security bug is reported" are absent, so coverage stops short of the anchor-5 synonym/extension completeness.

4 / 5

Distinctiveness Conflict Risk

Game-specific vectors ("save tampering", "cheat vectors", "multiplayer release") carve out a distinct niche, but the generic terms "security", "input validation", and "data exposure" leave minor overlap risk with a general code-security skill — mostly distinct rather than a fully clear niche.

4 / 5

Total

16

/

20

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.

Validation — 13 / 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

Path

.claude/skills/security-audit/SKILL.md

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.