[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PG79P4CMN4CH45315Z5KBJ":3,"skill-same:01M6PG79P4CMN4CH45315Z5KBJ":104},{"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":40,"publishedAt":61,"linkOnly":62,"markdownContent":63,"markdownBody":64,"frontMatter":65,"refName":74,"commitSha":75,"skillDirectory":76,"forksCount":14,"repositoryHtmlUrl":77,"repositoryHomepageUrl":6,"ownerHtmlUrl":78,"ownerBlogUrl":79,"ownerDescription":6,"updatedAt":80,"install":81,"resources":93},"01M6PG79P4CMN4CH45315Z5KBJ","growth-report",null,"Generates a 3-month SEO performance HTML report for any domain using DataForSEO data. Fetches baseline vs current traffic, keyword rankings, top content pages, and competitive landscape, then outputs a report styled with the Infrasity brand design system: #0D0A1A background, #8157F2 purple accent, Instrument Sans + DM Sans + DM Mono typography. Use this skill whenever a user provides a target domain and a list of competitor URLs and asks for an SEO report, performance report, SEO analysis, competitive SEO comparison, traffic report, ranking report, or 3-month SEO summary. Also trigger when the user says \"generate SEO report for X vs Y and Z\", \"create a performance report\", \"compare my SEO against competitors\", or pastes a domain and asks how it's performing versus the market. Always use this skill for SEO report generation — do not attempt to build the report without following this structured data-fetch and HTML generation workflow.","headmktlucca-ui\u002Fneuroads-lp","headmktlucca-ui","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F247379838?v=4","01M6PDVAV6M1W96D1SR1PDF8CS","NeuroAds","01M6PDVAZ4P281GNDKD45CYTF5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fgrowth-report\u002FSKILL.md",[18,23,26,29,34,37],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":35,"categoryName":36,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000034","行政与办公人员",{"categoryNo":38,"categoryName":39,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000035","市场营销",[41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60],"growth report","report","growth","list","top","traffic","seo analysis","ranking","landscape","mono","fetch","design","html report","how","analysis","data","generate","create","workflow","performance","2026-11-10 10:12:30",false,"---\nname: growth-report\ndescription: >\n  Generates a 3-month SEO performance HTML report for any domain using DataForSEO data.\n  Fetches baseline vs current traffic, keyword rankings, top content pages, and competitive\n  landscape, then outputs a report styled with the Infrasity brand design system:\n  #0D0A1A background, #8157F2 purple accent, Instrument Sans + DM Sans + DM Mono typography.\n  Use this skill whenever a user provides a target domain and a list of competitor URLs and asks\n  for an SEO report, performance report, SEO analysis, competitive SEO comparison, traffic report,\n  ranking report, or 3-month SEO summary. Also trigger when the user says \"generate SEO report for\n  X vs Y and Z\", \"create a performance report\", \"compare my SEO against competitors\", or pastes a\n  domain and asks how it's performing versus the market. Always use this skill for SEO report\n  generation — do not attempt to build the report without following this structured data-fetch and\n  HTML generation workflow.\nuser-invokable: true\nargument-hint: \"[target_domain] [competitor1] [competitor2] ...\"\nlicense: MIT\nmetadata:\n  author: Infrasity\n  version: \"1.3.0\"\n  category: seo\n  design: infrasity-brand-v1\n---\n\n# SEO Performance Report Skill\n\nGenerates a comprehensive 3-month SEO performance HTML report using live DataForSEO data.\nThe report covers traffic trends, keyword rankings, top content clusters, competitive positioning,\nstrategic priorities, and an executive summary — all in the Infrasity brand design system.\n\n---\n\n## STEP 0 — COLLECT ALL INPUTS BEFORE DOING ANYTHING\n\n**All four inputs are mandatory.** Do not make any API calls until all four are confirmed.\n\nCollect them in a single message using this exact format — ask for everything at once, never\nask for inputs one at a time:\n\n---\n\n**If the user has NOT provided all four inputs**, ask:\n\n> To generate the report I need 4 things:\n>\n> 1. **Target domain** — the site to report on, e.g. `firefly.ai`\n> 2. **Competitor domains** — up to 5–6 competitors, e.g. `spacelift.io, env0.com, terraform.io`\n> 3. **Date range** — start and end date for the 3-month window *(default: **Feb 20 → May 20, 2026**)*\n> 4. **Location** — country for search data *(default: **United States**)*\n>\n> Which of these do you want to change from the defaults?\n\n---\n\n**If the user has already provided the target domain and competitors** (e.g. \"generate SEO report\nfor firefly.ai vs spacelift.io, env0.com\"), confirm the two optional inputs:\n\n> Got it — I'll generate the report for **firefly.ai** vs spacelift.io, env0.com.\n>\n> Just confirming the defaults:\n> - **Date range:** Feb 20 → May 20, 2026\n> - **Location:** United States\n>\n> OK to proceed with these, or would you like to change either?\n\n---\n\n**Input parsing rules:**\n\n| Input | Rules |\n|---|---|\n| `TARGET_DOMAIN` | Strip `https:\u002F\u002F`, `http:\u002F\u002F`, `www.`, and trailing slashes. Store bare domain only (e.g. `firefly.ai`) |\n| `COMPETITORS` | Strip same prefixes from each. Accept comma-separated or space-separated list. Min 2, max 6 competitors. |\n| `START_DATE` | Parse any human date format → `YYYY-MM-DD`. Default: `2026-02-20` |\n| `END_DATE` | Parse any human date format → `YYYY-MM-DD`. Default: `2026-05-20` |\n| `LOCATION` | Accept country name. Default: `United States`. Must be a valid DataForSEO `location_name` (full country name only, never city or region). |\n\n**After confirmation, echo back the resolved inputs clearly before proceeding:**\n\n> ✓ **Target:** firefly.ai\n> ✓ **Competitors:** spacelift.io, env0.com, controlmonkey.io, scalr.com, terraform.io\n> ✓ **Date range:** Feb 20, 2026 → May 20, 2026\n> ✓ **Location:** United States\n>\n> Fetching data now...\n\n---\n\n## CRITICAL API SETTINGS\n\n**Always use `ignore_synonyms: false` on every DataForSEO call.**\nUsing the default `ignore_synonyms: true` underreports traffic and keyword counts by 30–50%.\nThis is the single most important parameter to get right — never omit it.\n\n---\n\n## STEP 1 — Baseline Metrics\n\nCall `dataforseo_labs_google_historical_rank_overview` with:\n```\ntarget:          TARGET_DOMAIN\nlocation_name:   LOCATION\nlanguage_code:   en\nignore_synonyms: false\n```\n\nFrom the returned monthly array, find the snapshot **closest to START_DATE** (match by year+month).\nExtract and store:\n- `baseline_traffic`  = `metrics.organic.etv`\n- `baseline_keywords` = `metrics.organic.count`\n- `baseline_top3`     = `metrics.organic.pos_1` + `metrics.organic.pos_2_3`\n\n> ⚠️ There is NO `pos_1_3` field in DataForSEO. Always compute Top 3 as `pos_1 + pos_2_3`.\n\nAlso extract **all monthly snapshots** between START_DATE and END_DATE for the traffic trend\nbars in the report (typically 3–4 data points):\n- For each snapshot store: `month_label` (e.g. \"Feb 2026\"), `etv`, `year`, `month`\n- Sort ascending by date\n- These become `TREND_LABEL_1..4`, `TREND_ETV_1..4` in the HTML template\n\n---\n\n## STEP 2 — Current Metrics\n\nCall `dataforseo_labs_google_domain_rank_overview` with:\n```\ntarget:          TARGET_DOMAIN\nlocation_name:   LOCATION\nlanguage_code:   en\nignore_synonyms: false\n```\n\nExtract from `metrics.organic`:\n- `current_traffic`     = `etv`\n- `current_keywords`    = `count`\n- `current_top3`        = `pos_1` + `pos_2_3`\n- `current_pos_1`       = `pos_1`\n- `current_pos_2_3`     = `pos_2_3`\n- `current_pos_4_10`    = `pos_4_10`\n- `current_pos_11_20`   = `pos_11_20`\n- `current_pos_21_100`  = sum of `pos_21_30` + `pos_31_40` + `pos_41_50` + `pos_51_60` + `pos_61_70` + `pos_71_80` + `pos_81_90` + `pos_91_100`\n\nCalculate all deltas:\n```\ntraffic_growth_pct  = ((current_traffic - baseline_traffic) \u002F baseline_traffic) * 100\nkeywords_change     = current_keywords - baseline_keywords\nkeywords_change_pct = (keywords_change \u002F baseline_keywords) * 100\ntop3_growth_pct     = ((current_top3 - baseline_top3) \u002F baseline_top3) * 100\n```\n\nFormat rules:\n- Prefix `+` for positive values, `-` is automatic for negative\n- Round all percentages to 1 decimal place\n- Add `pos` CSS class for positive deltas, `neg` for negative\n\n---\n\n## STEP 3 — Competitive Landscape\n\n### 3a — Current Traffic Snapshot\n\nCall `dataforseo_labs_bulk_traffic_estimation` with:\n```\ntargets:         [TARGET_DOMAIN, ...COMPETITORS]   ← all domains in a single API call\nlocation_name:   LOCATION\nlanguage_code:   en\nitem_types:      [\"organic\"]\nignore_synonyms: false\n```\n\nFor each domain returned, extract: `etv`, `count`.\n\nSort all domains **descending by etv**. Assign rank 1 = highest traffic.\nDetermine:\n- `competitive_rank`     = rank position of TARGET_DOMAIN (1 = #1)\n- `total_domains`        = total count of all domains in the table\n- `domain_above`         = domain ranked one position above TARGET_DOMAIN (if any)\n- `domain_below`         = domain ranked one position below TARGET_DOMAIN (if any)\n- `gap_to_next_above`    = etv of domain_above − current_traffic (0 if TARGET_DOMAIN is #1)\n- `lead_over_next_below` = current_traffic − etv of domain_below (0 if TARGET_DOMAIN is last)\n\n### 3b — Competitor Trend Signals (Historical, Option 1)\n\nFor **each competitor** (not the target domain), call `dataforseo_labs_google_historical_rank_overview`:\n```\ntarget:          COMPETITOR_DOMAIN\nlocation_name:   LOCATION\nlanguage_code:   en\nignore_synonyms: false\n```\n\nFrom the returned monthly array:\n- Find the snapshot closest to **START_DATE** → extract `comp_baseline_etv`\n- Find the snapshot closest to **END_DATE** → extract `comp_current_etv`\n- Calculate: `comp_trend_pct = ((comp_current_etv - comp_baseline_etv) \u002F comp_baseline_etv) * 100`\n\n**Trend badge assignment rules (±5% stability threshold):**\n\n| Condition | Badge | CSS class |\n|---|---|---|\n| `comp_trend_pct > +5%` | `↑ +X.X%` | `trend-up` (green) |\n| `comp_trend_pct \u003C -5%` | `↓ -X.X%` | `trend-down` (red) |\n| `-5% ≤ comp_trend_pct ≤ +5%` | `→ Stable (X.X%)` | `trend-stable` (gray) |\n\n**TARGET_DOMAIN trend for the competitive table** must also use the same START_DATE → END_DATE\nwindow for consistency. The historical data fetched in Step 1 already contains this:\n- `target_table_trend_pct = ((end_date_snapshot_etv - baseline_traffic) \u002F baseline_traffic) * 100`\n\nWhere `end_date_snapshot_etv` is the ETV from the Step 1 historical array snapshot closest to\nEND_DATE (not `current_traffic` from Step 2, which is a live figure).\n\nApply the same ±5% threshold rules to derive the target's trend badge.\n\n> ⚠️ `traffic_growth_pct` from Step 2 (baseline → live) is used for the timeline cards,\n> delta badges, and executive summary — but **NOT** for the competitive table trend column.\n> The competitive table trend column uses `target_table_trend_pct` (START_DATE → END_DATE)\n> for all domains including the target, ensuring a consistent apples-to-apples comparison.\n\n> ⚠️ Never default any competitor to \"Stable\" without running this calculation.\n> Every trend badge in the competitive table must be derived from real historical ETV data.\n\n---\n\n## STEP 4 — Top Content Clusters\n\nCall `dataforseo_labs_google_relevant_pages` with:\n```\ntarget:          TARGET_DOMAIN\nlocation_name:   LOCATION\nlanguage_code:   en\norder_by:        [\"metrics.organic.etv,desc\"]\nlimit:           3\nignore_synonyms: false\n```\n\nFor each of the top 3 pages extract:\n- `page_address` — shorten display URL: remove `https:\u002F\u002Fwww.` prefix, keep path\n- `metrics.organic.etv`   → page_etv (format with commas, round to nearest integer)\n- `metrics.organic.count` → page_keywords\n\n**Homepage concentration check:**\nIf `page_1_etv \u002F current_traffic > 0.80`, set `homepage_concentration = true`.\nThis triggers a specific paragraph in the executive summary.\n\n---\n\n## STEP 5 — Derive Report Targets (Q2 Card)\n\n```\nIF traffic_growth_pct >= 0:\n  traffic_goal   = round(current_traffic * (1 + traffic_growth_pct\u002F100))\nELSE:\n  traffic_goal   = round(baseline_traffic * 0.9)   ← recovery target\n\nkeywords_goal    = max(round(current_keywords * 1.2), round(baseline_keywords * 0.95))\ntop3_goal        = round(current_top3 * 1.3)\n\nIF competitive_rank == 1:\n  target_badge = \"Maintain #1\"\nELSE:\n  target_badge = \"Challenge #\" + str(competitive_rank - 1)\n```\n\nFormat traffic_goal as e.g. `62,000+`. Round to nearest thousand for clean presentation.\n\n---\n\n## STEP 6 — Derive Strategic Priority Cards\n\nAlways generate exactly 6 cards. Use actual data values in every description — no generic text.\nReference competitor trend data from Step 3b to enrich card descriptions where relevant.\n\n| # | Card title formula | Content rule |\n|---|---|---|\n| 1 | \"Close Gap to #[rank_above]\" | Name domain_above, state gap_to_next_above as ETV and its trend badge (growing\u002Fdeclining). If declining, frame as narrowing window opportunity. |\n| 2 | \"Defend vs. \u002F Watch [domain_below or fastest_growing_competitor]\" | If a lower-ranked competitor is growing fast (>+20%), flag it as a rising threat. Otherwise name domain_below, state lead_over_next_below. |\n| 3 | Traffic recovery OR scale | If declined: \"Reverse the [X]% Decline\" with pos_4_10 count as pipeline. If grew: \"Sustain [X]% Growth Trajectory\" and note market context (e.g. if most competitors declined) |\n| 4 | \"Scale Top Content Clusters\" | Reference page_1 URL and its ETV; flag homepage concentration if true |\n| 5 | \"Recover\u002FExpand Keyword Coverage\" | Use keywords_change as the specific number to recover or build on |\n| 6 | \"Convert Pos 4–10 to Top 3\" | Use current_pos_4_10 count; state that converting 20% would add ~N new top-3 rankings |\n\n---\n\n## STEP 7 — Derive Executive Summary (4 paragraphs)\n\nWrite naturally — no bullet points inside the paragraphs. All numbers must be real API values.\n\n- **Para 1:** Overall result. State traffic_growth_pct, competitive_rank of total_domains. State the trend distribution of competitors (how many are growing, stable, or declining derived from Step 3b) and whether the target is the fastest growing. Name the domains ranked immediately above and below with their ETVs and trend directions.\n\n- **Para 2:** If `homepage_concentration = true`: flag that X% of traffic comes from one page,\n  frame it as both a risk and an opportunity to diversify.\n  Otherwise: describe content breadth advantage — keyword count vs competitors.\n\n- **Para 3:** Top 3 keywords trend (top3_growth_pct). Flag keywords_change — if negative,\n  state the specific number lost and the urgency to recapture. If positive, call it momentum.\n\n- **Para 4:** Q2 strategy. Name the specific gap to close (gap_to_next_above), the competitor\n  to chase (domain_above) and whether it is growing or declining. If domain_above is declining,\n  frame the opportunity as a narrowing window. Name the recovery\u002Fscale action most impactful\n  based on the data.\n\n**Fastest growing determination** — compare `target_table_trend_pct` against all competitors'\n`comp_trend_pct` values from Step 3b. If TARGET_DOMAIN has the highest trend percentage in the\nset, set `is_fastest_growing = true`. Use this in Para 1 and the summary badge.\n\n**Summary badge format:**\n`Rank #[competitive_rank] | [current_traffic_K]K Traffic | [traffic_growth_pct]% Growth | [current_top3] Top-3 Keywords | [Fastest Growing \u002F Declining \u002F Stable]`\n\nWhere the last label is:\n- Fastest Growing if is_fastest_growing = true\n- Growing if traffic_growth_pct > 5% and not fastest growing\n- Declining if traffic_growth_pct \u003C -5% and not fastest growing\n- Stable if -5% \u003C= traffic_growth_pct \u003C= +5% and not fastest growing\n\n---\n\n## STEP 8 — Generate the HTML Report\n\nRead `references\u002Fhtml-template.md` for the complete HTML structure, CSS, and variable map.\n\nThe template uses the **Infrasity brand design system** exclusively:\n- Background: `#0D0A1A` (Blackish-Violet) — never white, never any other dark\n- Primary accent: `#8157F2` — the only accent colour; never substitute blue or green\n- Fonts: `Instrument Sans` for all headings \u002F KPI values \u002F section numbers,\n  `DM Sans` for all body \u002F labels \u002F UI text, `DM Mono` for paths \u002F code \u002F data values\n- Status colours: `#5DCEA6` (positive delta), `#F07070` (negative delta)\n\nDo **not** alter, override, or mix in any other colour palette or font stack.\nFill every `{{VARIABLE}}` with real data. Output the file to:\n```\n\u002Fmnt\u002Fuser-data\u002Foutputs\u002F{TARGET_DOMAIN}_seo_report.html\n```\n\nThen call `present_files` to deliver it to the user.\n\n---\n\n## ERROR HANDLING\n\n| Situation | Action |\n|---|---|\n| Domain returns no data from bulk_traffic_estimation | Omit that domain from the competitive table; add a footnote |\n| Historical snapshot missing for START_DATE or END_DATE month | Use nearest available month; note actual date used in report footer |\n| `baseline_traffic` is 0 (division by zero) | Set `traffic_growth_pct` to \"N\u002FA\", skip all delta badges that depend on it, and note in the report footer that baseline data was unavailable for START_DATE |\n| `baseline_top3` is 0 (division by zero) | Set top3_growth_pct to \"N\u002FA\" and skip the delta badge |\n| `comp_baseline_etv` is 0 (division by zero for competitor trend) | Mark that competitor as \"N\u002FA\" in the trend column |\n| `backlinks_bulk_ranks` 40204 error | Do not call this endpoint — it requires a separate subscription. Skip entirely. |\n| `ai_opt_llm_ment_agg_metrics` 40204 error | Do not include AI citations section. It is excluded from this skill. |\n\n---\n\n## WHAT NOT TO INCLUDE\n\n- ❌ **No AI\u002FLLM citation section** — excluded by design (requires paid DataForSEO add-on)\n- ❌ **No DFS Rank (0–1000) column** — excluded by design (requires separate subscription)\n- ❌ **No `ignore_synonyms: true`** — always `false`, no exceptions\n- ❌ **No placeholder text** — every number in the HTML must come from a real API response\n- ❌ **No asking for inputs one at a time** — always collect all missing inputs in a single message\n- ❌ **No defaulting competitors to \"Stable\"** — always derive trend from historical ETV comparison\n\n---\n\n## REFERENCE FILES\n\n- `references\u002Fhtml-template.md` — Full Infrasity-branded HTML template with CSS design system,\n  all section markup, competitive table row patterns, and complete variable substitution map.\n  **Always read this file before writing any HTML. The Infrasity design is the only permitted\n  output design — do not use any other colour palette, font stack, or layout.**","# SEO Performance Report Skill\n\nGenerates a comprehensive 3-month SEO performance HTML report using live DataForSEO data.\nThe report covers traffic trends, keyword rankings, top content clusters, competitive positioning,\nstrategic priorities, and an executive summary — all in the Infrasity brand design system.\n\n---\n\n## STEP 0 — COLLECT ALL INPUTS BEFORE DOING ANYTHING\n\n**All four inputs are mandatory.** Do not make any API calls until all four are confirmed.\n\nCollect them in a single message using this exact format — ask for everything at once, never\nask for inputs one at a time:\n\n---\n\n**If the user has NOT provided all four inputs**, ask:\n\n> To generate the report I need 4 things:\n>\n> 1. **Target domain** — the site to report on, e.g. `firefly.ai`\n> 2. **Competitor domains** — up to 5–6 competitors, e.g. `spacelift.io, env0.com, terraform.io`\n> 3. **Date range** — start and end date for the 3-month window *(default: **Feb 20 → May 20, 2026**)*\n> 4. **Location** — country for search data *(default: **United States**)*\n>\n> Which of these do you want to change from the defaults?\n\n---\n\n**If the user has already provided the target domain and competitors** (e.g. \"generate SEO report\nfor firefly.ai vs spacelift.io, env0.com\"), confirm the two optional inputs:\n\n> Got it — I'll generate the report for **firefly.ai** vs spacelift.io, env0.com.\n>\n> Just confirming the defaults:\n> - **Date range:** Feb 20 → May 20, 2026\n> - **Location:** United States\n>\n> OK to proceed with these, or would you like to change either?\n\n---\n\n**Input parsing rules:**\n\n| Input | Rules |\n|---|---|\n| `TARGET_DOMAIN` | Strip `https:\u002F\u002F`, `http:\u002F\u002F`, `www.`, and trailing slashes. Store bare domain only (e.g. `firefly.ai`) |\n| `COMPETITORS` | Strip same prefixes from each. Accept comma-separated or space-separated list. Min 2, max 6 competitors. |\n| `START_DATE` | Parse any human date format → `YYYY-MM-DD`. Default: `2026-02-20` |\n| `END_DATE` | Parse any human date format → `YYYY-MM-DD`. Default: `2026-05-20` |\n| `LOCATION` | Accept country name. Default: `United States`. Must be a valid DataForSEO `location_name` (full country name only, never city or region). |\n\n**After confirmation, echo back the resolved inputs clearly before proceeding:**\n\n> ✓ **Target:** firefly.ai\n> ✓ **Competitors:** spacelift.io, env0.com, controlmonkey.io, scalr.com, terraform.io\n> ✓ **Date range:** Feb 20, 2026 → May 20, 2026\n> ✓ **Location:** United States\n>\n> Fetching data now...\n\n---\n\n## CRITICAL API SETTINGS\n\n**Always use `ignore_synonyms: false` on every DataForSEO call.**\nUsing the default `ignore_synonyms: true` underreports traffic and keyword counts by 30–50%.\nThis is the single most important parameter to get right — never omit it.\n\n---\n\n## STEP 1 — Baseline Metrics\n\nCall `dataforseo_labs_google_historical_rank_overview` with:\n```\ntarget:          TARGET_DOMAIN\nlocation_name:   LOCATION\nlanguage_code:   en\nignore_synonyms: false\n```\n\nFrom the returned monthly array, find the snapshot **closest to START_DATE** (match by year+month).\nExtract and store:\n- `baseline_traffic`  = `metrics.organic.etv`\n- `baseline_keywords` = `metrics.organic.count`\n- `baseline_top3`     = `metrics.organic.pos_1` + `metrics.organic.pos_2_3`\n\n> ⚠️ There is NO `pos_1_3` field in DataForSEO. Always compute Top 3 as `pos_1 + pos_2_3`.\n\nAlso extract **all monthly snapshots** between START_DATE and END_DATE for the traffic trend\nbars in the report (typically 3–4 data points):\n- For each snapshot store: `month_label` (e.g. \"Feb 2026\"), `etv`, `year`, `month`\n- Sort ascending by date\n- These become `TREND_LABEL_1..4`, `TREND_ETV_1..4` in the HTML template\n\n---\n\n## STEP 2 — Current Metrics\n\nCall `dataforseo_labs_google_domain_rank_overview` with:\n```\ntarget:          TARGET_DOMAIN\nlocation_name:   LOCATION\nlanguage_code:   en\nignore_synonyms: false\n```\n\nExtract from `metrics.organic`:\n- `current_traffic`     = `etv`\n- `current_keywords`    = `count`\n- `current_top3`        = `pos_1` + `pos_2_3`\n- `current_pos_1`       = `pos_1`\n- `current_pos_2_3`     = `pos_2_3`\n- `current_pos_4_10`    = `pos_4_10`\n- `current_pos_11_20`   = `pos_11_20`\n- `current_pos_21_100`  = sum of `pos_21_30` + `pos_31_40` + `pos_41_50` + `pos_51_60` + `pos_61_70` + `pos_71_80` + `pos_81_90` + `pos_91_100`\n\nCalculate all deltas:\n```\ntraffic_growth_pct  = ((current_traffic - baseline_traffic) \u002F baseline_traffic) * 100\nkeywords_change     = current_keywords - baseline_keywords\nkeywords_change_pct = (keywords_change \u002F baseline_keywords) * 100\ntop3_growth_pct     = ((current_top3 - baseline_top3) \u002F baseline_top3) * 100\n```\n\nFormat rules:\n- Prefix `+` for positive values, `-` is automatic for negative\n- Round all percentages to 1 decimal place\n- Add `pos` CSS class for positive deltas, `neg` for negative\n\n---\n\n## STEP 3 — Competitive Landscape\n\n### 3a — Current Traffic Snapshot\n\nCall `dataforseo_labs_bulk_traffic_estimation` with:\n```\ntargets:         [TARGET_DOMAIN, ...COMPETITORS]   ← all domains in a single API call\nlocation_name:   LOCATION\nlanguage_code:   en\nitem_types:      [\"organic\"]\nignore_synonyms: false\n```\n\nFor each domain returned, extract: `etv`, `count`.\n\nSort all domains **descending by etv**. Assign rank 1 = highest traffic.\nDetermine:\n- `competitive_rank`     = rank position of TARGET_DOMAIN (1 = #1)\n- `total_domains`        = total count of all domains in the table\n- `domain_above`         = domain ranked one position above TARGET_DOMAIN (if any)\n- `domain_below`         = domain ranked one position below TARGET_DOMAIN (if any)\n- `gap_to_next_above`    = etv of domain_above − current_traffic (0 if TARGET_DOMAIN is #1)\n- `lead_over_next_below` = current_traffic − etv of domain_below (0 if TARGET_DOMAIN is last)\n\n### 3b — Competitor Trend Signals (Historical, Option 1)\n\nFor **each competitor** (not the target domain), call `dataforseo_labs_google_historical_rank_overview`:\n```\ntarget:          COMPETITOR_DOMAIN\nlocation_name:   LOCATION\nlanguage_code:   en\nignore_synonyms: false\n```\n\nFrom the returned monthly array:\n- Find the snapshot closest to **START_DATE** → extract `comp_baseline_etv`\n- Find the snapshot closest to **END_DATE** → extract `comp_current_etv`\n- Calculate: `comp_trend_pct = ((comp_current_etv - comp_baseline_etv) \u002F comp_baseline_etv) * 100`\n\n**Trend badge assignment rules (±5% stability threshold):**\n\n| Condition | Badge | CSS class |\n|---|---|---|\n| `comp_trend_pct > +5%` | `↑ +X.X%` | `trend-up` (green) |\n| `comp_trend_pct \u003C -5%` | `↓ -X.X%` | `trend-down` (red) |\n| `-5% ≤ comp_trend_pct ≤ +5%` | `→ Stable (X.X%)` | `trend-stable` (gray) |\n\n**TARGET_DOMAIN trend for the competitive table** must also use the same START_DATE → END_DATE\nwindow for consistency. The historical data fetched in Step 1 already contains this:\n- `target_table_trend_pct = ((end_date_snapshot_etv - baseline_traffic) \u002F baseline_traffic) * 100`\n\nWhere `end_date_snapshot_etv` is the ETV from the Step 1 historical array snapshot closest to\nEND_DATE (not `current_traffic` from Step 2, which is a live figure).\n\nApply the same ±5% threshold rules to derive the target's trend badge.\n\n> ⚠️ `traffic_growth_pct` from Step 2 (baseline → live) is used for the timeline cards,\n> delta badges, and executive summary — but **NOT** for the competitive table trend column.\n> The competitive table trend column uses `target_table_trend_pct` (START_DATE → END_DATE)\n> for all domains including the target, ensuring a consistent apples-to-apples comparison.\n\n> ⚠️ Never default any competitor to \"Stable\" without running this calculation.\n> Every trend badge in the competitive table must be derived from real historical ETV data.\n\n---\n\n## STEP 4 — Top Content Clusters\n\nCall `dataforseo_labs_google_relevant_pages` with:\n```\ntarget:          TARGET_DOMAIN\nlocation_name:   LOCATION\nlanguage_code:   en\norder_by:        [\"metrics.organic.etv,desc\"]\nlimit:           3\nignore_synonyms: false\n```\n\nFor each of the top 3 pages extract:\n- `page_address` — shorten display URL: remove `https:\u002F\u002Fwww.` prefix, keep path\n- `metrics.organic.etv`   → page_etv (format with commas, round to nearest integer)\n- `metrics.organic.count` → page_keywords\n\n**Homepage concentration check:**\nIf `page_1_etv \u002F current_traffic > 0.80`, set `homepage_concentration = true`.\nThis triggers a specific paragraph in the executive summary.\n\n---\n\n## STEP 5 — Derive Report Targets (Q2 Card)\n\n```\nIF traffic_growth_pct >= 0:\n  traffic_goal   = round(current_traffic * (1 + traffic_growth_pct\u002F100))\nELSE:\n  traffic_goal   = round(baseline_traffic * 0.9)   ← recovery target\n\nkeywords_goal    = max(round(current_keywords * 1.2), round(baseline_keywords * 0.95))\ntop3_goal        = round(current_top3 * 1.3)\n\nIF competitive_rank == 1:\n  target_badge = \"Maintain #1\"\nELSE:\n  target_badge = \"Challenge #\" + str(competitive_rank - 1)\n```\n\nFormat traffic_goal as e.g. `62,000+`. Round to nearest thousand for clean presentation.\n\n---\n\n## STEP 6 — Derive Strategic Priority Cards\n\nAlways generate exactly 6 cards. Use actual data values in every description — no generic text.\nReference competitor trend data from Step 3b to enrich card descriptions where relevant.\n\n| # | Card title formula | Content rule |\n|---|---|---|\n| 1 | \"Close Gap to #[rank_above]\" | Name domain_above, state gap_to_next_above as ETV and its trend badge (growing\u002Fdeclining). If declining, frame as narrowing window opportunity. |\n| 2 | \"Defend vs. \u002F Watch [domain_below or fastest_growing_competitor]\" | If a lower-ranked competitor is growing fast (>+20%), flag it as a rising threat. Otherwise name domain_below, state lead_over_next_below. |\n| 3 | Traffic recovery OR scale | If declined: \"Reverse the [X]% Decline\" with pos_4_10 count as pipeline. If grew: \"Sustain [X]% Growth Trajectory\" and note market context (e.g. if most competitors declined) |\n| 4 | \"Scale Top Content Clusters\" | Reference page_1 URL and its ETV; flag homepage concentration if true |\n| 5 | \"Recover\u002FExpand Keyword Coverage\" | Use keywords_change as the specific number to recover or build on |\n| 6 | \"Convert Pos 4–10 to Top 3\" | Use current_pos_4_10 count; state that converting 20% would add ~N new top-3 rankings |\n\n---\n\n## STEP 7 — Derive Executive Summary (4 paragraphs)\n\nWrite naturally — no bullet points inside the paragraphs. All numbers must be real API values.\n\n- **Para 1:** Overall result. State traffic_growth_pct, competitive_rank of total_domains. State the trend distribution of competitors (how many are growing, stable, or declining derived from Step 3b) and whether the target is the fastest growing. Name the domains ranked immediately above and below with their ETVs and trend directions.\n\n- **Para 2:** If `homepage_concentration = true`: flag that X% of traffic comes from one page,\n  frame it as both a risk and an opportunity to diversify.\n  Otherwise: describe content breadth advantage — keyword count vs competitors.\n\n- **Para 3:** Top 3 keywords trend (top3_growth_pct). Flag keywords_change — if negative,\n  state the specific number lost and the urgency to recapture. If positive, call it momentum.\n\n- **Para 4:** Q2 strategy. Name the specific gap to close (gap_to_next_above), the competitor\n  to chase (domain_above) and whether it is growing or declining. If domain_above is declining,\n  frame the opportunity as a narrowing window. Name the recovery\u002Fscale action most impactful\n  based on the data.\n\n**Fastest growing determination** — compare `target_table_trend_pct` against all competitors'\n`comp_trend_pct` values from Step 3b. If TARGET_DOMAIN has the highest trend percentage in the\nset, set `is_fastest_growing = true`. Use this in Para 1 and the summary badge.\n\n**Summary badge format:**\n`Rank #[competitive_rank] | [current_traffic_K]K Traffic | [traffic_growth_pct]% Growth | [current_top3] Top-3 Keywords | [Fastest Growing \u002F Declining \u002F Stable]`\n\nWhere the last label is:\n- Fastest Growing if is_fastest_growing = true\n- Growing if traffic_growth_pct > 5% and not fastest growing\n- Declining if traffic_growth_pct \u003C -5% and not fastest growing\n- Stable if -5% \u003C= traffic_growth_pct \u003C= +5% and not fastest growing\n\n---\n\n## STEP 8 — Generate the HTML Report\n\nRead `references\u002Fhtml-template.md` for the complete HTML structure, CSS, and variable map.\n\nThe template uses the **Infrasity brand design system** exclusively:\n- Background: `#0D0A1A` (Blackish-Violet) — never white, never any other dark\n- Primary accent: `#8157F2` — the only accent colour; never substitute blue or green\n- Fonts: `Instrument Sans` for all headings \u002F KPI values \u002F section numbers,\n  `DM Sans` for all body \u002F labels \u002F UI text, `DM Mono` for paths \u002F code \u002F data values\n- Status colours: `#5DCEA6` (positive delta), `#F07070` (negative delta)\n\nDo **not** alter, override, or mix in any other colour palette or font stack.\nFill every `{{VARIABLE}}` with real data. Output the file to:\n```\n\u002Fmnt\u002Fuser-data\u002Foutputs\u002F{TARGET_DOMAIN}_seo_report.html\n```\n\nThen call `present_files` to deliver it to the user.\n\n---\n\n## ERROR HANDLING\n\n| Situation | Action |\n|---|---|\n| Domain returns no data from bulk_traffic_estimation | Omit that domain from the competitive table; add a footnote |\n| Historical snapshot missing for START_DATE or END_DATE month | Use nearest available month; note actual date used in report footer |\n| `baseline_traffic` is 0 (division by zero) | Set `traffic_growth_pct` to \"N\u002FA\", skip all delta badges that depend on it, and note in the report footer that baseline data was unavailable for START_DATE |\n| `baseline_top3` is 0 (division by zero) | Set top3_growth_pct to \"N\u002FA\" and skip the delta badge |\n| `comp_baseline_etv` is 0 (division by zero for competitor trend) | Mark that competitor as \"N\u002FA\" in the trend column |\n| `backlinks_bulk_ranks` 40204 error | Do not call this endpoint — it requires a separate subscription. Skip entirely. |\n| `ai_opt_llm_ment_agg_metrics` 40204 error | Do not include AI citations section. It is excluded from this skill. |\n\n---\n\n## WHAT NOT TO INCLUDE\n\n- ❌ **No AI\u002FLLM citation section** — excluded by design (requires paid DataForSEO add-on)\n- ❌ **No DFS Rank (0–1000) column** — excluded by design (requires separate subscription)\n- ❌ **No `ignore_synonyms: true`** — always `false`, no exceptions\n- ❌ **No placeholder text** — every number in the HTML must come from a real API response\n- ❌ **No asking for inputs one at a time** — always collect all missing inputs in a single message\n- ❌ **No defaulting competitors to \"Stable\"** — always derive trend from historical ETV comparison\n\n---\n\n## REFERENCE FILES\n\n- `references\u002Fhtml-template.md` — Full Infrasity-branded HTML template with CSS design system,\n  all section markup, competitive table row patterns, and complete variable substitution map.\n  **Always read this file before writing any HTML. The Infrasity design is the only permitted\n  output design — do not use any other colour palette, font stack, or layout.**",{"name":5,"license":15,"metadata":66,"description":71,"argument-hint":72,"user-invokable":73},{"author":67,"design":68,"version":69,"category":70},"Infrasity","infrasity-brand-v1","1.3.0","seo","Generates a 3-month SEO performance HTML report for any domain using DataForSEO data. Fetches baseline vs current traffic, keyword rankings, top content pages, and competitive landscape, then outputs a report styled with the Infrasity brand design system: #0D0A1A background, #8157F2 purple accent, Instrument Sans + DM Sans + DM Mono typography. Use this skill whenever a user provides a target domain and a list of competitor URLs and asks for an SEO report, performance report, SEO analysis, competitive SEO comparison, traffic report, ranking report, or 3-month SEO summary. Also trigger when the user says \"generate SEO report for X vs Y and Z\", \"create a performance report\", \"compare my SEO against competitors\", or pastes a domain and asks how it's performing versus the market. Always use this skill for SEO report generation — do not attempt to build the report without following this structured data-fetch and HTML generation workflow.\n","[target_domain] [competitor1] [competitor2] ...",true,"main","7a940b8e5af16c95e5c190a524421d32fc7445a9",".agent\u002Fskills\u002Fgrowth-report","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui","https:\u002F\u002Fneuroads.com.br","2026-08-12 00:42:44",{"source":8,"skillName":5,"commands":82,"prompt":92,"zipAvailable":73},[83,86,89],{"tool":84,"command":85},"npx","npx skills add headmktlucca-ui\u002Fneuroads-lp --skill growth-report",{"tool":87,"command":88},"bunx","bunx skills add headmktlucca-ui\u002Fneuroads-lp --skill growth-report",{"tool":90,"command":91},"pnpm","pnpm dlx skills add headmktlucca-ui\u002Fneuroads-lp --skill growth-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fgrowth-report\u002FSKILL.md",[94,100],{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"README.md","REFERENCE","参考文档",4805,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fgrowth-report\u002FREADME.md",{"path":101,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fhtml-template.md",31703,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fgrowth-report\u002Freferences\u002Fhtml-template.md",[105,127,152,175,193,222],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":115,"publishedAt":61},"01M6PTDCZTXTGSTX4RFK901YSZ","xunit-skill","Generates xUnit.net tests in C#. Covers Fact\u002FTheory, constructor injection, IClassFixture, and FluentAssertions. Use when user mentions \"xUnit\", \"[Fact]\", \"[Theory]\", \"Assert.Equal\", \"C# xUnit\". Triggers on: \"xUnit\", \"[Fact]\", \"[Theory]\", \"Assert.Equal C#\", \"xUnit.net\".","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fxunit-skill\u002FSKILL.md",[111,114],{"categoryNo":112,"categoryName":113,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[116,117,118,119,120,121,122,123,124,125,126],"xunit","xunit skill","testing","injection","user","use","tests","triggers","unit","unit-testing","C#",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":135,"publishedAt":61},"01M6PTCB59ZTG5FTMWGPYEMMBP","xcuitest-skill","Generates XCUITest UI tests for iOS\u002FiPadOS apps in Swift. Apple's native testing framework for reliable, fast UI automation. Supports local simulators and TestMu AI cloud real devices. Use when user mentions \"XCUITest\", \"XCTest\", \"iOS UI test\", \"Swift test\", \"XCUIApplication\". Triggers on: \"XCUITest\", \"XCTest UI\", \"iOS UI test\", \"Swift UI test\", \"XCUIApplication\", \"TestMu\".","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fxcuitest-skill\u002FSKILL.md",[133,134],{"categoryNo":112,"categoryName":113,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[136,137,118,138,139,140,141,142,121,143,144,145,146,147,122,123,148,149,150,151],"xcuitest","xcuitest skill","automation","test","testing framework","ios","devices","mobile","mobile-testing","ui test","local","apple","apps","native","for","objective",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":160,"publishedAt":61},"01M6PTATMNTY9NF4J7KSR76YK6","world-builder","Create and manage generative game zones for Dorothy's Pokemon-style world. Use this skill when creating, updating, or designing game worlds via MCP tools.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fworld-builder\u002FSKILL.md",[158,159],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[161,162,163,164,58,165,166,167,121,168,169,170,171,172,173,150,174],"builder","world","world builder","MCP","mcp tools","Tools","game","pokemon","manage","style","via","theme","zone","generative",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":183,"publishedAt":61},"01M6PT9Z92JTSQEHE1QR0NNW5F","webdriverio-skill","Generates WebdriverIO (WDIO) automation tests in JavaScript or TypeScript. Supports local and TestMu AI cloud. Use when user mentions \"WebdriverIO\", \"WDIO\", \"wdio.conf\", \"browser.url\", \"$\", \"$$\". Triggers on: \"WebdriverIO\", \"WDIO\", \"wdio\", \"browser.$\".","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwebdriverio-skill\u002FSKILL.md",[181,182],{"categoryNo":112,"categoryName":113,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[184,118,185,138,186,187,188,189,120,121,190,146,122,123,191,192],"webdriverio skill","typescript","javascript","browser","cloud","e2e","e2e-testing","URL","conf",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":204,"publishedAt":61},"01M6PT9NVK36ZWCQ69YXK3FR4K","web-design-guidelines","Web platform design and accessibility guidelines. Use when building web interfaces, auditing accessibility, implementing responsive layouts, or reviewing web UI code. Triggers on tasks involving HTML, CSS, web components, WCAG compliance, responsive design, or web performance.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb\u002FSKILL.md",[199,202,203],{"categoryNo":200,"categoryName":201,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},[52,205,206,207,208,209,60,210,211,212,213,214,215,216,217,218,219,220,123,221],"web","guidelines","web design guidelines","web design","css","components","web components","tasks","code","web performance","ui","platform design","html","responsive design","responsive","platform","implementing",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":230,"publishedAt":61},"01M6PT9A3JKRE3X34276F2FW5R","watchos-design-guidelines","Apple Human Interface Guidelines for Apple Watch. Use when building watchOS apps, complications, or workout features. Triggers on tasks involving Watch UI, Digital Crown, glanceable interfaces, or wrist-based interactions.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwatchos\u002FSKILL.md",[228,229],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},[52,206,231,212,215,121,232,233,147,220,234,123,148,235,150,236,237],"watchos design guidelines","workout","human","watch","interface","platform-design","features"]