Web Presence logo

Web Presence

Community
rshankras
web-presence

The discovery surfaces outside the App Store app — your apps.apple.com product page ranking on Google, an owned landing page with a Smart App Banner, and the deal-site ecosystem that auto-amplifies price drops. Use when building a landing page, improving Google visibility for an app, planning a price-drop promotion, or auditing off-store discovery.

Overview

Publisherrshankras
Repositoryclaude-code-apple-skills
Skill nameweb-presence
Stars
744
Forks
70
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by rshankras on GitHub. Read the source before you install it.

Installation

Install the Web Presence AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/rshankras/claude-code-apple-skills.git /tmp/claude-code-apple-skills
mkdir -p .claude/skills
cp -r /tmp/claude-code-apple-skills/skills/app-store/web-presence .claude/skills/web-presence
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Web Presence in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Web Presence on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Web Presence is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Web Presence

Every app has a public web page at apps.apple.com that ranks in Google — most developers never work that surface. Pair it with an owned landing page and the deal-site ecosystem and the open web becomes a free acquisition channel that compounds with everything on-store.

When This Skill Activates

  • "Make my app findable on Google" / no results for the app's own name
  • Building or reviewing a product landing page
  • Planning a temporary price drop or sale
  • The store-growth audit flags P6.6 (web presence) or P7.5 (deal sites)

Surface 1: The apps.apple.com page is a Google citizen

The store page's Google snippet draws from your app name, subtitle, and description opening — one more reason the first description paragraph must be benefit-led plain language (see app-store/app-description-writer).

  • ✅ Search your app's name + category terms on Google periodically; if the store page doesn't rank for your own brand, something is wrong (usually a generic name — see product/app-namer).
  • ✅ Ratings, price, and In-App Purchase labels appear in the snippet — per-storefront ratings mechanics apply (app-store/ratings-mechanics).
  • ❌ Treating the store URL as un-shareable internal plumbing. It's often your best-ranking page; link to it from everywhere (with ?pt= provider token for attribution where you need source data).

Surface 2: An owned landing page + Smart App Banner

One page, one job: convert a web visitor into a store visitor.

  • Structure: name + one-line promise → 2–3 screenshots or a short capture → social proof → a prominent Download on the App Store badge (Apple's official artwork, linked with your attribution token).

  • Smart App Banner — one meta tag; Safari renders a native install/open banner:

    html
    <meta name="apple-itunes-app" content="app-id=YOUR_APP_ID, app-argument=https://yourapp.com/from-web">

    ✅ The banner shows Open for installed users — deep-linking into the app, down to specific in-app content via app-argument — and View for everyone else, opening the App Store in one tap. ❌ Custom "download our app" interstitials — the native banner already does this for free.

  • App Store Marketing Tools (tools.applemediaservices.com) — use for referral links, QR codes, and localized badge assets instead of hand-rolling them.

  • The landing page is also where pre-launch waitlists live (TestFlight public link — see product/beta-testing) and where press/link-in-bio traffic should land, because you can measure it before it enters the store funnel.

  • App Clips can front the landing page with an instant experience (generators/app-clip).

Surface 3: The deal-site ecosystem

Deal aggregators scrape App Store price drops automatically — no submission needed, just drop the price.

Price drop → aggregator listing → download spike → chart climb → organic downloads that outlive the sale. Velocity is the product; the discounted revenue is the cost of the campaign.

  • ✅ Drop meaningfully (50%+ or free-for-a-day reads as a deal; 10% doesn't scrape well).
  • ✅ Time drops to compound: with an in-app event, a seasonal moment, or the announced On-Sale badge surface (see generators/in-app-events), and have the next release ready so climbers land on a fresh listing.
  • ✅ Prompt for ratings during the spike window — sale users rate too, and the count sticks after prices recover.
  • ❌ Permanent-discount theater (always "90% off") — scrapers and users both learn to ignore it, and review teams notice manipulated anchor pricing.
  • ❌ Dropping the price of a subscription app's download — use offer codes instead (generators/offer-codes-setup).

Output Format

Audit report:

Google: brand query rank · store-page snippet quality (name/subtitle/desc opener)
Landing page: live? banner tag? attribution token? waitlist path?
Deal readiness: pricing model compatible? last drop + result? next planned window?

Each gap routed: copy fixes → app-store/app-description-writer; page build → this skill; price-drop plan → this skill + monetization pricing.

References

Frequently asked questions

What does the Web Presence AI skill do?

The discovery surfaces outside the App Store app — your apps.apple.com product page ranking on Google, an owned landing page with a Smart App Banner, and the deal-site ecosystem that auto-amplifies price drops. Use when building a landing page, improving Google visibility for an app, planning a price-drop promotion, or auditing off-store discovery.

Why use Web Presence on TypingMind?

Because you install it once and use it with any model. Web Presence is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Web Presence in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/rshankras/claude-code-apple-skills/tree/main/skills/app-store/web-presence. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Web Presence?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Web Presence?

As many as you like. As long as a model supports skills, you can use Web Presence with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Web Presence AI skill free?

Yes. It is published on GitHub by rshankras under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇