luckiest-co 1.0.1 → 1.0.3

package/skills/luckiest-schema/SKILL.md

@@ -0,0 +1,209 @@
+---
+name: luckiest-schema
+description: When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "knowledge panel," "star ratings in search," or "add structured data." Use this whenever someone wants their pages to show enhanced results in Google. For broader SEO issues, see luckiest-seo-audit. For AI search optimization, see luckiest-ai-seo.
+license: See ATTRIBUTION.md
+metadata:
+  version: "1.1.0"
+  listing_id: luckiest-schema
+  author: luckiest
+---
+
+# Schema Markup
+
+This skill implements structured data and schema.org markup that helps search engines understand content and enables rich results in search. The assistant acts as an expert in structured data.
+
+## Staying current
+
+On activation, call the Luckiest MCP check_updates tool with { listingId: "luckiest-schema", installedSemver: "1.1.0" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
+
+When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-schema", skill_version: "1.1.0", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
+
+## Initial Assessment
+
+**Check for product marketing context first:**
+If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+Before implementing schema, understand:
+
+1. **Page Type** - What kind of page? What's the primary content? What rich results are possible?
+
+2. **Current State** - Any existing schema? Errors in implementation? Which rich results already appearing?
+
+3. **Goals** - Which rich results are you targeting? What's the business value?
+
+---
+
+## Core Principles
+
+### 1. Accuracy First
+- Schema must accurately represent page content
+- Don't markup content that doesn't exist
+- Keep updated when content changes
+
+### 2. Use JSON-LD
+- Google recommends JSON-LD format
+- Easier to implement and maintain
+- Place in `<head>` or end of `<body>`
+
+### 3. Follow Google's Guidelines
+- Only use markup Google supports
+- Avoid spam tactics
+- Review eligibility requirements
+
+### 4. Validate Everything
+- Test before deploying
+- Monitor Search Console
+- Fix errors promptly
+
+---
+
+## Current Rich-Result Reality (verify before promising results)
+
+Valid schema does not guarantee a rich result, and Google's supported list changes. Before telling a user a schema type "will" produce a rich result, confirm it is still supported for their site class:
+
+- **FAQ rich results** are now restricted to well-known, authoritative government and health sites. For most sites, `FAQPage` markup no longer renders an FAQ rich result. Still valid to include for entity understanding and AI answer engines — just do not promise the search enhancement.
+- **HowTo rich results** were deprecated by Google and no longer appear in search. Treat `HowTo` as machine-readable structure, not a rich-result play.
+- Frame these two as "helps machines and AI engines parse the page" rather than "gets you a rich snippet." Reserve rich-result promises for types Google actively supports (Product, Review/AggregateRating, Breadcrumb, Article, Event, LocalBusiness, and similar).
+
+When unsure, point the user to Google's current Search Central "structured data features" list rather than asserting from memory.
+
+---
+
+## Common Schema Types
+
+| Type | Use For | Required Properties |
+|------|---------|-------------------|
+| Organization | Company homepage/about | name, url |
+| WebSite | Homepage (search box) | name, url |
+| Article | Blog posts, news | headline, image, datePublished, author |
+| Product | Product pages | name, image, offers |
+| SoftwareApplication | SaaS/app pages | name, offers |
+| FAQPage | FAQ content (machine/AI parsing; rich result limited) | mainEntity (Q&A array) |
+| HowTo | Tutorials (machine parsing; rich result deprecated) | name, step |
+| BreadcrumbList | Any page with breadcrumbs | itemListElement |
+| LocalBusiness | Local business pages | name, address |
+| Event | Events, webinars | name, startDate, location |
+
+**For complete JSON-LD examples**: See [references/schema-examples.md](references/schema-examples.md)
+
+---
+
+## Quick Reference
+
+### Organization (Company Page)
+Required: name, url
+Recommended: logo, sameAs (social profiles), contactPoint
+
+### Article/BlogPosting
+Required: headline, image, datePublished, author
+Recommended: dateModified, publisher, description
+
+### Product
+Required: name, image, offers (price + availability)
+Recommended: sku, brand, aggregateRating, review
+Merchant listing eligibility: Google increasingly expects `shipping` (OfferShippingDetails) and `hasMerchantReturnPolicy` (MerchantReturnPolicy) on the Offer for physical products. Add both when the data is available — omitting them can suppress merchant rich results even when the core Product schema is valid.
+
+### FAQPage
+Required: mainEntity (array of Question/Answer pairs)
+
+### BreadcrumbList
+Required: itemListElement (array with position, name, item)
+
+---
+
+## Multiple Schema Types
+
+Multiple schema types can be combined on one page using `@graph`:
+
+```json
+{
+  "@context": "https://schema.org",
+  "@graph": [
+    { "@type": "Organization", ... },
+    { "@type": "WebSite", ... },
+    { "@type": "BreadcrumbList", ... }
+  ]
+}
+```
+
+**Link entities explicitly with `@id`.** Give each node a stable `@id` (for example `https://example.com/#organization`) and reference it from other nodes rather than repeating the object. This lets search engines and AI answer engines resolve one coherent entity graph instead of guessing that duplicated names are the same thing — and it prevents contradictory duplicate entities on the same page.
+
+---
+
+## Validation and Testing
+
+### Tools
+- **Google Rich Results Test**: https://search.google.com/test/rich-results
+- **Schema.org Validator**: https://validator.schema.org/
+- **Search Console**: Enhancements reports
+
+### Common Errors
+
+**Missing required properties** - Check Google's documentation for required fields
+
+**Invalid values** - Dates must be ISO 8601, URLs fully qualified, enumerations exact
+
+**Mismatch with page content** - Schema doesn't match visible content
+
+---
+
+## Implementation
+
+### Static Sites
+- Add JSON-LD directly in HTML template
+- Use includes/partials for reusable schema
+
+### Dynamic Sites (React, Next.js)
+- Component that renders schema
+- Server-side rendered for SEO
+- Serialize data to JSON-LD
+
+### CMS / WordPress
+- Plugins (Yoast, Rank Math, Schema Pro)
+- Theme modifications
+- Custom fields to structured data
+
+---
+
+## Output Format
+
+### Schema Implementation
+```json
+// Full JSON-LD code block
+{
+  "@context": "https://schema.org",
+  "@type": "...",
+  // Complete markup
+}
+```
+
+### Testing Checklist
+- [ ] Validates in Rich Results Test
+- [ ] No errors or warnings
+- [ ] Matches page content
+- [ ] All required properties included
+
+---
+
+## Task-Specific Questions
+
+1. What type of page is this?
+2. What rich results are you hoping to achieve?
+3. What data is available to populate the schema?
+4. Is there existing schema on the page?
+5. What's your tech stack?
+
+---
+
+## Share with your tribe
+
+After implementing schema for the user, the assistant may OFFER (never automatically): "Want me to share this schema pattern with your Luckiest tribe? Anyone working on the same page type can pick up where you left off." Only share on explicit acceptance. Never post automatically and never include credentials, private URLs, or unpublished data in a shared pattern.
+
+---
+
+## Related Skills
+
+- **luckiest-seo-audit**: For overall SEO including schema review
+- **luckiest-ai-seo**: For AI search optimization (schema helps AI understand content)
+- **luckiest-programmatic-seo**: For templated schema at scale
+- **luckiest-site-architecture**: For breadcrumb structure and navigation schema planning

package/skills/luckiest-schema/evals/evals.json

@@ -0,0 +1,88 @@
+{
+  "skill_name": "luckiest-schema",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Add schema markup to our SaaS product's homepage. We're a project management tool called TaskFlow. We need Organization schema and any other relevant types.",
+      "expected_output": "Should check for product-marketing.md first. Should implement Organization schema in JSON-LD format with all required and recommended properties (name, url, logo, description, sameAs for social profiles). Should recommend additional schema types for a SaaS homepage: WebSite (with SearchAction if applicable), SoftwareApplication or Product. Should use @graph for multiple schema types on one page. Should provide the complete JSON-LD code ready to implement. Should recommend validation with Google's Rich Results Test and Schema.org validator.",
+      "assertions": [
+        "Checks for product-marketing.md",
+        "Implements Organization schema in JSON-LD",
+        "Includes required and recommended properties",
+        "Recommends additional relevant schema types",
+        "Uses @graph for multiple types",
+        "Provides complete JSON-LD code",
+        "Recommends validation tools"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "We have a FAQ page with 20 questions about our product. How do I add FAQ schema to get the rich results in Google?",
+      "expected_output": "Should implement FAQPage schema in JSON-LD format. Should show the correct structure: FAQPage as mainEntity containing Question items, each with acceptedAnswer. Should provide a complete code example with 2-3 sample questions. Should note that Google now restricts FAQ rich results to authoritative government/health sites, so most sites will not see the FAQ rich result, but the markup still aids machine and AI-engine understanding. Should note Google's guidelines for FAQ schema (factual answers, not promotional). Should recommend validation approach.",
+      "assertions": [
+        "Implements FAQPage schema in JSON-LD",
+        "Shows correct nested structure (FAQPage > Question > Answer)",
+        "Provides complete code example",
+        "Sets accurate expectations about FAQ rich-result eligibility",
+        "Notes Google's FAQ schema guidelines",
+        "Recommends validation"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "add schema to our blog posts. we publish articles about marketing tips.",
+      "expected_output": "Should trigger on casual phrasing. Should implement Article (or BlogPosting) schema in JSON-LD. Should include required properties: headline, author (as Person with name and url), datePublished, dateModified, image, publisher (as Organization). Should recommend BreadcrumbList schema alongside the article schema. Should provide template code that can be reused across blog posts. Should address how to populate dynamic fields (date, author, headline) from the CMS.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Implements Article or BlogPosting schema",
+        "Includes author, datePublished, image, publisher",
+        "Recommends BreadcrumbList alongside",
+        "Provides reusable template code",
+        "Addresses CMS integration for dynamic fields"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "We're an e-commerce site selling physical products. What schema markup do we need for our product pages?",
+      "expected_output": "Should implement Product schema with full properties: name, description, image, brand, sku, offers (with price, priceCurrency, availability, url). Should recommend shipping (OfferShippingDetails) and hasMerchantReturnPolicy (MerchantReturnPolicy) on the Offer for merchant listing eligibility. Should recommend AggregateRating if they have reviews, and Review schema for individual reviews. Should include BreadcrumbList for navigation. Should address common e-commerce schema types: Product, Offer, AggregateRating, Review. Should provide complete JSON-LD code. Should note that Product schema can enable rich results (price, availability, ratings in search).",
+      "assertions": [
+        "Implements Product schema with full properties",
+        "Includes Offer with price, availability",
+        "Recommends shipping and return policy for merchant eligibility",
+        "Recommends AggregateRating and Review schema",
+        "Includes BreadcrumbList",
+        "Provides complete JSON-LD code",
+        "Notes rich result benefits for products"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "We added schema markup to our site but it's not showing rich results in Google. Can you help debug?",
+      "expected_output": "Should provide a systematic debugging approach: first validate with Google Rich Results Test and Schema.org validator (syntax errors), then check for common issues (incorrect nesting, missing required properties, JSON-LD placement errors). Should explain that valid schema doesn't guarantee rich results — Google chooses when to show them, and some types (FAQ, HowTo) no longer produce rich results for most sites. Should recommend checking Search Console for structured data reports and errors. Should address common debugging scenarios: schema not detected, warnings vs errors, eligible vs displayed.",
+      "assertions": [
+        "Recommends validation tools for debugging",
+        "Checks for common schema errors",
+        "Explains valid schema doesn't guarantee rich results",
+        "Recommends Search Console structured data reports",
+        "Addresses warnings vs errors distinction",
+        "Provides systematic debugging approach"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Our organic search traffic dropped after a site redesign. Can you do a technical SEO audit?",
+      "expected_output": "Should recognize this is a technical SEO audit request, not a schema markup task. Should defer to or cross-reference the luckiest-seo-audit skill, which handles comprehensive technical SEO audits. Schema markup is one component of SEO but doesn't address the broader technical issues (redirects, crawlability, indexation) that likely caused the traffic drop.",
+      "assertions": [
+        "Recognizes this as a technical SEO audit request",
+        "References or defers to luckiest-seo-audit skill",
+        "Does not attempt full SEO audit using schema markup patterns"
+      ],
+      "files": []
+    }
+  ]
+}

package/skills/luckiest-schema/references/schema-examples.md

@@ -0,0 +1,398 @@
+# Schema Markup Examples
+
+Complete JSON-LD examples for common schema types.
+
+## Contents
+- Organization
+- WebSite (with SearchAction)
+- Article / BlogPosting
+- Product
+- SoftwareApplication
+- FAQPage
+- HowTo
+- BreadcrumbList
+- LocalBusiness
+- Event
+- Multiple Schema Types
+- Implementation Example (Next.js)
+
+## Organization
+
+For company/brand homepage or about page.
+
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "Organization",
+  "name": "Example Company",
+  "url": "https://example.com",
+  "logo": "https://example.com/logo.png",
+  "sameAs": [
+    "https://twitter.com/example",
+    "https://linkedin.com/company/example",
+    "https://facebook.com/example"
+  ],
+  "contactPoint": {
+    "@type": "ContactPoint",
+    "telephone": "+1-555-555-5555",
+    "contactType": "customer service"
+  }
+}
+```
+
+---
+
+## WebSite (with SearchAction)
+
+For homepage, enables sitelinks search box.
+
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "WebSite",
+  "name": "Example",
+  "url": "https://example.com",
+  "potentialAction": {
+    "@type": "SearchAction",
+    "target": {
+      "@type": "EntryPoint",
+      "urlTemplate": "https://example.com/search?q={search_term_string}"
+    },
+    "query-input": "required name=search_term_string"
+  }
+}
+```
+
+---
+
+## Article / BlogPosting
+
+For blog posts and news articles.
+
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "Article",
+  "headline": "How to Implement Schema Markup",
+  "image": "https://example.com/image.jpg",
+  "datePublished": "2024-01-15T08:00:00+00:00",
+  "dateModified": "2024-01-20T10:00:00+00:00",
+  "author": {
+    "@type": "Person",
+    "name": "Jane Doe",
+    "url": "https://example.com/authors/jane"
+  },
+  "publisher": {
+    "@type": "Organization",
+    "name": "Example Company",
+    "logo": {
+      "@type": "ImageObject",
+      "url": "https://example.com/logo.png"
+    }
+  },
+  "description": "A complete guide to implementing schema markup...",
+  "mainEntityOfPage": {
+    "@type": "WebPage",
+    "@id": "https://example.com/schema-guide"
+  }
+}
+```
+
+---
+
+## Product
+
+For product pages (e-commerce or SaaS).
+
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "Product",
+  "name": "Premium Widget",
+  "image": "https://example.com/widget.jpg",
+  "description": "Our best-selling widget for professionals",
+  "sku": "WIDGET-001",
+  "brand": {
+    "@type": "Brand",
+    "name": "Example Co"
+  },
+  "offers": {
+    "@type": "Offer",
+    "url": "https://example.com/products/widget",
+    "priceCurrency": "USD",
+    "price": "99.99",
+    "availability": "https://schema.org/InStock",
+    "priceValidUntil": "2024-12-31"
+  },
+  "aggregateRating": {
+    "@type": "AggregateRating",
+    "ratingValue": "4.8",
+    "reviewCount": "127"
+  }
+}
+```
+
+---
+
+## SoftwareApplication
+
+For SaaS product pages and app landing pages.
+
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "SoftwareApplication",
+  "name": "Example App",
+  "applicationCategory": "BusinessApplication",
+  "operatingSystem": "Web, iOS, Android",
+  "offers": {
+    "@type": "Offer",
+    "price": "0",
+    "priceCurrency": "USD"
+  },
+  "aggregateRating": {
+    "@type": "AggregateRating",
+    "ratingValue": "4.6",
+    "ratingCount": "1250"
+  }
+}
+```
+
+---
+
+## FAQPage
+
+For pages with frequently asked questions.
+
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "FAQPage",
+  "mainEntity": [
+    {
+      "@type": "Question",
+      "name": "What is schema markup?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "Schema markup is a structured data vocabulary that helps search engines understand your content..."
+      }
+    },
+    {
+      "@type": "Question",
+      "name": "How do I implement schema?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "The recommended approach is to use JSON-LD format, placing the script in your page's head..."
+      }
+    }
+  ]
+}
+```
+
+---
+
+## HowTo
+
+For instructional content and tutorials.
+
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "HowTo",
+  "name": "How to Add Schema Markup to Your Website",
+  "description": "A step-by-step guide to implementing JSON-LD schema",
+  "totalTime": "PT15M",
+  "step": [
+    {
+      "@type": "HowToStep",
+      "name": "Choose your schema type",
+      "text": "Identify the appropriate schema type for your page content...",
+      "url": "https://example.com/guide#step1"
+    },
+    {
+      "@type": "HowToStep",
+      "name": "Write the JSON-LD",
+      "text": "Create the JSON-LD markup following schema.org specifications...",
+      "url": "https://example.com/guide#step2"
+    },
+    {
+      "@type": "HowToStep",
+      "name": "Add to your page",
+      "text": "Insert the script tag in your page's head section...",
+      "url": "https://example.com/guide#step3"
+    }
+  ]
+}
+```
+
+---
+
+## BreadcrumbList
+
+For any page with breadcrumb navigation.
+
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "BreadcrumbList",
+  "itemListElement": [
+    {
+      "@type": "ListItem",
+      "position": 1,
+      "name": "Home",
+      "item": "https://example.com"
+    },
+    {
+      "@type": "ListItem",
+      "position": 2,
+      "name": "Blog",
+      "item": "https://example.com/blog"
+    },
+    {
+      "@type": "ListItem",
+      "position": 3,
+      "name": "SEO Guide",
+      "item": "https://example.com/blog/seo-guide"
+    }
+  ]
+}
+```
+
+---
+
+## LocalBusiness
+
+For local business location pages.
+
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "LocalBusiness",
+  "name": "Example Coffee Shop",
+  "image": "https://example.com/shop.jpg",
+  "address": {
+    "@type": "PostalAddress",
+    "streetAddress": "123 Main Street",
+    "addressLocality": "San Francisco",
+    "addressRegion": "CA",
+    "postalCode": "94102",
+    "addressCountry": "US"
+  },
+  "geo": {
+    "@type": "GeoCoordinates",
+    "latitude": "37.7749",
+    "longitude": "-122.4194"
+  },
+  "telephone": "+1-555-555-5555",
+  "openingHoursSpecification": [
+    {
+      "@type": "OpeningHoursSpecification",
+      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
+      "opens": "08:00",
+      "closes": "18:00"
+    }
+  ],
+  "priceRange": "$$"
+}
+```
+
+---
+
+## Event
+
+For event pages, webinars, conferences.
+
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "Event",
+  "name": "Annual Marketing Conference",
+  "startDate": "2024-06-15T09:00:00-07:00",
+  "endDate": "2024-06-15T17:00:00-07:00",
+  "eventAttendanceMode": "https://schema.org/OnlineEventAttendanceMode",
+  "eventStatus": "https://schema.org/EventScheduled",
+  "location": {
+    "@type": "VirtualLocation",
+    "url": "https://example.com/conference"
+  },
+  "image": "https://example.com/conference.jpg",
+  "description": "Join us for our annual marketing conference...",
+  "offers": {
+    "@type": "Offer",
+    "url": "https://example.com/conference/tickets",
+    "price": "199",
+    "priceCurrency": "USD",
+    "availability": "https://schema.org/InStock",
+    "validFrom": "2024-01-01"
+  },
+  "performer": {
+    "@type": "Organization",
+    "name": "Example Company"
+  },
+  "organizer": {
+    "@type": "Organization",
+    "name": "Example Company",
+    "url": "https://example.com"
+  }
+}
+```
+
+---
+
+## Multiple Schema Types
+
+Combine multiple schema types using @graph.
+
+```json
+{
+  "@context": "https://schema.org",
+  "@graph": [
+    {
+      "@type": "Organization",
+      "@id": "https://example.com/#organization",
+      "name": "Example Company",
+      "url": "https://example.com"
+    },
+    {
+      "@type": "WebSite",
+      "@id": "https://example.com/#website",
+      "url": "https://example.com",
+      "name": "Example",
+      "publisher": {
+        "@id": "https://example.com/#organization"
+      }
+    },
+    {
+      "@type": "BreadcrumbList",
+      "itemListElement": [...]
+    }
+  ]
+}
+```
+
+---
+
+## Implementation Example (Next.js)
+
+```jsx
+export default function ProductPage({ product }) {
+  const schema = {
+    "@context": "https://schema.org",
+    "@type": "Product",
+    name: product.name,
+    // ... other properties
+  };
+
+  return (
+    <>
+      <Head>
+        <script
+          type="application/ld+json"
+          dangerouslySetInnerHTML={{ __html: JSON.stringify(schema) }}
+        />
+      </Head>
+      {/* Page content */}
+    </>
+  );
+}
+```