[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71AF9TE6YYNDACBCX3D8N95":3,"skill-same:01M71AF9TE6YYNDACBCX3D8N95":79},{"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":28,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M71AF9TE6YYNDACBCX3D8N95","traffic-analysis",null,"When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions \"traffic sources\", \"dark traffic\", \"direct traffic\" or \"UTM parameters\". For GA4 setup, use analytics-tracking.","ariadoss\u002Fsuperskills","ariadoss","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F414341?v=4","01M71AC7383PT6JCRZSQJ4AVTM","Danilo Stern-Sapad","01M71AC73Y7NTBTJ9KQYNENRRE",12,"MIT","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fmarketing-skills\u002Fanalytics\u002Fsources\u002Ftraffic\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"analysis","traffic analysis","traffic","user","setup","direct","analytics","tracking","website","ga4 setup","ga4","analyze","utm","when","use","attribution","for","dark","sources","2026-11-10 10:12:30",false,"---\nname: traffic-analysis\ndescription: When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions \"traffic sources\", \"dark traffic\", \"direct traffic\" or \"UTM parameters\". For GA4 setup, use analytics-tracking.\nmetadata:\n  version: 1.1.1\n---\n\n# Analytics: Traffic\n\nGuides website traffic analysis across all channels (organic, paid, social, referral, direct). Covers traffic source attribution, dark traffic identification, and multi-channel reporting.\n\n**When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.\n\n## Scope\n\n- **Traffic sources**: Organic, paid, social, referral, direct, email\n- **Dark traffic**: Unattributed visits labeled as \"Direct \u002F None\"\n- **Attribution**: UTM tagging, segmenting, reporting accuracy\n\n## Branded vs. Non-Branded Traffic (Organic)\n\n| Type | Characteristics |\n|------|-----------------|\n| **Branded** | Higher CTR, conversion, purchase intent; users closer to funnel bottom |\n| **Non-branded** | Touchpoint with future users; most sites get more non-brand traffic; competition fiercer |\n\nBrand traffic grows over time as brand awareness increases.\n\n## Bot Traffic\n\nA large share of traffic can be **bot traffic**—RPA, search crawlers, spiders, scrapers. Exclude or segment when evaluating real user behavior; use GA4 filters or segments to isolate human traffic.\n\n## Traffic Channels\n\n| Channel | Typical Sources | Attribution |\n|---------|-----------------|-------------|\n| **Organic** | Google, Bing, other search | Referrer preserved |\n| **Paid (web)** | Google Ads, Meta Ads, etc. | UTM required |\n| **Paid (app)** | App install ads; Google App Campaigns, Apple Search Ads | UTM; in-app events |\n| **Paid (TV\u002FCTV)** | Streaming ads; Hulu, Roku, YouTube TV | UTM for QR\u002FURL; brand lift |\n| **Social** | Public posts (Facebook, LinkedIn, etc.) | Often preserved |\n| **Referral** | External sites, backlinks | Referrer preserved |\n| **Direct** | Typed URL, bookmarks | No referrer |\n| **Email** | Newsletters, campaigns | Often dark without UTM |\n\n## Dark Traffic\n\n### What It Is\n\nTraffic without clear origin--analytics tools default to \"Direct\" when referrer is missing. Common causes:\n\n- **Private\u002Fdark social**: WhatsApp, Messenger, Slack, Discord, TikTok shares\n- **Email clients**: Many strip referrer headers\n- **HTTPS->HTTP**: Referrer not passed\n- **Mobile apps**: In-app browsers often omit referrer\n- **Ad blockers, privacy tools**: Block tracking\n\n### Misattribution (Research)\n\nWhen traffic was sent from known sources, analytics often misattributed:\n\n- **100% as direct**: TikTok, Slack, Discord, WhatsApp, Mastodon\n- **75%**: Facebook Messenger\n- **30%**: Instagram DMs\n- **14%**: LinkedIn public posts\n- **12%**: Pinterest\n\n### Mitigation\n\n| Action | Purpose |\n|--------|---------|\n| **UTM parameters** | Tag links in emails, social, campaigns: `?utm_source=X&utm_medium=Y&utm_campaign=Z` |\n| **Block internal IPs** | Exclude company visits from reports |\n| **Segment direct traffic** | Split by page type to estimate dark vs. genuine direct |\n\n### Segmenting Direct Traffic\n\n1. **Expected direct**: Homepage, short URLs, brand pages--likely real direct\n2. **Unexpected direct**: Long URLs, deep pages, product pages--likely dark traffic\n3. **Report separately**: Use segments in GA4\u002Fanalytics to avoid overcounting direct\n\n## Attribution for Channel Optimization\n\nAds, growth channels, and medium can be optimized by viewing **attribution data**. Clean UTM + conversion tracking feeds attribution models; reliable attribution drives budget allocation and channel decisions.\n\n| Use | Action |\n|-----|--------|\n| **Optimize ads** | Compare paid channels (Google, Meta, LinkedIn) by attributed conversions; reallocate budget to winners |\n| **Optimize growth channels** | Identify which medium (cpc, email, social, referral) drives conversions; scale what works |\n| **Multi-touch attribution** | Requires clean UTM data; inconsistent tagging (e.g., `facebook` vs `Facebook`) fragments reports and misattributes |\n\n**GA4 Default Channel Grouping**: Align `utm_medium` and `utm_source` with [GA4's rules](https:\u002F\u002Fsupport.google.com\u002Fanalytics\u002Fanswer\u002F9756891) to avoid \"Unassigned\" traffic. ~30% of campaigns lack proper UTM markup, leading to wasted ad spend; teams standardizing UTM see 29% improvement in attribution accuracy.\n\n**Reference**: [UTM.io – utm_medium, utm_campaign & utm_source Optimization](https:\u002F\u002Fweb.utm.io\u002Fblog\u002Futm_medium-utm_campaign-utm_source\u002F), [UTMs for Marketing Attribution](https:\u002F\u002Fweb.utm.io\u002Fblog\u002Futms-for-marketing-attribution\u002F)\n\n## UTM Best Practices\n\n| Parameter | Use | Example |\n|-----------|-----|---------|\n| `utm_source` | Origin | `newsletter`, `facebook`, `google` |\n| `utm_medium` | Channel type | `email`, `cpc`, `social` |\n| `utm_campaign` | Campaign name | `summer_sale`, `product_launch` |\n| `utm_content` | Variant (optional) | `banner_a`, `cta_button` |\n| `utm_term` | Paid keyword (optional) | `running_shoes` |\n\n**GA4 alignment** (avoid Unassigned):\n\n| Channel | utm_medium | utm_source |\n|---------|------------|------------|\n| Paid Search | `cpc` | `google`, `bing` |\n| Paid Social | `paid-social`, `cpc` | `facebook`, `instagram` |\n| Email | `email` | `newsletter`, `mailchimp` |\n| Organic Social | `social` | `twitter`, `linkedin` |\n| App install | `cpc`, `app` | `google`, `facebook`, `apple` |\n| CTV \u002F Streaming | `video`, `ctv` | `hulu`, `roku`, `youtube` |\n| Display \u002F Banner | `display`, `cpc` | Publisher or network name |\n| Directory ads | `paid`, `cpc` | `taaft`, `shopify`, `g2`, `capterra` |\n\n- **Consistent naming**: Lowercase, hyphens; document conventions; never tag internal links (overwrites session attribution)\n- **Apply everywhere**: Every link in emails, social posts, ads\n- **Avoid**: Typos, inconsistent values; causes fragmentation\n\n## Traffic Diversification\n\n| Principle | Guideline |\n|-----------|-----------|\n| **Search share** | Keep organic search below ~75% of total traffic |\n| **Health** | Higher direct + referral share = healthier profile |\n| **Brand sites** | Diversified traffic is common for strong brands |\n| **Engagement** | Content, email, social, free tools drive return visits |\n\nSee **seo-monitoring** for full SEO data analysis framework.\n\n## Natural Traffic Benchmark\n\n**Location**: GA4 > Reports > Acquisition > Traffic acquisition\n\n1. Review organic traffic trend\n2. Record baseline (e.g., monthly total)\n3. Compare periodically to detect growth or decline\n\n## Output Format\n\n- **Traffic source** breakdown\n- **Dark traffic** estimate and actions\n- **UTM** tagging recommendations\n- **Segmentation** approach for reporting\n\n## Related Skills\n\n- **analytics-tracking**: Implement UTM, events, conversions; attribution models\n- **google-ads, paid-ads-strategy**: Paid channels; attribution informs budget allocation\n- **ai-traffic-tracking**: AI search traffic\n- **google-search-console**: GSC performance and indexing analysis\n- **seo-monitoring**: Full SEO data analysis system, benchmark, article database\n- **email-marketing**: Email strategy; UTM for email links\n","# Analytics: Traffic\n\nGuides website traffic analysis across all channels (organic, paid, social, referral, direct). Covers traffic source attribution, dark traffic identification, and multi-channel reporting.\n\n**When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.\n\n## Scope\n\n- **Traffic sources**: Organic, paid, social, referral, direct, email\n- **Dark traffic**: Unattributed visits labeled as \"Direct \u002F None\"\n- **Attribution**: UTM tagging, segmenting, reporting accuracy\n\n## Branded vs. Non-Branded Traffic (Organic)\n\n| Type | Characteristics |\n|------|-----------------|\n| **Branded** | Higher CTR, conversion, purchase intent; users closer to funnel bottom |\n| **Non-branded** | Touchpoint with future users; most sites get more non-brand traffic; competition fiercer |\n\nBrand traffic grows over time as brand awareness increases.\n\n## Bot Traffic\n\nA large share of traffic can be **bot traffic**—RPA, search crawlers, spiders, scrapers. Exclude or segment when evaluating real user behavior; use GA4 filters or segments to isolate human traffic.\n\n## Traffic Channels\n\n| Channel | Typical Sources | Attribution |\n|---------|-----------------|-------------|\n| **Organic** | Google, Bing, other search | Referrer preserved |\n| **Paid (web)** | Google Ads, Meta Ads, etc. | UTM required |\n| **Paid (app)** | App install ads; Google App Campaigns, Apple Search Ads | UTM; in-app events |\n| **Paid (TV\u002FCTV)** | Streaming ads; Hulu, Roku, YouTube TV | UTM for QR\u002FURL; brand lift |\n| **Social** | Public posts (Facebook, LinkedIn, etc.) | Often preserved |\n| **Referral** | External sites, backlinks | Referrer preserved |\n| **Direct** | Typed URL, bookmarks | No referrer |\n| **Email** | Newsletters, campaigns | Often dark without UTM |\n\n## Dark Traffic\n\n### What It Is\n\nTraffic without clear origin--analytics tools default to \"Direct\" when referrer is missing. Common causes:\n\n- **Private\u002Fdark social**: WhatsApp, Messenger, Slack, Discord, TikTok shares\n- **Email clients**: Many strip referrer headers\n- **HTTPS->HTTP**: Referrer not passed\n- **Mobile apps**: In-app browsers often omit referrer\n- **Ad blockers, privacy tools**: Block tracking\n\n### Misattribution (Research)\n\nWhen traffic was sent from known sources, analytics often misattributed:\n\n- **100% as direct**: TikTok, Slack, Discord, WhatsApp, Mastodon\n- **75%**: Facebook Messenger\n- **30%**: Instagram DMs\n- **14%**: LinkedIn public posts\n- **12%**: Pinterest\n\n### Mitigation\n\n| Action | Purpose |\n|--------|---------|\n| **UTM parameters** | Tag links in emails, social, campaigns: `?utm_source=X&utm_medium=Y&utm_campaign=Z` |\n| **Block internal IPs** | Exclude company visits from reports |\n| **Segment direct traffic** | Split by page type to estimate dark vs. genuine direct |\n\n### Segmenting Direct Traffic\n\n1. **Expected direct**: Homepage, short URLs, brand pages--likely real direct\n2. **Unexpected direct**: Long URLs, deep pages, product pages--likely dark traffic\n3. **Report separately**: Use segments in GA4\u002Fanalytics to avoid overcounting direct\n\n## Attribution for Channel Optimization\n\nAds, growth channels, and medium can be optimized by viewing **attribution data**. Clean UTM + conversion tracking feeds attribution models; reliable attribution drives budget allocation and channel decisions.\n\n| Use | Action |\n|-----|--------|\n| **Optimize ads** | Compare paid channels (Google, Meta, LinkedIn) by attributed conversions; reallocate budget to winners |\n| **Optimize growth channels** | Identify which medium (cpc, email, social, referral) drives conversions; scale what works |\n| **Multi-touch attribution** | Requires clean UTM data; inconsistent tagging (e.g., `facebook` vs `Facebook`) fragments reports and misattributes |\n\n**GA4 Default Channel Grouping**: Align `utm_medium` and `utm_source` with [GA4's rules](https:\u002F\u002Fsupport.google.com\u002Fanalytics\u002Fanswer\u002F9756891) to avoid \"Unassigned\" traffic. ~30% of campaigns lack proper UTM markup, leading to wasted ad spend; teams standardizing UTM see 29% improvement in attribution accuracy.\n\n**Reference**: [UTM.io – utm_medium, utm_campaign & utm_source Optimization](https:\u002F\u002Fweb.utm.io\u002Fblog\u002Futm_medium-utm_campaign-utm_source\u002F), [UTMs for Marketing Attribution](https:\u002F\u002Fweb.utm.io\u002Fblog\u002Futms-for-marketing-attribution\u002F)\n\n## UTM Best Practices\n\n| Parameter | Use | Example |\n|-----------|-----|---------|\n| `utm_source` | Origin | `newsletter`, `facebook`, `google` |\n| `utm_medium` | Channel type | `email`, `cpc`, `social` |\n| `utm_campaign` | Campaign name | `summer_sale`, `product_launch` |\n| `utm_content` | Variant (optional) | `banner_a`, `cta_button` |\n| `utm_term` | Paid keyword (optional) | `running_shoes` |\n\n**GA4 alignment** (avoid Unassigned):\n\n| Channel | utm_medium | utm_source |\n|---------|------------|------------|\n| Paid Search | `cpc` | `google`, `bing` |\n| Paid Social | `paid-social`, `cpc` | `facebook`, `instagram` |\n| Email | `email` | `newsletter`, `mailchimp` |\n| Organic Social | `social` | `twitter`, `linkedin` |\n| App install | `cpc`, `app` | `google`, `facebook`, `apple` |\n| CTV \u002F Streaming | `video`, `ctv` | `hulu`, `roku`, `youtube` |\n| Display \u002F Banner | `display`, `cpc` | Publisher or network name |\n| Directory ads | `paid`, `cpc` | `taaft`, `shopify`, `g2`, `capterra` |\n\n- **Consistent naming**: Lowercase, hyphens; document conventions; never tag internal links (overwrites session attribution)\n- **Apply everywhere**: Every link in emails, social posts, ads\n- **Avoid**: Typos, inconsistent values; causes fragmentation\n\n## Traffic Diversification\n\n| Principle | Guideline |\n|-----------|-----------|\n| **Search share** | Keep organic search below ~75% of total traffic |\n| **Health** | Higher direct + referral share = healthier profile |\n| **Brand sites** | Diversified traffic is common for strong brands |\n| **Engagement** | Content, email, social, free tools drive return visits |\n\nSee **seo-monitoring** for full SEO data analysis framework.\n\n## Natural Traffic Benchmark\n\n**Location**: GA4 > Reports > Acquisition > Traffic acquisition\n\n1. Review organic traffic trend\n2. Record baseline (e.g., monthly total)\n3. Compare periodically to detect growth or decline\n\n## Output Format\n\n- **Traffic source** breakdown\n- **Dark traffic** estimate and actions\n- **UTM** tagging recommendations\n- **Segmentation** approach for reporting\n\n## Related Skills\n\n- **analytics-tracking**: Implement UTM, events, conversions; attribution models\n- **google-ads, paid-ads-strategy**: Paid channels; attribution informs budget allocation\n- **ai-traffic-tracking**: AI search traffic\n- **google-search-console**: GSC performance and indexing analysis\n- **seo-monitoring**: Full SEO data analysis system, benchmark, article database\n- **email-marketing**: Email strategy; UTM for email links\n",{"name":5,"metadata":53,"description":7},{"version":54},"1.1.1","main","c7ec8d78e5dc37484c2cfe90ab04de163d97dd41","marketing-skills\u002Fanalytics\u002Fsources\u002Ftraffic",0,"https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills","https:\u002F\u002Fhyperion360.com\u002Fblog\u002Fparallel-ai-agents-engineering-workflow\u002F","https:\u002F\u002Fgithub.com\u002Fariadoss","https:\u002F\u002Fdanilosapad.com\u002F","CEO & Founder of @Hyperion360","2026-11-13 04:11:07",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add ariadoss\u002Fsuperskills --skill traffic-analysis",{"tool":71,"command":72},"bunx","bunx skills add ariadoss\u002Fsuperskills --skill traffic-analysis",{"tool":74,"command":75},"pnpm","pnpm dlx skills add ariadoss\u002Fsuperskills --skill traffic-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fmarketing-skills\u002Fanalytics\u002Fsources\u002Ftraffic\u002FSKILL.md",true,[],[80,104,128,147,176,192],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":89,"publishedAt":48},"01M71AZE3MPF891RM354EMRYA1","youtube","Download YouTube video transcripts when user provides a YouTube URL or asks to download\u002Fget\u002Ffetch a transcript from YouTube. Also use when user wants to transcribe or get captions\u002Fsubtitles from a YouTube video.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[86],{"categoryNo":87,"categoryName":88,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[82,32,90,91,92,93,94,95,96,42,97,98,99,100,101,43,102,103],"download","transcribe","write","transcript","video transcripts","Bash","URL","Captions","get","fetch","Video","read","subtitles","transcripts",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":48},"01M71AZAYR85PW6BJGSQXS4BN2","write-plan","Use when you have a spec or requirements for a multi-step task, before touching code. Produces an engineering plan complete with TDD tasks, DRY\u002FSOLID\u002FYAGNI principles, a required Test Plan & Verification section, and a coverage target — then auto-runs \u002Fplan-eng-review as an independent double-check before execution.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[111,112,92,113,114,115,116,117,118,42,119,120,121,122,123,45,124,125,126,127],"write plan","plan","dry","verification","review","tasks","code","you","auto","eng","coverage","complete","section","test plan","target","as","yagni",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":48},"01M71AZ8NDDP5ZMGEE6FSC4FKR","worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fworktrees\u002FSKILL.md",[],[130,135,136,137,43,138,139,140,141,142,143,114,144,42,145,146],"implementation","workspace","with","plans","feature","isolation","git","directory","work","git worktrees","selection","Safety",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":156,"publishedAt":48},"01M71AZ4ZQHTNWFRZVYHKQFP08","web-perf","Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-perf\u002FSKILL.md",[153],{"categoryNo":154,"categoryName":155,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[157,158,159,160,161,162,163,164,165,42,166,167,168,169,170,171,172,173,174,175],"web","perf","web perf","resources","MCP","layout","optimize","documentation","caching","qa","knowledge","devtools","issues","render","re","performance","chrome devtools","vitals","never",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":48},"01M71AZ2KZNWYEGKKRMJH8PYG2","verify","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[178,122,183,184,143,114,185,186,42,187,43,188,189,190,191],"commands","about","claims","output","assertions","claim","prs","evidence","running",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":198,"publishedAt":48},"01M71AZ0ACCK7N1QMWQK1FV2HJ","validate-idea","Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate-idea\u002FSKILL.md",[],[199,200,201,202,203,204,205,42,206,43,207],"validate","idea","validate idea","framework","it","minimalist","test","business","before building"]