[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CM6XBA55XY2M87WXSFZJM":3,"skill-same:01M75CM6XBA55XY2M87WXSFZJM":67},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M75CM6XBA55XY2M87WXSFZJM","ab-test-generator",null,"Generate A\u002FB test variants for affiliate content. Triggers on: \"create A\u002FB test\", \"test my headline\", \"optimize my CTA\", \"generate variants\", \"split test ideas\", \"improve click-through rate\", \"test my landing page copy\", \"headline alternatives\", \"CTA variations\", \"which version is better\", \"optimize conversions\", \"test my email subject line\", \"compare approaches\".","LongLeo287\u002FSEOSONA-OS","LongLeo287","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141803367?v=4","01M6JK75C62VCNZKR5BRZ386YV","LongLeo","01M75CK60XQGYJY3YDGGFJQDYT",2,"MIT","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Faffiliate-skills\u002Fskills\u002Fanalytics\u002Fab-test-generator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Faffiliate-skills\u002Fskills\u002Fanalytics\u002Fab-test-generator\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: ab-test-generator\ndescription: >\n  Generate A\u002FB test variants for affiliate content. Triggers on:\n  \"create A\u002FB test\", \"test my headline\", \"optimize my CTA\", \"generate variants\",\n  \"split test ideas\", \"improve click-through rate\", \"test my landing page copy\",\n  \"headline alternatives\", \"CTA variations\", \"which version is better\",\n  \"optimize conversions\", \"test my email subject line\", \"compare approaches\".\nlicense: MIT\nversion: \"1.0.0\"\ntags: [\"affiliate-marketing\", \"analytics\", \"optimization\", \"tracking\", \"ab-testing\", \"experiments\"]\ncompatibility: \"Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent\"\nmetadata:\n  author: affitor\n  version: \"1.0\"\n  stage: S6-Analytics\n---\n\n# A\u002FB Test Generator\n\nGenerate A\u002FB test variants for affiliate content — headlines, CTAs, landing page sections, email subject lines, and social post hooks. Each variant includes a hypothesis explaining why it might outperform the original. Output is a Markdown document with the original, variants, hypotheses, and a test plan.\n\n## Stage\n\nS6: Analytics — Small changes in headlines and CTAs can swing conversion rates by 20-50%. A\u002FB testing is how professional affiliates systematically find what converts best. This skill removes the guesswork by generating theory-driven variants using proven copywriting frameworks.\n\n## When to Use\n\n- User wants to improve conversion rates on existing content\n- User has a headline, CTA, or email subject line and wants alternatives\n- User says \"test my headline\", \"optimize my CTA\", \"A\u002FB test ideas\"\n- User has a landing page section that isn't converting\n- User wants to compare different messaging approaches\n- Chaining from S2-S5: take any content output and generate test variants\n\n## Input Schema\n\n```yaml\noriginal: string               # REQUIRED — the content to test (headline, CTA, paragraph,\n                               # email subject line, or full social post)\n\ncontent_type: string           # REQUIRED — \"headline\" | \"cta\" | \"landing_section\"\n                               # | \"email_subject\" | \"social_hook\"\n\ngoal: string                   # OPTIONAL — \"clicks\" | \"signups\" | \"purchases\"\n                               # Default: \"clicks\"\n\nnum_variants: number           # OPTIONAL — number of variants to generate (2-5)\n                               # Default: 3\n\naudience: string               # OPTIONAL — who sees this content\n                               # (e.g., \"SaaS founders\", \"content creators\")\n\nproduct: string                # OPTIONAL — product being promoted\n```\n\n**Chaining context**: If S2-S5 content exists in conversation, the user can reference it: \"test the headline from my blog post\" or \"generate CTA variants for my landing page.\"\n\n## Workflow\n\n### Step 1: Analyze Original Content\n\nBreak down the original into components:\n- **Emotional angle**: What emotion does it trigger? (curiosity, fear, desire, urgency)\n- **Specificity**: How specific vs vague?\n- **Structure**: Question, statement, command, statistic?\n- **Framework**: Which copywriting framework does it follow? (PAS, AIDA, 4U, BAB)\n\n### Step 2: Identify Testable Elements\n\nDetermine what to vary:\n- Emotional angle (switch from curiosity to urgency)\n- Specificity (add numbers, remove vagueness)\n- Structure (question vs statement)\n- Length (shorter vs longer)\n- Power words (swap key words for stronger alternatives)\n- Social proof (add or remove)\n\n### Step 3: Generate Variants\n\nCreate `num_variants` alternatives, each using a different approach:\n- **Variant A**: Different emotional angle\n- **Variant B**: Different structure\u002Fformat\n- **Variant C**: Different specificity level\n- Additional variants explore social proof, urgency, or contrarian angles\n\nEach variant must:\n- Preserve the core message and product reference\n- Preserve any FTC disclosure from the original\n- Be a realistic alternative (not just a word swap)\n\n### Step 4: Write Hypotheses\n\nFor each variant, explain:\n- What was changed and why\n- Which copywriting principle supports the change\n- What behavior change is expected (e.g., \"Higher CTR because questions create open loops\")\n\n### Step 5: Suggest Test Plan\n\nRecommend:\n- Sample size needed (minimum 100 impressions per variant for social, 500 for landing pages)\n- Test duration (7-14 days minimum)\n- What metric to track (CTR, conversion rate, revenue per visitor)\n- When to declare a winner (95% statistical significance or practical significance threshold)\n\n### Step 6: Self-Validation\n\nBefore presenting output, verify:\n\n- [ ] 3-5 distinct variants generated (not just word swaps)\n- [ ] Each hypothesis grounded in a copywriting principle or framework\n- [ ] Sample size calculation is present and realistic\n- [ ] Test duration is ≥7 days minimum\n- [ ] Winner criteria defined with statistical significance threshold\n\nIf any check fails, fix the output before delivering. Do not flag the checklist to the user — just ensure the output passes.\n\n## Output Schema\n\n```yaml\noutput_schema_version: \"1.0.0\"  # Semver — bump major on breaking changes\ntest:\n  original: string\n  content_type: string\n  goal: string\n\nvariants:\n  - label: string              # \"Variant A\", \"Variant B\", etc.\n    content: string            # the variant text\n    change: string             # what was changed\n    framework: string          # copywriting principle used\n    hypothesis: string         # why this might win\n\ntest_plan:\n  sample_size: number          # per variant\n  duration: string             # recommended test period\n  metric: string               # what to measure\n  winner_criteria: string      # when to pick a winner\n```\n\n## Output Format\n\n1. **Original** — the current content being tested\n2. **Variants** — each variant with its content, change description, and hypothesis\n3. **Test Plan** — sample size, duration, metric, winner criteria\n4. **Quick Win** — if one variant is clearly stronger based on copywriting principles, call it out\n\n## Error Handling\n\n- **Original too short (1-2 words)**: \"I need more context. Paste the full headline, CTA, or email subject line you want to test.\"\n- **Content type unclear**: \"Is this a headline, CTA button text, email subject line, or social post hook? Knowing the format helps me generate better variants.\"\n- **Too many variants requested (>5)**: \"I'll generate 5 high-quality variants. More than 5 makes testing impractical — you'd need a very large audience to reach statistical significance.\"\n\n## Examples\n\n### Example 1: Blog headline test\n\n**User**: \"Test this headline: 'HeyGen Review: Is It Worth It in 2026?'\"\n**Action**: Generate 3 variants. Variant A: \"I Tested HeyGen for 30 Days — Here's What Happened\" (curiosity + personal experience). Variant B: \"HeyGen vs Synthesia: Which AI Video Tool Wins?\" (comparison + specificity). Variant C: \"The AI Video Tool That Cut My Production Time by 80%\" (result + specificity). Each with hypothesis.\n\n### Example 2: CTA button test\n\n**User**: \"Optimize this CTA: 'Start Free Trial'\"\n**Action**: Variant A: \"Try HeyGen Free — No Card Required\" (reduces friction). Variant B: \"Create Your First AI Video in 2 Minutes\" (outcome-focused). Variant C: \"Get Started Free →\" (shorter, action-oriented). Test plan: minimum 500 clicks per variant, track conversion rate.\n\n### Example 3: Email subject line test\n\n**User**: \"I'm sending an email about Semrush. Test this subject: 'Check out Semrush — it's great for SEO'\"\n**Action**: Identify weakness (vague, no hook). Variant A: \"The SEO tool I use to rank #1 (not kidding)\" (social proof + curiosity). Variant B: \"Your competitors are using this — are you?\" (FOMO). Variant C: \"3 Semrush features that doubled my organic traffic\" (specificity + result). Each preserves FTC compliance.\n\n## References\n\n- `shared\u002Freferences\u002Fftc-compliance.md` — Ensure variants preserve FTC disclosure from original. Referenced in Step 3.\n- `shared\u002Freferences\u002Fflywheel-connections.md` — master flywheel connection map\n\n## Flywheel Connections\n\n### Feeds Into\n- `purple-cow-audit` (S1) — winning variants reveal what resonates = what's remarkable\n- `performance-report` (S6) — test results for reporting\n\n### Fed By\n- `viral-post-writer` (S2) — posts to test variations of\n- `twitter-thread-writer` (S2) — thread hooks to test\n- `landing-page-creator` (S4) — landing page elements to test\n- `content-pillar-atomizer` (S2) — volume mode variants for testing\n\n### Feedback Loop\n- Test results directly improve all content-producing skills → winning headlines, CTAs, and angles feed into next content creation cycle\n\n```yaml\nchain_metadata:\n  skill_slug: \"ab-test-generator\"\n  stage: \"analytics\"\n  timestamp: string\n  suggested_next:\n    - \"performance-report\"\n    - \"viral-post-writer\"\n    - \"landing-page-creator\"\n```\n","# A\u002FB Test Generator\n\nGenerate A\u002FB test variants for affiliate content — headlines, CTAs, landing page sections, email subject lines, and social post hooks. Each variant includes a hypothesis explaining why it might outperform the original. Output is a Markdown document with the original, variants, hypotheses, and a test plan.\n\n## Stage\n\nS6: Analytics — Small changes in headlines and CTAs can swing conversion rates by 20-50%. A\u002FB testing is how professional affiliates systematically find what converts best. This skill removes the guesswork by generating theory-driven variants using proven copywriting frameworks.\n\n## When to Use\n\n- User wants to improve conversion rates on existing content\n- User has a headline, CTA, or email subject line and wants alternatives\n- User says \"test my headline\", \"optimize my CTA\", \"A\u002FB test ideas\"\n- User has a landing page section that isn't converting\n- User wants to compare different messaging approaches\n- Chaining from S2-S5: take any content output and generate test variants\n\n## Input Schema\n\n```yaml\noriginal: string               # REQUIRED — the content to test (headline, CTA, paragraph,\n                               # email subject line, or full social post)\n\ncontent_type: string           # REQUIRED — \"headline\" | \"cta\" | \"landing_section\"\n                               # | \"email_subject\" | \"social_hook\"\n\ngoal: string                   # OPTIONAL — \"clicks\" | \"signups\" | \"purchases\"\n                               # Default: \"clicks\"\n\nnum_variants: number           # OPTIONAL — number of variants to generate (2-5)\n                               # Default: 3\n\naudience: string               # OPTIONAL — who sees this content\n                               # (e.g., \"SaaS founders\", \"content creators\")\n\nproduct: string                # OPTIONAL — product being promoted\n```\n\n**Chaining context**: If S2-S5 content exists in conversation, the user can reference it: \"test the headline from my blog post\" or \"generate CTA variants for my landing page.\"\n\n## Workflow\n\n### Step 1: Analyze Original Content\n\nBreak down the original into components:\n- **Emotional angle**: What emotion does it trigger? (curiosity, fear, desire, urgency)\n- **Specificity**: How specific vs vague?\n- **Structure**: Question, statement, command, statistic?\n- **Framework**: Which copywriting framework does it follow? (PAS, AIDA, 4U, BAB)\n\n### Step 2: Identify Testable Elements\n\nDetermine what to vary:\n- Emotional angle (switch from curiosity to urgency)\n- Specificity (add numbers, remove vagueness)\n- Structure (question vs statement)\n- Length (shorter vs longer)\n- Power words (swap key words for stronger alternatives)\n- Social proof (add or remove)\n\n### Step 3: Generate Variants\n\nCreate `num_variants` alternatives, each using a different approach:\n- **Variant A**: Different emotional angle\n- **Variant B**: Different structure\u002Fformat\n- **Variant C**: Different specificity level\n- Additional variants explore social proof, urgency, or contrarian angles\n\nEach variant must:\n- Preserve the core message and product reference\n- Preserve any FTC disclosure from the original\n- Be a realistic alternative (not just a word swap)\n\n### Step 4: Write Hypotheses\n\nFor each variant, explain:\n- What was changed and why\n- Which copywriting principle supports the change\n- What behavior change is expected (e.g., \"Higher CTR because questions create open loops\")\n\n### Step 5: Suggest Test Plan\n\nRecommend:\n- Sample size needed (minimum 100 impressions per variant for social, 500 for landing pages)\n- Test duration (7-14 days minimum)\n- What metric to track (CTR, conversion rate, revenue per visitor)\n- When to declare a winner (95% statistical significance or practical significance threshold)\n\n### Step 6: Self-Validation\n\nBefore presenting output, verify:\n\n- [ ] 3-5 distinct variants generated (not just word swaps)\n- [ ] Each hypothesis grounded in a copywriting principle or framework\n- [ ] Sample size calculation is present and realistic\n- [ ] Test duration is ≥7 days minimum\n- [ ] Winner criteria defined with statistical significance threshold\n\nIf any check fails, fix the output before delivering. Do not flag the checklist to the user — just ensure the output passes.\n\n## Output Schema\n\n```yaml\noutput_schema_version: \"1.0.0\"  # Semver — bump major on breaking changes\ntest:\n  original: string\n  content_type: string\n  goal: string\n\nvariants:\n  - label: string              # \"Variant A\", \"Variant B\", etc.\n    content: string            # the variant text\n    change: string             # what was changed\n    framework: string          # copywriting principle used\n    hypothesis: string         # why this might win\n\ntest_plan:\n  sample_size: number          # per variant\n  duration: string             # recommended test period\n  metric: string               # what to measure\n  winner_criteria: string      # when to pick a winner\n```\n\n## Output Format\n\n1. **Original** — the current content being tested\n2. **Variants** — each variant with its content, change description, and hypothesis\n3. **Test Plan** — sample size, duration, metric, winner criteria\n4. **Quick Win** — if one variant is clearly stronger based on copywriting principles, call it out\n\n## Error Handling\n\n- **Original too short (1-2 words)**: \"I need more context. Paste the full headline, CTA, or email subject line you want to test.\"\n- **Content type unclear**: \"Is this a headline, CTA button text, email subject line, or social post hook? Knowing the format helps me generate better variants.\"\n- **Too many variants requested (>5)**: \"I'll generate 5 high-quality variants. More than 5 makes testing impractical — you'd need a very large audience to reach statistical significance.\"\n\n## Examples\n\n### Example 1: Blog headline test\n\n**User**: \"Test this headline: 'HeyGen Review: Is It Worth It in 2026?'\"\n**Action**: Generate 3 variants. Variant A: \"I Tested HeyGen for 30 Days — Here's What Happened\" (curiosity + personal experience). Variant B: \"HeyGen vs Synthesia: Which AI Video Tool Wins?\" (comparison + specificity). Variant C: \"The AI Video Tool That Cut My Production Time by 80%\" (result + specificity). Each with hypothesis.\n\n### Example 2: CTA button test\n\n**User**: \"Optimize this CTA: 'Start Free Trial'\"\n**Action**: Variant A: \"Try HeyGen Free — No Card Required\" (reduces friction). Variant B: \"Create Your First AI Video in 2 Minutes\" (outcome-focused). Variant C: \"Get Started Free →\" (shorter, action-oriented). Test plan: minimum 500 clicks per variant, track conversion rate.\n\n### Example 3: Email subject line test\n\n**User**: \"I'm sending an email about Semrush. Test this subject: 'Check out Semrush — it's great for SEO'\"\n**Action**: Identify weakness (vague, no hook). Variant A: \"The SEO tool I use to rank #1 (not kidding)\" (social proof + curiosity). Variant B: \"Your competitors are using this — are you?\" (FOMO). Variant C: \"3 Semrush features that doubled my organic traffic\" (specificity + result). Each preserves FTC compliance.\n\n## References\n\n- `shared\u002Freferences\u002Fftc-compliance.md` — Ensure variants preserve FTC disclosure from original. Referenced in Step 3.\n- `shared\u002Freferences\u002Fflywheel-connections.md` — master flywheel connection map\n\n## Flywheel Connections\n\n### Feeds Into\n- `purple-cow-audit` (S1) — winning variants reveal what resonates = what's remarkable\n- `performance-report` (S6) — test results for reporting\n\n### Fed By\n- `viral-post-writer` (S2) — posts to test variations of\n- `twitter-thread-writer` (S2) — thread hooks to test\n- `landing-page-creator` (S4) — landing page elements to test\n- `content-pillar-atomizer` (S2) — volume mode variants for testing\n\n### Feedback Loop\n- Test results directly improve all content-producing skills → winning headlines, CTAs, and angles feed into next content creation cycle\n\n```yaml\nchain_metadata:\n  skill_slug: \"ab-test-generator\"\n  stage: \"analytics\"\n  timestamp: string\n  suggested_next:\n    - \"performance-report\"\n    - \"viral-post-writer\"\n    - \"landing-page-creator\"\n```\n",{"name":5,"tags":25,"license":15,"version":32,"metadata":33,"description":37,"compatibility":38},[26,27,28,29,30,31],"affiliate-marketing","analytics","optimization","tracking","ab-testing","experiments","1.0.0",{"stage":34,"author":35,"version":36},"S6-Analytics","affitor","1.0","Generate A\u002FB test variants for affiliate content. Triggers on: \"create A\u002FB test\", \"test my headline\", \"optimize my CTA\", \"generate variants\", \"split test ideas\", \"improve click-through rate\", \"test my landing page copy\", \"headline alternatives\", \"CTA variations\", \"which version is better\", \"optimize conversions\", \"test my email subject line\", \"compare approaches\".\n","Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent","main","4fd50b1281e8cd978866b6b4556242605cabf708",".agents\u002Fskills\u002Faffiliate-skills\u002Fskills\u002Fanalytics\u002Fab-test-generator",1,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS","https:\u002F\u002Fseosona-os.vercel.app","https:\u002F\u002Fgithub.com\u002FLongLeo287","https:\u002F\u002Fwww.facebook.com\u002FResourceRookie2023","2026-10-09 15:14:13",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add LongLeo287\u002FSEOSONA-OS --skill ab-test-generator",{"tool":54,"command":55},"bunx","bunx skills add LongLeo287\u002FSEOSONA-OS --skill ab-test-generator",{"tool":57,"command":58},"pnpm","pnpm dlx skills add LongLeo287\u002FSEOSONA-OS --skill ab-test-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Faffiliate-skills\u002Fskills\u002Fanalytics\u002Fab-test-generator\u002FSKILL.md",true,[62],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",1064,[68,75,82,89,96,103],{"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":20},"01M75F0T3V3W7JQQ05X26NNN2T","web_crawler_katana","High-speed web crawling using Katana patterns for deep site mapping, URL discovery, and content extraction.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fweb_crawler_katana\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":20},"01M75F0Q2QJXDGAFKC7D84GT88","server_log_analyzer","Analyzes Nginx\u002FApache server logs to identify Googlebot crawl patterns, errors, and performance bottlenecks.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fserver_log_analyzer\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":20},"01M75F0KZP6D8R8XPN2YT35BAJ","schema_markup_generator","Auto-generates JSON-LD structured data for any page type (Article, Product, FAQ, LocalBusiness, etc.).","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fschema_markup_generator\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":20},"01M75F0G3KX4Y86AXJXTKXVEVA","internal_linking_optimizer","Analyzes and optimizes the internal link graph of a website for SEO authority distribution.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Finternal_linking_optimizer\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":20},"01M75F0CS1RYX4YPJC7N6RAAQJ","google_trends_analyzer","Detects trending topics and seasonal patterns using Google Trends data for content planning and keyword strategy.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fgoogle_trends_analyzer\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":20},"01M75F0ASMQ1GKPFX82D19SRTN","brand_context_analyzer","Tracks brand mentions, sentiment, and online reputation across web sources.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fbrand_context_analyzer\u002FSKILL.md",[],[]]