Name: app-analytics
Rating: 64.8 (1 reviews)
Author: Eronred

app-analytics

When the user wants to set up, interpret, or improve their app analytics and tracking. Also use when the user mentions "analytics", "tracking", "metrics", "KPIs", "App Store Connect analytics", "install tracking", "funnel", "attribution", or "how is my app performing". For A/B testing, see ab-test-store-listing. For retention metrics, see retention-optimization.

Quality

76%

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/app-analytics/SKILL.md

Quality

Content

57%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 content-rich reference skill with concrete events, benchmarks, and output templates, but it leans on inlined reference material and basic definitions Claude already knows. Moving dense reference tables into bundle files and tightening the dashboard mockups would materially improve it.

Suggestions

Move the metrics/framework tables and event tracking plan into separate reference files under references/, keeping SKILL.md as a concise overview that links to them one level deep.

Trim or remove the ASCII placeholder dashboards (filled with [N]/[X]%) and basic metric definitions like DAU/MAU that Claude already knows; keep only the benchmark numbers that add novel value.

Add an explicit workflow section that sequences audit → tracking plan → dashboard setup → interpretation with checkpoints, and either supply the referenced app-marketing-context.md or drop the dangling reference.

Dimension	Reasoning	Score
Conciseness	Mostly efficient tables of benchmarks and event names, but includes basic definitions Claude already knows (DAU = Daily Active Users) and ASCII placeholder dashboards with [N]/[X]% that pad tokens without adding guidance.	3 / 5
Actionability	Provides a concrete event tracking plan with named events and properties, explicit naming conventions, and output-format templates; minor gaps in actual tool setup steps keep it just short of fully copy-paste ready.	4 / 5
Workflow Clarity	The Initial Assessment is a clear numbered sequence, but the remainder is a reference catalog with no validation checkpoints or explicit error-recovery loops; the workflow is implied rather than gated.	3 / 5
Progressive Disclosure	Has section structure, but ~200 lines of metrics/event/dashboard reference material are inlined rather than split into bundle files, and the referenced app-marketing-context.md does not exist in any bundle directory.	3 / 5
	Total	13 / 20 Passed

Description

95%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, well-structured description that clearly states capabilities, provides rich natural trigger terms, and disambiguates from adjacent skills. The only minor gap is that the action list is compact rather than comprehensive.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("set up, interpret, or improve their app analytics and tracking") but does not enumerate the full breadth of the analytics domain, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what it does and when to use it, with a concrete "Use when the user mentions…" clause listing specific trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive coverage of natural terms users would say — "analytics", "tracking", "metrics", "KPIs", "funnel", "attribution", "how is my app performing" — including synonyms and platform-specific phrasing.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (app analytics) with distinct triggers and explicit boundary disambiguation pointing A/B testing and retention to sibling skills, minimizing conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Eronred/aso-skills
Path: skills/app-analytics/SKILL.md
Commit: 4df730f

Reviewed: 6 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.