CtrlK
BlogDocsLog inGet started
Tessl Logo

yandex-js-sdk

Integrates the Yandex Games JavaScript SDK (YaGames) into JavaScript games. Initializes the SDK and lifecycle hooks, manages player authentication and authorization, handles per-player cloud storage, controls ad placements (interstitial, rewarded video, sticky banner), implements in-app purchases and leaderboards, retrieves remote config flags, and supports social features such as review prompts and home-screen shortcuts. Use when the user mentions Yandex Games, YaGames, yandex sdk, deploying a game to the Yandex.Games platform, or integrating features like ads, leaderboards, in-app purchases, or player authentication into a Yandex-hosted JavaScript game.

75

Quality

93%

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

86%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 highly actionable, token-efficient SDK reference with executable code throughout and a well-sequenced integration workflow. Its main weakness is structure: it is a monolithic single-file reference with no progressive disclosure to separate reference files.

Suggestions

Move the larger capability areas (Advertisement, Payments/IAP, Leaderboards) into separate files under references/ and link to them from SKILL.md so the main file stays a concise overview with one-level-deep references.

Add an explicit validation checkpoint for storage writes — e.g., re-read with getData() after setData() to confirm the merge persisted — since each call overwrites the full document.

Add a verification step in the consume-purchase flow (re-call getPurchases() to confirm the token is gone after consumePurchase) to close the validation gap on that destructive operation.

DimensionReasoningScore

Conciseness

The body is lean reference-style content: tight executable snippets with prose reserved for SDK-specific gotchas ('Treat wasShown === false as a failure', 'Grant the reward inside onRewarded', 'Every call writes the full document'), avoiding any explanation of concepts Claude already knows.

5 / 5

Actionability

Nearly every section provides fully executable, copy-paste-ready JavaScript functions (getPlayer, showInterstitial, purchase, setLeaderboardScore, etc.) that cover the common integration cases with real SDK method calls.

5 / 5

Workflow Clarity

The Quick Start bootstrap is sequenced as numbered steps 1–7 with 'Verify each step before proceeding to the next', a try/catch fallback for player init, and a purchaseToken check; minor gaps remain, notably no formal validate-retry loop for the full-document storage overwrite.

4 / 5

Progressive Disclosure

The skill is well-organized with clear section headers and an overview map, but at ~390 lines everything is inlined into SKILL.md with no references/ bundle files; distinct capability areas (ads, IAP, leaderboards) that could be split into one-level-deep references are kept inline.

3 / 5

Total

17

/

20

Passed

Description

100%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 comprehensively enumerates concrete SDK capabilities and pairs them with explicit, natural-language trigger phrases. It clearly answers both what the skill does and when to use it with minimal conflict risk.

DimensionReasoningScore

Specificity

The description lists many concrete actions — 'Initializes the SDK and lifecycle hooks, manages player authentication... handles per-player cloud storage, controls ad placements (interstitial, rewarded video, sticky banner), implements in-app purchases and leaderboards, retrieves remote config flags' — giving comprehensive coverage rather than vague language.

5 / 5

Completeness

It explicitly answers both 'what' (the enumerated SDK capabilities) and 'when' via the 'Use when the user mentions Yandex Games, YaGames... or integrating features like ads, leaderboards, in-app purchases, or player authentication' trigger clause.

5 / 5

Trigger Term Quality

It includes natural user phrasings plus synonyms and platform variants — 'Yandex Games, YaGames, yandex sdk... Yandex.Games platform' — alongside feature keywords users would actually say.

5 / 5

Distinctiveness Conflict Risk

The Yandex Games / YaGames niche is highly specific with distinct platform triggers, so overlap with other skills is minimal.

5 / 5

Total

20

/

20

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
popey/gamedev.sh-skills
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.