[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72A40HAWYW837WBFSQYV22C":3,"skill-same:01M72A40HAWYW837WBFSQYV22C":54},{"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":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":13,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":40,"install":41,"resources":53},"01M72A40HAWYW837WBFSQYV22C","seo-page",null,"Deep single-page SEO analysis covering on-page elements, content quality, technical meta tags, schema, images, and performance. Use when user says \"analyze this page\", \"check page SEO\", or provides a single URL for review.","Sansar35\u002Fclaude-agent","Sansar35","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145020281?v=4","01M724CQ2SCC86MGNSD87D0D4K","01M724CQ3965G9WJ3QXE3AJ5YY",1,"MIT","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fantigravity\u002Fseo-page\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: seo-page\ndescription: >\n  Deep single-page SEO analysis covering on-page elements, content quality,\n  technical meta tags, schema, images, and performance. Use when user says\n  \"analyze this page\", \"check page SEO\", or provides a single URL for review.\nrisk: safe\nsource: \"https:\u002F\u002Fgithub.com\u002FAgriciDaniel\u002Fclaude-seo\"\ndate_added: \"2026-03-21\"\nuser-invokable: true\nargument-hint: \"[url]\"\nallowed-tools:\n  - Read\n  - Grep\n  - Glob\n  - Bash\n  - WebFetch\n---\n\n# Single Page Analysis\n\n## When to Use\n- Use when the user provides a single URL for detailed on-page SEO review.\n- Use when auditing one page rather than an entire site.\n- Use when checking metadata, content, schema, images, and page-level technical signals together.\n\n## What to Analyze\n\n### On-Page SEO\n- Title tag: 50-60 characters, includes primary keyword, unique\n- Meta description: 150-160 characters, compelling, includes keyword\n- H1: exactly one, matches page intent, includes keyword\n- H2-H6: logical hierarchy (no skipped levels), descriptive\n- URL: short, descriptive, hyphenated, no parameters\n- Internal links: sufficient, relevant anchor text, no orphan pages\n- External links: to authoritative sources, reasonable count\n\n### Content Quality\n- Word count vs page type minimums (see quality-gates.md)\n- Readability: Flesch Reading Ease score, grade level\n- Keyword density: natural (1-3%), semantic variations present\n- E-E-A-T signals: author bio, credentials, first-hand experience markers\n- Content freshness: publication date, last updated date\n\n### Technical Elements\n- Canonical tag: present, self-referencing or correct\n- Meta robots: index\u002Ffollow unless intentionally blocked\n- Open Graph: og:title, og:description, og:image, og:url\n- Twitter Card: twitter:card, twitter:title, twitter:description\n- Hreflang: if multi-language, correct implementation\n\n### Schema Markup\n- Detect all types (JSON-LD preferred)\n- Validate required properties\n- Identify missing opportunities\n- NEVER recommend HowTo (deprecated) or FAQ (restricted to gov\u002Fhealth)\n\n### Images\n- Alt text: present, descriptive, includes keywords where natural\n- File size: flag >200KB (warning), >500KB (critical)\n- Format: recommend WebP\u002FAVIF over JPEG\u002FPNG\n- Dimensions: width\u002Fheight set for CLS prevention\n- Lazy loading: loading=\"lazy\" on below-fold images\n\n### Core Web Vitals (reference only, not measurable from HTML alone)\n- Flag potential LCP issues (huge hero images, render-blocking resources)\n- Flag potential INP issues (heavy JS, no async\u002Fdefer)\n- Flag potential CLS issues (missing image dimensions, injected content)\n\n## Output\n\n### Page Score Card\n```\nOverall Score: XX\u002F100\n\nOn-Page SEO:     XX\u002F100  ████████░░\nContent Quality: XX\u002F100  ██████████\nTechnical:       XX\u002F100  ███████░░░\nSchema:          XX\u002F100  █████░░░░░\nImages:          XX\u002F100  ████████░░\n```\n\n### Issues Found\nOrganized by priority: Critical -> High -> Medium -> Low\n\n### Recommendations\nSpecific, actionable improvements with expected impact\n\n### Schema Suggestions\nReady-to-use JSON-LD code for detected opportunities\n\n## DataForSEO Integration (Optional)\n\nIf DataForSEO MCP tools are available, use `serp_organic_live_advanced` for real SERP positions and `backlinks_summary` for backlink data and spam scores.\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess page content. Suggest the user verify the URL and try again. |\n| Page requires authentication (401\u002F403) | Report that the page is behind authentication. Suggest the user provide the rendered HTML directly or a publicly accessible URL. |\n| JavaScript-rendered content (empty body in HTML) | Note that key content may be rendered client-side. Analyze the available HTML and flag that results may be incomplete. Suggest using a browser-rendered snapshot if available. |\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# Single Page Analysis\n\n## When to Use\n- Use when the user provides a single URL for detailed on-page SEO review.\n- Use when auditing one page rather than an entire site.\n- Use when checking metadata, content, schema, images, and page-level technical signals together.\n\n## What to Analyze\n\n### On-Page SEO\n- Title tag: 50-60 characters, includes primary keyword, unique\n- Meta description: 150-160 characters, compelling, includes keyword\n- H1: exactly one, matches page intent, includes keyword\n- H2-H6: logical hierarchy (no skipped levels), descriptive\n- URL: short, descriptive, hyphenated, no parameters\n- Internal links: sufficient, relevant anchor text, no orphan pages\n- External links: to authoritative sources, reasonable count\n\n### Content Quality\n- Word count vs page type minimums (see quality-gates.md)\n- Readability: Flesch Reading Ease score, grade level\n- Keyword density: natural (1-3%), semantic variations present\n- E-E-A-T signals: author bio, credentials, first-hand experience markers\n- Content freshness: publication date, last updated date\n\n### Technical Elements\n- Canonical tag: present, self-referencing or correct\n- Meta robots: index\u002Ffollow unless intentionally blocked\n- Open Graph: og:title, og:description, og:image, og:url\n- Twitter Card: twitter:card, twitter:title, twitter:description\n- Hreflang: if multi-language, correct implementation\n\n### Schema Markup\n- Detect all types (JSON-LD preferred)\n- Validate required properties\n- Identify missing opportunities\n- NEVER recommend HowTo (deprecated) or FAQ (restricted to gov\u002Fhealth)\n\n### Images\n- Alt text: present, descriptive, includes keywords where natural\n- File size: flag >200KB (warning), >500KB (critical)\n- Format: recommend WebP\u002FAVIF over JPEG\u002FPNG\n- Dimensions: width\u002Fheight set for CLS prevention\n- Lazy loading: loading=\"lazy\" on below-fold images\n\n### Core Web Vitals (reference only, not measurable from HTML alone)\n- Flag potential LCP issues (huge hero images, render-blocking resources)\n- Flag potential INP issues (heavy JS, no async\u002Fdefer)\n- Flag potential CLS issues (missing image dimensions, injected content)\n\n## Output\n\n### Page Score Card\n```\nOverall Score: XX\u002F100\n\nOn-Page SEO:     XX\u002F100  ████████░░\nContent Quality: XX\u002F100  ██████████\nTechnical:       XX\u002F100  ███████░░░\nSchema:          XX\u002F100  █████░░░░░\nImages:          XX\u002F100  ████████░░\n```\n\n### Issues Found\nOrganized by priority: Critical -> High -> Medium -> Low\n\n### Recommendations\nSpecific, actionable improvements with expected impact\n\n### Schema Suggestions\nReady-to-use JSON-LD code for detected opportunities\n\n## DataForSEO Integration (Optional)\n\nIf DataForSEO MCP tools are available, use `serp_organic_live_advanced` for real SERP positions and `backlinks_summary` for backlink data and spam scores.\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess page content. Suggest the user verify the URL and try again. |\n| Page requires authentication (401\u002F403) | Report that the page is behind authentication. Suggest the user provide the rendered HTML directly or a publicly accessible URL. |\n| JavaScript-rendered content (empty body in HTML) | Note that key content may be rendered client-side. Analyze the available HTML and flag that results may be incomplete. Suggest using a browser-rendered snapshot if available. |\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":23,"source":24,"date_added":25,"description":26,"allowed-tools":27,"argument-hint":33,"user-invokable":34},"safe","https:\u002F\u002Fgithub.com\u002FAgriciDaniel\u002Fclaude-seo","2026-03-21","Deep single-page SEO analysis covering on-page elements, content quality, technical meta tags, schema, images, and performance. Use when user says \"analyze this page\", \"check page SEO\", or provides a single URL for review.\n",[28,29,30,31,32],"Read","Grep","Glob","Bash","WebFetch","[url]",true,"main","d046d088ce5a79a083f0abc0fe1b7ded73bc5b1f","claude-config\u002Fskills\u002Fantigravity\u002Fseo-page","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent","https:\u002F\u002Fgithub.com\u002FSansar35","2026-05-10 16:04:53",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":34},[43,46,49],{"tool":44,"command":45},"npx","npx skills add Sansar35\u002Fclaude-agent --skill seo-page",{"tool":47,"command":48},"bunx","bunx skills add Sansar35\u002Fclaude-agent --skill seo-page",{"tool":50,"command":51},"pnpm","pnpm dlx skills add Sansar35\u002Fclaude-agent --skill seo-page","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fantigravity\u002Fseo-page\u002FSKILL.md",[],[55,62,69,76,83,91],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M72DVAN1JYEA302MT0C5MGD6","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M72DV8J5NBRRM4RPDFRV95N7","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M72DV5EMHW0BHP9BZ167MDCB","zinc-database","Access ZINC (230M+ purchasable compounds). Search by ZINC ID\u002FSMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzinc-database\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M72DV216QY0E693ZPEVQ0DBS","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M72DTXQREMCRKA8NHCVKHN4W","zapier-workflows","Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to \"run\" any process. Also handles Perplexity-based research and Google Sheets data tracking.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M72DTT17TBSJ0Y8J2XZ4C9TZ","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[]]