CtrlK
BlogDocsLog inGet started
Tessl Logo

graphics-api-hooking

Guide for graphics API interception, overlay rendering, and render-pipeline analysis across DirectX, OpenGL, and Vulkan. Use this skill when working with Present or SwapBuffers hooks, DXGI swap chains, shader or draw-call interception, screenshot-sensitive overlays, or graphics debugging in game security research.

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/graphics-api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

A broad, concrete reference for graphics API hooking with useful code and a clear external data-source workflow, but it is over-long, contains partial/non-executable snippets, and references a wiki/ bundle that does not exist. Tightening inline content and either shipping or removing the wiki references would raise its quality.

Suggestions

Move the large inline reference catalogs (per-API hooks, overlay/shader techniques, OBS pipeline) into separate reference files and keep SKILL.md as a concise overview with one-level-deep links.

Either provide the referenced wiki/ files (wiki/overviews/graphics-api.md, wiki/index.md, wiki/AGENTS.md) or remove the dead references so navigation pointers resolve.

Make code examples complete and executable (real return values, required includes/declarations) or explicitly mark illustrative snippets as pseudocode.

DimensionReasoningScore

Conciseness

The body is a ~480-line monolithic reference; while the specialized OBS/AI-pipeline detail earns its place, sections like World-to-Screen and overlay basics re-explain concepts Claude already knows and could be tightened.

2 / 3

Actionability

Many concrete code snippets are present, but several are partial or non-executable (e.g. 'return invalid', '// Render overlay here', missing includes/declarations); the archive/description fetch URLs are the most copy-paste-ready guidance.

2 / 3

Workflow Clarity

This is a reference catalog rather than a sequenced workflow; the only real sequence is the fetch priority order (description → archive → README), which lacks validation checkpoints.

2 / 3

Progressive Disclosure

Content is largely inline and monolithic, and the referenced wiki paths (wiki/overviews/graphics-api.md, wiki/index.md, wiki/AGENTS.md) point to no existing bundle directory, so the disclosure pointers are partly dead.

2 / 3

Total

8

/

12

Passed

Description

100%

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, well-scoped description that states concrete capabilities and provides an explicit, natural-language trigger clause with good keyword coverage. It uses third-person voice and is unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'graphics API interception, overlay rendering, and render-pipeline analysis across DirectX, OpenGL, and Vulkan' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Guide for graphics API interception, overlay rendering, and render-pipeline analysis') and when ('Use this skill when working with ...'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Covers natural terms users would say: 'Present or SwapBuffers hooks, DXGI swap chains, shader or draw-call interception, screenshot-sensitive overlays, ... graphics debugging'.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (graphics API hooking for game security research) with distinct, specific triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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