seo-patterns
Implements technical SEO: meta tags, JSON-LD structured data, sitemaps, and crawlability fixes. Use when adding schema markup, JSON-LD, robots.txt updates, canonical URLs, Open Graph tags, or improving crawlability.
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that clearly defines its scope (technical SEO), lists specific concrete capabilities, and includes an explicit 'Use when' clause with rich, natural trigger terms. It uses proper third-person voice and is concise without being vague. The description would perform well in a large skill library due to its distinct technical SEO niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: meta tags, JSON-LD structured data, sitemaps, crawlability fixes, schema markup, robots.txt updates, canonical URLs, and Open Graph tags. | 3 / 3 |
Completeness | Clearly answers both 'what' (implements technical SEO: meta tags, JSON-LD structured data, sitemaps, crawlability fixes) and 'when' (explicit 'Use when' clause listing specific trigger scenarios like adding schema markup, robots.txt updates, canonical URLs, etc.). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'meta tags', 'JSON-LD', 'structured data', 'sitemaps', 'schema markup', 'robots.txt', 'canonical URLs', 'Open Graph tags', 'crawlability', and 'SEO' — all terms a user would naturally use when requesting this type of work. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to technical SEO specifically, with distinct triggers like JSON-LD, robots.txt, canonical URLs, and schema markup that are unlikely to conflict with general web development or content-focused skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, well-structured SEO skill with clear workflows, validation checkpoints, and actionable code examples. Its main weaknesses are minor redundancy (duplicate REFERENCE.md mentions, some overlap between workflow checkpoints and checklists) and the inability to verify the referenced REFERENCE.md bundle file. Overall it provides practical, concrete guidance that Claude can immediately act on.
Suggestions
Consolidate the two separate references to REFERENCE.md into a single, clearly signaled section to reduce redundancy.
Ensure REFERENCE.md is included in the bundle so the progressive disclosure actually works — or inline the most critical structured data examples if no bundle is available.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some redundancy — the crawlability checklist repeats points already covered in the workflow, and the structured data reference is mentioned twice (sections 'Structured Data & Crawlability' and 'Anti-Patterns & Structured Data Reference' both point to REFERENCE.md). The checklists add value but could be tighter. | 2 / 3 |
Actionability | Provides fully executable code examples (Next.js metadata export, robots.txt), specific character counts for meta descriptions and titles, concrete image dimensions, and clear checklists. The guidance is copy-paste ready and specific. | 3 / 3 |
Workflow Clarity | The 5-step implementation workflow has explicit checkpoints at each stage, includes a recovery step for robots.txt misconfiguration, and ends with a monitoring/verification step. The sequence is logical and validation is built into each step. | 3 / 3 |
Progressive Disclosure | References REFERENCE.md twice for structured data examples and anti-patterns, which is good progressive disclosure. However, the bundle has no files, so we can't verify REFERENCE.md exists. The duplicate references to the same file are slightly disorganized, and the inline content is reasonably sized but the crawlability checklist could arguably live in the reference file. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- monkilabs/opencastle
- Commit
cc13aaf
- Reviewed
Table of Contents
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.