Asc Ppp Pricing
rorkai/app-store-connect-cli-skills
Set territory-specific pricing for subscriptions and in-app purchases using current asc setup, pricing summary, price import, and price schedule commands.
Turn an app idea into validated, App-Store-ready name candidates.
$ npx skills add rshankras/claude-code-apple-skills --skill app-namer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rshankras/claude-code-apple-skills app-namer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/rshankras/claude-code-apple-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/product/app-namer .claude/skills/app-namer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "app-namer" agent skill from https://github.com/rshankras/claude-code-apple-skills/tree/main/skills/product/app-namer into .claude/skills/app-namer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "app-namer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/rshankras/claude-code-apple-skills/tree/main/skills/product/app-namerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add rshankras/claude-code-apple-skills --skill app-namer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rshankras/claude-code-apple-skills app-namer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rshankras/claude-code-apple-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/product/app-namer .agents/skills/app-namer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "app-namer" agent skill from https://github.com/rshankras/claude-code-apple-skills/tree/main/skills/product/app-namer into .agents/skills/app-namer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "app-namer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rshankras/claude-code-apple-skills --skill app-namer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rshankras/claude-code-apple-skills app-namer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rshankras/claude-code-apple-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/product/app-namer .cursor/skills/app-namer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "app-namer" agent skill from https://github.com/rshankras/claude-code-apple-skills/tree/main/skills/product/app-namer into .cursor/skills/app-namer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "app-namer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/rshankras/claude-code-apple-skills.git --path skills/product/app-namer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add rshankras/claude-code-apple-skills --skill app-namer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rshankras/claude-code-apple-skills app-namer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rshankras/claude-code-apple-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/product/app-namer .gemini/skills/app-namer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "app-namer" agent skill from https://github.com/rshankras/claude-code-apple-skills/tree/main/skills/product/app-namer into .gemini/skills/app-namer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "app-namer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install rshankras/claude-code-apple-skills app-namerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add rshankras/claude-code-apple-skills --skill app-namer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rshankras/claude-code-apple-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/product/app-namer .github/skills/app-namer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "app-namer" agent skill from https://github.com/rshankras/claude-code-apple-skills/tree/main/skills/product/app-namer into .github/skills/app-namer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "app-namer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rshankras/claude-code-apple-skills --skill app-namer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rshankras/claude-code-apple-skills app-namer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rshankras/claude-code-apple-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/product/app-namer .opencode/skills/app-namer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "app-namer" agent skill from https://github.com/rshankras/claude-code-apple-skills/tree/main/skills/product/app-namer into .opencode/skills/app-namer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "app-namer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
app-namerTurn an app idea into validated, App-Store-ready name candidates.
App Namer is an agent skill from rshankras/claude-code-apple-skills. Turn an app idea into validated, App-Store-ready name candidates. Use when the user says "name my app", "what should I call it", "app name ideas", "help me name this app", "is this name available", or needs to pick a brandable, ownable name before reserving it in App Store Connect.
Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `naming-strategies.md` and `validation-checklist.md`).
It sits in Mobile, covering App store release. It works with App Store Connect. The repository describes itself as: Claude Code skills for Apple platform development (iOS, macOS, iPadOS) — product validation, code generation, App Store optimization, and more. The licence is MIT.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 9ffb831. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteWebSearchWebFetchAskUserQuestionFrom allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
App Namer loads about 3.4k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 1,323 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from rshankras/claude-code-apple-skills at commit 9ffb831, republished under its MIT licence (© rshankras). 1,323 words, ~3,411 tokens.
.claude/skills/app-namer/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.Takes an app idea or one-liner and produces a ranked shortlist of 5-8 validated name candidates — not random brainstorming. Each candidate is generated from a naming archetype, paired with a subtitle, checked against App Store display rules, and run through an availability gauntlet (App Store Connect name, trademark, domain, handle) before it's recommended.
The output is a name you can reserve in App Store Connect today, with the keyword work already aligned to feed the app-store/keyword-optimizer skill.
Use this skill when the user:
idea-generator and needs the name before writing the PRDNo app idea yet? Run product/idea-generator first, then come back with the chosen idea.
Already have a locked name and just want ASO? Skip this skill — go to app-store/keyword-optimizer.
Before generating names, load both reference files:
| File | Purpose |
|---|---|
| naming-strategies.md | The 3 archetypes, naming techniques, App Store display mechanics (30-char limit, home-screen truncation, name/subtitle interplay), good/bad examples |
| validation-checklist.md | The knockout gauntlet — App Store Connect name availability, trademark sanity check, domain/.app, social handles, linguistic safety |
Idea/positioning
↓ elicit
Naming brief (what it does, who it's for, personality, scope ceiling)
↓ generate across archetypes
20-40 raw candidates (branded / descriptive / hybrid)
↓ filter (pronounce, spell, truncate, confusability)
8-12 survivors
↓ pair with subtitle + score
Ranked candidates with name + subtitle + display preview
↓ validate (ASC name / trademark / domain / handle)
5-8 validated candidates
↓
Recommendation + "reserve now" actionIf the user hasn't given enough context, gather it with AskUserQuestion. You need:
| Field | Why it matters |
|---|---|
| One-liner | What the app does in one sentence — drives descriptive/hybrid candidates |
| Target user | Tone calibration (pro tool vs. playful consumer app) |
| Personality | Serious, playful, minimal, premium, technical? Sets the archetype mix |
| Category | App Store category — affects trademark class and competitor naming norms |
| Scope ceiling | Will it stay single-purpose or grow? A too-descriptive name boxes you in |
| Existing brand | Company/developer name, existing app family to stay consistent with |
If the user gives a one-liner and nothing else, infer sensible defaults, state your assumptions, and proceed — don't block on a full questionnaire.
Generate 20-40 raw candidates spread across the three archetypes (see naming-strategies.md for each technique and examples):
Aim for roughly 40% hybrid, 30% branded, 30% descriptive for a typical indie app — hybrid names tend to win because they're ownable and memorable, with the descriptive keyword pushed into the subtitle.
Use the techniques in naming-strategies.md: real words, compounds, portmanteaus, prefix/suffix, dropped vowels, foreign words, metaphors.
Kill any candidate that fails a basic filter before spending effort scoring it:
Target 8-12 survivors going into scoring.
For each survivor, write the Name — Subtitle pairing the way it appears on the App Store. This is where the ASO strategy lives:
[Brand Name] — [Descriptive keyword phrase]
Halide — Pro Camera
Streaks — Habit Tracker
Bear — Markdown NotesThe name carries the brand; the subtitle carries the searchable keywords. This means a branded/hybrid name doesn't need to be descriptive — the subtitle does that job. Both are 30-char fields and both are indexed. (See app-store/keyword-optimizer for full keyword allocation.)
Score each candidate 1-10 on six dimensions:
| Dimension | WEAK (1-3) | STRONG (4-7) | EXCELLENT (8-10) |
|---|---|---|---|
| Memorability | Forgettable, generic | Distinctive | Sticky, instantly recalled |
| Clarity/Fit | Misleading or opaque | Evokes the benefit (with subtitle) | Name+subtitle = instant understanding |
| Availability | Name & domain taken, TM conflict | Domain workaround, name free | Name + .com/.app + clean TM headroom |
| ASO Value | Dead keyword-wise | Subtitle carries keywords | Brandable + subtitle owns a keyword |
| Pronounce/Spell | Fails radio test | Minor ambiguity | Say it once, spell it right, Siri-safe |
| Scalability | Boxed into v1 scope | Some room | Grows with the product |
Overall = weighted average, with Availability and Memorability weighted 1.5× (an unavailable name scores zero regardless of how clever it is).
Run the top 5-8 through the gauntlet in validation-checklist.md. For each, record status as available / taken / conflict / unchecked:
.com, then .app, then get-/try-/use- prefixesUse WebSearch/WebFetch to check what's checkable (existing App Store apps, trademark databases, domain registrars). For anything you can't verify, mark it unchecked and tell the user exactly how to check — never report a name as available if you didn't verify it.
Present the ranked shortlist, then make a single clear recommendation. End with the action: reserve the winning name in App Store Connect now — App Store names are unique and first-come, so a name that's available today can be gone tomorrow.
{
"naming_brief": {
"one_liner": "On-device app that turns leftover ingredients into recipe suggestions",
"target_user": "Home cooks who want to reduce food waste",
"personality": "warm, simple, a little playful",
"category": "Food & Drink",
"scope_ceiling": "could expand to meal planning and grocery lists",
"assumptions": ["No existing brand to match", "iOS-first, US market primary"]
},
"shortlist": [
{
"rank": 1,
"name": "Larder",
"archetype": "hybrid",
"name_subtitle": "Larder — Recipes From Leftovers",
"char_counts": { "name": 6, "subtitle": 30 },
"home_screen_preview": "Larder",
"rationale": "Evokes the source (what's in your larder) without being literal about recipes; warm, short, and far more ownable than the generic 'Pantry'; subtitle carries the 'recipes' + 'leftovers' keywords.",
"scores": {
"memorability": 8,
"clarity_fit": 8,
"availability": 9,
"aso_value": 8,
"pronounce_spell": 9,
"scalability": 9
},
"overall_score": 8.4,
"validation": {
"app_store_name": "no live 'Larder' recipe app found — verify in ASC New App and reserve",
"trademark": "unchecked — run USPTO TESS for 'Larder' in Class 9/42 before committing",
"domain": "larder.com taken; larder.app available — recommended buy",
"handle": "@larder taken; @larderapp available",
"linguistic": "clean in EN/ES/DE/JA; Siri-safe"
},
"risks": "Slightly less self-explanatory than 'Pantry' on its own — the subtitle does the clarifying. Confirm the trademark knockout before reserving."
}
],
"filtered_out": [
{ "name": "Pantry", "reason": "Too generic to own — App Store name and pantry.com almost certainly taken, un-trademarkable" },
{ "name": "LeftoverChef", "reason": "Two-word compound truncates badly on Home Screen; 'Chef' is crowded and trademark-risky" },
{ "name": "Fridgify", "reason": "Cute but fails the radio test — users will spell it 'Fridgefy'/'Fridgi'" }
],
"recommendation": "Lead with Rank 1 if a clean App Store variant clears reservation; otherwise Rank 2. Reserve the winner in App Store Connect immediately, then run app-store/keyword-optimizer to lock the subtitle and keyword field.",
"next_step": "Reserve the name in App Store Connect → run keyword-optimizer for subtitle + 100-char keywords → feed the name into prd-generator"
}Brief: "A minimalist iOS app that tracks daily water intake with a single tap. For health-conscious people who find existing trackers cluttered. Personality: clean, calm, premium. Stays single-purpose."
Generate (sample of ~30):
Filter: Drop "Intake" (generic, taken), "Hydrate" (crowded, hard to own), "Aqo" (fails spell test).
Pair + score top survivors:
| Name | Pairing | Memorable | Avail. | ASO | Overall |
|---|---|---|---|---|---|
| Brim | Brim — Water Tracker | 8 | 7 | 7 | 7.6 |
| Sip | Sip — Daily Water | 9 | 5 | 7 | 7.2 |
| Droplet | Droplet — Hydration | 7 | 6 | 8 | 7.0 |
Validate (top 3): "Sip" — App Store name almost certainly taken (very common), sip.com taken. "Brim" — exact App Store name worth checking, brim.app likely available, no obvious TM conflict in Class 9. "Droplet" — used by DigitalOcean (TM risk in software).
Recommendation: "Go with Brim — Water Tracker. It's short (stands alone on the Home Screen), calm and ownable, almost certainly clears the App Store name, and brim.app is available. Avoid Droplet (DigitalOcean trademark in software). Reserve 'Brim' in App Store Connect now, then run keyword-optimizer to fill the subtitle and keyword field around 'water, hydration, drink, reminder.'"
product/idea-generator → pick an idea
↓
product/app-namer (THIS SKILL) → name it + reserve it
↓
app-store/keyword-optimizer → lock subtitle + 100-char keywords around the name
↓
product/prd-generator → [App Name] is now filled in
↓
generators/app-icon-generator → icon that matches the name's personalityThe name you pick here is the highest-weighted ASO field and a permanent brand decision — it flows into the keyword strategy, the PRD, the icon, and the bundle ID. Get it right before you build.
idea-generator firstkeyword-optimizer for ASOkeyword-optimizer/existing-app-strategy.md before changing a name that's workingAt the end of this skill you should have:
Name — Subtitle with char counts ≤ 30next_step pointing to keyword-optimizer and prd-generatorSave results to app-name-shortlist.json (project root), using the Output Structure above.
Generate wide, filter hard, validate before you fall in love. The best app name is short, ownable, spellable, available today, and lets the subtitle do the keyword work.
© rshankras, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files in skills/product/app-namer of rshankras/claude-code-apple-skills.
Open the folder on GitHubat commit 9ffb831
App Namer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| App Namer this skillrshankras/claude-code-apple-skills | 785 | — | ~3.4k | Automated safety check: Pass | MIT | |
| Asc Ppp Pricingrorkai/app-store-connect-cli-skills | 1.1k | 3 repos | ~4.2k | Automated safety check: Pass | MIT | |
| Asc Subscription Localizationrorkai/app-store-connect-cli-skills | 1.1k | 2 repos | ~2.7k | Automated safety check: Pass | MIT | |
| Sync Asc Skillsrorkai/App-Store-Connect-CLI | 7.7k | — | ~782 | Automated safety check: Pass | MIT | |
| Asc Wall Submitrorkai/app-store-connect-cli-skills | 1.1k | 3 repos | ~422 | Automated safety check: Pass | MIT | |
| Asc Metricsappeeky/aso-skills | 2.2k | — | ~1.3k | Automated safety check: Pass | MIT |
rorkai/app-store-connect-cli-skills
Set territory-specific pricing for subscriptions and in-app purchases using current asc setup, pricing summary, price import, and price schedule commands.
rorkai/app-store-connect-cli-skills
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources.
rorkai/App-Store-Connect-CLI
Check rorkai/app-store-connect-cli-skills against the current ASC CLI surface and correct proven drift when authorized.
rorkai/app-store-connect-cli-skills
Submit or update a Wall of Apps entry in the App-Store-Connect-CLI repository using asc apps wall submit.
appeeky/aso-skills
When the user wants to analyze their own app's actual performance data from App Store Connect — real downloads, revenue, IAP, subscriptions, trials, or country breakdowns synced via Appeeky Connect.
CamilleScholtz/swmpc
Guidance for using asc cli in this repo (flags, output formats, pagination, auth, and discovery).
rshankras/claude-code-apple-skills
Generate accessibility infrastructure for VoiceOver, Dynamic Type, and accessibility features.
rshankras/claude-code-apple-skills
SwiftUI animation patterns including springs, transitions, PhaseAnimator, KeyframeAnimator, SF Symbol effects, scroll-driven effects, mesh gradients, text renderers, and shader effects.
rshankras/claude-code-apple-skills
Generate compelling App Store descriptions that convert browsers into users.
rshankras/claude-code-apple-skills
Generates an app icon for macOS or iOS — a fast CoreGraphics placeholder and/or flat layered source art to finish in Icon Composer (the Liquid Glass / iOS 26+ standard).
rshankras/claude-code-apple-skills
Revenue beyond the single-app price tag — own-app bundles, Family Sharing as a conversion lever, cross-developer bundles & suites, and institutional licensing via Group Purchases / Apple School &…
rshankras/claude-code-apple-skills
Generate CI/CD configuration for automated builds, tests, and distribution of iOS/macOS apps.
Works with
Categories
Turn an app idea into validated, App-Store-ready name candidates. App Namer is an agent skill from rshankras/claude-code-apple-skills. Turn an app idea into validated, App-Store-ready name candidates.
App Namer fits situations like: the user says name my app; what should I call it; help me name this app; is this name available.
Run `npx skills add rshankras/claude-code-apple-skills --skill app-namer -a claude-code`. Or copy the skill folder (skills/product/app-namer in rshankras/claude-code-apple-skills) into .claude/skills/app-namer in your project. Claude Code loads it when a task matches its description.
Run `npx skills add rshankras/claude-code-apple-skills --skill app-namer -a codex`. Or copy the skill folder (skills/product/app-namer in rshankras/claude-code-apple-skills) into .agents/skills/app-namer in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rshankras/claude-code-apple-skills --skill app-namer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/app-namer, .gemini/skills/app-namer, .github/skills/app-namer and .opencode/skills/app-namer in your project.
SKILL.md names no scripts, command-line tools or credentials: App Namer is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, WebSearch, WebFetch, AskUserQuestion.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
App Namer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.4k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with App Namer: Asc Ppp Pricing (rorkai/app-store-connect-cli-skills, 1.1k stars), Asc Subscription Localization (rorkai/app-store-connect-cli-skills, 1.1k stars), Sync Asc Skills (rorkai/App-Store-Connect-CLI, 7.7k stars) and Asc Wall Submit (rorkai/app-store-connect-cli-skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
rshankras (a GitHub user) maintains it in rshankras/claude-code-apple-skills, which has 785 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on July 24, 2026.
Source: rshankras/claude-code-apple-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.