app-marketing-context

Overview of app-marketing-context skill

app-marketing-context is a foundation skill for building the app marketing context document that other ASO and product marketing workflows can reuse. It is best for product marketers, founders, growth leads, and AI agents that need a single source of truth before writing store copy, positioning, briefs, or campaign assets.

What the app-marketing-context skill does

This skill helps you create or update app-marketing-context.md by gathering the app facts that matter most: app overview, value proposition, target user, differentiation, positioning, and launch constraints. The real job-to-be-done is not “write marketing,” but “capture the inputs that make every later marketing prompt more accurate.”

When to use it

Use the app-marketing-context skill when you are starting an ASO or app marketing project, revising a product narrative, or noticing that different prompts keep producing inconsistent positioning. It is also the right first step when a repo asks for a marketing brief, app context, or source document before generating other outputs.

Why it is worth installing

Unlike a generic prompt, this skill gives you a repeatable intake flow and a standard document structure. That reduces guesswork, keeps marketing inputs centralized, and makes it easier for downstream skills to stay aligned to the same app facts and audience definition.

How to Use app-marketing-context skill

Install and locate the source file

Install the app-marketing-context skill from Eronred/aso-skills with:

npx skills add Eronred/aso-skills --skill app-marketing-context

Then open skills/app-marketing-context/SKILL.md first. In this repo, there are no helper scripts, rules, or resources to expand the workflow, so the skill file itself is the main source of truth.

Feed it the right starting input

The app-marketing-context usage pattern works best when you give the skill a rough goal plus whatever is already known. Strong inputs include the app name, platform, category, pricing model, launch stage, and a short description of the problem the app solves. If you already have a draft context file, tell the skill to update it instead of rebuilding from scratch.

A weak prompt is: “Help with marketing.”
A stronger prompt is: “Create app-marketing-context.md for a subscription iOS fitness app aimed at busy beginners; we need clearer positioning and an update to our target user section.”

Turn a vague goal into a usable brief

For best results, ask the skill to answer the missing questions in sequence: what the app is, who it is for, why it is different, and what evidence supports that difference. If you are using app-marketing-context for Product Marketing, include any constraints that affect messaging, such as launch timing, geographies, or a monetization shift.

Read the document the skill is built around

The skill’s core output is a context file with structured sections, so review those sections before generating anything downstream. Start with SKILL.md, then look for an existing app-marketing-context.md in the project root or .claude/. If it exists, update it section by section; if it does not, let the skill interview you and create it.

app-marketing-context skill FAQ

Is app-marketing-context only for ASO work?

No. The app-marketing-context skill is useful for ASO, but it is broader than store optimization. It also supports product marketing, launch planning, and any workflow that needs stable app context before writing copy or strategy.

How is this different from a normal prompt?

A normal prompt usually creates one-off output. app-marketing-context install gives you a reusable document and a consistent intake flow, which makes later prompts easier to steer and less likely to contradict each other.

Can beginners use this skill?

Yes, if they can answer basic product questions. The skill is especially helpful when a beginner does not yet know how to structure a marketing brief, because it turns the process into a guided set of questions instead of a blank-page exercise.

When should I not use it?

Do not use app-marketing-context when you only need a quick headline, ad variation, or one-off store metadata tweak. It is overkill for isolated copy tasks and works best when the goal is to build a durable reference for future marketing work.

How to Improve app-marketing-context skill

Give it sharper source facts

The quality of app-marketing-context usage depends on the quality of your inputs. Provide concrete details for the app name, pricing, platform, audience, category, and launch status instead of broad claims like “great UX” or “AI-powered.” Specific facts make the resulting context document more useful to every downstream skill.

Clarify differentiation with proof

The most important part of the skill is usually the value proposition and differentiation. If you want better output, include evidence such as feature comparisons, retention signals, user quotes, or a clear before-and-after benefit. Without that, the document tends to become generic positioning language.

Update the context as the product changes

Use the app-marketing-context guide as a living file, not a one-time artifact. Revisit it after pricing changes, audience shifts, new platform launches, or major feature releases so later marketing prompts stay aligned with current reality.

Watch for the usual failure modes

The most common mistake is under-specifying the target user and problem, which leads to vague positioning. Another failure mode is mixing product facts with aspirational claims. Keep the file grounded in what the app actually does today, then iterate after the first draft instead of trying to perfect everything in one pass.