{
  "markdown": "# ASO.dev Agent Skills\n\nAgent Skills for App Store Optimization workflows at ASO.dev, compatible with Codex and other tools that consume `SKILL.md` folders.\n\nEach skill is a folder with a single `SKILL.md` file:\n\n```text\nskills/<skill-name>/SKILL.md\n```\n\nSkill names match folder names and use lowercase letters, digits, and hyphens.\n\nThe root `marketplace.json` describes the full ASO.dev skill pack for tools that consume plugin/marketplace manifests. `.claude-plugin/marketplace.json` and `.claude-plugin/plugin.json` make the same pack installable as a Claude Code plugin marketplace. Claude Code discovers skill folders automatically from the default `skills/` directory.\n\n## Local Companion\n\nThe current live integration is the ASO.dev local AI Companion MCP:\n\n- `http://localhost:42111`\n- `http://127.0.0.1:42111`\n\nThe local MCP/Companion surface is not the ASO.dev product API. Do not assume the future API repeats MCP tool names, endpoints, payloads, or auth.\n\nTechnical references for tool surfaces live in `tools/`:\n\n- `tools/aso-dev-local-mcp.md` - current localhost MCP tools, endpoints, payloads, and safety rules.\n- `tools/asodev-public-api.md` - ASO.dev Developer API and Partners API OpenAPI sources, auth/header notes, and MCP separation rules.\n- `tools/asodev-product-surface-map.md` - public ASO.dev product surfaces mapped to skills.\n\n## Install\n\nThese skills use the common `SKILL.md` Agent Skills format. Install by copying the folders from `skills/*` into the target agent's skills directory.\n\n`tools/` contains repository-level technical references, not Agent Skill folders. If an agent is installed outside this repository and needs detailed MCP endpoint/payload docs or public API OpenAPI notes, keep this repository in the workspace or copy `tools/` into the project root as reference documentation.\n\n### Codex\n\nUser/global install:\n\n```bash\nmkdir -p \"${CODEX_HOME:-$HOME/.codex}/skills\"\ncp -R skills/* \"${CODEX_HOME:-$HOME/.codex}/skills/\"\n```\n\nRestart Codex after copying if the session is already running.\n\n### Claude Code\n\nRecommended GitHub marketplace install after this repository is published:\n\n```text\nclaude\n> /plugin marketplace add asodevapp/skills\n> /plugin install asodev-skills@asodev-skills\n```\n\nFor local development, from this repository:\n\n```text\nclaude\n> /plugin marketplace add .\n> /plugin install asodev-skills@asodev-skills\n```\n\nClaude Code uses slash commands inside a `claude` session for marketplace installs; `claude install-skill github.com/...` is not the documented install command.\n\nFor official Anthropic marketplace submission, use the Claude.ai or Console submission forms and the prepared fields in [`OFFICIAL_MARKETPLACE_SUBMISSION.md`](OFFICIAL_MARKETPLACE_SUBMISSION.md).\n\nPersonal skills, available across projects:\n\n```bash\nmkdir -p \"$HOME/.claude/skills\"\ncp -R skills/* \"$HOME/.claude/skills/\"\n```\n\nProject skills, checked into a repository:\n\n```bash\nmkdir -p .claude/skills\ncp -R skills/* .claude/skills/\n```\n\nRestart Claude Code, then ask \"What Skills are available?\" or invoke a skill with `/skill-name`.\n\nFor Claude.ai, upload skills through the Claude Skills UI instead of copying to a local directory.\n\n### Cursor\n\nProject skills:\n\n```bash\nmkdir -p .cursor/skills\ncp -R skills/* .cursor/skills/\n```\n\nUser/global skills, when supported by your Cursor build:\n\n```bash\nmkdir -p \"$HOME/.cursor/skills\"\ncp -R skills/* \"$HOME/.cursor/skills/\"\n```\n\nReload the Cursor window or restart Cursor. If a global install is not discovered, use the project-level `.cursor/skills/` path.\n\n### Antigravity\n\nCurrent community convention for global Antigravity skills:\n\n```bash\nmkdir -p \"$HOME/.gemini/antigravity/skills\"\ncp -R skills/* \"$HOME/.gemini/antigravity/skills/\"\n```\n\nThen restart Antigravity or reload the workspace. If your Antigravity build exposes a different skills directory in settings, use that directory instead.\n\n### Verify Install\n\nAfter installing in any tool, ask the agent:\n\n```text\nWhat ASO.dev skills are available?\n```\n\nThen try task-specific prompts such as:\n\n- \"Optimize current App Store metadata in the active ASO.dev editor\"\n- \"Draft an In-App Event for the next seasonal campaign\"\n- \"Prepare an App Store featuring nomination\"\n- \"Reply to unanswered low-star reviews\"\n\nMore scenario prompts are in [`EXAMPLES.md`](EXAMPLES.md).\n\n## Validate\n\nRun:\n\n```bash\n./validate-skills.sh\n```\n\nFor the Claude Code plugin marketplace manifest, you can also run:\n\n```bash\nclaude plugin validate .\n```\n\nThe validator checks:\n\n- every skill folder has `SKILL.md`\n- YAML frontmatter parses correctly\n- `name` and `description` exist\n- `name` matches the folder name\n- skill names use Codex-friendly lowercase hyphen format\n- `marketplace.json` parses and points to a plugin source\n- `.claude-plugin/marketplace.json` and `.claude-plugin/plugin.json` parse using Claude Code's default `skills/` discovery\n- repository tool references in `tools/` exist and are non-empty\n\nExpected output:\n\n```text\nAll skills look valid.\n```\n\n## Skills\n\n### Tools and Integrations\n\n- `app-store-connect-mcp` - local MCP and localhost Companion workflow; detailed contract is in `tools/aso-dev-local-mcp.md`\n- `asodev-public-api` - Developer API and Partners API integration workflow; live OpenAPI sources and current sparse-contract notes are in `tools/asodev-public-api.md`\n\n### Core Workflow\n\n- `aso-audit` - full ASO health check across metadata, keywords, creative, reviews, monetization, competitors, and analytics\n- `current-metadata-fetch` - read current Apple/Google editor metadata\n- `metadata-validation` - validate drafts before filling\n- `app-context` - read or write per-app project context\n- `app-analytics` - interpret ASO.dev Measurements and App Store metric changes\n\n### Metadata and Localization\n\n- `android-aso` - Google Play Store metadata, creative, ratings, and experiments\n- `metadata-editor` - rewrite and bulk-fill App Store / Google Play metadata\n- `figma-json-localization` - localize Figma/ASO.dev screenshot JSON to all App Store Connect locales while preserving all system/template tags\n- `keyword-research` - analyze keyword/search query CSVs and prioritize ASO keywords using ASO.dev keyword, Spy, SAP, and Search Term Rank data\n- `keyword-coverage` - plan CSV-derived or researched keyword distribution across fields/locales\n- `localization-cross-localization` - localize metadata and cross-localization strategy\n- `whats-new-release-notes` - write release notes / What's New\n- `seasonal-calendar` - seasonal ASO, holiday campaigns, keyword swaps, and timing/revert plans\n\n### Growth\n\n- `competitor-analysis` - analyze competitors, App Info, App Clash, Spy, changelog, reviews, and creative gaps\n- `apple-search-ads-intelligence` - analyze Apple Ads intelligence, paid keyword demand, competitor ads, and CPP alignment\n- `featuring-nomination` - App Store featuring nomination strategy and drafts\n- `in-app-events` - In-App Event strategy, metadata, media direction, and localizations\n- `cpp-ppo-pages` - CPP/PPO, A/B test plans, variants, and conversion test interpretation\n- `screenshot-brief` - screenshot sequence and creative copy\n\n### Reviews\n\n- `reviews-ratings` - review health, CSV review analysis, sentiment, feature requests, replies, complaint drafts, and rating strategy\n\n### Monetization\n\n- `in-app-purchases` - IAP metadata/localization drafts; MCP fill when available\n- `in-app-subscriptions` - subscription metadata/localization drafts; MCP fill when available\n- `monetization-strategy` - monetization model, paywall, trial, and revenue strategy\n- `pricing-availability` - pricing, territory plans, and ASO.dev CSV price templates; MCP fill when available\n- `subscription-lifecycle` - trial conversion, renewal, churn, billing recovery, and win-back\n\n## Current MCP Surfaces\n\nDetailed endpoints and payload examples are in `tools/aso-dev-local-mcp.md`.\n\nThe current local MCP supports these draft/read workflows:\n\n| Domain | Read | Fill/update draft |\n|---|---|---|\n| Apple metadata | `get_editor_data` | `bulk_fill` |\n| Google metadata | `get_google_editor_data` | `bulk_fill_google` |\n| Featuring nomination | `get_nomination_data` | `fill_nomination` |\n| In-App Event | `get_app_event_data` | `fill_app_event` |\n| Single review | `get_review_data` | `fill_review` |\n| Review list | `get_reviews_data` | `fill_reviews` |\n| Project context | `get_project_context` | `save_project_context` |\n| Validation | `validate_ai_companion_data` | none |\n\nPlanned MCP surfaces include IAP localization, subscription localization, pricing/availability, and later CPP/PPO.\n\n## Public API Surfaces\n\nDetailed OpenAPI source links and separation rules are in `tools/asodev-public-api.md`.\n\nCurrent public API docs:\n\n- Developer API docs UI: `https://developer.aso.dev/docs/`\n- Developer API OpenAPI JSON: `https://developer.aso.dev/openapi/developer-v1.json`\n- Partners API docs UI: `https://partners.aso.dev/docs/`\n- Partners API OpenAPI JSON: `https://partners.aso.dev/openapi/partners-v1.json`\n\nThese public APIs are separate from the local MCP. The current contracts are intentionally sparse and should be re-checked live before implementing API behavior.\n\n## Operating Rule\n\nSkills follow this pattern:\n\n1. Read current state from local MCP when the surface exists.\n2. Draft only requested fields.\n3. Validate through `validate_ai_companion_data` when supported.\n4. Fill ASO.dev drafts only when the user explicitly asks.\n\n## License\n\nThis repository is licensed under the terms of `LICENSE`.\n",
  "bytes": 9486,
  "sha": "d8f8a4f8763bb5e0c6b5b658f90d6b20843940bb52d64eaa64bf81cafbaf6eaf",
  "repo_slug": "asodevapp/skills",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_asodevapp_skills_asodev_1ac35abb/readme"
}