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

86%

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

77%Weight 40%Scale 1-5

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

The body is well-organized, actionable, and closes with a strong verification checklist, making it a high-quality single-document skill. Its main weakness is progressive disclosure: it is entirely self-contained with no reference files, so detailed material is inlined rather than split out.

Suggestions

Extract the longer reference material (e.g. full JSON-LD schema templates per page type, the Google Image Search checklist) into files under references/ and link to them one level deep, leaving SKILL.md as a leaner overview.

Trim the 'General SEO Writing Rules' section to the few rules that are non-obvious for SEO specifically, removing widely-known advice like 'descriptive link text' and 'alt text on images' that Claude already applies.

Replace the generateMetadata stub (`{ ... }`) with a minimal but executable example so every code block is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's competence, with executable code snippets and rules rather than explanations of basic SEO concepts, but sections like the 8-item 'General SEO Writing Rules' and the 'Verification Checklist' restate widely-known guidance that could be trimmed.	4 / 5
Actionability	It provides concrete, mostly copy-paste-ready code (Metadata export, generateMetadata, metadataBase, sitemap entries, frontmatter) and specific rules (title suffix ' — Grida', 160-char limits, OG image 1200x630), with only minor gaps like the generateMetadata example being a stub.	4 / 5
Workflow Clarity	It includes an explicit 'Verification Checklist' that sequences the pre-ship validation steps with checkboxes, plus a clear per-surface structure and a feedback-style reminder to re-set metadataBase; the checklist serves as the validation checkpoint the rubric rewards.	5 / 5
Progressive Disclosure	The SKILL.md is a single monolithic document with no references/ or other bundle files and no one-level-deep links to detailed materials; it is well-sectioned but everything is inlined, so content that could be split out (e.g. full JSON-LD schema examples) is not.	3 / 5
	Total	16 / 20 Passed

Description

96%Weight 40%Scale 1-5

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

This is a strong, model description: it pairs a comprehensive, concrete capability list with an explicit 'Use when' clause and natural trigger phrases, all in third person. The only minor weakness is that some trigger terms (e.g. 'metadata', 'sitemap') are generic enough to risk minor overlap with adjacent skills.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete capabilities (Next.js metadata API, Open Graph/Twitter cards, sitemaps, image search optimization, structured data/JSON-LD, Docusaurus frontmatter, content writing for search), giving comprehensive coverage of what the skill does.	5 / 5
Completeness	It explicitly answers both 'what' (a long list of concrete SEO capabilities) and 'when' ('Use when creating or editing public-facing pages under editor/app/(www), writing blog posts, authoring docs, or reviewing SEO-related metadata'), plus concrete trigger phrases.	5 / 5
Trigger Term Quality	It provides an explicit, comprehensive set of natural trigger phrases ('SEO', 'metadata', 'sitemap', 'open graph', 'og image', 'meta tags', 'search ranking', 'structured data', 'JSON-LD') that users would naturally say, including synonyms and the common 'og image' variant.	5 / 5
Distinctiveness Conflict Risk	It occupies a clear SEO niche with distinct triggers and minimal conflict risk, but terms like 'metadata' and 'sitemap' are broad enough to occasionally overlap with non-SEO skills, keeping it just below a 5.	4 / 5
	Total	19 / 20 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: 8ef5e53

Reviewed: about 11 hours 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.