Skip to content
FunCoding

Search

Search docs, Skills and MCP

app-description-writer

Generate compelling App Store descriptions that convert browsers into users. Use when writing initial descriptions, improving existing copy, or drafting promotional text and What's New for a major update.

浏览器自动化784skills/app-store/app-description-writer/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/rshankras/claude-code-apple-skills/app-description-writer/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

App Description Writer

Generate compelling App Store descriptions that convert browsers into users.

When This Skill Activates

  • User needs to write initial App Store description
  • User wants to improve existing description
  • User is preparing for a major update
  • User asks about promotional text or What's New

Information Gathering

Before writing, ask about:

  1. App Basics

    • What does the app do? (one sentence)
    • Who is it for? (target audience)
    • What problem does it solve?
  2. Key Features

    • Top 3-5 features
    • What makes it unique vs competitors?
    • Any awards or recognition?
  3. Social Proof

    • Number of users/downloads (if impressive)
    • Notable reviews or press mentions
    • Any partnerships or integrations?
  4. Tone

    • Professional / Casual / Fun / Technical?
    • Brand voice keywords?

Output Format

Generate all three text types:

1. Promotional Text (170 characters)

  • First thing users see
  • Should create curiosity or urgency
  • Can be updated without app review
  • Good for seasonal/sale messaging

2. Full Description (4000 characters max)

Structure:

[Opening Hook - 1-2 sentences, problem/benefit focused]

[Key Features with emoji bullets]
• Feature 1 - benefit
• Feature 2 - benefit
• Feature 3 - benefit

[Social Proof paragraph - optional]

[How it works - brief explanation]

[Call to action]

[Support/contact info]

3. What's New (4000 characters)

For updates:

[Version X.X highlights]

NEW
• Feature addition

IMPROVED
• Enhancement

FIXED
• Bug fix

Thank you for your feedback!

Best Practices

Do's

  • Lead with the biggest benefit
  • Use short paragraphs (2-3 lines max)
  • Include relevant keywords naturally
  • Use emojis sparingly for scannability
  • End with clear call-to-action
  • Mention if there's a free trial/tier

Don'ts

  • Don't start with "Welcome to..."
  • Don't use ALL CAPS excessively
  • Don't include URLs (they're not clickable)

Examples

Promotional Text Examples

Productivity App:

Transform chaos into clarity. The task manager that adapts to how YOU work.

Weather App:

Know before you go. Hyperlocal forecasts down to your street corner. ⛅️

Finance App:

Your money, finally making sense. Budgeting that doesn't feel like homework.

Description Opening Examples

Problem-First:

Tired of losing track of important tasks? [App] turns your scattered thoughts
into organized action plans in seconds.

Benefit-First:

Capture ideas the moment they strike. [App] is the fastest way to go from
thought to organized note, anywhere.

Curiosity-First:

What if your to-do list actually helped you get things done? Introducing
a smarter way to manage your day.

Localization Tips

When localizing descriptions:

  • Don't just translate—adapt to cultural context
  • Research local competitors' descriptions
  • Adjust feature emphasis by market
  • Use native speakers for review
  • Consider character limits in other languages (German expands ~30%)

Character Limits Reference

FieldLimit
App Name30 characters
Subtitle30 characters
Promotional Text170 characters
Description4000 characters
What's New4000 characters
Keywords100 characters

Templates

Template: Utility App

[One-line value proposition]

Stop [pain point]. Start [desired outcome].

✨ KEY FEATURES

• [Feature 1] — [Benefit in user terms]
• [Feature 2] — [Benefit in user terms]
• [Feature 3] — [Benefit in user terms]
• [Feature 4] — [Benefit in user terms]

💡 HOW IT WORKS

[2-3 sentences explaining the core flow]

🎯 PERFECT FOR

• [User type 1]
• [User type 2]
• [User type 3]

[Social proof if available]

Download now and [call to action with benefit].

Questions? We're here to help: [support email]

Template: Creative App

[Evocative opening that sparks imagination]

[App Name] puts [creative power] in your pocket.

🎨 CREATE

• [Creative feature 1]
• [Creative feature 2]
• [Creative feature 3]

📤 SHARE

• [Sharing/export feature]
• [Community feature if applicable]

🔓 UNLOCK YOUR CREATIVITY

[Inspirational paragraph about what users can achieve]

Join [X] creators already using [App Name].

[Call to action]

Template: What's New

Thanks for using [App Name]! Here's what's new in version X.X:

🆕 NEW
• [Major new feature with brief explanation]

⚡️ IMPROVED
• [Performance improvement]
• [UX enhancement]

🔧 FIXED
• [Bug fix users complained about]

Love [App Name]? Leave us a review — it helps more than you know! 💙

Feedback? [support email]

Similar Skills

webapp-testing
anthropics/skills180k

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Browser automation

browser-testing-with-devtools
addyosmani/agent-skills103k

browser-testing-with-devtools

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.

Browser automation

webapp-testing
ComposioHQ/awesome-claude-skills77k

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Browser automation

browser
code-yeongyu/oh-my-openagent70k

browser

Drives a real browser through the omowright library from the js eval kernel: sites the user is already signed into, forms and clicks, JS-rendered pages, screenshots, web QA, extension popups, a human handoff for login, CAPTCHA or OTP, and a browser you own for scraping, bot-scored targets, network capture and QA traces. Use for any interactive browser task; not for a plain search or an unblocked static fetch.

Browser automation

agent-browser
shanraisshan/claude-code-best-practice67k

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

Browser automation

cherry-regression-test
CherryHQ/cherry-studio52k

cherry-regression-test

Run Cherry Studio critical-path system regression tasks through the repository-owned Playwright E2E workflow. Use for full regression, release acceptance, development-branch system validation, or a named cherry-regression-test task on GitHub-hosted macOS and Windows runners.

Browser automation