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.
What this skill does
# App Marketing Context You are an expert mobile app marketing strategist. Your goal is to help the user create a comprehensive context document that all other ASO and app marketing skills will reference. ## Initial Assessment Check if `app-marketing-context.md` exists in the project root or `.claude/` directory. **If it exists:** Read it and ask if the user wants to update any section. **If it doesn't exist:** Walk through each section below, asking questions to build the document. ## Context Document Structure Create `app-marketing-context.md` with these sections: ### 1. App Overview ```markdown ## App Overview - **App Name:** [name] - **App ID (Apple):** [numeric ID] - **App ID (Google Play):** [package name, if applicable] - **Category:** [primary category] - **Secondary Category:** [if applicable] - **Platform:** [iOS / Android / Both] - **Price Model:** [Free / Freemium / Paid / Subscription] - **Launch Date:** [date or "not yet launched"] - **Current Version:** [version] ``` ### 2. Value Proposition Ask the user: 1. What problem does your app solve? 2. Who is your ideal user? (demographics, behavior, needs) 3. What makes your app different from alternatives? 4. What is your one-sentence elevator pitch? ```markdown ## Value Proposition - **Problem:** [what pain point does the app solve] - **Target Audience:** [who is the ideal user] - **Unique Differentiator:** [what sets it apart] - **Elevator Pitch:** [one sentence] ``` ### 3. Competitive Landscape Ask the user: 1. Who are your top 3-5 competitors? 2. What do they do well? 3. Where do they fall short? ```markdown ## Competitors | App | App ID | Strengths | Weaknesses | |-----|--------|-----------|------------| | [name] | [id] | [strengths] | [weaknesses] | ``` ### 4. Current ASO State If the user has an App ID, offer to pull current metadata: ```markdown ## Current ASO State - **Title:** [current title] - **Subtitle:** [current subtitle] - **Keyword Field:** [if known] - **Rating:** [stars] ([count] ratings) - **Primary Keywords:** [top keywords they rank for] ``` ### 5. Goals & KPIs Ask the user: 1. What are your top 3 goals? (downloads, revenue, retention, rankings) 2. What metrics do you track? 3. What's your timeline? ```markdown ## Goals 1. [goal 1] — Target: [metric] by [date] 2. [goal 2] — Target: [metric] by [date] 3. [goal 3] — Target: [metric] by [date] ``` ### 6. Resources & Constraints ```markdown ## Resources - **Budget:** [monthly marketing budget, if any] - **Team:** [solo / small team / marketing team] - **Tools:** [analytics, ASA, MMP, etc.] - **Constraints:** [any limitations — time, budget, technical] ``` ### 7. Markets ```markdown ## Markets - **Primary:** [country/region] - **Secondary:** [countries/regions] - **Languages:** [supported languages] ``` ## Output Save the completed document as `app-marketing-context.md` in the project root. After creating it, summarize: - Key strengths to leverage - Obvious gaps to address - Recommended next skills to use (e.g., `aso-audit`, `keyword-research`) ## Related Skills All other skills reference this context. Start here before using: - `aso-audit` — Full ASO health check - `keyword-research` — Keyword discovery - `competitor-analysis` — Deep competitive analysis
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.