AGENT SKILL

seo-fundamentals

Core principles of SEO including E-E-A-T, Core Web Vitals, technical foundations, content quality, and how modern search engines evaluate pages.

License 许可
MIT
最近更新
2026-11-10
Stars
★ 1
Forks
0

01 前言 Front Matter

name
seo-fundamentals
risk
safe
source
community
date_added
2026-02-27
description
Core principles of SEO including E-E-A-T, Core Web Vitals, technical foundations, content quality, and how modern search engines evaluate pages.

02 资源文件 1

03 SKILL.md 正文


SEO Fundamentals

Foundational principles for sustainable search visibility. This skill explains how search engines evaluate quality, not tactical shortcuts.


1. E-E-A-T (Quality Evaluation Framework)

E-E-A-T is not a direct ranking factor. It is a framework used by search engines to evaluate content quality, especially for sensitive or high-impact topics.

Dimension What It Represents Common Signals
Experience First-hand, real-world involvement Original examples, lived experience, demonstrations
Expertise Subject-matter competence Credentials, depth, accuracy
Authoritativeness Recognition by others Mentions, citations, links
Trustworthiness Reliability and safety HTTPS, transparency, accuracy

Pages competing in the same space are often differentiated by trust and experience, not keywords.


2. Core Web Vitals (Page Experience Signals)

Core Web Vitals measure how users experience a page, not whether it deserves to rank.

Metric Target What It Reflects
LCP < 2.5s Loading performance
INP < 200ms Interactivity
CLS < 0.1 Visual stability

Important context:

  • CWV rarely override poor content
  • They matter most when content quality is comparable
  • Failing CWV can hold back otherwise good pages

3. Technical SEO Principles

Technical SEO ensures pages are accessible, understandable, and stable.

Crawl & Index Control

Element Purpose
XML sitemaps Help discovery
robots.txt Control crawl access
Canonical tags Consolidate duplicates
HTTP status codes Communicate page state
HTTPS Security and trust

Performance & Accessibility

Factor Why It Matters
Page speed User satisfaction
Mobile-friendly design Mobile-first indexing
Clean URLs Crawl clarity
Semantic HTML Accessibility & understanding

4. Content SEO Principles

Page-Level Elements

Element Principle
Title tag Clear topic + intent
Meta description Click relevance, not ranking
H1 Page’s primary subject
Headings Logical structure
Alt text Accessibility and context

Content Quality Signals

Dimension What Search Engines Look For
Depth Fully answers the query
Originality Adds unique value
Accuracy Factually correct
Clarity Easy to understand
Usefulness Satisfies intent

5. Structured Data (Schema)

Structured data helps search engines understand meaning, not boost rankings directly.

Type Purpose
Article Content classification
Organization Entity identity
Person Author information
FAQPage Q&A clarity
Product Commerce details
Review Ratings context
BreadcrumbList Site structure

Schema enables eligibility for rich results but does not guarantee them.


6. AI-Assisted Content Principles

Search engines evaluate output quality, not authorship method.

Effective Use

  • AI as a drafting or research assistant
  • Human review for accuracy and clarity
  • Original insights and synthesis
  • Clear accountability

Risky Use

  • Publishing unedited AI output
  • Factual errors or hallucinations
  • Thin or duplicated content
  • Keyword-driven text with no value

7. Relative Importance of SEO Factors

There is no fixed ranking factor order. However, when competing pages are similar, importance tends to follow this pattern:

Relative Weight Factor
Highest Content relevance & quality
High Authority & trust signals
Medium Page experience (CWV, UX)
Medium Mobile optimization
Baseline Technical accessibility

Technical SEO enables ranking; content quality earns it.


8. Measurement & Evaluation

SEO fundamentals should be validated using multiple signals, not single metrics.

Area What to Observe
Visibility Indexed pages, impressions
Engagement Click-through, dwell time
Performance CWV field data
Coverage Indexing status
Authority Mentions and links

Key Principle: Sustainable SEO is built on useful content, technical clarity, and trust over time. There are no permanent shortcuts.

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

04 同仓库更多 Skills

YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

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.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

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.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

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.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

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/site/platform", 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.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

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.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

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/ui, 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/ui.

★ 1