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.

A well-structured, template-driven instruction skill: the two-branch entry assessment, per-section questions, and ready-to-use document templates make it immediately actionable. Weaknesses are minor — a role-play opener, an unspecified metadata-pull step, and no explicit completeness check before saving.

Suggestions

Specify how current ASO metadata should be pulled (e.g., which tool, store page URL, or manual paste) instead of the vague "offer to pull current metadata".

Add a final validation step before saving — e.g., check that all seven sections are populated and prompt the user for any skipped ones.

Trim the "You are an expert..." role-play opener; the instructions and templates already convey the task.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, copy-paste markdown templates with placeholder fields — efficient with almost no over-explanation of concepts. It is not anchor 5 because the opener ("You are an expert mobile app marketing strategist. Your goal is to help the user create a comprehensive context document...") is mild padding that earns no tokens.	4 / 5
Actionability	Concrete guidance throughout: exact file locations to check (project root, `.claude/`), per-section question lists, complete markdown templates, and a defined output filename. It misses anchor 5 only because "offer to pull current metadata" names no method, tool, or command for pulling metadata from an App ID.	4 / 5
Workflow Clarity	A clear two-branch sequence (exists → ask about updates / missing → walk each section) ending in save and a summary of strengths, gaps, and next skills. Not anchor 5 because there is no explicit validation checkpoint (e.g., confirming every section was completed) before saving the document — though as a non-destructive, non-batch skill the feedback-loop cap does not apply.	4 / 5
Progressive Disclosure	No bundle files exist, and the single-file body is well organized with one section per document part and clear headers. At ~125 lines the seven section templates are navigable and appropriately placed in SKILL.md, but the size sits above the under-50-line simple-skill zone where organization alone earns a 5.	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.

A well-constructed description with explicit what/when structure, third-person voice, and concrete quoted trigger terms. Its main limitation is thin action specificity and a broad "any ASO or app marketing project" trigger that overlaps its own skill family.

Suggestions

Enumerate the concrete actions inside the description (e.g., builds the app overview, value proposition, competitor table, ASO state, goals, and markets sections) to lift specificity from one action pair to several.

Add missing natural trigger synonyms such as the spelled-out "app store optimization" or "app brief" to broaden trigger coverage.

Narrow "when starting any ASO or app marketing project" to distinguish this foundation skill from the sibling skills (aso-audit, keyword-research) that share that trigger space.

Dimension	Reasoning	Score
Specificity	The description names the domain (app marketing context document) and one concrete action pair ("create or update their app marketing context document"), but stops there. It does not reach anchor 4, which expects several specific actions listed with only minor coverage gaps.	3 / 5
Completeness	It explicitly answers what ("create or update their app marketing context document") and when, with a concrete "When the user wants to..." clause plus quoted trigger phrases ("Also use when the user mentions..."). This matches the anchor-5 example structure of a clear what followed by explicit trigger conditions, rather than the weaker when-clause of anchor 4.	5 / 5
Trigger Term Quality	Quoted triggers "app context", "marketing brief", "app positioning", plus "ASO or app marketing project" give good natural keyword coverage. It falls short of anchor 5 because common variations like the spelled-out "app store optimization" or "app brief" are missing.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche ("This is the foundation skill — all other skills check for this context first") with distinctive quoted triggers like "app positioning" and "marketing brief". It is not anchor 5 because the broad phrase "any ASO or app marketing project" overlaps with the sibling skills it references (aso-audit, keyword-research, competitor-analysis).	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: 8de1ee1

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.