[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FANSVEV75JCY9Z6VX074AW":3,"skill-same:01M7FANSVEV75JCY9Z6VX074AW":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7FANSVEV75JCY9Z6VX074AW","app-store-optimization",null,"Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns an impression into an install. Use this to audit or optimize an app listing, plan a launch listing, diagnose poor install conversion, or improve store search visibility.","siddu1004\u002FSFP","siddu1004","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260113491?v=4","01M7F8W1SAJAR49097VRTE1TW5","Siddhardh Vanguri","01M7F8W1SYGY7JE15AHAECCT9R",5,"MIT","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fapp-store-optimization\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: app-store-optimization\ndescription: Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns an impression into an install. Use this to audit or optimize an app listing, plan a launch listing, diagnose poor install conversion, or improve store search visibility.\n---\n\n# App store optimization\n\nTwo levers, and they are separate problems: being **found**, and being **installed** once found.\nDiagnose which is failing before changing anything.\n\n## Being found\n\nThe stores index different fields, so the same metadata does not work on both.\n\n- **App name \u002F title** — the single heaviest field. Brand plus the primary descriptive term. Do not\n  spend it on brand alone.\n- **Subtitle and keyword field** — no repetition across fields; duplicated terms are wasted\n  characters, not reinforcement.\n- **Long description** — indexed on one store, effectively not on the other. Write it for the store\n  that indexes it and for humans on the store that does not.\n- **Category** — pick where you can rank, not where you technically belong.\n\nTarget terms with real intent. Ranking first for a term nobody searches is a vanity result.\n\n## Being installed\n\nMost visitors decide from the first screenshot and the rating, without scrolling or reading.\n\n- **Screenshots** — the first two carry the decision. Lead with the outcome or the core screen, with\n  a caption stating the benefit. Never lead with an onboarding or login screen.\n- **Icon** — recognizable at actual size, distinct from category conventions. Test at real scale on\n  a device.\n- **Rating** — the strongest single conversion factor. Prompt for review after a success moment,\n  never on launch or mid-task.\n- **Video** — only if it demonstrates something a screenshot cannot. A weak one costs installs.\n\n## Reviews\n\nRespond to negative reviews specifically and without defensiveness, naming the fix and its version\nwhere there is one. Prospects read the responses as much as the complaints, and a pattern of real\nanswers converts.\n\nWatch review text for recurring themes — it is the cheapest continuous product research available.\n\n## Testing\n\nChange one element at a time and let it run a full weekly cycle; app traffic is strongly\nday-of-week seasonal. Attributing a lift to the wrong change is worse than not testing.\n\n## Sources\n\n`references\u002Fsources.md` in this skill lists the outside authorities that settle the questions\nhere — what each one is authoritative for, and what you may do with it. Check them before\nanswering on anything they cover, and cite what you used. Most are free to read and not free\nto reproduce; the use note on each is binding.\n\n## Tooling\n\nThe consoles are the source of truth: App Store Connect and Google Play Console, including their\nown experiment features — product page optimization and store listing experiments — which test on\nreal store traffic rather than a simulation.\n\nKeyword and competitor research: AppTweak, Sensor Tower, data.ai, AppFollow, and similar. Treat\ntheir volume estimates as directional; the stores do not publish the underlying numbers.\n\nReview management and reply workflows live in the consoles or in the same tools, and replying is\nthe part most teams skip.\n\n## Never\n\n- Chase a keyword the app does not deliver on. Installs from a mismatched query become one-star reviews and a worse ranking than you started with.\n- Change metadata, screenshots, and the icon in the same release. Nothing that moves afterward can be attributed.\n- Solicit ratings from a user mid-task. The prompt lands where frustration is highest and the score reflects that.\n- Ignore reviews on the version you just shipped. They are the fastest signal you will get that a release broke something.\n","# App store optimization\n\nTwo levers, and they are separate problems: being **found**, and being **installed** once found.\nDiagnose which is failing before changing anything.\n\n## Being found\n\nThe stores index different fields, so the same metadata does not work on both.\n\n- **App name \u002F title** — the single heaviest field. Brand plus the primary descriptive term. Do not\n  spend it on brand alone.\n- **Subtitle and keyword field** — no repetition across fields; duplicated terms are wasted\n  characters, not reinforcement.\n- **Long description** — indexed on one store, effectively not on the other. Write it for the store\n  that indexes it and for humans on the store that does not.\n- **Category** — pick where you can rank, not where you technically belong.\n\nTarget terms with real intent. Ranking first for a term nobody searches is a vanity result.\n\n## Being installed\n\nMost visitors decide from the first screenshot and the rating, without scrolling or reading.\n\n- **Screenshots** — the first two carry the decision. Lead with the outcome or the core screen, with\n  a caption stating the benefit. Never lead with an onboarding or login screen.\n- **Icon** — recognizable at actual size, distinct from category conventions. Test at real scale on\n  a device.\n- **Rating** — the strongest single conversion factor. Prompt for review after a success moment,\n  never on launch or mid-task.\n- **Video** — only if it demonstrates something a screenshot cannot. A weak one costs installs.\n\n## Reviews\n\nRespond to negative reviews specifically and without defensiveness, naming the fix and its version\nwhere there is one. Prospects read the responses as much as the complaints, and a pattern of real\nanswers converts.\n\nWatch review text for recurring themes — it is the cheapest continuous product research available.\n\n## Testing\n\nChange one element at a time and let it run a full weekly cycle; app traffic is strongly\nday-of-week seasonal. Attributing a lift to the wrong change is worse than not testing.\n\n## Sources\n\n`references\u002Fsources.md` in this skill lists the outside authorities that settle the questions\nhere — what each one is authoritative for, and what you may do with it. Check them before\nanswering on anything they cover, and cite what you used. Most are free to read and not free\nto reproduce; the use note on each is binding.\n\n## Tooling\n\nThe consoles are the source of truth: App Store Connect and Google Play Console, including their\nown experiment features — product page optimization and store listing experiments — which test on\nreal store traffic rather than a simulation.\n\nKeyword and competitor research: AppTweak, Sensor Tower, data.ai, AppFollow, and similar. Treat\ntheir volume estimates as directional; the stores do not publish the underlying numbers.\n\nReview management and reply workflows live in the consoles or in the same tools, and replying is\nthe part most teams skip.\n\n## Never\n\n- Chase a keyword the app does not deliver on. Installs from a mismatched query become one-star reviews and a worse ranking than you started with.\n- Change metadata, screenshots, and the icon in the same release. Nothing that moves afterward can be attributed.\n- Solicit ratings from a user mid-task. The prompt lands where frustration is highest and the score reflects that.\n- Ignore reviews on the version you just shipped. They are the fastest signal you will get that a release broke something.\n",{"name":5,"description":7},"main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fbusiness-ops\u002Fskills\u002Fapp-store-optimization",0,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fsfp-hive","https:\u002F\u002Fgithub.com\u002Fsiddu1004","I am a student at Amrita Vishwa Vidyapeetham pursuing my BTECH degree in Electronics and Electrical Engineering (2024-2028).","2026-11-09 16:04:40",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add siddu1004\u002FSFP --skill app-store-optimization",{"tool":39,"command":40},"bunx","bunx skills add siddu1004\u002FSFP --skill app-store-optimization",{"tool":42,"command":43},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill app-store-optimization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fapp-store-optimization\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fsources.md","REFERENCE","参考文档",1858,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fapp-store-optimization\u002Freferences\u002Fsources.md",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7FEEDADZBNBVY19H3XZKCBQ","scientific-schematics","Generates scientific diagram drafts using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.7 Flash for quality review. Refines when the review requests improvement, with at most two generations. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways, and complex scientific visualizations.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fscientific-schematics\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7FEE0JS04FE58MST48D0MMC","polyhaven-texture-apply","Apply realistic PBR textures from PolyHaven to any Blender object. Supports metals, wood, concrete, fabric, and more. Trigger when asked to texture an object, apply a material from PolyHaven, make something look like metal\u002Fwood\u002Fmarble, or change object surface.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-texture-apply\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7FEDJRWV194TY411WVRS84W","polyhaven-studio-setup","Set up a professional product photography studio in Blender using PolyHaven HDRIs and PBR ground materials. Trigger when asked to create a studio setup, add HDRI lighting, set up product photography, or create a showroom scene.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-studio-setup\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7FED5H2FGS50XGETMGSM0RV","polyhaven-scene-builder","Build complete product scenes using PolyHaven assets — HDRI environment, textured ground\u002Fpedestal, and optional props from the 3D model library. Trigger when asked to build a product scene, create a showcase setup, add a pedestal, or compose a product shot.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-scene-builder\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7FECSNZ2CJA7Z8TPE5R844R","polyhaven-material-swap","Cycle through multiple PolyHaven materials on a product and render each variant. Great for showing color\u002Ffinish options. Trigger when asked to show material variants, swap textures, create color options, show finish comparisons, or render product in different materials.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-material-swap\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7FECBPQ6YWH48PYAMS0C5CE","polyhaven-hdri-showcase","Render the same product across multiple HDRI environments and output a comparison grid. Trigger when asked to compare lighting setups, test different environments, show product in multiple settings, or create an HDRI comparison.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-hdri-showcase\u002FSKILL.md",[],[]]