freemcplab / Directory / Playground / claude-code-aso-skill

● Community wsbs20 ⚡ Instant

claude-code-aso-skill

Name: claude-code-aso-skill MCP Server
Author: wsbs20

by wsbs20 · wsbs20/claude-code-aso-skill

Agent-based ASO framework for Claude Code: a fleet of sub-agents for planning, execution, reports, action items, and executive summaries — slash-command driven.

A multi-agent take on App Store Optimization. Rather than one monolith, it spins up specialized AEO sub-agents — planners, executors, reporters, action-item managers, summarizers — triggered by slash commands. Produces structured reports after each run and lets you customize the action list. Aimed at beginners who want iOS + Android ASO without separate tools per platform.

▶ Watch demo 📦 Install 💡 Use Cases

Why use it

Key features

Fleet of AEO sub-agents (planning / execution / reporting / summary)
Slash-command activation
Report after every automation task
Customizable action items
iOS + Android in one interface — beginner-friendly

Live Demo

What it looks like in practice

claude-code-aso-skill-2.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "claude-code-aso-skill-2": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/wsbs20/claude-code-aso-skill",
        "~/.claude/skills/claude-code-aso-skill"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "claude-code-aso-skill-2": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/wsbs20/claude-code-aso-skill",
        "~/.claude/skills/claude-code-aso-skill"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "claude-code-aso-skill-2": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/wsbs20/claude-code-aso-skill",
        "~/.claude/skills/claude-code-aso-skill"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "claude-code-aso-skill-2": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/wsbs20/claude-code-aso-skill",
        "~/.claude/skills/claude-code-aso-skill"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "claude-code-aso-skill-2",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/wsbs20/claude-code-aso-skill",
        "~/.claude/skills/claude-code-aso-skill"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "claude-code-aso-skill-2": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/wsbs20/claude-code-aso-skill",
          "~/.claude/skills/claude-code-aso-skill"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add claude-code-aso-skill-2 -- git clone https://github.com/wsbs20/claude-code-aso-skill ~/.claude/skills/claude-code-aso-skill

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use claude-code-aso-skill

Generate an ASO report with action items in one command

👤 Indie devs who want a weekly ASO sanity check ⏱ ~20 min beginner

When to use: Every week or two, you want a snapshot of where your listing stands.

Prerequisites

Skill installed — git clone https://github.com/wsbs20/claude-code-aso-skill ~/.claude/skills/claude-code-aso-skill

Flow

Fire the slash command

/aso-report my app: com.acme.habit — cover metadata, competitors, screenshots.✓ Copied

→ Planning agent kicks off, execution follows, summary lands
Review action items

Show the action items; let me customize the list.✓ Copied

→ Editable list; you remove / promote as needed

Outcome: A report you can read in 5 minutes with ordered next steps.

Pitfalls

Treating the action items as done when they're just suggested — Mark status explicitly; the skill tracks state

Combine with: aso-skill

Pre-launch ASO check across iOS and Android

👤 Small teams launching on both platforms ⏱ ~90 min intermediate

When to use: 2–3 weeks before a dual-platform launch.

Flow

Run planning agent

/aso-plan launch for iOS + Android. Target markets: US, UK, DE.✓ Copied

→ Per-platform per-market checklist
Execute

/aso-execute — run the checks.✓ Copied

→ Reports per platform with gaps highlighted

Outcome: You walk in to launch day with nothing to chase.

Combinations

Pair with other MCPs for X10 leverage

claude-code-aso-skill-2 + aso-skill

Use this skill for reporting/coordination; aso-skill for App Store Connect submission

After /aso-report, hand the action items to aso-skill to actually submit metadata changes.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call
/aso-plan	app id + scope	Start of any ASO session
/aso-execute	plan id	After plan approved
/aso-report	app id	End-of-session snapshot

Cost & Limits

What this costs to run

API quota: None
Tokens per call: Moderate — multi-agent runs burn more than single-shot
Monetary: Free
Tip: Run /aso-report weekly, not daily — the agents overlap

Security

Permissions, secrets, blast radius

Credential storage: None by itself; pair with aso-skill for actual ASC auth

Data egress: Public store data

Troubleshooting

Common errors and fixes

Agents produce contradictory suggestions

Tighten the plan scope; broad scopes cause disagreement

Reports feel generic

Supply explicit competitor list and target keywords in the plan step

Alternatives