seo

SEO best practices for the Grida project across Next.js pages, blog posts, and documentation. Covers Next.js metadata API, Open Graph / Twitter cards, sitemaps, image search optimization, structured data (JSON-LD), Docusaurus frontmatter, and content writing for search. Use when creating or editing public-facing pages under editor/app/(www), writing blog posts, authoring docs, or reviewing SEO-related metadata. Trigger phrases: "SEO", "metadata", "sitemap", "open graph", "og image", "meta tags", "search ranking", "structured data", "JSON-LD".

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is actionable and well-structured with a clear scope table and verification checklist. Its main weakness is conciseness: several passages restate general SEO knowledge Claude already has, which could be trimmed without losing project-specific value.

Suggestions

Trim general-knowledge SEO explanations (e.g., 'search engines discover pages' via linking, 'Page speed is a ranking factor', 'Google uses mobile-first indexing', 'Write for humans first') and keep only Grida-specific rules and thresholds to improve conciseness.

Replace or remove the stub `generateMetadata({ params }): Promise<Metadata> { ... }` dynamic example with a minimal concrete body, or mark it explicitly as a pattern, since the actionability anchor rewards fully executable examples.

Consolidate the General SEO Writing Rules into project-specific deviations from the norm rather than restating universal best practices, which would let the section earn its tokens.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with tables, rules, and code, but it restates SEO basics Claude already knows ("search engines discover pages" via linking, "Page speed is a ranking factor", "Google uses mobile-first indexing", "Write for humans first", avoid "click here"), so it could be tightened rather than fully lean.	2 / 3
Actionability	Provides copy-paste-ready code (metadata export object, `metadataBase: new URL(...)`, sitemap entry, Docusaurus frontmatter) and specific thresholds (under 160 chars, `priority: 1` homepage-only, 1200x630 OG images, named JSON-LD schema types), matching the executable-examples anchor.	3 / 3
Workflow Clarity	A Scope table sequences surfaces to locations, and a "Verification Checklist" provides explicit pre-ship checkpoints; the low-risk operations and the sitemap robots.txt gotcha fit the clear-sequence-with-validation anchor rather than the implicit-checkpoint anchor at 2.	3 / 3
Progressive Disclosure	No bundle files are needed; the single SKILL.md is organized into well-navigable sections (Scope, Next.js Pages, Documentation, Blog, Crawl Control, General Rules, Verification Checklist) with a helpful scope table, matching the well-organized-sections anchor rather than the monolithic anchor at 1.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it enumerates concrete SEO capabilities, provides an explicit 'Use when' clause, lists natural trigger phrases, and is scoped to a distinct niche. It cleanly satisfies all four dimensions.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities across surfaces — "Next.js metadata API", "Open Graph / Twitter cards", "sitemaps", "image search optimization", "structured data (JSON-LD)", "Docusaurus frontmatter", and "content writing for search" — matching the multiple-specific-actions anchor rather than the domain-only anchor at 2.	3 / 3
Completeness	It states what the skill does (the enumerated SEO areas) and when to use it via an explicit "Use when creating or editing public-facing pages..., writing blog posts, authoring docs, or reviewing SEO-related metadata" clause, satisfying both what and when rather than the implied-when anchor at 2.	3 / 3
Trigger Term Quality	An explicit "Trigger phrases" block supplies natural terms a user would say ("SEO", "metadata", "sitemap", "open graph", "og image", "meta tags", "search ranking", "structured data", "JSON-LD"), giving good coverage beyond the single-phrase anchor at 2.	3 / 3
Distinctiveness Conflict Risk	Scoping to the Grida project with specific surfaces (Next.js `(www)`, Docusaurus docs/blog) and distinct SEO triggers gives it a clear niche unlikely to fire for unrelated skills, rather than the somewhat-generic anchor at 2.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: gridaco/grida
Path: .agents/skills/seo/SKILL.md
Commit: 2e0d276

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.