[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F6VENCABHXFCTQWC0S0FQ3":3,"skill-same:01M6F6VENCABHXFCTQWC0S0FQ3":86},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":27,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":39,"commitSha":66,"skillDirectory":67,"forksCount":68,"repositoryHtmlUrl":69,"repositoryHomepageUrl":6,"ownerHtmlUrl":70,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":71,"install":72,"resources":85},"01M6F6VENCABHXFCTQWC0S0FQ3","geo-report",null,"Generate a professional, client-facing GEO report combining all audit results into a single deliverable with scores, findings, and prioritized actions","boisenoise\u002Fskills-collections","boisenoise","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F193180?v=4","01M6CDBDQK6BDN55ZMA6B6PKBM","01M6CDBDVSJ3JPTBYN26FZ7TZK",12,"MIT","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-geo-report\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"report","geo report","geo","2026","PDF","headless","action-plan","executive-summary","professional","client-deliverable","scripts","main","community","reports","only","read","access","plan","Bash","actions","audit","generate","2026-11-10 10:12:30",false,"---\nname: geo-report\ndescription: Generate a professional, client-facing GEO report combining all audit\n  results into a single deliverable with scores, findings, and prioritized actions\ncategory: seo\nrisk: safe\nsource: https:\u002F\u002Fgithub.com\u002Fzubair-trabzada\u002Fgeo-seo-claude\nsource_repo: zubair-trabzada\u002Fgeo-seo-claude\nsource_type: community\ndate_added: '2026-09-20'\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fzubair-trabzada\u002Fgeo-seo-claude\u002Fblob\u002Fmain\u002FLICENSE\ncompatibility: Docs-only; upstream helper scripts and templates are not bundled. Site\n  audits need network access to the target site; PDF reports need pandoc and headless\n  Chrome.\nversion: 1.0.0\nauthor: geo-seo-claude\ntags:\n- geo\n- report\n- client-deliverable\n- executive-summary\n- action-plan\nallowed-tools: Read, Grep, Glob, Bash, WebFetch, Write\n---\n\n# GEO Client Report Generator\n\n## Purpose\n\nThis skill aggregates outputs from all GEO audit skills into a single, professional report that can be delivered directly to a client or stakeholder. The report is written for **business owners and marketing leaders**, not developers — technical findings are translated into business impact and clear action items with priority levels.\n\n## How to Use This Skill\n\n1. Run the following audits first (or use existing report data):\n   - `geo-platform-optimizer` -> GEO-PLATFORM-OPTIMIZATION.md\n   - `geo-schema` -> GEO-SCHEMA-REPORT.md\n   - `geo-technical` -> GEO-TECHNICAL-AUDIT.md\n   - `geo-content` -> GEO-CONTENT-ANALYSIS.md\n   - (Optional) `geo-llmstxt` -> llms.txt assessment\n   - (Optional) `geo-brand-mentions` -> brand authority data\n2. Collect all scores and findings\n3. Calculate the composite GEO Readiness Score\n4. Generate the client report using the template below\n5. Output: GEO-CLIENT-REPORT.md\n\n---\n\n## GEO Readiness Score Calculation\n\n### Component Weights\n\n| Component | Weight | Source Skill |\n|---|---|---|\n| AI Platform Readiness | 25% | geo-platform-optimizer |\n| Content Quality & E-E-A-T | 25% | geo-content |\n| Technical Foundation | 20% | geo-technical |\n| Schema & Structured Data | 15% | geo-schema |\n| Brand Authority & Entity Presence | 15% | geo-platform-optimizer (entity signals) |\n\n### Score Formula\n```\nGEO Score = (Platform Score * 0.25) + (Content Score * 0.25) + (Technical Score * 0.20) + (Schema Score * 0.15) + (Brand Score * 0.15)\n```\n\nValidate each available component in [0,100] and round only the final sum. These weights are an editorial rubric, not a platform-endorsed ranking or citation probability. Missing audits are N\u002FA, not zero; do not publish a comparable composite unless all five components use the same rubric\u002Fscope\u002Fdate. Example: five scores of 80 yield 80\u002F100; this does not predict 80% citation likelihood.\n\n### Score Interpretation for Clients\n\n| Score Range | Label | Client-Facing Description |\n|---|---|---|\n| 85-100 | Excellent | Few gaps under the documented audit rubric; actual visibility unmeasured unless separately sampled. |\n| 70-84 | Good | Several documented improvements remain. |\n| 55-69 | Moderate | Review the observed gaps and coverage limits. |\n| 40-54 | Below Average | Many rubric checks need attention; no competitive-loss inference follows. |\n| 0-39 | Needs Attention | Prioritize verified access\u002Fcontent defects; score alone does not prove invisibility. |\n\n---\n\n## Report Template\n\nThe complete report follows this exact structure. Each section includes instructions on what to write and how.\n\n---\n\n### Section 1: Executive Summary\n\nWrite exactly ONE paragraph (4-6 sentences) covering:\n- What was analyzed (domain, number of pages, date of analysis)\n- The overall GEO Readiness Score with context (\"XX\u002F100, which places [brand] in the [label] tier\")\n- The single most impactful finding (positive or negative)\n- Top 3 priority recommendations in one sentence\n- One evidence-supported business implication. Include monetary scenarios only with measured baseline, explicit assumptions and uncertainty; otherwise state impact unmeasured.\n\n**Tone**: Confident, direct, professional. No jargon. Distinguish observations, uncertainty and hypotheses. Write as a consultant delivering findings, not as a tool generating a report.\n\n### Section 2: GEO Readiness Score\n\nPresent the overall score prominently:\n\n```\n## GEO Readiness Score: XX\u002F100 — [Label]\n```\n\nThen break down by component in a table:\n\n```markdown\n| Component | Score | Weight | Weighted Score |\n|---|---|---|---|\n| AI Platform Readiness | XX\u002F100 | 25% | XX |\n| Content Quality & E-E-A-T | XX\u002F100 | 25% | XX |\n| Technical Foundation | XX\u002F100 | 20% | XX |\n| Schema & Structured Data | XX\u002F100 | 15% | XX |\n| Brand Authority | XX\u002F100 | 15% | XX |\n| **Overall** | | | **XX\u002F100** |\n```\n\n### Section 3: AI Visibility Dashboard\n\nPresent per-platform readiness scores:\n\n```markdown\n## AI Visibility Dashboard\n\n| AI Platform | Readiness Score | Key Gap | Priority Action |\n|---|---|---|---|\n| Google AI Overviews | XX\u002F100 | [One-line gap] | [One-line action] |\n| ChatGPT Web Search | XX\u002F100 | [One-line gap] | [One-line action] |\n| Perplexity AI | XX\u002F100 | [One-line gap] | [One-line action] |\n| Google Gemini | XX\u002F100 | [One-line gap] | [One-line action] |\n| Bing Copilot | XX\u002F100 | [One-line gap] | [One-line action] |\n```\n\nAdd a brief paragraph explaining what these scores mean: \"These scores summarize checks in our disclosed rubric; they do not estimate citation probability. Report measured citations separately with prompt set, locale, date, account\u002Fmode and sampling limitations.\"\n\n### Section 4: AI Crawler Access Status\n\nPresent as a clear table:\n\n```markdown\n## AI Crawler Access\n\n| AI Crawler | Platform | Status | Impact | Recommendation |\n|---|---|---|---|---|\n| Googlebot | Google Search + AIO | Allowed\u002FBlocked | Critical | [Action] |\n| OAI-SearchBot | OpenAI search discovery | Allowed\u002FBlocked\u002FUnknown | [Observed effect] | [Action] |\n| GPTBot | OpenAI model-training crawl | Allowed\u002FBlocked\u002FUnknown | Policy choice | [Action] |\n| Bingbot | Bing + Copilot + ChatGPT | Allowed\u002FBlocked | High | [Action] |\n| PerplexityBot | Perplexity AI | Allowed\u002FBlocked | Medium | [Action] |\n| Google-Extended | Gemini Training | Allowed\u002FBlocked | Medium | [Action] |\n| ClaudeBot | Anthropic Claude | Allowed\u002FBlocked | Medium | [Action] |\n| Applebot-Extended | Apple Intelligence | Allowed\u002FBlocked | Medium | [Action] |\n```\n\n**Translate for the client**: Distinguish search discovery, user-requested fetching and training controls using current vendor documentation. Allowing training is not required for search eligibility. Respect the owner’s licensing\u002Fprivacy opt-outs; robots rules do not guarantee crawling, indexing, citation or access control.\n\n### Section 5: Brand Authority Analysis\n\nPresent entity presence across platforms:\n\n```markdown\n## Brand Authority\n\n| Platform | Presence | Status | Impact on AI Visibility |\n|---|---|---|---|\n| Wikipedia | Yes\u002FNo | [Detail] | [Observed relevance; no universal citation share] |\n| Wikidata | Yes\u002FNo | [Detail] | High — machine-readable entity data |\n| LinkedIn | Yes\u002FNo | [Detail] | High — Bing Copilot and ChatGPT signal |\n| YouTube | Yes\u002FNo | [Detail] | High — Gemini and Perplexity signal |\n| Reddit | Yes\u002FNo | [Detail] | [Observed relevance; no universal citation share] |\n| Google Knowledge Panel | Yes\u002FNo | [Detail] | High — Gemini entity recognition |\n| Crunchbase | Yes\u002FNo | [Detail] | Medium — entity validation |\n| GitHub | Yes\u002FNo | [Detail] | Medium — tech brand signal |\n```\n\n**Translate for the client**: \"AI platforms build trust by cross-referencing your brand across multiple authoritative sources. Accurate relevant profiles help readers verify identity; no causal citation increase is established by profile count alone.\"\n\n### Section 6: Citability Analysis\n\n#### Top 5 Most Citable Pages\nFor each page:\n- URL\n- Why it is citable (structure, depth, E-E-A-T signals)\n- One specific improvement that would make it even more citable\n\n#### Top 5 Least Citable Pages\nFor each page:\n- URL\n- Why it is unlikely to be cited (thin content, poor structure, missing signals)\n- Specific rewrite or restructure recommendation\n\n**Business impact framing**: \"Your most citable pages are your best candidates for appearing in AI-generated answers. Prioritize those pages only after assessing audience need, observed defects, effort and measured outcomes.\"\n\n### Section 7: Technical Health Summary\n\nPresent the key technical findings in business-friendly language:\n\n```markdown\n## Technical Health\n\n| Area | Status | Business Impact |\n|---|---|---|\n| Core Web Vitals | Good\u002FNeeds Work\u002FPoor | [Impact on user experience and rankings] |\n| Server-Side Rendering | Yes\u002FPartial\u002FNo | [Impact on AI crawler visibility] |\n| Mobile Optimization | Good\u002FNeeds Work\u002FPoor | [Impact on Google's mobile-first indexing] |\n| Security (HTTPS + Headers) | Good\u002FNeeds Work\u002FPoor | [Impact on trust signals] |\n| Page Speed | Fast\u002FAverage\u002FSlow | [Impact on user experience and crawl budget] |\n| IndexNow Protocol | Implemented\u002FNot | [Impact on Bing\u002FChatGPT indexing speed] |\n```\n\n**Rendering finding**: Compare fetched HTML and rendered content for representative URLs and named crawlers. Client-side rendering does not by itself prove an empty page, exclusion or the highest-impact defect. Report observed missing content and rendering limitations.\n\n### Section 8: Schema & Structured Data\n\n```markdown\n## Schema & Structured Data\n\n### Current Implementation\n| Schema Type | Present | Status | AI Impact |\n|---|---|---|---|\n| Organization | Yes\u002FNo | [Valid\u002FIssues] | Critical — entity recognition |\n| Article + Author | Yes\u002FNo | [Valid\u002FIssues] | High — E-E-A-T signal |\n| sameAs (entity links) | Yes\u002FNo | [Count] links | Critical — cross-platform entity graph |\n| [Business-specific] | Yes\u002FNo | [Valid\u002FIssues] | [Impact] |\n| WebSite | Yes\u002FNo | [Valid\u002FIssues] | [Applicable use; Google sitelinks search box retired in 2024] |\n| BreadcrumbList | Yes\u002FNo | [Valid\u002FIssues] | Low-Medium — navigation context |\n```\n\nOnly claim code is prepared if actual reviewed markup is included and matches visible content. Valid schema is not a promise of rich results or AI citation.\n\n### Section 9: llms.txt Status\n\n```markdown\n## llms.txt — AI Content Guide\n\n| File | Status | Recommendation |\n|---|---|---|\n| \u002Fllms.txt | Present\u002FMissing | [Action] |\n| \u002Fllms-full.txt | Present\u002FMissing | [Action] |\n```\n\n**Translate for the client**: \"llms.txt is a proposal for a content guide, not robots access control or a required AI-search eligibility file. No adoption, ranking or competitive benefit is implied; treat implementation as optional and avoid publishing private content.\"\n\n### Section 10: Prioritized Action Plan\n\nThis is the most important section of the report. Organize actions by timeline and impact.\n\n```markdown\n## Prioritized Action Plan\n\n### Quick Wins (This Week)\n*High impact, low effort — can be implemented immediately*\n\n| # | Action | Impact | Effort | Platforms Affected |\n|---|---|---|---|---|\n| 1 | [Specific action] | [High\u002FMed] | [Hours estimate] | [Which AI platforms] |\n| 2 | [Specific action] | [High\u002FMed] | [Hours estimate] | [Which AI platforms] |\n```\n\n**Quick Win criteria**: Can be done in \u003C 4 hours by one person. Examples:\n- Unblock AI crawlers in robots.txt\n- Add publication dates to existing content\n- Add author bylines with credentials\n- Fix broken meta descriptions\n- Add sameAs properties to existing Organization schema\n- Create\u002Fclaim llms.txt file\n\n```markdown\n### Medium-Term Improvements (This Month)\n*Significant impact, moderate effort — requires content or technical changes*\n\n| # | Action | Impact | Effort | Platforms Affected |\n|---|---|---|---|---|\n| 1 | [Specific action] | [High\u002FMed] | [Days estimate] | [Which AI platforms] |\n```\n\n**Medium-Term criteria**: 1-5 days of work. Examples:\n- Restructure top 10 pages with question-based headings and direct answers\n- Implement comprehensive Schema.org markup\n- Create author pages with credentials and sameAs links\n- Optimize Core Web Vitals (image compression, code splitting)\n- Register and configure Bing Webmaster Tools\n- Implement IndexNow protocol\n\n```markdown\n### Strategic Initiatives (This Quarter)\n*Long-term competitive advantage, requires ongoing investment*\n\n| # | Action | Impact | Effort | Platforms Affected |\n|---|---|---|---|---|\n| 1 | [Specific action] | [High\u002FMed] | [Weeks estimate] | [Which AI platforms] |\n```\n\n**Strategic criteria**: Ongoing effort over weeks\u002Fmonths. Examples:\n- Build Wikipedia\u002FWikidata entity presence\n- Develop active Reddit community engagement strategy\n- Create YouTube content strategy aligned with search queries\n- Implement server-side rendering (if currently client-rendered)\n- Build topical authority through comprehensive content strategy\n- Establish original research\u002Fdata publication program\n\n### Estimated Impact\nAfter the action plan, include an impact estimate:\n\nUse measured baseline data or state “impact not quantified.” Never translate rubric\npoints directly into citation\u002Ftraffic\u002Frevenue lift. An explicitly hypothetical scenario\nmay show the arithmetic: 100 incremental qualified visits × 2% conversion × $50\ncontribution per conversion = $100\u002Fmonth before implementation cost, assuming those\nvisits and conversions occur. Record attribution window, uncertainty and validation\nplan; this arithmetic is not a forecast or industry benchmark.\n\n### Section 11: Competitor Comparison (if competitor URLs provided)\n\nIf competitor URLs were analyzed alongside the primary domain:\n\n```markdown\n## Competitor Comparison\n\n| Metric | [Your Brand] | [Competitor 1] | [Competitor 2] |\n|---|---|---|---|\n| Overall GEO Score | XX\u002F100 | XX\u002F100 | XX\u002F100 |\n| Google AIO Readiness | XX\u002F100 | XX\u002F100 | XX\u002F100 |\n| ChatGPT Readiness | XX\u002F100 | XX\u002F100 | XX\u002F100 |\n| Perplexity Readiness | XX\u002F100 | XX\u002F100 | XX\u002F100 |\n| Schema Coverage | [Detail] | [Detail] | [Detail] |\n| Wikipedia Presence | Yes\u002FNo | Yes\u002FNo | Yes\u002FNo |\n| Reddit Authority | [Detail] | [Detail] | [Detail] |\n| SSR Status | Yes\u002FNo | Yes\u002FNo | Yes\u002FNo |\n\n### Where You Lead\n[Specific areas where the brand outperforms competitors]\n\n### Where You Trail\n[Specific areas where competitors have an advantage, with actions to close the gap]\n```\n\n### Section 12: Appendix\n\n```markdown\n## Appendix\n\n### Methodology\nThis GEO audit was conducted using the following methodology:\n- **Pages analyzed**: [List of specific URLs audited]\n- **Platforms assessed**: Google AI Overviews, ChatGPT, Perplexity AI, Google Gemini, Bing Copilot\n- **Technical checks**: HTTP headers, robots.txt, HTML source analysis, structured data validation\n- **Content assessment**: E-E-A-T framework (Experience, Expertise, Authoritativeness, Trustworthiness) as a disclosed editorial framework; cite the exact edition actually consulted\n- **Schema validation**: JSON-LD parsing and Schema.org specification compliance\n- **Date of analysis**: [Date]\n\n### Data Sources\n- Google Search Quality Rater Guidelines (actual consulted edition\u002Fdate\u002Flink)\n- Schema.org full type hierarchy\n- Only studies actually consulted, with URL, sample\u002Fmethod\u002Fdate and applicable limitations\n- Core Web Vitals documentation actually consulted (URL\u002Fdate)\n- AI crawler user-agent documentation (per-platform official docs)\n\n### Glossary\n\n| Term | Definition |\n|---|---|\n| GEO | Generative Engine Optimization — optimizing content to be cited by AI search platforms |\n| AIO | AI Overviews — Google's AI-generated answer boxes at the top of search results |\n| E-E-A-T | Experience, Expertise, Authoritativeness, Trustworthiness — Google's content quality framework |\n| SSR | Server-Side Rendering — generating HTML on the server so crawlers can read content without JavaScript |\n| CWV | Core Web Vitals — Google's page experience metrics (LCP, INP, CLS) |\n| LCP | Largest Contentful Paint — time to render the largest visible element |\n| INP | Interaction to Next Paint — responsiveness metric (replaced FID in March 2024) |\n| CLS | Cumulative Layout Shift — visual stability metric |\n| JSON-LD | JavaScript Object Notation for Linked Data — preferred structured data format |\n| sameAs | Schema.org property linking an entity to its profiles on other platforms |\n| IndexNow | Protocol for instantly notifying search engines of content changes |\n| llms.txt | Proposed standard file for guiding AI systems about a site's content |\n| YMYL | Your Money or Your Life — topics requiring highest E-E-A-T standards |\n| SERP | Search Engine Results Page |\n| Topical Authority | The depth and breadth of a site's coverage of its core topic area |\n```\n\n---\n\n## Formatting and Tone Guidelines\n\n### Formatting\n- Use clean markdown throughout: tables, headers (H2\u002FH3), bullet points, bold for emphasis\n- Tables for data, bullets for recommendations, bold for key terms\n- One blank line between sections for readability\n- Use horizontal rules (---) to separate major sections\n- All URLs should be absolute (not relative)\n\n### Tone\n- **Professional but accessible** — written for a business owner, not a developer\n- **Confident and direct** — state verified observations clearly and label uncertain inferences\n- **Action-oriented** — every finding should connect to a specific action\n- **Business-impact focused** — translate technical issues into business outcomes\n- Avoid: jargon without explanation, unsupported certainty, passive voice, irrelevant caveats\n- Use: \"Your site [does\u002Fdoes not]...\", \"We recommend...\", \"This impacts...\"\n\n### Dollar-Value Framing\nConnect recommendations to verified user\u002Fbusiness problems and measured baselines.\nUse the explicit hypothetical arithmetic above only as a scenario, never as evidence\nthat a score increase causes traffic or revenue. Report implementation costs and\nmeasurement gaps; never guarantee results.\n---\n\n## Output\n\nGenerate **GEO-CLIENT-REPORT.md** using the complete template above, filled with actual audit data. The report should be:\n- Appropriate to scope and audience; word count does not imply a fixed page count\n- Ready for factual\u002Fprivacy\u002Fowner review before authorized delivery\n- Self-contained (no references to other report files — all relevant data is included)\n- Printable and presentable (clean markdown formatting)\n\n## When to Use\n\n- You need a Generative Engine Optimization task for a website: audit, citability, crawlers, schema, llms.txt, content, platform tuning, or client reporting.\n- Run read-only analysis first; propose site changes before making any.\n\n## Limitations\n\n- Audits are read-only analysis; never publish, deploy, or modify the target site without explicit approval.\n- Scores and citation likelihoods are heuristics, not guarantees from AI search platforms.\n- Docs-only import: upstream scripts, agents, hooks, and schema templates are not bundled.\n\n### Example\n\n```bash\ncurl -s https:\u002F\u002Fexample.com\u002Frobots.txt\ncurl -s https:\u002F\u002Fexample.com\u002Fllms.txt\n```\n\n> Adapted from [zubair-trabzada\u002Fgeo-seo-claude](https:\u002F\u002Fgithub.com\u002Fzubair-trabzada\u002Fgeo-seo-claude) (MIT); frontmatter, When to Use\u002FLimitations, and safety boundaries added for upstream compliance. Docs-only import: upstream runtime helpers not bundled.\n","# GEO Client Report Generator\n\n## Purpose\n\nThis skill aggregates outputs from all GEO audit skills into a single, professional report that can be delivered directly to a client or stakeholder. The report is written for **business owners and marketing leaders**, not developers — technical findings are translated into business impact and clear action items with priority levels.\n\n## How to Use This Skill\n\n1. Run the following audits first (or use existing report data):\n   - `geo-platform-optimizer` -> GEO-PLATFORM-OPTIMIZATION.md\n   - `geo-schema` -> GEO-SCHEMA-REPORT.md\n   - `geo-technical` -> GEO-TECHNICAL-AUDIT.md\n   - `geo-content` -> GEO-CONTENT-ANALYSIS.md\n   - (Optional) `geo-llmstxt` -> llms.txt assessment\n   - (Optional) `geo-brand-mentions` -> brand authority data\n2. Collect all scores and findings\n3. Calculate the composite GEO Readiness Score\n4. Generate the client report using the template below\n5. Output: GEO-CLIENT-REPORT.md\n\n---\n\n## GEO Readiness Score Calculation\n\n### Component Weights\n\n| Component | Weight | Source Skill |\n|---|---|---|\n| AI Platform Readiness | 25% | geo-platform-optimizer |\n| Content Quality & E-E-A-T | 25% | geo-content |\n| Technical Foundation | 20% | geo-technical |\n| Schema & Structured Data | 15% | geo-schema |\n| Brand Authority & Entity Presence | 15% | geo-platform-optimizer (entity signals) |\n\n### Score Formula\n```\nGEO Score = (Platform Score * 0.25) + (Content Score * 0.25) + (Technical Score * 0.20) + (Schema Score * 0.15) + (Brand Score * 0.15)\n```\n\nValidate each available component in [0,100] and round only the final sum. These weights are an editorial rubric, not a platform-endorsed ranking or citation probability. Missing audits are N\u002FA, not zero; do not publish a comparable composite unless all five components use the same rubric\u002Fscope\u002Fdate. Example: five scores of 80 yield 80\u002F100; this does not predict 80% citation likelihood.\n\n### Score Interpretation for Clients\n\n| Score Range | Label | Client-Facing Description |\n|---|---|---|\n| 85-100 | Excellent | Few gaps under the documented audit rubric; actual visibility unmeasured unless separately sampled. |\n| 70-84 | Good | Several documented improvements remain. |\n| 55-69 | Moderate | Review the observed gaps and coverage limits. |\n| 40-54 | Below Average | Many rubric checks need attention; no competitive-loss inference follows. |\n| 0-39 | Needs Attention | Prioritize verified access\u002Fcontent defects; score alone does not prove invisibility. |\n\n---\n\n## Report Template\n\nThe complete report follows this exact structure. Each section includes instructions on what to write and how.\n\n---\n\n### Section 1: Executive Summary\n\nWrite exactly ONE paragraph (4-6 sentences) covering:\n- What was analyzed (domain, number of pages, date of analysis)\n- The overall GEO Readiness Score with context (\"XX\u002F100, which places [brand] in the [label] tier\")\n- The single most impactful finding (positive or negative)\n- Top 3 priority recommendations in one sentence\n- One evidence-supported business implication. Include monetary scenarios only with measured baseline, explicit assumptions and uncertainty; otherwise state impact unmeasured.\n\n**Tone**: Confident, direct, professional. No jargon. Distinguish observations, uncertainty and hypotheses. Write as a consultant delivering findings, not as a tool generating a report.\n\n### Section 2: GEO Readiness Score\n\nPresent the overall score prominently:\n\n```\n## GEO Readiness Score: XX\u002F100 — [Label]\n```\n\nThen break down by component in a table:\n\n```markdown\n| Component | Score | Weight | Weighted Score |\n|---|---|---|---|\n| AI Platform Readiness | XX\u002F100 | 25% | XX |\n| Content Quality & E-E-A-T | XX\u002F100 | 25% | XX |\n| Technical Foundation | XX\u002F100 | 20% | XX |\n| Schema & Structured Data | XX\u002F100 | 15% | XX |\n| Brand Authority | XX\u002F100 | 15% | XX |\n| **Overall** | | | **XX\u002F100** |\n```\n\n### Section 3: AI Visibility Dashboard\n\nPresent per-platform readiness scores:\n\n```markdown\n## AI Visibility Dashboard\n\n| AI Platform | Readiness Score | Key Gap | Priority Action |\n|---|---|---|---|\n| Google AI Overviews | XX\u002F100 | [One-line gap] | [One-line action] |\n| ChatGPT Web Search | XX\u002F100 | [One-line gap] | [One-line action] |\n| Perplexity AI | XX\u002F100 | [One-line gap] | [One-line action] |\n| Google Gemini | XX\u002F100 | [One-line gap] | [One-line action] |\n| Bing Copilot | XX\u002F100 | [One-line gap] | [One-line action] |\n```\n\nAdd a brief paragraph explaining what these scores mean: \"These scores summarize checks in our disclosed rubric; they do not estimate citation probability. Report measured citations separately with prompt set, locale, date, account\u002Fmode and sampling limitations.\"\n\n### Section 4: AI Crawler Access Status\n\nPresent as a clear table:\n\n```markdown\n## AI Crawler Access\n\n| AI Crawler | Platform | Status | Impact | Recommendation |\n|---|---|---|---|---|\n| Googlebot | Google Search + AIO | Allowed\u002FBlocked | Critical | [Action] |\n| OAI-SearchBot | OpenAI search discovery | Allowed\u002FBlocked\u002FUnknown | [Observed effect] | [Action] |\n| GPTBot | OpenAI model-training crawl | Allowed\u002FBlocked\u002FUnknown | Policy choice | [Action] |\n| Bingbot | Bing + Copilot + ChatGPT | Allowed\u002FBlocked | High | [Action] |\n| PerplexityBot | Perplexity AI | Allowed\u002FBlocked | Medium | [Action] |\n| Google-Extended | Gemini Training | Allowed\u002FBlocked | Medium | [Action] |\n| ClaudeBot | Anthropic Claude | Allowed\u002FBlocked | Medium | [Action] |\n| Applebot-Extended | Apple Intelligence | Allowed\u002FBlocked | Medium | [Action] |\n```\n\n**Translate for the client**: Distinguish search discovery, user-requested fetching and training controls using current vendor documentation. Allowing training is not required for search eligibility. Respect the owner’s licensing\u002Fprivacy opt-outs; robots rules do not guarantee crawling, indexing, citation or access control.\n\n### Section 5: Brand Authority Analysis\n\nPresent entity presence across platforms:\n\n```markdown\n## Brand Authority\n\n| Platform | Presence | Status | Impact on AI Visibility |\n|---|---|---|---|\n| Wikipedia | Yes\u002FNo | [Detail] | [Observed relevance; no universal citation share] |\n| Wikidata | Yes\u002FNo | [Detail] | High — machine-readable entity data |\n| LinkedIn | Yes\u002FNo | [Detail] | High — Bing Copilot and ChatGPT signal |\n| YouTube | Yes\u002FNo | [Detail] | High — Gemini and Perplexity signal |\n| Reddit | Yes\u002FNo | [Detail] | [Observed relevance; no universal citation share] |\n| Google Knowledge Panel | Yes\u002FNo | [Detail] | High — Gemini entity recognition |\n| Crunchbase | Yes\u002FNo | [Detail] | Medium — entity validation |\n| GitHub | Yes\u002FNo | [Detail] | Medium — tech brand signal |\n```\n\n**Translate for the client**: \"AI platforms build trust by cross-referencing your brand across multiple authoritative sources. Accurate relevant profiles help readers verify identity; no causal citation increase is established by profile count alone.\"\n\n### Section 6: Citability Analysis\n\n#### Top 5 Most Citable Pages\nFor each page:\n- URL\n- Why it is citable (structure, depth, E-E-A-T signals)\n- One specific improvement that would make it even more citable\n\n#### Top 5 Least Citable Pages\nFor each page:\n- URL\n- Why it is unlikely to be cited (thin content, poor structure, missing signals)\n- Specific rewrite or restructure recommendation\n\n**Business impact framing**: \"Your most citable pages are your best candidates for appearing in AI-generated answers. Prioritize those pages only after assessing audience need, observed defects, effort and measured outcomes.\"\n\n### Section 7: Technical Health Summary\n\nPresent the key technical findings in business-friendly language:\n\n```markdown\n## Technical Health\n\n| Area | Status | Business Impact |\n|---|---|---|\n| Core Web Vitals | Good\u002FNeeds Work\u002FPoor | [Impact on user experience and rankings] |\n| Server-Side Rendering | Yes\u002FPartial\u002FNo | [Impact on AI crawler visibility] |\n| Mobile Optimization | Good\u002FNeeds Work\u002FPoor | [Impact on Google's mobile-first indexing] |\n| Security (HTTPS + Headers) | Good\u002FNeeds Work\u002FPoor | [Impact on trust signals] |\n| Page Speed | Fast\u002FAverage\u002FSlow | [Impact on user experience and crawl budget] |\n| IndexNow Protocol | Implemented\u002FNot | [Impact on Bing\u002FChatGPT indexing speed] |\n```\n\n**Rendering finding**: Compare fetched HTML and rendered content for representative URLs and named crawlers. Client-side rendering does not by itself prove an empty page, exclusion or the highest-impact defect. Report observed missing content and rendering limitations.\n\n### Section 8: Schema & Structured Data\n\n```markdown\n## Schema & Structured Data\n\n### Current Implementation\n| Schema Type | Present | Status | AI Impact |\n|---|---|---|---|\n| Organization | Yes\u002FNo | [Valid\u002FIssues] | Critical — entity recognition |\n| Article + Author | Yes\u002FNo | [Valid\u002FIssues] | High — E-E-A-T signal |\n| sameAs (entity links) | Yes\u002FNo | [Count] links | Critical — cross-platform entity graph |\n| [Business-specific] | Yes\u002FNo | [Valid\u002FIssues] | [Impact] |\n| WebSite | Yes\u002FNo | [Valid\u002FIssues] | [Applicable use; Google sitelinks search box retired in 2024] |\n| BreadcrumbList | Yes\u002FNo | [Valid\u002FIssues] | Low-Medium — navigation context |\n```\n\nOnly claim code is prepared if actual reviewed markup is included and matches visible content. Valid schema is not a promise of rich results or AI citation.\n\n### Section 9: llms.txt Status\n\n```markdown\n## llms.txt — AI Content Guide\n\n| File | Status | Recommendation |\n|---|---|---|\n| \u002Fllms.txt | Present\u002FMissing | [Action] |\n| \u002Fllms-full.txt | Present\u002FMissing | [Action] |\n```\n\n**Translate for the client**: \"llms.txt is a proposal for a content guide, not robots access control or a required AI-search eligibility file. No adoption, ranking or competitive benefit is implied; treat implementation as optional and avoid publishing private content.\"\n\n### Section 10: Prioritized Action Plan\n\nThis is the most important section of the report. Organize actions by timeline and impact.\n\n```markdown\n## Prioritized Action Plan\n\n### Quick Wins (This Week)\n*High impact, low effort — can be implemented immediately*\n\n| # | Action | Impact | Effort | Platforms Affected |\n|---|---|---|---|---|\n| 1 | [Specific action] | [High\u002FMed] | [Hours estimate] | [Which AI platforms] |\n| 2 | [Specific action] | [High\u002FMed] | [Hours estimate] | [Which AI platforms] |\n```\n\n**Quick Win criteria**: Can be done in \u003C 4 hours by one person. Examples:\n- Unblock AI crawlers in robots.txt\n- Add publication dates to existing content\n- Add author bylines with credentials\n- Fix broken meta descriptions\n- Add sameAs properties to existing Organization schema\n- Create\u002Fclaim llms.txt file\n\n```markdown\n### Medium-Term Improvements (This Month)\n*Significant impact, moderate effort — requires content or technical changes*\n\n| # | Action | Impact | Effort | Platforms Affected |\n|---|---|---|---|---|\n| 1 | [Specific action] | [High\u002FMed] | [Days estimate] | [Which AI platforms] |\n```\n\n**Medium-Term criteria**: 1-5 days of work. Examples:\n- Restructure top 10 pages with question-based headings and direct answers\n- Implement comprehensive Schema.org markup\n- Create author pages with credentials and sameAs links\n- Optimize Core Web Vitals (image compression, code splitting)\n- Register and configure Bing Webmaster Tools\n- Implement IndexNow protocol\n\n```markdown\n### Strategic Initiatives (This Quarter)\n*Long-term competitive advantage, requires ongoing investment*\n\n| # | Action | Impact | Effort | Platforms Affected |\n|---|---|---|---|---|\n| 1 | [Specific action] | [High\u002FMed] | [Weeks estimate] | [Which AI platforms] |\n```\n\n**Strategic criteria**: Ongoing effort over weeks\u002Fmonths. Examples:\n- Build Wikipedia\u002FWikidata entity presence\n- Develop active Reddit community engagement strategy\n- Create YouTube content strategy aligned with search queries\n- Implement server-side rendering (if currently client-rendered)\n- Build topical authority through comprehensive content strategy\n- Establish original research\u002Fdata publication program\n\n### Estimated Impact\nAfter the action plan, include an impact estimate:\n\nUse measured baseline data or state “impact not quantified.” Never translate rubric\npoints directly into citation\u002Ftraffic\u002Frevenue lift. An explicitly hypothetical scenario\nmay show the arithmetic: 100 incremental qualified visits × 2% conversion × $50\ncontribution per conversion = $100\u002Fmonth before implementation cost, assuming those\nvisits and conversions occur. Record attribution window, uncertainty and validation\nplan; this arithmetic is not a forecast or industry benchmark.\n\n### Section 11: Competitor Comparison (if competitor URLs provided)\n\nIf competitor URLs were analyzed alongside the primary domain:\n\n```markdown\n## Competitor Comparison\n\n| Metric | [Your Brand] | [Competitor 1] | [Competitor 2] |\n|---|---|---|---|\n| Overall GEO Score | XX\u002F100 | XX\u002F100 | XX\u002F100 |\n| Google AIO Readiness | XX\u002F100 | XX\u002F100 | XX\u002F100 |\n| ChatGPT Readiness | XX\u002F100 | XX\u002F100 | XX\u002F100 |\n| Perplexity Readiness | XX\u002F100 | XX\u002F100 | XX\u002F100 |\n| Schema Coverage | [Detail] | [Detail] | [Detail] |\n| Wikipedia Presence | Yes\u002FNo | Yes\u002FNo | Yes\u002FNo |\n| Reddit Authority | [Detail] | [Detail] | [Detail] |\n| SSR Status | Yes\u002FNo | Yes\u002FNo | Yes\u002FNo |\n\n### Where You Lead\n[Specific areas where the brand outperforms competitors]\n\n### Where You Trail\n[Specific areas where competitors have an advantage, with actions to close the gap]\n```\n\n### Section 12: Appendix\n\n```markdown\n## Appendix\n\n### Methodology\nThis GEO audit was conducted using the following methodology:\n- **Pages analyzed**: [List of specific URLs audited]\n- **Platforms assessed**: Google AI Overviews, ChatGPT, Perplexity AI, Google Gemini, Bing Copilot\n- **Technical checks**: HTTP headers, robots.txt, HTML source analysis, structured data validation\n- **Content assessment**: E-E-A-T framework (Experience, Expertise, Authoritativeness, Trustworthiness) as a disclosed editorial framework; cite the exact edition actually consulted\n- **Schema validation**: JSON-LD parsing and Schema.org specification compliance\n- **Date of analysis**: [Date]\n\n### Data Sources\n- Google Search Quality Rater Guidelines (actual consulted edition\u002Fdate\u002Flink)\n- Schema.org full type hierarchy\n- Only studies actually consulted, with URL, sample\u002Fmethod\u002Fdate and applicable limitations\n- Core Web Vitals documentation actually consulted (URL\u002Fdate)\n- AI crawler user-agent documentation (per-platform official docs)\n\n### Glossary\n\n| Term | Definition |\n|---|---|\n| GEO | Generative Engine Optimization — optimizing content to be cited by AI search platforms |\n| AIO | AI Overviews — Google's AI-generated answer boxes at the top of search results |\n| E-E-A-T | Experience, Expertise, Authoritativeness, Trustworthiness — Google's content quality framework |\n| SSR | Server-Side Rendering — generating HTML on the server so crawlers can read content without JavaScript |\n| CWV | Core Web Vitals — Google's page experience metrics (LCP, INP, CLS) |\n| LCP | Largest Contentful Paint — time to render the largest visible element |\n| INP | Interaction to Next Paint — responsiveness metric (replaced FID in March 2024) |\n| CLS | Cumulative Layout Shift — visual stability metric |\n| JSON-LD | JavaScript Object Notation for Linked Data — preferred structured data format |\n| sameAs | Schema.org property linking an entity to its profiles on other platforms |\n| IndexNow | Protocol for instantly notifying search engines of content changes |\n| llms.txt | Proposed standard file for guiding AI systems about a site's content |\n| YMYL | Your Money or Your Life — topics requiring highest E-E-A-T standards |\n| SERP | Search Engine Results Page |\n| Topical Authority | The depth and breadth of a site's coverage of its core topic area |\n```\n\n---\n\n## Formatting and Tone Guidelines\n\n### Formatting\n- Use clean markdown throughout: tables, headers (H2\u002FH3), bullet points, bold for emphasis\n- Tables for data, bullets for recommendations, bold for key terms\n- One blank line between sections for readability\n- Use horizontal rules (---) to separate major sections\n- All URLs should be absolute (not relative)\n\n### Tone\n- **Professional but accessible** — written for a business owner, not a developer\n- **Confident and direct** — state verified observations clearly and label uncertain inferences\n- **Action-oriented** — every finding should connect to a specific action\n- **Business-impact focused** — translate technical issues into business outcomes\n- Avoid: jargon without explanation, unsupported certainty, passive voice, irrelevant caveats\n- Use: \"Your site [does\u002Fdoes not]...\", \"We recommend...\", \"This impacts...\"\n\n### Dollar-Value Framing\nConnect recommendations to verified user\u002Fbusiness problems and measured baselines.\nUse the explicit hypothetical arithmetic above only as a scenario, never as evidence\nthat a score increase causes traffic or revenue. Report implementation costs and\nmeasurement gaps; never guarantee results.\n---\n\n## Output\n\nGenerate **GEO-CLIENT-REPORT.md** using the complete template above, filled with actual audit data. The report should be:\n- Appropriate to scope and audience; word count does not imply a fixed page count\n- Ready for factual\u002Fprivacy\u002Fowner review before authorized delivery\n- Self-contained (no references to other report files — all relevant data is included)\n- Printable and presentable (clean markdown formatting)\n\n## When to Use\n\n- You need a Generative Engine Optimization task for a website: audit, citability, crawlers, schema, llms.txt, content, platform tuning, or client reporting.\n- Run read-only analysis first; propose site changes before making any.\n\n## Limitations\n\n- Audits are read-only analysis; never publish, deploy, or modify the target site without explicit approval.\n- Scores and citation likelihoods are heuristics, not guarantees from AI search platforms.\n- Docs-only import: upstream scripts, agents, hooks, and schema templates are not bundled.\n\n### Example\n\n```bash\ncurl -s https:\u002F\u002Fexample.com\u002Frobots.txt\ncurl -s https:\u002F\u002Fexample.com\u002Fllms.txt\n```\n\n> Adapted from [zubair-trabzada\u002Fgeo-seo-claude](https:\u002F\u002Fgithub.com\u002Fzubair-trabzada\u002Fgeo-seo-claude) (MIT); frontmatter, When to Use\u002FLimitations, and safety boundaries added for upstream compliance. Docs-only import: upstream runtime helpers not bundled.\n",{"name":5,"risk":55,"tags":56,"author":57,"source":58,"license":14,"version":59,"category":60,"date_added":61,"description":7,"source_repo":62,"source_type":40,"allowed-tools":63,"compatibility":64,"license_source":65},"safe",[30,28,37,35,34],"geo-seo-claude","https:\u002F\u002Fgithub.com\u002Fzubair-trabzada\u002Fgeo-seo-claude","1.0.0","seo","2026-09-20","zubair-trabzada\u002Fgeo-seo-claude","Read, Grep, Glob, Bash, WebFetch, Write","Docs-only; upstream helper scripts and templates are not bundled. Site audits need network access to the target site; PDF reports need pandoc and headless Chrome.","https:\u002F\u002Fgithub.com\u002Fzubair-trabzada\u002Fgeo-seo-claude\u002Fblob\u002Fmain\u002FLICENSE","7bf2279c8a65758319526a721d5c4b75683aec9c","skills\u002Fantigravity-geo-report",3,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections","https:\u002F\u002Fgithub.com\u002Fboisenoise","2026-11-12 14:21:24",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add boisenoise\u002Fskills-collections --skill geo-report",{"tool":78,"command":79},"bunx","bunx skills add boisenoise\u002Fskills-collections --skill geo-report",{"tool":81,"command":82},"pnpm","pnpm dlx skills add boisenoise\u002Fskills-collections --skill geo-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-geo-report\u002FSKILL.md",true,[],[87,113,139,163,182,205],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":50},"01M6WNH92BHVFXHGPDZCPJ0AG0","web-access","Use Treg for public web or platform data only when existing search, browser and connected tools cannot cover the task, with explicit cost and data boundaries.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FSKILL.md",[],[96,44,97,98,99,100,101,102,103,43,104,42,105,106,107,108,109,110,111,112,31],"web","web access","official","development","browser","search","data","Tools","fetch","youtube","free tools","platform","critical","free","cover","normal","when",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":123,"publishedAt":50},"01M6WNF9XAYAB2CZDDJBAKNM93","treg","Use the Treg CLI or MCP catalog to discover, price and call authorized external tools with team-scoped credentials and a user-approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FSKILL.md",[120],{"categoryNo":121,"categoryName":122,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[115,124,125,126,98,99,127,103,128,129,130,131,132,133,134,108,135,136,137,138,31],"MCP","cli","github","license","Budget","credentials","team","catalog","use","call","discover","external tools","with","scoped","blob",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":143,"sourceHtmlUrl":144,"categories":145,"keywords":149,"publishedAt":50},"01M6WN93MEAZ4E41DYAHJRPHQT","recruit","Turn a job description into an evidence-linked candidate shortlist through Treg, with job-related ranking and optional authorized business contact enrichment.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FSKILL.md",[146],{"categoryNo":147,"categoryName":148,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000038","人力资源",[141,126,98,127,150,151,152,153,154,155,108,156,157,158,136,159,160,161,162,138,115,31],"https","email","enrichment","business","evidence","phone","ranking","post","job description","for","person","candidate","reason",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":167,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":50},"01M6WN8R5RXSMHM9B4D9FAFX42","rea-growth","Analyze a company’s public growth and content through Treg, distinguish observations from hypotheses, and produce an evidence-linked playbook within an approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FSKILL.md",[],[171,172,173,126,98,127,174,175,150,176,128,177,178,179,154,108,180,181,138,115,31],"growth","rea","rea growth","produce","content","playbook","marketing","analyze","public","observations","company",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":186,"sourceHtmlUrl":187,"categories":188,"keywords":189,"publishedAt":50},"01M6WN2EVE3RQRGWAKBT4S7YT2","make-ugc","Create original AI UGC-style product videos through Treg: research hooks, approve a licensed presenter and voice, generate clips, add captions and report costs.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FSKILL.md",[],[190,191,126,192,98,193,127,194,195,196,197,198,108,199,200,201,202,203,204,138],"make","make ugc","research","create","Video","Captions","ads","short","hooks","head","style","niche","trending","talking-head","approve",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":209,"sourceHtmlUrl":210,"categories":211,"keywords":212,"publishedAt":50},"01M6WN10ARAA63Y8K1YNGXJ2RM","lead-signals","Find and qualify public buying signals through Treg, rank fitting business accounts and optionally enrich authorized business contact information.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FSKILL.md",[],[213,214,215,126,98,127,216,217,153,218,219,108,220,221,222,223,224,225,226,138],"signals","lead","lead signals","how","find","ready","as","how to","qualify","people","information","enrich","changes","funding"]