[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M738AT3WF5TB4SSDBHWD70QM":3,"skill-same:01M738AT3WF5TB4SSDBHWD70QM":93},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M738AT3WF5TB4SSDBHWD70QM","google-keyword-research",null,"Research Google keywords for SEO and paid search using Google Ads planning data (Keyword Planner). Use for keyword ideas, search volume, \"how many people search for\" questions, CPC and bid estimates, competition, seasonality, or a Search Viability Loop that prices commercial keyword clusters against contribution-based acquisition ceilings and read-only forecasts before proposing a paid test.","maltehedderich\u002Fcore-skills","maltehedderich","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12952192?v=4","01M6QVCWP46HX90VYH1107TWGD","Malte Hedderich","01M738A7KAQFR3FM2RVQDBXQPX",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmaltehedderich\u002Fcore-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-keyword-research\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: google-keyword-research\ndescription: Research Google keywords for SEO and paid search using Google Ads planning data (Keyword Planner). Use for keyword ideas, search volume, \"how many people search for\" questions, CPC and bid estimates, competition, seasonality, or a Search Viability Loop that prices commercial keyword clusters against contribution-based acquisition ceilings and read-only forecasts before proposing a paid test.\n---\n\n# Google Keyword Research\n\nUse observed Keyword Planner data to make a relevant keyword selection. Scripts retrieve data and calculate scenarios; the agent judges intent, product fit, evidence, and priority.\n\n## Choose the decision\n\n- **SEO or raw research:** use the brief, research, and shortlist flow below. Do not require an offer, margins, conversion tracking, or a viability exercise for these requests.\n- **Paid-search viability:** when the user asks whether Search ads can work, what they can afford, or to run the Search Viability Loop, read [search-viability-loop.md](references\u002Fsearch-viability-loop.md). Lock the offer and calculate acquisition ceilings before building keyword clusters. Use the offline calculator and read-only forecasts to produce a decision sheet.\n- **Both:** maintain separate SEO and paid-search conclusions. Informational terms can be useful for SEO while failing the first paid test's intent filter.\n\nA request for paid keyword ideas or bid data alone does not require the full viability mode. Do not infer campaign execution permission from research or a GO result.\n\n## Establish the brief\n\nRead supplied product context and keyword lists. Establish the audience, product or topic, and whether the decision concerns SEO, paid search, or both. Use the request's geography and language; ask when either is missing. Do not silently default to the US or the account's locale.\n\nKeep separate markets in separate runs and rankings. Multiple geo IDs in one call describe a combined market, not individual country results. Worldwide targeting requires an explicit request. If only raw metrics are requested, return them without imposing a strategy exercise.\n\n## Get access and choose a command\n\nRun the bundled script using its installed absolute path:\n\n```sh\nuv run \u002Fpath\u002Fto\u002Fgoogle-keyword-research\u002Fscripts\u002Fgoogle_keywords.py --help\n```\n\nRead [setup.md](references\u002Fsetup.md) for first-time authentication, missing credentials, or access errors. Use external YAML via `--config` or Google Ads environment variables. Never ask the user to paste credentials into chat. `doctor` checks account access; only `doctor --check-planning` verifies planning access.\n\nRead [cli-and-metrics.md](references\u002Fcli-and-metrics.md) for arguments, output fields, limits, and interpretation.\n\n- Use `locations` and `languages` to resolve market IDs. Select the intended location from the returned canonical names; do not silently resolve ambiguous names.\n- Use `ideas` for keyword discovery from seed terms, a URL, or both, or from a whole domain with `--site`. Use coherent themes and a relevant product or landing-page URL. Google receives the supplied terms, URL, or domain.\n- Use `metrics` to measure an existing list. Ideas already contain historical metrics, so a second call is usually unnecessary. `--from-month\u002F--to-month` selects a custom historical window, e.g. to compare seasons.\n- For more than a handful of rows, pass `--output file.json` (and `--csv` if wanted). Stdout then shows a compact TSV summary instead of the full JSON; read the file only for the fields you need.\n- Use `forecast` only after selecting a commercial cluster and establishing its budget and CPC ceiling. It models a proposed scenario without saving a plan or creating a campaign. Its v25 limitations are documented in the CLI reference.\n- All commands read account data or generate planning results. They do not create campaigns, saved plans, bids, or budgets.\n\nDo the accessible setup and research work, then identify the exact missing user action if OAuth consent or Cloud approval prevents live calls. Continue with clearly labeled provisional candidates if useful. Missing access never justifies fabricated volumes, bids, or competition scores.\n\n## Select and explain\n\n1. Apply product relevance first: identify what the searcher wants and whether the product or proposed content can satisfy it. Hold ambiguous terms and exclude unsupported promises.\n2. Group the returned terms by intent or use case. Rank by relevance, intent, observed demand, seasonality, and business value. Explain the tradeoffs instead of hiding them behind an arbitrary composite score.\n3. For SEO, use volume as demand evidence. Verify the live search results before claiming an intent match or an achievable ranking opportunity: use web search or browser tools when available, in the target market and language where possible, and note the result types (organic, local pack, shopping, video, AI overview), whether ads appear, and which page types rank (product, category, comparison, guide, forum). Without such a tool, label the intent assessment unverified. Google Ads competition measures advertising, not organic difficulty.\n4. For paid research, use advertiser competition and bid ranges as auction context. They do not establish an affordable bid, conversion rate, or profitability. Route affordability and test-budget decisions to the viability loop, which keeps observations, forecasts, and assumptions separate.\n5. Idea rows carry Google's keyword `concepts`. A `BRAND` or `OTHER_BRANDS` concept is a brand hint, not a verdict; you still judge brand and intent from the term and market.\n6. Preserve null versus zero, returned close-variant groups, and each market's settings. Do not sum overlapping groups into a total addressable search market. Treat a truncated ideas response as a sample; its API order is not a priority ranking.\n\n## Deliver\n\nProvide a concise ranked shortlist with intent, relevance, available metrics, seasonal observations, and a reason for selection. Separate SEO and advertising implications when both are requested. Include exclusions or uncertainties that change the decision.\n\nFor viability work, `search_viability.py scaffold` turns a metrics\u002Fideas export into profile keyword entries for you to judge, and `evaluate --forecast-plans DIR` writes the exact forecast plan files the gates check. Deliver the reference's decision CSV, input\u002Fresult JSON, keyword and negative exports, and a concise GO \u002F NO_GO \u002F INCOMPLETE explanation. `economics` returning READY means only that the economics brief is ready for keyword research. Only `evaluate` can return a full viability decision, and the proposed campaign needs its own combined check.\n\nLink requested JSON\u002FCSV exports and state geography, language, network, retrieval time, returned months, and any truncation or missing data. Preserve raw API output separately from your judgment. Reuse task exports for follow-up analysis when their settings and freshness fit; historical statistics refresh monthly. An unavailable result is unknown demand, not zero demand.\n","# Google Keyword Research\n\nUse observed Keyword Planner data to make a relevant keyword selection. Scripts retrieve data and calculate scenarios; the agent judges intent, product fit, evidence, and priority.\n\n## Choose the decision\n\n- **SEO or raw research:** use the brief, research, and shortlist flow below. Do not require an offer, margins, conversion tracking, or a viability exercise for these requests.\n- **Paid-search viability:** when the user asks whether Search ads can work, what they can afford, or to run the Search Viability Loop, read [search-viability-loop.md](references\u002Fsearch-viability-loop.md). Lock the offer and calculate acquisition ceilings before building keyword clusters. Use the offline calculator and read-only forecasts to produce a decision sheet.\n- **Both:** maintain separate SEO and paid-search conclusions. Informational terms can be useful for SEO while failing the first paid test's intent filter.\n\nA request for paid keyword ideas or bid data alone does not require the full viability mode. Do not infer campaign execution permission from research or a GO result.\n\n## Establish the brief\n\nRead supplied product context and keyword lists. Establish the audience, product or topic, and whether the decision concerns SEO, paid search, or both. Use the request's geography and language; ask when either is missing. Do not silently default to the US or the account's locale.\n\nKeep separate markets in separate runs and rankings. Multiple geo IDs in one call describe a combined market, not individual country results. Worldwide targeting requires an explicit request. If only raw metrics are requested, return them without imposing a strategy exercise.\n\n## Get access and choose a command\n\nRun the bundled script using its installed absolute path:\n\n```sh\nuv run \u002Fpath\u002Fto\u002Fgoogle-keyword-research\u002Fscripts\u002Fgoogle_keywords.py --help\n```\n\nRead [setup.md](references\u002Fsetup.md) for first-time authentication, missing credentials, or access errors. Use external YAML via `--config` or Google Ads environment variables. Never ask the user to paste credentials into chat. `doctor` checks account access; only `doctor --check-planning` verifies planning access.\n\nRead [cli-and-metrics.md](references\u002Fcli-and-metrics.md) for arguments, output fields, limits, and interpretation.\n\n- Use `locations` and `languages` to resolve market IDs. Select the intended location from the returned canonical names; do not silently resolve ambiguous names.\n- Use `ideas` for keyword discovery from seed terms, a URL, or both, or from a whole domain with `--site`. Use coherent themes and a relevant product or landing-page URL. Google receives the supplied terms, URL, or domain.\n- Use `metrics` to measure an existing list. Ideas already contain historical metrics, so a second call is usually unnecessary. `--from-month\u002F--to-month` selects a custom historical window, e.g. to compare seasons.\n- For more than a handful of rows, pass `--output file.json` (and `--csv` if wanted). Stdout then shows a compact TSV summary instead of the full JSON; read the file only for the fields you need.\n- Use `forecast` only after selecting a commercial cluster and establishing its budget and CPC ceiling. It models a proposed scenario without saving a plan or creating a campaign. Its v25 limitations are documented in the CLI reference.\n- All commands read account data or generate planning results. They do not create campaigns, saved plans, bids, or budgets.\n\nDo the accessible setup and research work, then identify the exact missing user action if OAuth consent or Cloud approval prevents live calls. Continue with clearly labeled provisional candidates if useful. Missing access never justifies fabricated volumes, bids, or competition scores.\n\n## Select and explain\n\n1. Apply product relevance first: identify what the searcher wants and whether the product or proposed content can satisfy it. Hold ambiguous terms and exclude unsupported promises.\n2. Group the returned terms by intent or use case. Rank by relevance, intent, observed demand, seasonality, and business value. Explain the tradeoffs instead of hiding them behind an arbitrary composite score.\n3. For SEO, use volume as demand evidence. Verify the live search results before claiming an intent match or an achievable ranking opportunity: use web search or browser tools when available, in the target market and language where possible, and note the result types (organic, local pack, shopping, video, AI overview), whether ads appear, and which page types rank (product, category, comparison, guide, forum). Without such a tool, label the intent assessment unverified. Google Ads competition measures advertising, not organic difficulty.\n4. For paid research, use advertiser competition and bid ranges as auction context. They do not establish an affordable bid, conversion rate, or profitability. Route affordability and test-budget decisions to the viability loop, which keeps observations, forecasts, and assumptions separate.\n5. Idea rows carry Google's keyword `concepts`. A `BRAND` or `OTHER_BRANDS` concept is a brand hint, not a verdict; you still judge brand and intent from the term and market.\n6. Preserve null versus zero, returned close-variant groups, and each market's settings. Do not sum overlapping groups into a total addressable search market. Treat a truncated ideas response as a sample; its API order is not a priority ranking.\n\n## Deliver\n\nProvide a concise ranked shortlist with intent, relevance, available metrics, seasonal observations, and a reason for selection. Separate SEO and advertising implications when both are requested. Include exclusions or uncertainties that change the decision.\n\nFor viability work, `search_viability.py scaffold` turns a metrics\u002Fideas export into profile keyword entries for you to judge, and `evaluate --forecast-plans DIR` writes the exact forecast plan files the gates check. Deliver the reference's decision CSV, input\u002Fresult JSON, keyword and negative exports, and a concise GO \u002F NO_GO \u002F INCOMPLETE explanation. `economics` returning READY means only that the economics brief is ready for keyword research. Only `evaluate` can return a full viability decision, and the proposed campaign needs its own combined check.\n\nLink requested JSON\u002FCSV exports and state geography, language, network, retrieval time, returned months, and any truncation or missing data. Preserve raw API output separately from your judgment. Reuse task exports for follow-up analysis when their settings and freshness fit; historical statistics refresh monthly. An unavailable result is unknown demand, not zero demand.\n",{"name":5,"description":7},"main","66185f8bef2d0844af45f0f89408a57b434dabab","skills\u002Fgoogle-keyword-research","https:\u002F\u002Fgithub.com\u002Fmaltehedderich\u002Fcore-skills","https:\u002F\u002Fgithub.com\u002Fmaltehedderich","hedderich.pro","2026-11-06 03:25:30",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add maltehedderich\u002Fcore-skills --skill google-keyword-research",{"tool":37,"command":38},"bunx","bunx skills add maltehedderich\u002Fcore-skills --skill google-keyword-research",{"tool":40,"command":41},"pnpm","pnpm dlx skills add maltehedderich\u002Fcore-skills --skill google-keyword-research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmaltehedderich\u002Fcore-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-keyword-research\u002FSKILL.md",true,[45,51,55,59,63,67,71,77,81,85,89],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",321,"https:\u002F\u002Fgithub.com\u002Fmaltehedderich\u002Fcore-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-keyword-research\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"README.md",3028,"https:\u002F\u002Fgithub.com\u002Fmaltehedderich\u002Fcore-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-keyword-research\u002FREADME.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fcli-and-metrics.md",11727,"https:\u002F\u002Fgithub.com\u002Fmaltehedderich\u002Fcore-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-keyword-research\u002Freferences\u002Fcli-and-metrics.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fsearch-viability-loop.md",13482,"https:\u002F\u002Fgithub.com\u002Fmaltehedderich\u002Fcore-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-keyword-research\u002Freferences\u002Fsearch-viability-loop.md",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fsetup.md",6476,"https:\u002F\u002Fgithub.com\u002Fmaltehedderich\u002Fcore-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-keyword-research\u002Freferences\u002Fsetup.md",{"path":68,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fviability-calculator.md",10946,"https:\u002F\u002Fgithub.com\u002Fmaltehedderich\u002Fcore-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-keyword-research\u002Freferences\u002Fviability-calculator.md",{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"scripts\u002Fgoogle_keywords.py","SCRIPT","脚本",32572,"https:\u002F\u002Fgithub.com\u002Fmaltehedderich\u002Fcore-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-keyword-research\u002Fscripts\u002Fgoogle_keywords.py",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"scripts\u002Fsearch_viability.py",37219,"https:\u002F\u002Fgithub.com\u002Fmaltehedderich\u002Fcore-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-keyword-research\u002Fscripts\u002Fsearch_viability.py",{"path":82,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":83,"sourceHtmlUrl":84},"tests\u002Ftest_forecast.py",8264,"https:\u002F\u002Fgithub.com\u002Fmaltehedderich\u002Fcore-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-keyword-research\u002Ftests\u002Ftest_forecast.py",{"path":86,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":87,"sourceHtmlUrl":88},"tests\u002Ftest_google_keywords.py",23133,"https:\u002F\u002Fgithub.com\u002Fmaltehedderich\u002Fcore-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-keyword-research\u002Ftests\u002Ftest_google_keywords.py",{"path":90,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":91,"sourceHtmlUrl":92},"tests\u002Ftest_search_viability.py",23034,"https:\u002F\u002Fgithub.com\u002Fmaltehedderich\u002Fcore-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-keyword-research\u002Ftests\u002Ftest_search_viability.py",[94,101,108,115,122,129],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M738B4X0Z2QZJ3TT8TJMJP3X","motion-design","Plan, build, and review short motion-design films for SaaS and app marketing: launch videos, product films, promo and social ad clips, app trailers, and landing-page loops of roughly 6–45 seconds. Develops the brief, promise, storyline, rendered key frames, timed beat sheet, and sound plan first, has them critiqued with fresh eyes, and gets sign-off before any animation, because iterating on a plan is far cheaper than iterating on renders. Then builds the film (following the project's motion studio when one exists, otherwise a code-rendered timeline) and reviews cuts with a scored rubric and prioritized fixes. Use whenever the user wants to make, script, storyboard, animate, render, critique, or fix a product video, motion graphics ad, launch clip, or app promo, even if they only say 'make a video for my app' or share a cut for feedback. Not for UI micro-interactions inside the product itself.","https:\u002F\u002Fgithub.com\u002Fmaltehedderich\u002Fcore-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmotion-design\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M738B146PWHZQGNFF5QS5NZW","mise","Set up, migrate, or maintain a project on the team's mise stack: mise tools and tasks under one shared task-naming convention, deployment environments as mise config environments (mise.\u003Cenv>.toml), uv for Python, bun for JavaScript and TypeScript, Terraform in terraform\u002F, and optional fnox secrets (Proton Pass locally, environment variables in CI and on deployed hosts). Invoke it to replace a Makefile, justfile, or package scripts, add or rename tasks, add secrets or environments, or bootstrap a repository.","https:\u002F\u002Fgithub.com\u002Fmaltehedderich\u002Fcore-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmise\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M738AX33QEAK4E2HA69JMF0T","grafana","Set up lean application monitoring in Grafana Cloud for a solo maintainer running several web apps, APIs, mobile backends, or jobs on GCP or AWS. Use when adding metrics or monitoring to an app; sending OpenTelemetry (OTLP) or Prometheus metrics to Grafana Cloud; querying Cloud Run, Lambda, Cloud Monitoring, or CloudWatch metrics from Grafana; building or fixing app and portfolio dashboards; or keeping active series within the free tier. Also covers client-side health signals for mobile and browser apps and whether a first alert is worth adding.","https:\u002F\u002Fgithub.com\u002Fmaltehedderich\u002Fcore-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgrafana\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M738APY4H5ZR5M51PYFMNBA8","frontend-design","Design, implement, and refine polished web interfaces: new screens, components, dashboards, landing pages, and visual redesigns. Use when UI quality, layout, typography, responsive behavior, or interaction polish is part of the task, including requests to make an interface look better. Reuses or establishes a design system and verifies the rendered result. Not for backend-only work or logic changes with no visual impact.","https:\u002F\u002Fgithub.com\u002Fmaltehedderich\u002Fcore-skills\u002Fblob\u002Fmain\u002Fskills\u002Ffrontend-design\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":19},"01M738AJH0XQPD2BNWZSW3QBYW","apple-ads-keyword-research","Read Apple Ads (formerly Apple Search Ads) campaign data and research App Store keywords through the Apple Ads Platform API. Use for campaign, ad group, keyword, or search term performance (spend, taps, installs, CPT, CPI), Apple's keyword and phrase suggestions, relative App Store search popularity by country and genre, impression share and rank, ASO keyword ideas, or deciding which App Store keywords to add, pause, negate, or bid on. Read-only; it never changes campaigns.","https:\u002F\u002Fgithub.com\u002Fmaltehedderich\u002Fcore-skills\u002Fblob\u002Fmain\u002Fskills\u002Fapple-ads-keyword-research\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":19},"01M738AF5NTF7PMB06S0J3NES2","agentic-browsing-auditor","Verify and improve a website, current page, or frontend repository for Lighthouse Agentic Browsing readiness. Use when asked to audit, raise, improve, or debug agentic browsing level, WebMCP readiness, llms.txt discoverability, agent-accessible forms, accessibility-tree quality for agents, or layout stability for AI\u002Fbrowser agents.","https:\u002F\u002Fgithub.com\u002Fmaltehedderich\u002Fcore-skills\u002Fblob\u002Fmain\u002Fskills\u002Fagentic-browsing-auditor\u002FSKILL.md",[],[]]