[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C49PYVTWSJ82TSJCACX56G":3,"skill-same:01M7C49PYVTWSJ82TSJCACX56G":56},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7C49PYVTWSJ82TSJCACX56G","seo-fundamentals",null,"Core principles of SEO including E-E-A-T, Core Web Vitals, technical foundations, content quality, and how modern search engines evaluate pages.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fseo-fundamentals\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: seo-fundamentals\ndescription: Core principles of SEO including E-E-A-T, Core Web Vitals, technical foundations, content quality, and how modern search engines evaluate pages.\nrisk: safe\nsource: community\ndate_added: '2026-02-27'\n---\n\n---\n\n# SEO Fundamentals\n\n> **Foundational principles for sustainable search visibility.**\n> This skill explains _how search engines evaluate quality_, not tactical shortcuts.\n\n---\n\n## 1. E-E-A-T (Quality Evaluation Framework)\n\nE-E-A-T is **not a direct ranking factor**.\nIt is a framework used by search engines to **evaluate content quality**, especially for sensitive or high-impact topics.\n\n| Dimension             | What It Represents                 | Common Signals                                      |\n| --------------------- | ---------------------------------- | --------------------------------------------------- |\n| **Experience**        | First-hand, real-world involvement | Original examples, lived experience, demonstrations |\n| **Expertise**         | Subject-matter competence          | Credentials, depth, accuracy                        |\n| **Authoritativeness** | Recognition by others              | Mentions, citations, links                          |\n| **Trustworthiness**   | Reliability and safety             | HTTPS, transparency, accuracy                       |\n\n> Pages competing in the same space are often differentiated by **trust and experience**, not keywords.\n\n---\n\n## 2. Core Web Vitals (Page Experience Signals)\n\nCore Web Vitals measure **how users experience a page**, not whether it deserves to rank.\n\n| Metric  | Target  | What It Reflects    |\n| ------- | ------- | ------------------- |\n| **LCP** | \u003C 2.5s  | Loading performance |\n| **INP** | \u003C 200ms | Interactivity       |\n| **CLS** | \u003C 0.1   | Visual stability    |\n\n**Important context:**\n\n- CWV rarely override poor content\n- They matter most when content quality is comparable\n- Failing CWV can _hold back_ otherwise good pages\n\n---\n\n## 3. Technical SEO Principles\n\nTechnical SEO ensures pages are **accessible, understandable, and stable**.\n\n### Crawl & Index Control\n\n| Element           | Purpose                |\n| ----------------- | ---------------------- |\n| XML sitemaps      | Help discovery         |\n| robots.txt        | Control crawl access   |\n| Canonical tags    | Consolidate duplicates |\n| HTTP status codes | Communicate page state |\n| HTTPS             | Security and trust     |\n\n### Performance & Accessibility\n\n| Factor                 | Why It Matters                |\n| ---------------------- | ----------------------------- |\n| Page speed             | User satisfaction             |\n| Mobile-friendly design | Mobile-first indexing         |\n| Clean URLs             | Crawl clarity                 |\n| Semantic HTML          | Accessibility & understanding |\n\n---\n\n## 4. Content SEO Principles\n\n### Page-Level Elements\n\n| Element          | Principle                    |\n| ---------------- | ---------------------------- |\n| Title tag        | Clear topic + intent         |\n| Meta description | Click relevance, not ranking |\n| H1               | Page’s primary subject       |\n| Headings         | Logical structure            |\n| Alt text         | Accessibility and context    |\n\n### Content Quality Signals\n\n| Dimension   | What Search Engines Look For |\n| ----------- | ---------------------------- |\n| Depth       | Fully answers the query      |\n| Originality | Adds unique value            |\n| Accuracy    | Factually correct            |\n| Clarity     | Easy to understand           |\n| Usefulness  | Satisfies intent             |\n\n---\n\n## 5. Structured Data (Schema)\n\nStructured data helps search engines **understand meaning**, not boost rankings directly.\n\n| Type           | Purpose                |\n| -------------- | ---------------------- |\n| Article        | Content classification |\n| Organization   | Entity identity        |\n| Person         | Author information     |\n| FAQPage        | Q&A clarity            |\n| Product        | Commerce details       |\n| Review         | Ratings context        |\n| BreadcrumbList | Site structure         |\n\n> Schema enables eligibility for rich results but does not guarantee them.\n\n---\n\n## 6. AI-Assisted Content Principles\n\nSearch engines evaluate **output quality**, not authorship method.\n\n### Effective Use\n\n- AI as a drafting or research assistant\n- Human review for accuracy and clarity\n- Original insights and synthesis\n- Clear accountability\n\n### Risky Use\n\n- Publishing unedited AI output\n- Factual errors or hallucinations\n- Thin or duplicated content\n- Keyword-driven text with no value\n\n---\n\n## 7. Relative Importance of SEO Factors\n\nThere is **no fixed ranking factor order**.\nHowever, when competing pages are similar, importance tends to follow this pattern:\n\n| Relative Weight | Factor                      |\n| --------------- | --------------------------- |\n| Highest         | Content relevance & quality |\n| High            | Authority & trust signals   |\n| Medium          | Page experience (CWV, UX)   |\n| Medium          | Mobile optimization         |\n| Baseline        | Technical accessibility     |\n\n> Technical SEO enables ranking; content quality earns it.\n\n---\n\n## 8. Measurement & Evaluation\n\nSEO fundamentals should be validated using **multiple signals**, not single metrics.\n\n| Area        | What to Observe            |\n| ----------- | -------------------------- |\n| Visibility  | Indexed pages, impressions |\n| Engagement  | Click-through, dwell time  |\n| Performance | CWV field data             |\n| Coverage    | Indexing status            |\n| Authority   | Mentions and links         |\n\n---\n\n> **Key Principle:**\n> Sustainable SEO is built on _useful content_, _technical clarity_, and _trust over time_.\n> There are no permanent shortcuts.\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\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","---\n\n# SEO Fundamentals\n\n> **Foundational principles for sustainable search visibility.**\n> This skill explains _how search engines evaluate quality_, not tactical shortcuts.\n\n---\n\n## 1. E-E-A-T (Quality Evaluation Framework)\n\nE-E-A-T is **not a direct ranking factor**.\nIt is a framework used by search engines to **evaluate content quality**, especially for sensitive or high-impact topics.\n\n| Dimension             | What It Represents                 | Common Signals                                      |\n| --------------------- | ---------------------------------- | --------------------------------------------------- |\n| **Experience**        | First-hand, real-world involvement | Original examples, lived experience, demonstrations |\n| **Expertise**         | Subject-matter competence          | Credentials, depth, accuracy                        |\n| **Authoritativeness** | Recognition by others              | Mentions, citations, links                          |\n| **Trustworthiness**   | Reliability and safety             | HTTPS, transparency, accuracy                       |\n\n> Pages competing in the same space are often differentiated by **trust and experience**, not keywords.\n\n---\n\n## 2. Core Web Vitals (Page Experience Signals)\n\nCore Web Vitals measure **how users experience a page**, not whether it deserves to rank.\n\n| Metric  | Target  | What It Reflects    |\n| ------- | ------- | ------------------- |\n| **LCP** | \u003C 2.5s  | Loading performance |\n| **INP** | \u003C 200ms | Interactivity       |\n| **CLS** | \u003C 0.1   | Visual stability    |\n\n**Important context:**\n\n- CWV rarely override poor content\n- They matter most when content quality is comparable\n- Failing CWV can _hold back_ otherwise good pages\n\n---\n\n## 3. Technical SEO Principles\n\nTechnical SEO ensures pages are **accessible, understandable, and stable**.\n\n### Crawl & Index Control\n\n| Element           | Purpose                |\n| ----------------- | ---------------------- |\n| XML sitemaps      | Help discovery         |\n| robots.txt        | Control crawl access   |\n| Canonical tags    | Consolidate duplicates |\n| HTTP status codes | Communicate page state |\n| HTTPS             | Security and trust     |\n\n### Performance & Accessibility\n\n| Factor                 | Why It Matters                |\n| ---------------------- | ----------------------------- |\n| Page speed             | User satisfaction             |\n| Mobile-friendly design | Mobile-first indexing         |\n| Clean URLs             | Crawl clarity                 |\n| Semantic HTML          | Accessibility & understanding |\n\n---\n\n## 4. Content SEO Principles\n\n### Page-Level Elements\n\n| Element          | Principle                    |\n| ---------------- | ---------------------------- |\n| Title tag        | Clear topic + intent         |\n| Meta description | Click relevance, not ranking |\n| H1               | Page’s primary subject       |\n| Headings         | Logical structure            |\n| Alt text         | Accessibility and context    |\n\n### Content Quality Signals\n\n| Dimension   | What Search Engines Look For |\n| ----------- | ---------------------------- |\n| Depth       | Fully answers the query      |\n| Originality | Adds unique value            |\n| Accuracy    | Factually correct            |\n| Clarity     | Easy to understand           |\n| Usefulness  | Satisfies intent             |\n\n---\n\n## 5. Structured Data (Schema)\n\nStructured data helps search engines **understand meaning**, not boost rankings directly.\n\n| Type           | Purpose                |\n| -------------- | ---------------------- |\n| Article        | Content classification |\n| Organization   | Entity identity        |\n| Person         | Author information     |\n| FAQPage        | Q&A clarity            |\n| Product        | Commerce details       |\n| Review         | Ratings context        |\n| BreadcrumbList | Site structure         |\n\n> Schema enables eligibility for rich results but does not guarantee them.\n\n---\n\n## 6. AI-Assisted Content Principles\n\nSearch engines evaluate **output quality**, not authorship method.\n\n### Effective Use\n\n- AI as a drafting or research assistant\n- Human review for accuracy and clarity\n- Original insights and synthesis\n- Clear accountability\n\n### Risky Use\n\n- Publishing unedited AI output\n- Factual errors or hallucinations\n- Thin or duplicated content\n- Keyword-driven text with no value\n\n---\n\n## 7. Relative Importance of SEO Factors\n\nThere is **no fixed ranking factor order**.\nHowever, when competing pages are similar, importance tends to follow this pattern:\n\n| Relative Weight | Factor                      |\n| --------------- | --------------------------- |\n| Highest         | Content relevance & quality |\n| High            | Authority & trust signals   |\n| Medium          | Page experience (CWV, UX)   |\n| Medium          | Mobile optimization         |\n| Baseline        | Technical accessibility     |\n\n> Technical SEO enables ranking; content quality earns it.\n\n---\n\n## 8. Measurement & Evaluation\n\nSEO fundamentals should be validated using **multiple signals**, not single metrics.\n\n| Area        | What to Observe            |\n| ----------- | -------------------------- |\n| Visibility  | Indexed pages, impressions |\n| Engagement  | Click-through, dwell time  |\n| Performance | CWV field data             |\n| Coverage    | Indexing status            |\n| Authority   | Mentions and links         |\n\n---\n\n> **Key Principle:**\n> Sustainable SEO is built on _useful content_, _technical clarity_, and _trust over time_.\n> There are no permanent shortcuts.\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\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":24,"source":25,"date_added":26,"description":7},"safe","community","2026-02-27","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fseo-fundamentals",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill seo-fundamentals",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill seo-fundamentals",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill seo-fundamentals","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fseo-fundamentals\u002FSKILL.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"scripts\u002Fseo_checker.py","SCRIPT","脚本",6584,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fseo-fundamentals\u002Fscripts\u002Fseo_checker.py",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]