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

app-marketing-context

When the user wants to create or update their app marketing context document. Also use when the user mentions "app context", "marketing brief", "app positioning", or when starting any ASO or app marketing project. This is the foundation skill — all other skills check for this context first.

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-marketing-context/SKILL.md

Quality

Content

75%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 an efficient, well-structured instruction-only skill with concrete templates, explicit questions, and a clear branching workflow. Its weaknesses are minor: a few mild openers, an unspecified metadata-pulling method, and no verification step before recommending next skills.

Suggestions

Add a concrete method or command for pulling current ASO metadata in section 4 (currently just 'offer to pull current metadata' with no mechanism).

Add a verification checkpoint after saving (e.g., re-read the saved file and confirm all sections are populated) before summarizing and recommending next skills.

Trim the 'You are an expert mobile app marketing strategist' opener to keep the body maximally token-efficient.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean templates and bulleted question lists with no padding about concepts Claude already knows; only minor openers like 'You are an expert mobile app marketing strategist' could be trimmed.	4 / 5
Actionability	Concrete section templates with field-by-field placeholders, explicit questions to ask, and an exact output path give mostly executable guidance, with minor gaps such as no method for pulling current metadata in section 4.	4 / 5
Workflow Clarity	A clear sequence (check existence -> branch to update or build -> save -> summarize -> recommend next skills) with an explicit existence-check branch; minor validation gap in that it does not confirm the saved document is complete before recommending next skills.	4 / 5
Progressive Disclosure	A single self-contained SKILL.md with clear section headers and a well-signaled Related Skills list; the substantial inline templates are appropriate as the deliverable, leaving only minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

78%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 is strong: it clearly states the skill's purpose and provides explicit natural-language triggers with synonyms. Its main weakness is the broad 'any ASO or app marketing project' phrasing, which slightly raises conflict risk against sibling ASO skills.

Suggestions

Narrow the trigger phrasing from 'any ASO or app marketing project' to the specific context-setting step (e.g., 'Use when starting a new ASO/marketing effort that needs a shared context document') to reduce overlap with sibling skills.

Add one or two more concrete actions beyond 'create or update' (e.g., 'gather app positioning and competitive context') to lift specificity toward a 4.

Dimension	Reasoning	Score
Specificity	The phrase 'create or update their app marketing context document' names the artifact and two concrete actions, matching the anchor for naming a domain with 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It explicitly answers what it does ('create or update their app marketing context document') and when to use it ('Also use when the user mentions...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger terms like 'app context', 'marketing brief', 'app positioning', and 'ASO or app marketing project' give good keyword coverage, though a few additional synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	It targets a clear app-marketing/ASO niche, but 'when starting any ASO or app marketing project' is broad enough to create minor overlap risk with closely related sibling skills.	4 / 5
	Total	16 / 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-marketing-context/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.