[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75QRPSG5M0W6ZSEE6SWD48R":3,"skill-same:01M75QRPSG5M0W6ZSEE6SWD48R":126},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":13,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":41,"install":42,"resources":55},"01M75QRPSG5M0W6ZSEE6SWD48R","app-store-optimization",null,"App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A\u002FB test planning, launch checklists, and tracking ranking changes.","TehutiRaEl\u002FTHEHIVE","TehutiRaEl","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F267495122?v=4","01M75N1QQQHT359S3XMYK7NPCB","01M75N1QRAW5P8P43HEHWMXCTE",0,"MIT","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fmarketing-skill\u002Fskills\u002Fapp-store-optimization\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"app-store-optimization\"\ndescription: App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A\u002FB test planning, launch checklists, and tracking ranking changes.\ntriggers:\n  - ASO\n  - app store optimization\n  - app store ranking\n  - app keywords\n  - app metadata\n  - play store optimization\n  - app store listing\n  - improve app rankings\n  - app visibility\n  - app store SEO\n  - mobile app marketing\n  - app conversion rate\n---\n\n# App Store Optimization (ASO)\n\n---\n\n## Keyword Research Workflow\n\nDiscover and evaluate keywords that drive app store visibility.\n\n### Workflow: Conduct Keyword Research\n\n1. Define target audience and core app functions:\n   - Primary use case (what problem does the app solve)\n   - Target user demographics\n   - Competitive category\n2. Generate seed keywords from:\n   - App features and benefits\n   - User language (not developer terminology)\n   - App store autocomplete suggestions\n3. Expand keyword list using:\n   - Modifiers (free, best, simple)\n   - Actions (create, track, organize)\n   - Audiences (for students, for teams, for business)\n4. Evaluate each keyword:\n   - Search volume (estimated monthly searches)\n   - Competition (number and quality of ranking apps)\n   - Relevance (alignment with app function)\n5. Score and prioritize keywords:\n   - Primary: Title and keyword field (iOS)\n   - Secondary: Subtitle and short description\n   - Tertiary: Full description only\n6. Map keywords to metadata locations\n7. Document keyword strategy for tracking\n8. **Validation:** Keywords scored; placement mapped; no competitor brand names included; no plurals in iOS keyword field\n\n### Keyword Evaluation Criteria\n\n| Factor | Weight | High Score Indicators |\n|--------|--------|----------------------|\n| Relevance | 35% | Describes core app function |\n| Volume | 25% | 10,000+ monthly searches |\n| Competition | 25% | Top 10 apps have \u003C4.5 avg rating |\n| Conversion | 15% | Transactional intent (\"best X app\") |\n\n### Keyword Placement Priority\n\n| Location | Search Weight |\n|----------|---------------|\n| App Title | Highest |\n| Subtitle (iOS) | High |\n| Keyword Field (iOS) | High |\n| Short Description (Android) | High |\n| Full Description | Medium |\n\nSee: [references\u002Fkeyword-research-guide.md](references\u002Fkeyword-research-guide.md)\n\n---\n\n## Metadata Optimization Workflow\n\nOptimize app store listing elements for search ranking and conversion.\n\n### Workflow: Optimize App Metadata\n\n1. Audit current metadata against platform limits:\n   - Title character count and keyword presence\n   - Subtitle\u002Fshort description usage\n   - Keyword field efficiency (iOS)\n   - Description keyword density\n2. Optimize title following formula:\n   ```\n   [Brand Name] - [Primary Keyword] [Secondary Keyword]\n   ```\n3. Write subtitle (iOS) or short description (Android):\n   - Focus on primary benefit\n   - Include secondary keyword\n   - Use action verbs\n4. Optimize keyword field (iOS only):\n   - Remove duplicates from title\n   - Remove plurals (Apple indexes both forms)\n   - No spaces after commas\n   - Prioritize by score\n5. Rewrite full description:\n   - Hook paragraph with value proposition\n   - Feature bullets with keywords\n   - Social proof section\n   - Call to action\n6. Validate character counts for each field\n7. Calculate keyword density (target 2-3% primary)\n8. **Validation:** All fields within character limits; primary keyword in title; no keyword stuffing (>5%); natural language preserved\n\n### Platform Character Limits\n\n| Field | Apple App Store | Google Play Store |\n|-------|-----------------|-------------------|\n| Title | 30 characters | 50 characters |\n| Subtitle | 30 characters | N\u002FA |\n| Short Description | N\u002FA | 80 characters |\n| Keywords | 100 characters | N\u002FA |\n| Promotional Text | 170 characters | N\u002FA |\n| Full Description | 4,000 characters | 4,000 characters |\n| What's New | 4,000 characters | 500 characters |\n\n### Description Structure\n\n```\nPARAGRAPH 1: Hook (50-100 words)\n├── Address user pain point\n├── State main value proposition\n└── Include primary keyword\n\nPARAGRAPH 2-3: Features (100-150 words)\n├── Top 5 features with benefits\n├── Bullet points for scanability\n└── Secondary keywords naturally integrated\n\nPARAGRAPH 4: Social Proof (50-75 words)\n├── Download count or rating\n├── Press mentions or awards\n└── Summary of user testimonials\n\nPARAGRAPH 5: Call to Action (25-50 words)\n├── Clear next step\n└── Reassurance (free trial, no signup)\n```\n\nSee: [references\u002Fplatform-requirements.md](references\u002Fplatform-requirements.md)\n\n---\n\n## Competitor Analysis Workflow\n\nAnalyze top competitors to identify keyword gaps and positioning opportunities.\n\n### Workflow: Analyze Competitor ASO Strategy\n\n1. Identify top 10 competitors:\n   - Direct competitors (same core function)\n   - Indirect competitors (overlapping audience)\n   - Category leaders (top downloads)\n2. Extract competitor keywords from:\n   - App titles and subtitles\n   - First 100 words of descriptions\n   - Visible metadata patterns\n3. Build competitor keyword matrix:\n   - Map which keywords each competitor targets\n   - Calculate coverage percentage per keyword\n4. Identify keyword gaps:\n   - Keywords with \u003C40% competitor coverage\n   - High volume terms competitors miss\n   - Long-tail opportunities\n5. Analyze competitor visual assets:\n   - Icon design patterns\n   - Screenshot messaging and style\n   - Video presence and quality\n6. Compare ratings and review patterns:\n   - Average rating by competitor\n   - Common praise themes\n   - Common complaint themes\n7. Document positioning opportunities\n8. **Validation:** 10+ competitors analyzed; keyword matrix complete; gaps identified with volume estimates; visual audit documented\n\n### Competitor Analysis Matrix\n\n| Analysis Area | Data Points |\n|---------------|-------------|\n| Keywords | Title keywords, description frequency |\n| Metadata | Character utilization, keyword density |\n| Visuals | Icon style, screenshot count\u002Fstyle |\n| Ratings | Average rating, total count, velocity |\n| Reviews | Top praise, top complaints |\n\n### Gap Analysis Template\n\n| Opportunity Type | Example | Action |\n|------------------|---------|--------|\n| Keyword gap | \"habit tracker\" (40% coverage) | Add to keyword field |\n| Feature gap | Competitor lacks widget | Highlight in screenshots |\n| Visual gap | No videos in top 5 | Create app preview |\n| Messaging gap | None mention \"free\" | Test free positioning |\n\n---\n\n## App Launch Workflow\n\nExecute a structured launch for maximum initial visibility.\n\n### Workflow: Launch App to Stores\n\n1. Complete pre-launch preparation (4 weeks before):\n   - Finalize keywords and metadata\n   - Prepare all visual assets\n   - Set up analytics (Firebase, Mixpanel)\n   - Build press kit and media list\n2. Submit for review (2 weeks before):\n   - Complete all store requirements\n   - Verify compliance with guidelines\n   - Prepare launch communications\n3. Configure post-launch systems:\n   - Set up review monitoring\n   - Prepare response templates\n   - Configure rating prompt timing\n4. Execute launch day:\n   - Verify app is live in both stores\n   - Announce across all channels\n   - Begin review response cycle\n5. Monitor initial performance (days 1-7):\n   - Track download velocity hourly\n   - Monitor reviews and respond within 24 hours\n   - Document any issues for quick fixes\n6. Conduct 7-day retrospective:\n   - Compare performance to projections\n   - Identify quick optimization wins\n   - Plan first metadata update\n7. Schedule first update (2 weeks post-launch)\n8. **Validation:** App live in stores; analytics tracking; review responses within 24h; download velocity documented; first update scheduled\n\n### Pre-Launch Checklist\n\n| Category | Items |\n|----------|-------|\n| Metadata | Title, subtitle, description, keywords |\n| Visual Assets | Icon, screenshots (all sizes), video |\n| Compliance | Age rating, privacy policy, content rights |\n| Technical | App binary, signing certificates |\n| Analytics | SDK integration, event tracking |\n| Marketing | Press kit, social content, email ready |\n\n### Launch Timing Considerations\n\n| Factor | Recommendation |\n|--------|----------------|\n| Day of week | Tuesday-Wednesday (avoid weekends) |\n| Time of day | Morning in target market timezone |\n| Seasonal | Align with relevant category seasons |\n| Competition | Avoid major competitor launch dates |\n\nSee: [references\u002Faso-best-practices.md](references\u002Faso-best-practices.md)\n\n---\n\n## A\u002FB Testing Workflow\n\nTest metadata and visual elements to improve conversion rates.\n\n### Workflow: Run A\u002FB Test\n\n1. Select test element (prioritize by impact):\n   - Icon (highest impact)\n   - Screenshot 1 (high impact)\n   - Title (high impact)\n   - Short description (medium impact)\n2. Form hypothesis:\n   ```\n   If we [change], then [metric] will [improve\u002Fincrease] by [amount]\n   because [rationale].\n   ```\n3. Create variants:\n   - Control: Current version\n   - Treatment: Single variable change\n4. Calculate required sample size:\n   - Baseline conversion rate\n   - Minimum detectable effect (usually 5%)\n   - Statistical significance (95%)\n5. Launch test:\n   - Apple: Use Product Page Optimization\n   - Android: Use Store Listing Experiments\n6. Run test for minimum duration:\n   - At least 7 days\n   - Until statistical significance reached\n7. Analyze results:\n   - Compare conversion rates\n   - Check statistical significance\n   - Document learnings\n8. **Validation:** Single variable tested; sample size sufficient; significance reached (95%); results documented; winner implemented\n\n### A\u002FB Test Prioritization\n\n| Element | Conversion Impact | Test Complexity |\n|---------|-------------------|-----------------|\n| App Icon | 10-25% lift possible | Medium (design needed) |\n| Screenshot 1 | 15-35% lift possible | Medium |\n| Title | 5-15% lift possible | Low |\n| Short Description | 5-10% lift possible | Low |\n| Video | 10-20% lift possible | High |\n\n### Sample Size Quick Reference\n\n| Baseline CVR | Impressions Needed (per variant) |\n|--------------|----------------------------------|\n| 1% | 31,000 |\n| 2% | 15,500 |\n| 5% | 6,200 |\n| 10% | 3,100 |\n\n### Test Documentation Template\n\n```\nTEST ID: ASO-2025-001\nELEMENT: App Icon\nHYPOTHESIS: A bolder color icon will increase conversion by 10%\nSTART DATE: [Date]\nEND DATE: [Date]\n\nRESULTS:\n├── Control CVR: 4.2%\n├── Treatment CVR: 4.8%\n├── Lift: +14.3%\n├── Significance: 97%\n└── Decision: Implement treatment\n\nLEARNINGS:\n- Bold colors outperform muted tones in this category\n- Apply to screenshot backgrounds for next test\n```\n\n---\n\n## Before\u002FAfter Examples\n\n### Title Optimization\n\n**Productivity App:**\n\n| Version | Title | Analysis |\n|---------|-------|----------|\n| Before | \"MyTasks\" | No keywords, brand only (8 chars) |\n| After | \"MyTasks - Todo List & Planner\" | Primary + secondary keywords (29 chars) |\n\n**Fitness App:**\n\n| Version | Title | Analysis |\n|---------|-------|----------|\n| Before | \"FitTrack Pro\" | Generic modifier (12 chars) |\n| After | \"FitTrack: Workout Log & Gym\" | Category keywords (27 chars) |\n\n### Subtitle Optimization (iOS)\n\n| Version | Subtitle | Analysis |\n|---------|----------|----------|\n| Before | \"Get Things Done\" | Vague, no keywords |\n| After | \"Daily Task Manager & Planner\" | Two keywords, benefit clear |\n\n### Keyword Field Optimization (iOS)\n\n**Before (Inefficient - 89 chars, 8 keywords):**\n```\ntask manager, todo list, productivity app, daily planner, reminder app\n```\n\n**After (Optimized - 97 chars, 14 keywords):**\n```\ntask,todo,checklist,reminder,organize,daily,planner,schedule,deadline,goals,habit,widget,sync,team\n```\n\n**Improvements:**\n- Removed spaces after commas (+8 chars)\n- Removed duplicates (task manager → task)\n- Removed plurals (reminders → reminder)\n- Removed words in title\n- Added more relevant keywords\n\n### Description Opening\n\n**Before:**\n```\nMyTasks is a comprehensive task management solution designed\nto help busy professionals organize their daily activities\nand boost productivity.\n```\n\n**After:**\n```\nForget missed deadlines. MyTasks keeps every task, reminder,\nand project in one place—so you focus on doing, not remembering.\nTrusted by 500,000+ professionals.\n```\n\n**Improvements:**\n- Leads with user pain point\n- Specific benefit (not generic \"boost productivity\")\n- Social proof included\n- Keywords natural, not stuffed\n\n### Screenshot Caption Evolution\n\n| Version | Caption | Issue |\n|---------|---------|-------|\n| Before | \"Task List Feature\" | Feature-focused, passive |\n| Better | \"Create Task Lists\" | Action verb, but still feature |\n| Best | \"Never Miss a Deadline\" | Benefit-focused, emotional |\n\n---\n\n## Tools and References\n\n### Scripts\n\n| Script | Purpose | Usage |\n|--------|---------|-------|\n| [keyword_analyzer.py](scripts\u002Fkeyword_analyzer.py) | Analyze keywords for volume and competition | `python keyword_analyzer.py --keywords \"todo,task,planner\"` |\n| [metadata_optimizer.py](scripts\u002Fmetadata_optimizer.py) | Validate metadata character limits and density | `python metadata_optimizer.py --platform ios --title \"App Title\"` |\n| [competitor_analyzer.py](scripts\u002Fcompetitor_analyzer.py) | Extract and compare competitor keywords | `python competitor_analyzer.py --competitors \"App1,App2,App3\"` |\n| [aso_scorer.py](scripts\u002Faso_scorer.py) | Calculate overall ASO health score | `python aso_scorer.py --app-id com.example.app` |\n| [ab_test_planner.py](scripts\u002Fab_test_planner.py) | Plan tests and calculate sample sizes | `python ab_test_planner.py --cvr 0.05 --lift 0.10` |\n| [review_analyzer.py](scripts\u002Freview_analyzer.py) | Analyze review sentiment and themes | `python review_analyzer.py --app-id com.example.app` |\n| [launch_checklist.py](scripts\u002Flaunch_checklist.py) | Generate platform-specific launch checklists | `python launch_checklist.py --platform ios` |\n| [localization_helper.py](scripts\u002Flocalization_helper.py) | Manage multi-language metadata | `python localization_helper.py --locales \"en,es,de,ja\"` |\n\n### References\n\n| Document | Content |\n|----------|---------|\n| [platform-requirements.md](references\u002Fplatform-requirements.md) | iOS and Android metadata specs, visual asset requirements |\n| [aso-best-practices.md](references\u002Faso-best-practices.md) | Optimization strategies, rating management, launch tactics |\n| [keyword-research-guide.md](references\u002Fkeyword-research-guide.md) | Research methodology, evaluation framework, tracking |\n\n### Assets\n\n| Template | Purpose |\n|----------|---------|\n| [aso-audit-template.md](assets\u002Faso-audit-template.md) | Structured audit checklist for app store listings |\n\n---\n\n## Platform Notes\n\n| Platform \u002F Constraint | Behavior \u002F Impact |\n|-----------------------|-------------------|\n| iOS keyword changes | Require app submission |\n| iOS promotional text | Editable without an app update |\n| Android metadata changes | Index in 1-2 hours |\n| Android keyword field | None — use description instead |\n| Keyword volume data | Estimates only; no official source |\n| Competitor data | Public listings only |\n\n**When not to use this skill:** web apps (use web SEO), enterprise\u002Finternal apps, TestFlight-only betas, or paid advertising strategy.\n\n---\n\n## Related Skills\n\n| Skill | Integration Point |\n|-------|-------------------|\n| [content-creator](..\u002Fcontent-creator\u002F) | App description copywriting |\n| [marketing-demand-acquisition](..\u002Fmarketing-demand-acquisition\u002F) | Launch promotion campaigns |\n| [marketing-strategy-pmm](..\u002Fmarketing-strategy-pmm\u002F) | Go-to-market planning |\n\n## Proactive Triggers\n\n- **No keyword optimization in title** → App title is the #1 ranking factor. Include top keyword.\n- **Screenshots don't show value** → Screenshots should tell a story, not show UI.\n- **No ratings strategy** → Below 4.0 stars kills conversion. Implement in-app rating prompts.\n- **Description keyword-stuffed** → Natural language with keywords beats keyword stuffing.\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---------------------|------------|\n| \"ASO audit\" | Full app store listing audit with prioritized fixes |\n| \"Keyword research\" | Keyword list with search volume and difficulty scores |\n| \"Optimize my listing\" | Rewritten title, subtitle, description, keyword field |\n\n## Communication\n\nAll output passes quality verification:\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Output format: Bottom Line → What (with confidence) → Why → How to Act\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n","# App Store Optimization (ASO)\n\n---\n\n## Keyword Research Workflow\n\nDiscover and evaluate keywords that drive app store visibility.\n\n### Workflow: Conduct Keyword Research\n\n1. Define target audience and core app functions:\n   - Primary use case (what problem does the app solve)\n   - Target user demographics\n   - Competitive category\n2. Generate seed keywords from:\n   - App features and benefits\n   - User language (not developer terminology)\n   - App store autocomplete suggestions\n3. Expand keyword list using:\n   - Modifiers (free, best, simple)\n   - Actions (create, track, organize)\n   - Audiences (for students, for teams, for business)\n4. Evaluate each keyword:\n   - Search volume (estimated monthly searches)\n   - Competition (number and quality of ranking apps)\n   - Relevance (alignment with app function)\n5. Score and prioritize keywords:\n   - Primary: Title and keyword field (iOS)\n   - Secondary: Subtitle and short description\n   - Tertiary: Full description only\n6. Map keywords to metadata locations\n7. Document keyword strategy for tracking\n8. **Validation:** Keywords scored; placement mapped; no competitor brand names included; no plurals in iOS keyword field\n\n### Keyword Evaluation Criteria\n\n| Factor | Weight | High Score Indicators |\n|--------|--------|----------------------|\n| Relevance | 35% | Describes core app function |\n| Volume | 25% | 10,000+ monthly searches |\n| Competition | 25% | Top 10 apps have \u003C4.5 avg rating |\n| Conversion | 15% | Transactional intent (\"best X app\") |\n\n### Keyword Placement Priority\n\n| Location | Search Weight |\n|----------|---------------|\n| App Title | Highest |\n| Subtitle (iOS) | High |\n| Keyword Field (iOS) | High |\n| Short Description (Android) | High |\n| Full Description | Medium |\n\nSee: [references\u002Fkeyword-research-guide.md](references\u002Fkeyword-research-guide.md)\n\n---\n\n## Metadata Optimization Workflow\n\nOptimize app store listing elements for search ranking and conversion.\n\n### Workflow: Optimize App Metadata\n\n1. Audit current metadata against platform limits:\n   - Title character count and keyword presence\n   - Subtitle\u002Fshort description usage\n   - Keyword field efficiency (iOS)\n   - Description keyword density\n2. Optimize title following formula:\n   ```\n   [Brand Name] - [Primary Keyword] [Secondary Keyword]\n   ```\n3. Write subtitle (iOS) or short description (Android):\n   - Focus on primary benefit\n   - Include secondary keyword\n   - Use action verbs\n4. Optimize keyword field (iOS only):\n   - Remove duplicates from title\n   - Remove plurals (Apple indexes both forms)\n   - No spaces after commas\n   - Prioritize by score\n5. Rewrite full description:\n   - Hook paragraph with value proposition\n   - Feature bullets with keywords\n   - Social proof section\n   - Call to action\n6. Validate character counts for each field\n7. Calculate keyword density (target 2-3% primary)\n8. **Validation:** All fields within character limits; primary keyword in title; no keyword stuffing (>5%); natural language preserved\n\n### Platform Character Limits\n\n| Field | Apple App Store | Google Play Store |\n|-------|-----------------|-------------------|\n| Title | 30 characters | 50 characters |\n| Subtitle | 30 characters | N\u002FA |\n| Short Description | N\u002FA | 80 characters |\n| Keywords | 100 characters | N\u002FA |\n| Promotional Text | 170 characters | N\u002FA |\n| Full Description | 4,000 characters | 4,000 characters |\n| What's New | 4,000 characters | 500 characters |\n\n### Description Structure\n\n```\nPARAGRAPH 1: Hook (50-100 words)\n├── Address user pain point\n├── State main value proposition\n└── Include primary keyword\n\nPARAGRAPH 2-3: Features (100-150 words)\n├── Top 5 features with benefits\n├── Bullet points for scanability\n└── Secondary keywords naturally integrated\n\nPARAGRAPH 4: Social Proof (50-75 words)\n├── Download count or rating\n├── Press mentions or awards\n└── Summary of user testimonials\n\nPARAGRAPH 5: Call to Action (25-50 words)\n├── Clear next step\n└── Reassurance (free trial, no signup)\n```\n\nSee: [references\u002Fplatform-requirements.md](references\u002Fplatform-requirements.md)\n\n---\n\n## Competitor Analysis Workflow\n\nAnalyze top competitors to identify keyword gaps and positioning opportunities.\n\n### Workflow: Analyze Competitor ASO Strategy\n\n1. Identify top 10 competitors:\n   - Direct competitors (same core function)\n   - Indirect competitors (overlapping audience)\n   - Category leaders (top downloads)\n2. Extract competitor keywords from:\n   - App titles and subtitles\n   - First 100 words of descriptions\n   - Visible metadata patterns\n3. Build competitor keyword matrix:\n   - Map which keywords each competitor targets\n   - Calculate coverage percentage per keyword\n4. Identify keyword gaps:\n   - Keywords with \u003C40% competitor coverage\n   - High volume terms competitors miss\n   - Long-tail opportunities\n5. Analyze competitor visual assets:\n   - Icon design patterns\n   - Screenshot messaging and style\n   - Video presence and quality\n6. Compare ratings and review patterns:\n   - Average rating by competitor\n   - Common praise themes\n   - Common complaint themes\n7. Document positioning opportunities\n8. **Validation:** 10+ competitors analyzed; keyword matrix complete; gaps identified with volume estimates; visual audit documented\n\n### Competitor Analysis Matrix\n\n| Analysis Area | Data Points |\n|---------------|-------------|\n| Keywords | Title keywords, description frequency |\n| Metadata | Character utilization, keyword density |\n| Visuals | Icon style, screenshot count\u002Fstyle |\n| Ratings | Average rating, total count, velocity |\n| Reviews | Top praise, top complaints |\n\n### Gap Analysis Template\n\n| Opportunity Type | Example | Action |\n|------------------|---------|--------|\n| Keyword gap | \"habit tracker\" (40% coverage) | Add to keyword field |\n| Feature gap | Competitor lacks widget | Highlight in screenshots |\n| Visual gap | No videos in top 5 | Create app preview |\n| Messaging gap | None mention \"free\" | Test free positioning |\n\n---\n\n## App Launch Workflow\n\nExecute a structured launch for maximum initial visibility.\n\n### Workflow: Launch App to Stores\n\n1. Complete pre-launch preparation (4 weeks before):\n   - Finalize keywords and metadata\n   - Prepare all visual assets\n   - Set up analytics (Firebase, Mixpanel)\n   - Build press kit and media list\n2. Submit for review (2 weeks before):\n   - Complete all store requirements\n   - Verify compliance with guidelines\n   - Prepare launch communications\n3. Configure post-launch systems:\n   - Set up review monitoring\n   - Prepare response templates\n   - Configure rating prompt timing\n4. Execute launch day:\n   - Verify app is live in both stores\n   - Announce across all channels\n   - Begin review response cycle\n5. Monitor initial performance (days 1-7):\n   - Track download velocity hourly\n   - Monitor reviews and respond within 24 hours\n   - Document any issues for quick fixes\n6. Conduct 7-day retrospective:\n   - Compare performance to projections\n   - Identify quick optimization wins\n   - Plan first metadata update\n7. Schedule first update (2 weeks post-launch)\n8. **Validation:** App live in stores; analytics tracking; review responses within 24h; download velocity documented; first update scheduled\n\n### Pre-Launch Checklist\n\n| Category | Items |\n|----------|-------|\n| Metadata | Title, subtitle, description, keywords |\n| Visual Assets | Icon, screenshots (all sizes), video |\n| Compliance | Age rating, privacy policy, content rights |\n| Technical | App binary, signing certificates |\n| Analytics | SDK integration, event tracking |\n| Marketing | Press kit, social content, email ready |\n\n### Launch Timing Considerations\n\n| Factor | Recommendation |\n|--------|----------------|\n| Day of week | Tuesday-Wednesday (avoid weekends) |\n| Time of day | Morning in target market timezone |\n| Seasonal | Align with relevant category seasons |\n| Competition | Avoid major competitor launch dates |\n\nSee: [references\u002Faso-best-practices.md](references\u002Faso-best-practices.md)\n\n---\n\n## A\u002FB Testing Workflow\n\nTest metadata and visual elements to improve conversion rates.\n\n### Workflow: Run A\u002FB Test\n\n1. Select test element (prioritize by impact):\n   - Icon (highest impact)\n   - Screenshot 1 (high impact)\n   - Title (high impact)\n   - Short description (medium impact)\n2. Form hypothesis:\n   ```\n   If we [change], then [metric] will [improve\u002Fincrease] by [amount]\n   because [rationale].\n   ```\n3. Create variants:\n   - Control: Current version\n   - Treatment: Single variable change\n4. Calculate required sample size:\n   - Baseline conversion rate\n   - Minimum detectable effect (usually 5%)\n   - Statistical significance (95%)\n5. Launch test:\n   - Apple: Use Product Page Optimization\n   - Android: Use Store Listing Experiments\n6. Run test for minimum duration:\n   - At least 7 days\n   - Until statistical significance reached\n7. Analyze results:\n   - Compare conversion rates\n   - Check statistical significance\n   - Document learnings\n8. **Validation:** Single variable tested; sample size sufficient; significance reached (95%); results documented; winner implemented\n\n### A\u002FB Test Prioritization\n\n| Element | Conversion Impact | Test Complexity |\n|---------|-------------------|-----------------|\n| App Icon | 10-25% lift possible | Medium (design needed) |\n| Screenshot 1 | 15-35% lift possible | Medium |\n| Title | 5-15% lift possible | Low |\n| Short Description | 5-10% lift possible | Low |\n| Video | 10-20% lift possible | High |\n\n### Sample Size Quick Reference\n\n| Baseline CVR | Impressions Needed (per variant) |\n|--------------|----------------------------------|\n| 1% | 31,000 |\n| 2% | 15,500 |\n| 5% | 6,200 |\n| 10% | 3,100 |\n\n### Test Documentation Template\n\n```\nTEST ID: ASO-2025-001\nELEMENT: App Icon\nHYPOTHESIS: A bolder color icon will increase conversion by 10%\nSTART DATE: [Date]\nEND DATE: [Date]\n\nRESULTS:\n├── Control CVR: 4.2%\n├── Treatment CVR: 4.8%\n├── Lift: +14.3%\n├── Significance: 97%\n└── Decision: Implement treatment\n\nLEARNINGS:\n- Bold colors outperform muted tones in this category\n- Apply to screenshot backgrounds for next test\n```\n\n---\n\n## Before\u002FAfter Examples\n\n### Title Optimization\n\n**Productivity App:**\n\n| Version | Title | Analysis |\n|---------|-------|----------|\n| Before | \"MyTasks\" | No keywords, brand only (8 chars) |\n| After | \"MyTasks - Todo List & Planner\" | Primary + secondary keywords (29 chars) |\n\n**Fitness App:**\n\n| Version | Title | Analysis |\n|---------|-------|----------|\n| Before | \"FitTrack Pro\" | Generic modifier (12 chars) |\n| After | \"FitTrack: Workout Log & Gym\" | Category keywords (27 chars) |\n\n### Subtitle Optimization (iOS)\n\n| Version | Subtitle | Analysis |\n|---------|----------|----------|\n| Before | \"Get Things Done\" | Vague, no keywords |\n| After | \"Daily Task Manager & Planner\" | Two keywords, benefit clear |\n\n### Keyword Field Optimization (iOS)\n\n**Before (Inefficient - 89 chars, 8 keywords):**\n```\ntask manager, todo list, productivity app, daily planner, reminder app\n```\n\n**After (Optimized - 97 chars, 14 keywords):**\n```\ntask,todo,checklist,reminder,organize,daily,planner,schedule,deadline,goals,habit,widget,sync,team\n```\n\n**Improvements:**\n- Removed spaces after commas (+8 chars)\n- Removed duplicates (task manager → task)\n- Removed plurals (reminders → reminder)\n- Removed words in title\n- Added more relevant keywords\n\n### Description Opening\n\n**Before:**\n```\nMyTasks is a comprehensive task management solution designed\nto help busy professionals organize their daily activities\nand boost productivity.\n```\n\n**After:**\n```\nForget missed deadlines. MyTasks keeps every task, reminder,\nand project in one place—so you focus on doing, not remembering.\nTrusted by 500,000+ professionals.\n```\n\n**Improvements:**\n- Leads with user pain point\n- Specific benefit (not generic \"boost productivity\")\n- Social proof included\n- Keywords natural, not stuffed\n\n### Screenshot Caption Evolution\n\n| Version | Caption | Issue |\n|---------|---------|-------|\n| Before | \"Task List Feature\" | Feature-focused, passive |\n| Better | \"Create Task Lists\" | Action verb, but still feature |\n| Best | \"Never Miss a Deadline\" | Benefit-focused, emotional |\n\n---\n\n## Tools and References\n\n### Scripts\n\n| Script | Purpose | Usage |\n|--------|---------|-------|\n| [keyword_analyzer.py](scripts\u002Fkeyword_analyzer.py) | Analyze keywords for volume and competition | `python keyword_analyzer.py --keywords \"todo,task,planner\"` |\n| [metadata_optimizer.py](scripts\u002Fmetadata_optimizer.py) | Validate metadata character limits and density | `python metadata_optimizer.py --platform ios --title \"App Title\"` |\n| [competitor_analyzer.py](scripts\u002Fcompetitor_analyzer.py) | Extract and compare competitor keywords | `python competitor_analyzer.py --competitors \"App1,App2,App3\"` |\n| [aso_scorer.py](scripts\u002Faso_scorer.py) | Calculate overall ASO health score | `python aso_scorer.py --app-id com.example.app` |\n| [ab_test_planner.py](scripts\u002Fab_test_planner.py) | Plan tests and calculate sample sizes | `python ab_test_planner.py --cvr 0.05 --lift 0.10` |\n| [review_analyzer.py](scripts\u002Freview_analyzer.py) | Analyze review sentiment and themes | `python review_analyzer.py --app-id com.example.app` |\n| [launch_checklist.py](scripts\u002Flaunch_checklist.py) | Generate platform-specific launch checklists | `python launch_checklist.py --platform ios` |\n| [localization_helper.py](scripts\u002Flocalization_helper.py) | Manage multi-language metadata | `python localization_helper.py --locales \"en,es,de,ja\"` |\n\n### References\n\n| Document | Content |\n|----------|---------|\n| [platform-requirements.md](references\u002Fplatform-requirements.md) | iOS and Android metadata specs, visual asset requirements |\n| [aso-best-practices.md](references\u002Faso-best-practices.md) | Optimization strategies, rating management, launch tactics |\n| [keyword-research-guide.md](references\u002Fkeyword-research-guide.md) | Research methodology, evaluation framework, tracking |\n\n### Assets\n\n| Template | Purpose |\n|----------|---------|\n| [aso-audit-template.md](assets\u002Faso-audit-template.md) | Structured audit checklist for app store listings |\n\n---\n\n## Platform Notes\n\n| Platform \u002F Constraint | Behavior \u002F Impact |\n|-----------------------|-------------------|\n| iOS keyword changes | Require app submission |\n| iOS promotional text | Editable without an app update |\n| Android metadata changes | Index in 1-2 hours |\n| Android keyword field | None — use description instead |\n| Keyword volume data | Estimates only; no official source |\n| Competitor data | Public listings only |\n\n**When not to use this skill:** web apps (use web SEO), enterprise\u002Finternal apps, TestFlight-only betas, or paid advertising strategy.\n\n---\n\n## Related Skills\n\n| Skill | Integration Point |\n|-------|-------------------|\n| [content-creator](..\u002Fcontent-creator\u002F) | App description copywriting |\n| [marketing-demand-acquisition](..\u002Fmarketing-demand-acquisition\u002F) | Launch promotion campaigns |\n| [marketing-strategy-pmm](..\u002Fmarketing-strategy-pmm\u002F) | Go-to-market planning |\n\n## Proactive Triggers\n\n- **No keyword optimization in title** → App title is the #1 ranking factor. Include top keyword.\n- **Screenshots don't show value** → Screenshots should tell a story, not show UI.\n- **No ratings strategy** → Below 4.0 stars kills conversion. Implement in-app rating prompts.\n- **Description keyword-stuffed** → Natural language with keywords beats keyword stuffing.\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---------------------|------------|\n| \"ASO audit\" | Full app store listing audit with prioritized fixes |\n| \"Keyword research\" | Keyword list with search volume and difficulty scores |\n| \"Optimize my listing\" | Rewritten title, subtitle, description, keyword field |\n\n## Communication\n\nAll output passes quality verification:\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Output format: Bottom Line → What (with confidence) → Why → How to Act\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n",{"name":5,"triggers":23,"description":7},[24,25,26,27,28,29,30,31,32,33,34,35],"ASO","app store optimization","app store ranking","app keywords","app metadata","play store optimization","app store listing","improve app rankings","app visibility","app store SEO","mobile app marketing","app conversion rate","main","b4ebd6d8c3b36347a5d435bcb343a5fc1c6f08d1","skills-library\u002Fmarketing-skill\u002Fskills\u002Fapp-store-optimization","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE","https:\u002F\u002Fgithub.com\u002FTehutiRaEl","2026-11-15 04:00:21",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add TehutiRaEl\u002FTHEHIVE --skill app-store-optimization",{"tool":48,"command":49},"bunx","bunx skills add TehutiRaEl\u002FTHEHIVE --skill app-store-optimization",{"tool":51,"command":52},"pnpm","pnpm dlx skills add TehutiRaEl\u002FTHEHIVE --skill app-store-optimization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fmarketing-skill\u002Fskills\u002Fapp-store-optimization\u002FSKILL.md",true,[56,62,68,72,76,80,84,88,92,98,102,106,110,114,118,122],{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"assets\u002Faso-audit-template.md","ASSET","资产文件",4871,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fmarketing-skill\u002Fskills\u002Fapp-store-optimization\u002Fassets\u002Faso-audit-template.md",{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"expected_output.json","REFERENCE","参考文档",5492,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fmarketing-skill\u002Fskills\u002Fapp-store-optimization\u002Fexpected_output.json",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"HOW_TO_USE.md",10252,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fmarketing-skill\u002Fskills\u002Fapp-store-optimization\u002FHOW_TO_USE.md",{"path":73,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":74,"sourceHtmlUrl":75},"README.md",14917,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fmarketing-skill\u002Fskills\u002Fapp-store-optimization\u002FREADME.md",{"path":77,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Faso-best-practices.md",12488,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fmarketing-skill\u002Fskills\u002Fapp-store-optimization\u002Freferences\u002Faso-best-practices.md",{"path":81,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fkeyword-research-guide.md",11906,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fmarketing-skill\u002Fskills\u002Fapp-store-optimization\u002Freferences\u002Fkeyword-research-guide.md",{"path":85,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fplatform-requirements.md",9575,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fmarketing-skill\u002Fskills\u002Fapp-store-optimization\u002Freferences\u002Fplatform-requirements.md",{"path":89,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":90,"sourceHtmlUrl":91},"sample_input.json",723,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fmarketing-skill\u002Fskills\u002Fapp-store-optimization\u002Fsample_input.json",{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Fab_test_planner.py","SCRIPT","脚本",22857,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fmarketing-skill\u002Fskills\u002Fapp-store-optimization\u002Fscripts\u002Fab_test_planner.py",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Faso_scorer.py",18966,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fmarketing-skill\u002Fskills\u002Fapp-store-optimization\u002Fscripts\u002Faso_scorer.py",{"path":103,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Fcompetitor_analyzer.py",21340,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fmarketing-skill\u002Fskills\u002Fapp-store-optimization\u002Fscripts\u002Fcompetitor_analyzer.py",{"path":107,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":108,"sourceHtmlUrl":109},"scripts\u002Fkeyword_analyzer.py",13108,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fmarketing-skill\u002Fskills\u002Fapp-store-optimization\u002Fscripts\u002Fkeyword_analyzer.py",{"path":111,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":112,"sourceHtmlUrl":113},"scripts\u002Flaunch_checklist.py",28949,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fmarketing-skill\u002Fskills\u002Fapp-store-optimization\u002Fscripts\u002Flaunch_checklist.py",{"path":115,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":116,"sourceHtmlUrl":117},"scripts\u002Flocalization_helper.py",22142,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fmarketing-skill\u002Fskills\u002Fapp-store-optimization\u002Fscripts\u002Flocalization_helper.py",{"path":119,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":120,"sourceHtmlUrl":121},"scripts\u002Fmetadata_optimizer.py",20824,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fmarketing-skill\u002Fskills\u002Fapp-store-optimization\u002Fscripts\u002Fmetadata_optimizer.py",{"path":123,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":124,"sourceHtmlUrl":125},"scripts\u002Freview_analyzer.py",25561,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fmarketing-skill\u002Fskills\u002Fapp-store-optimization\u002Fscripts\u002Freview_analyzer.py",[127,134,140,147,154,161],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":18},"01M76XP63XDM4PFPX8MMVYN9JX","preamble-gate","Use BEFORE doing any work in this repo — before the first file edit, commit, push, PR, branch operation, workflow dispatch, scheduled trigger or timer, agent\u002Fsubagent spawn, dependency install, or message sent to an outside service. Forces a plain-language preamble to the founder first: WHAT you are about to do, WHY, HOW, why it is NECESSARY, the PROJECTED IMPROVEMENT, and the COST and RISK — then, for consequential work (governance, security, money, CI\u002Ftriggers, rewriting history, multi-agent fan-out), waits for an explicit go-ahead. Read-only investigation (reading files, grep, git log\u002Fdiff, answering questions) is exempt. Applies to every AI that works in this repo, not just Claude. Founder rule, 2026-11-10, written after an unattended automation ran up cost and froze the hive. Not a substitute for wired-or-not (which governs how completion is CLAIMED); this governs what happens BEFORE work starts.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpreamble-gate\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":18},"01M75RAYXC1W361YR9NBXD59AM","visionary-recommender","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills\u002Fvisionary-recommender\u002FSKILL.md",[],[],{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":18},"01M75RAQN9Q450RD57J2S6FSR4","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":18},"01M75RAG1XMCJMF30HFV5S79AK","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":18},"01M75RA8RK2JVWB8MYGRB65V75","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":18},"01M75RA08RXYRFSTNC6EEEX4ZD","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[]]