SEO Validate
softspark/ai-toolkit
SEO validator: meta/OG, Schema.org, hreflang, Core Web Vitals, crawlability.
Meta tag patterns, structured data (JSON-LD), Core Web Vitals optimization, and SSR/SSG strategies for search visibility.
$ npx skills add vibeeval/vibecosystem --skill seo-patterns -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vibeeval/vibecosystem seo-patterns --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/seo-patterns .claude/skills/seo-patterns && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "seo-patterns" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/seo-patterns into .claude/skills/seo-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-patterns", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vibeeval/vibecosystem/tree/main/skills/seo-patternsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vibeeval/vibecosystem --skill seo-patterns -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vibeeval/vibecosystem seo-patterns --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/seo-patterns .agents/skills/seo-patterns && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "seo-patterns" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/seo-patterns into .agents/skills/seo-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-patterns", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vibeeval/vibecosystem --skill seo-patterns -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vibeeval/vibecosystem seo-patterns --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/seo-patterns .cursor/skills/seo-patterns && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "seo-patterns" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/seo-patterns into .cursor/skills/seo-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-patterns", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vibeeval/vibecosystem.git --path skills/seo-patterns--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vibeeval/vibecosystem --skill seo-patterns -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vibeeval/vibecosystem seo-patterns --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/seo-patterns .gemini/skills/seo-patterns && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "seo-patterns" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/seo-patterns into .gemini/skills/seo-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-patterns", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vibeeval/vibecosystem seo-patternsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vibeeval/vibecosystem --skill seo-patterns -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/seo-patterns .github/skills/seo-patterns && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "seo-patterns" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/seo-patterns into .github/skills/seo-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-patterns", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vibeeval/vibecosystem --skill seo-patterns -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vibeeval/vibecosystem seo-patterns --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/seo-patterns .opencode/skills/seo-patterns && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "seo-patterns" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/seo-patterns into .opencode/skills/seo-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-patterns", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
seo-patternsMeta tag patterns, structured data (JSON-LD), Core Web Vitals optimization, and SSR/SSG strategies for search visibility.
SEO Patterns is an agent skill from vibeeval/vibecosystem. Meta tag patterns, structured data (JSON-LD), Core Web Vitals optimization, and SSR/SSG strategies for search visibility.
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Schema markup, Web performance and On-page SEO. The repository describes itself as: AI software team for Claude Code - 138 agents, 295 skills, 73 hooks. Self-learning, multi-agent swarm, autonomous skill evolution. The licence is MIT.
Read from SKILL.md and the folder at commit 3b763b1. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
schema.orgyoutube.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
SEO Patterns loads about 2.9k tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 195 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from vibeeval/vibecosystem at commit 3b763b1, republished under its MIT licence (© vibeeval). 195 words, ~2,880 tokens.
.claude/skills/seo-patterns/SKILL.md (or your agent's skills folder).Technical SEO patterns for web applications and content sites.
// Next.js App Router metadata
import { Metadata } from 'next'
export function generateMetadata({ params }): Metadata {
const product = getProduct(params.slug)
return {
title: `${product.name} | Your App`, // 50-60 chars
description: product.summary.slice(0, 155), // 150-160 chars
alternates: {
canonical: `https://example.com/products/${params.slug}`,
languages: {
'en': `https://example.com/en/products/${params.slug}`,
'tr': `https://example.com/tr/products/${params.slug}`,
}
},
openGraph: {
title: product.name,
description: product.summary,
url: `https://example.com/products/${params.slug}`,
siteName: 'Your App',
images: [{
url: product.imageUrl,
width: 1200,
height: 630,
alt: product.name,
}],
type: 'website',
locale: 'en_US',
},
twitter: {
card: 'summary_large_image',
title: product.name,
description: product.summary,
images: [product.imageUrl],
},
robots: {
index: true,
follow: true,
'max-image-preview': 'large',
'max-snippet': -1,
}
}
}// Product schema
function ProductJsonLd({ product }: { product: Product }) {
const schema = {
'@context': 'https://schema.org',
'@type': 'Product',
name: product.name,
description: product.description,
image: product.images,
sku: product.sku,
brand: {
'@type': 'Brand',
name: product.brand,
},
offers: {
'@type': 'Offer',
url: `https://example.com/products/${product.slug}`,
priceCurrency: 'USD',
price: product.price,
availability: product.inStock
? 'https://schema.org/InStock'
: 'https://schema.org/OutOfStock',
seller: {
'@type': 'Organization',
name: 'Your App',
}
},
aggregateRating: product.reviewCount > 0 ? {
'@type': 'AggregateRating',
ratingValue: product.avgRating,
reviewCount: product.reviewCount,
} : undefined,
}
return <script type="application/ld+json">{JSON.stringify(schema)}</script>
}
// FAQ schema (wins featured snippets)
function FaqJsonLd({ faqs }: { faqs: { question: string; answer: string }[] }) {
const schema = {
'@context': 'https://schema.org',
'@type': 'FAQPage',
mainEntity: faqs.map(faq => ({
'@type': 'Question',
name: faq.question,
acceptedAnswer: {
'@type': 'Answer',
text: faq.answer,
}
}))
}
return <script type="application/ld+json">{JSON.stringify(schema)}</script>
}
// BreadcrumbList schema
function BreadcrumbJsonLd({ items }: { items: { name: string; url: string }[] }) {
const schema = {
'@context': 'https://schema.org',
'@type': 'BreadcrumbList',
itemListElement: items.map((item, i) => ({
'@type': 'ListItem',
position: i + 1,
name: item.name,
item: item.url,
}))
}
return <script type="application/ld+json">{JSON.stringify(schema)}</script>
}// LCP (Largest Contentful Paint) - Target: < 2.5s
// Priority: preload hero image, avoid lazy-loading above-fold content
import Image from 'next/image'
function HeroSection({ image }: { image: string }) {
return (
<Image
src={image}
alt="Hero"
width={1200}
height={600}
priority // Preload, no lazy loading
sizes="100vw" // Responsive sizing hints
quality={85} // Balance quality vs size
/>
)
}
// CLS (Cumulative Layout Shift) - Target: < 0.1
// Always set explicit width/height on images and embeds
function VideoEmbed({ videoId }: { videoId: string }) {
return (
<div style={{ aspectRatio: '16/9', width: '100%' }}>
<iframe
src={`https://youtube.com/embed/${videoId}`}
width="100%"
height="100%"
loading="lazy"
title="Video"
/>
</div>
)
}
// INP (Interaction to Next Paint) - Target: < 200ms
// Defer heavy computation, use web workers
function SearchResults() {
const [query, setQuery] = useState('')
const [results, setResults] = useState([])
// Debounce input to prevent blocking main thread
const debouncedSearch = useMemo(
() => debounce((q: string) => {
startTransition(() => {
setResults(search(q))
})
}, 300),
[]
)
return (
<input
type="search"
onChange={(e) => {
setQuery(e.target.value)
debouncedSearch(e.target.value)
}}
/>
)
}// Static Generation (SSG): content that rarely changes
// Best for: blog posts, product pages, documentation
export async function generateStaticParams() {
const products = await getProductSlugs()
return products.map(slug => ({ slug }))
}
export default async function ProductPage({ params }) {
const product = await getProduct(params.slug)
return <ProductDetail product={product} />
}
// Incremental Static Regeneration (ISR): SSG with refresh
export const revalidate = 3600 // Regenerate every hour
// Server-Side Rendering (SSR): dynamic, personalized content
// Use only when content changes per request (user-specific, real-time data)
export const dynamic = 'force-dynamic'// app/sitemap.ts
export default async function sitemap(): MetadataRoute.Sitemap {
const products = await getAllProducts()
const posts = await getAllBlogPosts()
return [
{ url: 'https://example.com', lastModified: new Date(), priority: 1.0 },
...products.map(p => ({
url: `https://example.com/products/${p.slug}`,
lastModified: p.updatedAt,
changeFrequency: 'weekly' as const,
priority: 0.8,
})),
...posts.map(p => ({
url: `https://example.com/blog/${p.slug}`,
lastModified: p.updatedAt,
changeFrequency: 'monthly' as const,
priority: 0.6,
})),
]
}
// app/robots.ts
export default function robots(): MetadataRoute.Robots {
return {
rules: [
{ userAgent: '*', allow: '/', disallow: ['/api/', '/admin/', '/checkout/'] },
],
sitemap: 'https://example.com/sitemap.xml',
}
}┌──────────────────────────────────────┐
│ Nav: Logo | Features | Pricing | CTA │ ← Sticky, minimal
├──────────────────────────────────────┤
│ HERO SECTION │
│ H1: Value proposition (6-12 words) │
│ Subtitle: How it works (1 sentence) │
│ CTA button + social proof line │
│ Hero image/screenshot │
├──────────────────────────────────────┤
│ SOCIAL PROOF BAR │
│ "Trusted by X teams" + logos │
├──────────────────────────────────────┤
│ FEATURES (3-4 cards) │
│ Icon + Title + 1 sentence each │
├──────────────────────────────────────┤
│ HOW IT WORKS (3 steps) │
│ Step 1 → Step 2 → Step 3 │
├──────────────────────────────────────┤
│ TESTIMONIALS (2-3 quotes) │
│ Photo + Name + Role + Quote │
├──────────────────────────────────────┤
│ PRICING (3 tiers) │
│ Free | Pro (highlighted) | Enterprise│
├──────────────────────────────────────┤
│ FAQ (5-8 questions, JSON-LD) │
├──────────────────────────────────────┤
│ FINAL CTA │
│ Repeat hero CTA with urgency │
├──────────────────────────────────────┤
│ FOOTER │
│ Legal links + sitemap links │
└──────────────────────────────────────┘Formula 1 — Problem-Solution:
H1: "Stop [pain point]. Start [desired outcome]."
Example: "Stop losing leads. Start converting visitors."
Formula 2 — Before-After:
H1: "[Tool] turns [bad state] into [good state]."
Example: "[Product] turns messy spreadsheets into real-time dashboards."
Formula 3 — Social Proof Lead:
H1: "[N]+ teams use [tool] to [outcome]."
Example: "2,000+ teams use [Product] to ship 3x faster."// Pricing page structured data
function PricingJsonLd({ plans }: { plans: Plan[] }) {
const schema = {
'@context': 'https://schema.org',
'@type': 'WebPage',
name: 'Pricing',
description: 'Plans and pricing for Your App',
mainEntity: plans.map(plan => ({
'@type': 'Offer',
name: plan.name,
price: plan.price,
priceCurrency: 'USD',
description: plan.description,
eligibleDuration: { '@type': 'QuantitativeValue', value: 1, unitCode: 'MON' }
}))
}
return <script type="application/ld+json">{JSON.stringify(schema)}</script>
}
// SEO tips for pricing pages:
// - Title: "[Product] Pricing — Free, Pro & Enterprise Plans"
// - Include pricing in meta description (Google shows it in snippets)
// - Use comparison table with feature checkmarks
// - FAQ section below pricing (common objections → JSON-LD)
// - "Free tier" callout improves CTR from search results// SoftwareApplication schema (rich results for SaaS)
function SoftwareAppJsonLd({ app }: { app: SaaSApp }) {
const schema = {
'@context': 'https://schema.org',
'@type': 'SoftwareApplication',
name: app.name,
applicationCategory: app.category, // 'BusinessApplication', 'DeveloperApplication'
operatingSystem: 'Web',
offers: {
'@type': 'AggregateOffer',
lowPrice: app.freeTier ? '0' : app.lowestPrice,
highPrice: app.highestPrice,
priceCurrency: 'USD',
offerCount: app.planCount
},
aggregateRating: app.reviewCount > 0 ? {
'@type': 'AggregateRating',
ratingValue: app.avgRating,
ratingCount: app.reviewCount,
bestRating: 5,
worstRating: 1
} : undefined,
screenshot: app.screenshotUrl,
featureList: app.features.join(', ')
}
return <script type="application/ld+json">{JSON.stringify(schema)}</script>
}© vibeeval, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/seo-patterns of vibeeval/vibecosystem.
Open the folder on GitHubat commit 3b763b1
SEO Patterns next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| SEO Patterns this skillvibeeval/vibecosystem | 531 | — | ~2.9k | Automated safety check: Pass | MIT | |
| SEO Validatesoftspark/ai-toolkit | 179 | — | ~3.9k | Automated safety check: Notes | Apache-2.0 | |
| Persian SEOTronIsHere/vibefarsiui | 207 | — | ~1.7k | Automated safety check: Warn | None | |
| SEO Auditjosstei/maestro-orchestrate | 465 | — | ~218 | Automated safety check: Pass | Apache-2.0 | |
| SEO Audittextura-agency/next16-claude-starter | 132 | — | ~2.2k | Automated safety check: Notes | Unlicense | |
| SEO Geoericrisco/rsc-harness | 156 | — | ~2.8k | Automated safety check: Pass | MIT |
softspark/ai-toolkit
SEO validator: meta/OG, Schema.org, hreflang, Core Web Vitals, crawlability.
TronIsHere/vibefarsiui
Technical and on-page SEO for Persian (Farsi) websites: lang and hreflang for fa-IR, RTL-safe metadata, Persian titles and descriptions, slug and URL strategy for Persian content, ZWNJ and keyword…
josstei/maestro-orchestrate
Run a Maestro-style SEO assessment for meta tags, structured data, crawlability, and Core Web Vitals
textura-agency/next16-claude-starter
Audit a page or the whole site for technical and on-page SEO — crawlability, metadata, heading outline, structured data, internal linking, Core Web Vitals, and the animation-specific crawlability…
ericrisco/rsc-harness
A skill your agent uses when one existing page needs to rank in Google AND get cited by AI answer engines — auditing a URL for on-page SEO, structured-data JSON-LD, GEO citation levers, Core Web…
adobe/skills
Optimize AEM Edge Delivery Services commerce product pages for search engine crawling and indexing.
vibeeval/vibecosystem
Framework for measuring and tracking agent response quality over time.
vibeeval/vibecosystem
Security-focused differential code review with blast radius analysis, risk-adaptive depth (DEEP/FOCUSED/SURGICAL), git history correlation, and structured finding format.
vibeeval/vibecosystem
A skill your agent uses when making any factual claim about the codebase — existence, absence, or behavior.
vibeeval/vibecosystem
Systematic false positive verification for security findings.
vibeeval/vibecosystem
n8n otomasyon workflow'lari. An agent skill from vibeeval/vibecosystem.
vibeeval/vibecosystem
A skill your agent uses when context compression is imminent, when resuming a session, or when preserving critical decisions across long tasks.
Categories
Meta tag patterns, structured data (JSON-LD), Core Web Vitals optimization, and SSR/SSG strategies for search visibility. SEO Patterns is an agent skill from vibeeval/vibecosystem. Meta tag patterns, structured data (JSON-LD), Core Web Vitals optimization, and SSR/SSG strategies for search visibility.
SEO Patterns fits situations like: tasks that involve Schema markup; tasks that involve Web performance; tasks that involve On-page SEO.
Run `npx skills add vibeeval/vibecosystem --skill seo-patterns -a claude-code`. Or copy the skill folder (skills/seo-patterns in vibeeval/vibecosystem) into .claude/skills/seo-patterns in your project. Claude Code loads it when a task matches its description.
Run `npx skills add vibeeval/vibecosystem --skill seo-patterns -a codex`. Or copy the skill folder (skills/seo-patterns in vibeeval/vibecosystem) into .agents/skills/seo-patterns in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vibeeval/vibecosystem --skill seo-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/seo-patterns, .gemini/skills/seo-patterns, .github/skills/seo-patterns and .opencode/skills/seo-patterns in your project.
SKILL.md names no scripts, command-line tools or credentials: SEO Patterns is instructions for the agent only.
SKILL.md names 2 domains. In commands or code: schema.org and youtube.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
SEO Patterns is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with SEO Patterns: SEO Validate (softspark/ai-toolkit, 179 stars), Persian SEO (TronIsHere/vibefarsiui, 207 stars), SEO Audit (josstei/maestro-orchestrate, 465 stars) and SEO Audit (textura-agency/next16-claude-starter, 132 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
vibeeval (a GitHub user) maintains it in vibeeval/vibecosystem, which has 531 GitHub stars. The repository holds 144 skills in this directory. The repository was last updated on August 8, 2026.
Source: vibeeval/vibecosystem on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.