Name: gameanalytics
Rating: 56.8 (1 reviews)
Author: membranedev

gameanalytics

GameAnalytics integration. Manage data, records, and automate workflows. Use when the user wants to interact with GameAnalytics data.

Quality

65%

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 ./skills/gameanalytics/SKILL.md

Quality

Content

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

The body is a well-structured, actionable integration guide with a genuinely clear connection-state workflow and copy-paste commands. Its main weakness is conciseness: a marketing-style intro and a few over-explanatory passages pad the token budget without adding skill-specific value.

Suggestions

Trim the opening GameAnalytics marketing paragraph and the 'so you can focus on the integration logic rather than auth plumbing' commentary — Claude already understands auth plumbing.

Add an explicit validation checkpoint after running an action (e.g. check the `output` field / exit state) before treating the result as final, which would lift workflow clarity to the top anchor.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes explanatory padding Claude already knows (e.g. the GameAnalytics marketing intro, 'This skill uses the Membrane CLI...so you can focus on the integration logic rather than auth plumbing') that could be trimmed; sits between the score 2 and 4 anchors.	3 / 5
Actionability	Commands are concrete and copy-paste ready (`membrane connection ensure`, `action run`, `request` with a flag table), covering the common cases with minor gaps (e.g. no worked example of passing a real input payload's output).	4 / 5
Workflow Clarity	The connection lifecycle is clearly sequenced with a state-machine and polling loop (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and explicit 'skip to Step 2' routing; just missing a final validation checkpoint that the action actually succeeded before relying on its output, so it stays below 5.	4 / 5
Progressive Disclosure	Well-organized sections (Install, Auth, Connecting, Searching actions, Running actions, Proxy, Best practices) with no bundle files needed and content appropriately scoped to an overview; minor gaps in cross-linking keep it just under the clean-overview ceiling.	4 / 5
	Total	15 / 20 Passed

Description

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

The description cleanly answers both what and when with an explicit trigger clause, and the GameAnalytics domain gives it strong distinctiveness. It is held back by generic verbs ('Manage', 'automate workflows') that under-specify the concrete actions available.

Suggestions

Replace generic verbs with concrete GameAnalytics actions, e.g. 'query player metrics, build funnels and cohorts, run segmentation and A/B tests, pull SQL reports'.

Sharpen the trigger clause with the natural phrases users say, e.g. 'Use when the user asks about player retention, engagement, monetization, or GameAnalytics reports.'

Dimension	Reasoning	Score
Specificity	Names the domain and a few actions ('Manage data, records, and automate workflows') but the verbs are generic and no concrete GameAnalytics-specific operations are enumerated; fits the 'names domain and 1-2 concrete actions, not comprehensive' anchor better than score 4 since coverage is thin.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with GameAnalytics data') are present, but the 'when' trigger is broad and could be more specific.	4 / 5
Trigger Term Quality	'interact with GameAnalytics data' and 'Manage data, records, and automate workflows' give good keyword coverage of natural terms users would say, with only a few common variations (e.g. 'analytics', 'metrics', 'reports') missing.	4 / 5
Distinctiveness Conflict Risk	'GameAnalytics integration' carves out a clear niche with minimal conflict risk against other skills; the only overlap risk is with generic data-management skills, keeping it just below the distinct-anchor ceiling.	4 / 5
	Total	15 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/gameanalytics/SKILL.md
Commit: f484c82

Reviewed: 5 days 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.