[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"extension-skill-brightdata-seo-audit-bn":3,"guides-for-brightdata-seo-audit":270,"similar-k17begs4z89dp62tky5mmdh239867xn8":271},{"_creationTime":4,"_id":5,"children":6,"community":7,"display":9,"evaluation":21,"identity":186,"isFallback":190,"parentExtension":191,"providers":245,"relations":248,"repo":249,"workflow":269},1778054268187.7822,"k17begs4z89dp62tky5mmdh239867xn8",[],{"reviewCount":8},0,{"description":10,"installMethods":11,"name":12,"sourceUrl":13,"tags":14},"When the user wants to audit, review, or diagnose SEO issues on their site. Uses live web data via the Bright Data CLI for accurate detection of JS-injected schema, hreflang, canonicals, and live SERP-based ranking checks. Also use when the user mentions \"SEO audit,\" \"technical SEO,\" \"why am I not ranking,\" \"SEO issues,\" \"on-page SEO,\" \"meta tags review,\" \"SEO health check,\" \"my traffic dropped,\" \"lost rankings,\" \"not showing up in Google,\" \"site isn't ranking,\" \"Google update hit me,\" \"page speed,\" \"core web vitals,\" \"crawl errors,\" or \"indexing issues.\" Use this even if the user just says something vague like \"my SEO is bad\" or \"help with SEO\" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For implementing structured data, see schema-markup. For AI search optimization, see ai-seo.",{},"SEO Audit (Bright Data)","https://github.com/brightdata/skills/tree/HEAD/skills/seo-audit",[15,16,17,18,19,20],"seo","audit","brightdata","cli","scraping","web-data",{"_creationTime":22,"_id":23,"extensionId":5,"locale":24,"result":25,"trustSignals":175,"workflow":184},1778054318963.3506,"kn78c2p9cq9vn6q5n2v6brk8fs867wtz","en",{"checks":26,"evaluatedAt":165,"extensionSummary":166,"promptVersionExtension":167,"promptVersionScoring":168,"rationale":169,"score":170,"summary":171,"tags":172,"targetMarket":173,"tier":174},[27,32,35,38,42,45,49,53,56,59,63,68,71,75,78,81,84,87,90,93,97,101,105,110,114,117,120,123,127,130,133,136,139,142,146,149,152,155,158,162],{"category":28,"check":29,"severity":30,"summary":31},"Practical Utility","Problem relevance","pass","The description clearly states the user problem of auditing and diagnosing SEO issues on their site.",{"category":28,"check":33,"severity":30,"summary":34},"Unique selling proposition","The extension offers significant value over a simple prompt by using the Bright Data CLI for live web data, enabling detection of JS-injected schema, hreflang, canonicals, and live SERP-based ranking checks, which standard tools cannot provide.",{"category":28,"check":36,"severity":30,"summary":37},"Production readiness","The skill provides a comprehensive workflow for SEO audits, including data gathering, analysis, and reporting, covering the complete lifecycle of an audit.",{"category":39,"check":40,"severity":30,"summary":41},"Scope","Single responsibility principle","The extension focuses solely on SEO auditing using Bright Data CLI, with clear scope boundaries defined by related skills for other tasks.",{"category":39,"check":43,"severity":30,"summary":44},"Description quality","The displayed description accurately reflects the extension's capabilities, including its use of the Bright Data CLI for live web data and specific SEO checks, and clearly lists relevant trigger phrases.",{"category":46,"check":47,"severity":30,"summary":48},"Invocation","Scoped tools","The skill utilizes narrowly scoped `bdata` commands for specific SEO tasks (e.g., fetching robots.txt, scraping URLs, performing SERP queries) rather than a single generalist tool.",{"category":50,"check":51,"severity":30,"summary":52},"Documentation","Configuration & parameter reference","The README and SKILL.md files clearly outline prerequisites like the Bright Data CLI installation and authentication, and reference relevant commands and output structures.",{"category":39,"check":54,"severity":30,"summary":55},"Tool naming","Tools are referred to by their `bdata` command names (e.g., `bdata scrape`, `bdata search`), which are descriptive within the context of the Bright Data CLI.",{"category":39,"check":57,"severity":30,"summary":58},"Minimal I/O surface","The `bdata` commands used appear to request only necessary data, and the output is structured for analysis, aligning with the skill's purpose.",{"category":60,"check":61,"severity":30,"summary":62},"License","License usability","The repository includes an MIT License file, which is a permissive open-source license.",{"category":64,"check":65,"severity":66,"summary":67},"Maintenance","Commit recency","not_applicable","The commit history is not available for this evaluation, so recency cannot be determined.",{"category":64,"check":69,"severity":66,"summary":70},"Dependency Management","No third-party dependencies are explicitly managed within this skill's code; it relies on the user having the Bright Data CLI installed.",{"category":72,"check":73,"severity":30,"summary":74},"Security","Secret Management","The skill relies on the user's pre-configured Bright Data CLI authentication, and does not handle or expose secrets directly.",{"category":72,"check":76,"severity":30,"summary":77},"Injection","The skill uses the Bright Data CLI, which is designed to handle web data securely. No direct handling of untrusted external data is evident within the skill's logic.",{"category":72,"check":79,"severity":30,"summary":80},"Transitive Supply-Chain Grenades","The skill relies on the Bright Data CLI, which is a distinct tool. The skill itself does not fetch remote content or execute arbitrary commands at runtime.",{"category":72,"check":82,"severity":30,"summary":83},"Sandbox Isolation","The skill primarily orchestrates calls to the Bright Data CLI. It does not appear to modify files outside its own scope or use absolute paths.",{"category":72,"check":85,"severity":30,"summary":86},"Sandbox escape primitives","The skill's logic involves calling the `bdata` CLI, which is assumed to be sandboxed by its own execution environment. No direct sandbox escape primitives are observed in the skill's code.",{"category":72,"check":88,"severity":30,"summary":89},"Data Exfiltration","The skill's purpose is to audit SEO and it uses the Bright Data CLI for this. There's no indication of it exfiltrating confidential data.",{"category":72,"check":91,"severity":30,"summary":92},"Hidden Text Tricks","The bundled files do not contain any hidden text tricks, invisible characters, or obfuscated instructions.",{"category":94,"check":95,"severity":30,"summary":96},"Hooks","Opaque code execution","The skill's logic is in plain shell scripts and relies on the `bdata` CLI, with no evidence of obfuscated code, base64 payloads, or runtime fetched scripts.",{"category":98,"check":99,"severity":30,"summary":100},"Portability","Structural Assumption","The skill relies on the Bright Data CLI being installed and authenticated, which is a clear precondition, and does not make assumptions about user project structure.",{"category":102,"check":103,"severity":66,"summary":104},"Trust","Issues Attention","Issue data is not available for this repository.",{"category":106,"check":107,"severity":108,"summary":109},"Versioning","Release Management","warning","There is no version specified in the SKILL.md frontmatter, package.json, or any other manifest file, and no GitHub releases or CHANGELOG are present. Install instructions in the README reference the main branch implicitly.",{"category":111,"check":112,"severity":30,"summary":113},"Code Execution","Validation","The skill orchestrates calls to the Bright Data CLI, which is expected to handle its own input validation. The skill logic itself does not appear to handle complex input validation beyond passing arguments to `bdata`.",{"category":72,"check":115,"severity":30,"summary":116},"Unguarded Destructive Operations","The skill performs read-only operations for SEO auditing and does not involve any destructive actions.",{"category":111,"check":118,"severity":30,"summary":119},"Error Handling","The skill relies on the error handling of the Bright Data CLI. Shell scripts used for orchestrating `bdata` calls are expected to exit non-zero on failure.",{"category":111,"check":121,"severity":66,"summary":122},"Logging","The skill does not perform destructive actions or outbound calls that would necessitate local audit logging. It relies on the logging capabilities of the Bright Data CLI.",{"category":124,"check":125,"severity":30,"summary":126},"Compliance","GDPR","The skill's purpose is SEO auditing and uses web scraping tools. It does not appear to operate on personal data requiring specific GDPR sanitization beyond what the Bright Data CLI handles.",{"category":124,"check":128,"severity":30,"summary":129},"Target market","The extension focuses on SEO audits, which are globally applicable. No regional-specific signals or jurisdictions are encoded in the prompts or workflow.",{"category":98,"check":131,"severity":30,"summary":132},"Runtime stability","The skill assumes the presence of the Bright Data CLI and standard shell utilities (`curl`, `grep`, `jq`), which are common. No specific OS or editor assumptions are made.",{"category":46,"check":134,"severity":30,"summary":135},"Precise Purpose","The skill's description clearly defines its purpose (SEO audit), the artifact it operates on (websites), and the user intent (diagnose SEO issues), along with specific trigger phrases and boundaries.",{"category":46,"check":137,"severity":30,"summary":138},"Concise Frontmatter","The SKILL.md frontmatter is concise and self-contained, summarizing the core capability and providing trigger phrases within a reasonable character limit.",{"category":50,"check":140,"severity":30,"summary":141},"Concise Body","The SKILL.md file is well-structured with progressive disclosure to references, keeping the main body concise and focused.",{"category":143,"check":144,"severity":30,"summary":145},"Context","Progressive Disclosure","The SKILL.md file effectively uses relative links to reference files for detailed procedures, recipes, and templates, adhering to progressive disclosure.",{"category":143,"check":147,"severity":66,"summary":148},"Forked exploration","The skill performs audits which can involve multiple steps, but it does not appear to engage in deep, open-ended code review or research that would require `context: fork`.",{"category":28,"check":150,"severity":30,"summary":151},"Usage examples","The README provides clear examples of how to use the associated `bdata` commands for search and scrape, and mentions how the competitive-intel skill integrates these.",{"category":28,"check":153,"severity":30,"summary":154},"Edge cases","The 'Hard Rules' and 'Failure Handling' sections in the documentation explicitly address edge cases like missing sitemaps, 404 errors from `bdata` calls, and the requirement to continue running lower tiers even if Tier 1 is blocked, providing recovery paths.",{"category":111,"check":156,"severity":66,"summary":157},"Tool Fallback","The skill relies exclusively on the Bright Data CLI and does not integrate with external tools that would require fallback mechanisms.",{"category":159,"check":160,"severity":30,"summary":161},"Safety","Halt on unexpected state","The documentation explicitly states that if `bdata` is missing or unauthenticated, the skill should stop immediately and point the user to prerequisites, indicating a halt on unexpected pre-state.",{"category":98,"check":163,"severity":30,"summary":164},"Cross-skill coupling","The skill is self-contained and focuses on SEO audits using the Bright Data CLI. It explicitly mentions related skills for installation (`brightdata-cli`) and specific tasks (`scrape`, `search`) without implying a dependency on them being loaded concurrently.",1778054317578,"This skill performs detailed SEO audits by utilizing the Bright Data CLI to fetch live web data. It can detect JavaScript-injected schema, validate hreflang attributes, analyze canonical tags, and perform SERP-based ranking checks. The tool supports both single-page deep audits and site-wide audits, using stratified sampling and providing actionable recommendations with evidence cited from `bdata` commands.","2.0.0","3.4.0","The extension is highly polished, with excellent documentation and a clear, focused purpose. The use of the Bright Data CLI is well-integrated, and the audit process is comprehensive. The only minor issue is the lack of a specific version, which is flagged as a warning.",95,"A comprehensive SEO audit tool leveraging the Bright Data CLI for live web data analysis.",[15,16,17,18,19,20],"global","verified",{"codeQuality":176,"collectedAt":177,"documentation":178,"maintenance":180,"security":181,"testCoverage":183},{},1778054304135,{"descriptionLength":179,"readmeSize":8},839,{},{"hasNpmPackage":182,"smitheryVerified":182},false,{"hasCi":182,"hasTests":182},{"updatedAt":185},1778054318963,{"githubOwner":17,"githubRepo":187,"locale":24,"slug":188,"type":189},"skills","seo-audit","skill",true,{"_creationTime":192,"_id":193,"community":194,"display":195,"identity":208,"parentExtension":211,"providers":238,"relations":243,"workflow":244},1778054268187.776,"k177secs2fy2665c3z8prspg0s867xd1",{"reviewCount":8},{"description":196,"installMethods":197,"name":198,"sourceUrl":199,"tags":200},"Web scraping, Google search, structured data extraction, and MCP server integration powered by Bright Data. Includes 11 skills: scrape any webpage as markdown (with bot detection/CAPTCHA bypass), search Google with structured JSON results, extract data from 40+ websites (Amazon, LinkedIn, Instagram, TikTok, YouTube, and more), orchestrate Bright Data's 60+ MCP tools, Bright Data CLI for terminal-based scraping/search/data extraction/zone management, real-time competitive intelligence (competitor snapshots, pricing comparison, review mining, hiring signals, market landscape mapping), built-in best practices for Web Unlocker, SERP API, Web Scraper API, and Browser API, Python SDK best practices for the brightdata-sdk package, scraper builder for any website, design system mirroring, and Browser API session debugging.",{},"Bright Data Plugin for Claude Code","https://github.com/brightdata/skills",[201,202,203,204,205,18,206,207],"web-scraping","data-extraction","search","mcp","bright-data","competitive-intelligence","python-sdk",{"githubOwner":17,"githubRepo":187,"locale":24,"slug":209,"type":210},"brightdata-plugin","plugin",{"_creationTime":212,"_id":213,"community":214,"display":215,"identity":221,"providers":224,"relations":233,"workflow":235},1778054268187.7754,"k17f4hb22c0s5mwjyyx9xtwwen86727s",{"reviewCount":8},{"description":216,"installMethods":217,"name":218,"sourceUrl":199,"tags":219},"Official Bright Data plugin for Claude Code - Web scraping, search, structured data extraction, and Python SDK",{},"Bright Data Plugin",[201,203,202,207,18,204,17,220],"api",{"githubOwner":17,"githubRepo":187,"locale":24,"slug":222,"type":223},"brightdata-plugins","marketplace",{"extract":225,"llm":231},{"commitSha":226,"license":227,"marketplace":228},"d0eeb1fbab809ffffe7c270186bd3eb78cf0c8ba","MIT",{"name":222,"pluginCount":229,"version":230},1,"1.6.0",{"promptVersionExtension":167,"promptVersionScoring":168,"score":232,"targetMarket":173,"tier":174},98,{"repoId":234},"kd7e4q3ah25vmt87x67vanphhn864r9h",{"anyEnrichmentAt":236,"extractAt":237,"githubAt":236,"llmAt":185,"updatedAt":185},1778054269540,1778054268187,{"extract":239,"llm":240},{"commitSha":226,"license":227},{"promptVersionExtension":167,"promptVersionScoring":168,"score":241,"targetMarket":173,"tier":242},65,"flagged",{"parentExtensionId":213,"repoId":234},{"anyEnrichmentAt":236,"extractAt":237,"githubAt":236,"llmAt":185,"updatedAt":185},{"extract":246,"llm":247},{"commitSha":226,"license":227},{"promptVersionExtension":167,"promptVersionScoring":168,"score":170,"targetMarket":173,"tier":174},{"parentExtensionId":193,"repoId":234},{"_creationTime":250,"_id":234,"identity":251,"providers":252,"workflow":266},1777995558409.835,{"githubOwner":17,"githubRepo":187,"sourceUrl":199},{"discover":253,"github":257},{"sources":254},[255,256],"skills-sh","vskill",{"closedIssues90d":258,"forks":259,"homepage":260,"license":227,"openIssues90d":261,"pushedAt":262,"readmeSize":263,"stars":264,"topics":265},3,19,"https://skills.sh/brightdata",4,1777367346000,36677,111,[],{"discoverAt":267,"extractAt":268,"githubAt":268,"updatedAt":268},1777995558409,1778054276871,{"anyEnrichmentAt":236,"extractAt":237,"githubAt":236,"llmAt":185,"updatedAt":185},[],[272,293,310,337,358,378],{"_creationTime":273,"_id":274,"community":275,"display":276,"identity":285,"providers":287,"relations":291,"workflow":292},1778054268187.7783,"k1799kwx7k8g1vx165qr4np3298670sw",{"reviewCount":8},{"description":277,"installMethods":278,"name":279,"sourceUrl":280,"tags":281},"Guide for using the Bright Data CLI (`brightdata` / `bdata`) to scrape websites, search the web, extract structured data from 40+ platforms, manage proxy zones, and check account budget. Use this skill whenever the user wants to scrape a URL, search Google/Bing/Yandex, extract data from Amazon/LinkedIn/Instagram/TikTok/YouTube/Reddit or any other platform, check their Bright Data balance or zones, or do anything involving web data collection from the terminal. Also trigger when the user mentions brightdata, bdata, web scraping CLI, SERP API, or wants to install Bright Data skills into their coding agent.",{},"Bright Data CLI","https://github.com/brightdata/skills/tree/HEAD/skills/brightdata-cli",[17,18,201,202,282,283,284],"serp-api","automation","terminal",{"githubOwner":17,"githubRepo":187,"locale":24,"slug":286,"type":189},"brightdata-cli",{"extract":288,"llm":289},{"commitSha":226,"license":227},{"promptVersionExtension":167,"promptVersionScoring":168,"score":290,"targetMarket":173,"tier":174},99,{"parentExtensionId":193,"repoId":234},{"anyEnrichmentAt":236,"extractAt":237,"githubAt":236,"llmAt":185,"updatedAt":185},{"_creationTime":294,"_id":295,"community":296,"display":297,"identity":304,"providers":305,"relations":308,"workflow":309},1778054268187.7817,"k1771h37s3zz945hdh08zdmkm1866n54",{"reviewCount":8},{"description":298,"installMethods":299,"name":300,"sourceUrl":301,"tags":302},"Search the web via the Bright Data CLI — `bdata search` for Google/Bing/Yandex SERP, `bdata discover` for intent-ranked semantic results. Use when the user wants SERP results, needs URLs to feed into scraping, or wants semantic web discovery with optional page content. Hands off to `scrape` once target URLs are chosen, and to `data-feeds` when the user wants structured data from a known platform. Requires the Bright Data CLI; proactively guides install + login if missing.",{},"Bright Data — Search","https://github.com/brightdata/skills/tree/HEAD/skills/search",[17,18,203,201,303,15],"discovery",{"githubOwner":17,"githubRepo":187,"locale":24,"slug":203,"type":189},{"extract":306,"llm":307},{"commitSha":226,"license":227},{"promptVersionExtension":167,"promptVersionScoring":168,"score":170,"targetMarket":173,"tier":174},{"parentExtensionId":193,"repoId":234},{"anyEnrichmentAt":236,"extractAt":237,"githubAt":236,"llmAt":185,"updatedAt":185},{"_creationTime":311,"_id":312,"community":313,"display":314,"identity":323,"providers":326,"relations":331,"workflow":333},1778054123074.251,"k179s5hjesm00qgha5rrnfmcrx8679v0",{"reviewCount":8},{"description":315,"installMethods":316,"name":317,"sourceUrl":318,"tags":319},"Run a comprehensive SEO audit on a website covering technical health, on-page optimization, content quality, and backlink profile. Use when the user asks for an SEO audit, site review, SEO health check, \"what's wrong with my SEO\", website analysis, or a full diagnostic of their site's search performance. For speed-specific issues, see audit-speed. For technical crawl/index issues only, see diagnose-seo.",{},"SEO Audit","https://github.com/calm-north/seojuice-skills/tree/HEAD/skills/audit",[15,16,320,321,322],"website-analysis","content-optimization","technical-seo",{"githubOwner":324,"githubRepo":325,"locale":24,"slug":16,"type":189},"calm-north","seojuice-skills",{"extract":327,"llm":330},{"commitSha":328,"license":329},"c1f633bea512365ba04477076369e418ecc82ffd","MIT-0",{"promptVersionExtension":167,"promptVersionScoring":168,"score":170,"targetMarket":173,"tier":174},{"repoId":332},"kd77p09fwtcsr2sfmxw6921ek1864v0a",{"anyEnrichmentAt":334,"extractAt":335,"githubAt":334,"llmAt":336,"updatedAt":336},1778054123513,1778054123074,1778054162250,{"_creationTime":338,"_id":339,"community":340,"display":341,"identity":351,"providers":353,"relations":356,"workflow":357},1778054123074.2515,"k17an427chh58vrfr9bqc9zfa5867a4z",{"reviewCount":8},{"description":342,"installMethods":343,"name":344,"sourceUrl":345,"tags":346},"Deep Core Web Vitals and page speed audit. Use when the user asks about page speed, Core Web Vitals, LCP, CLS, INP, FCP, TTFB, Lighthouse scores, why a page is slow, performance optimization, or resource size analysis. For broader technical SEO issues, see diagnose-seo.",{},"Audit Speed","https://github.com/calm-north/seojuice-skills/tree/HEAD/skills/audit-speed",[15,347,348,349,350,16],"performance","web-vitals","lighthouse","optimization",{"githubOwner":324,"githubRepo":325,"locale":24,"slug":352,"type":189},"audit-speed",{"extract":354,"llm":355},{"commitSha":328,"license":227},{"promptVersionExtension":167,"promptVersionScoring":168,"score":170,"targetMarket":173,"tier":174},{"repoId":332},{"anyEnrichmentAt":334,"extractAt":335,"githubAt":334,"llmAt":336,"updatedAt":336},{"_creationTime":359,"_id":360,"community":361,"display":362,"identity":371,"providers":373,"relations":376,"workflow":377},1778054268187.7769,"k172m64tv232jy9hym6z4dt68d866pke",{"reviewCount":8},{"description":363,"installMethods":364,"name":365,"sourceUrl":366,"tags":367},"Debug Bright Data Scraping Browser sessions using the Browser Sessions API. Use this skill when the user encounters a Bright Data browser session error, puppeteer stack trace, failed scraper run, or asks about session bandwidth, duration, captchas, or connection issues. Also use when a Bright Data scraper produces unexpected results such as empty data, 0 items found, missing products, or fewer results than expected — session data can reveal whether the issue is network/proxy-side (blocks, captchas, redirects, timeouts) or client-side (selectors, extraction logic). Triggers on phrases like 'why did my session fail', 'debug my bright data session', 'check my scraping browser sessions', 'how much bandwidth did my scraper use', 'got 0 results', 'found 0', 'scraper returned empty', 'scraper not working', 'script didn't work', or when a Bright Data error code or brd.superproxy.io stack trace appears in the conversation. Requires BRIGHTDATA_API_KEY environment variable.",{},"Bright Data — Browser Session Debugger","https://github.com/brightdata/skills/tree/HEAD/skills/brd-browser-debug",[17,19,368,220,369,370],"debugging","browser-automation","session-analysis",{"githubOwner":17,"githubRepo":187,"locale":24,"slug":372,"type":189},"brd-browser-debug",{"extract":374,"llm":375},{"commitSha":226,"license":329},{"promptVersionExtension":167,"promptVersionScoring":168,"score":170,"targetMarket":173,"tier":174},{"parentExtensionId":193,"repoId":234},{"anyEnrichmentAt":236,"extractAt":237,"githubAt":236,"llmAt":185,"updatedAt":185},{"_creationTime":379,"_id":380,"community":381,"display":382,"identity":393,"providers":395,"relations":401,"workflow":403},1778054586606.9207,"k17dgzjgvsrbv3nsbp0kz4c1ax8665ww",{"reviewCount":8},{"description":383,"installMethods":384,"name":385,"sourceUrl":386,"tags":387},"Vercel filesystem detectors",{},"Vercel Filesystem Detectors","https://github.com/vercel/vercel/tree/HEAD/packages/fs-detectors",[388,389,390,391,18,392],"vercel","build-system","framework-detection","monorepo","utility",{"githubOwner":388,"githubRepo":388,"locale":24,"slug":394,"type":189},"vercel-fs-detectors",{"extract":396,"llm":399},{"commitSha":397,"license":398},"da93fccb68ef705f866ddb8d4ff596495589442a","Apache-2.0",{"promptVersionExtension":167,"promptVersionScoring":168,"score":400,"targetMarket":173,"tier":174},100,{"repoId":402},"kd70sna36fh1a450f5r7e0f8p986555e",{"anyEnrichmentAt":404,"extractAt":405,"githubAt":404,"llmAt":406,"updatedAt":406},1778054590995,1778054586606,1778054733091]