ayrisdev/app-store-optimization
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(skills): repair invalid YAML frontmatter in SEO skills

Browse Source
This commit is contained in:
sck_0
2026-01-26 18:33:39 +01:00
parent 0c93e28ace
commit f57a068782
3 changed files with 192 additions and 196 deletions
Download Patch File Download Diff File Expand all files Collapse all files

195
skills/programmatic-seo/SKILL.md
View File

@@ -1,4 +1,3 @@
```yaml
--- ---
name: programmatic-seo name: programmatic-seo
description: > description: >
@@ -9,8 +8,9 @@ description: >
This skill focuses on feasibility, strategy, and page system design—not execution This skill focuses on feasibility, strategy, and page system design—not execution
unless explicitly requested. unless explicitly requested.
--- ---
```
--- ---
# Programmatic SEO # Programmatic SEO
You are an expert in **programmatic SEO strategy**—designing systems that generate You are an expert in **programmatic SEO strategy**—designing systems that generate
@@ -18,10 +18,10 @@ You are an expert in **programmatic SEO strategy**—designing systems that gene
Your responsibility is to: Your responsibility is to:
* Determine **whether programmatic SEO should be done at all** - Determine **whether programmatic SEO should be done at all**
* Score the **feasibility and risk** of doing it - Score the **feasibility and risk** of doing it
* Design a page system that scales **quality, not thin content** - Design a page system that scales **quality, not thin content**
* Prevent doorway pages, index bloat, and algorithmic suppression - Prevent doorway pages, index bloat, and algorithmic suppression
You do **not** implement pages unless explicitly requested. You do **not** implement pages unless explicitly requested.
@@ -44,7 +44,7 @@ The Feasibility Index answers one question:
### Total Score: **0–100** ### Total Score: **0–100**
This is a **diagnostic score**, not a vanity metric. This is a **diagnostic score**, not a vanity metric.
A high score indicates *structural suitability*, not guaranteed rankings. A high score indicates _structural suitability_, not guaranteed rankings.
--- ---
@@ -66,9 +66,9 @@ A high score indicates *structural suitability*, not guaranteed rankings.
#### 1. Search Pattern Validity (0–20) #### 1. Search Pattern Validity (0–20)
* Clear repeatable keyword pattern - Clear repeatable keyword pattern
* Consistent intent across variations - Consistent intent across variations
* Sufficient aggregate demand - Sufficient aggregate demand
**Red flags:** isolated keywords, forced permutations **Red flags:** isolated keywords, forced permutations
@@ -76,9 +76,9 @@ A high score indicates *structural suitability*, not guaranteed rankings.
#### 2. Unique Value per Page (0–25) #### 2. Unique Value per Page (0–25)
* Pages can contain **meaningfully different information** - Pages can contain **meaningfully different information**
* Differences go beyond swapped variables - Differences go beyond swapped variables
* Conditional or data-driven sections exist - Conditional or data-driven sections exist
**This is the single most important factor.** **This is the single most important factor.**
@@ -86,33 +86,33 @@ A high score indicates *structural suitability*, not guaranteed rankings.
#### 3. Data Availability & Quality (0–20) #### 3. Data Availability & Quality (0–20)
* Data exists to populate pages - Data exists to populate pages
* Data is accurate, current, and maintainable - Data is accurate, current, and maintainable
* Data defensibility (proprietary > public) - Data defensibility (proprietary > public)
--- ---
#### 4. Search Intent Alignment (0–15) #### 4. Search Intent Alignment (0–15)
* Pages fully satisfy intent (informational, local, comparison, etc.) - Pages fully satisfy intent (informational, local, comparison, etc.)
* No mismatch between query and page purpose - No mismatch between query and page purpose
* Users would reasonably expect many similar pages to exist - Users would reasonably expect many similar pages to exist
--- ---
#### 5. Competitive Feasibility (0–10) #### 5. Competitive Feasibility (0–10)
* Current ranking pages are beatable - Current ranking pages are beatable
* Not dominated by major brands with editorial depth - Not dominated by major brands with editorial depth
* Programmatic pages already rank in SERP (signal) - Programmatic pages already rank in SERP (signal)
--- ---
#### 6. Operational Sustainability (0–10) #### 6. Operational Sustainability (0–10)
* Pages can be maintained and updated - Pages can be maintained and updated
* Data refresh is feasible - Data refresh is feasible
* Scale will not create long-term quality debt - Scale will not create long-term quality debt
--- ---
@@ -135,23 +135,23 @@ If the verdict is **Do Not Proceed**, stop and recommend alternatives.
### 1. Business Context ### 1. Business Context
* Product or service - Product or service
* Target audience - Target audience
* Role of these pages in the funnel - Role of these pages in the funnel
* Primary conversion goal - Primary conversion goal
### 2. Search Opportunity ### 2. Search Opportunity
* Keyword pattern and variables - Keyword pattern and variables
* Estimated page count - Estimated page count
* Demand distribution - Demand distribution
* Trends and seasonality - Trends and seasonality
### 3. Competitive Landscape ### 3. Competitive Landscape
* Who ranks now - Who ranks now
* Nature of ranking pages (editorial vs programmatic) - Nature of ranking pages (editorial vs programmatic)
* Content depth and differentiation - Content depth and differentiation
--- ---
@@ -181,10 +181,10 @@ Weaker data requires **stronger editorial value**.
### 3. URL & Architecture Discipline ### 3. URL & Architecture Discipline
* Prefer subfolders by default - Prefer subfolders by default
* One clear page type per directory - One clear page type per directory
* Predictable, human-readable URLs - Predictable, human-readable URLs
* No parameter-based duplication - No parameter-based duplication
--- ---
@@ -192,10 +192,10 @@ Weaker data requires **stronger editorial value**.
Each page must fully satisfy the intent behind its pattern: Each page must fully satisfy the intent behind its pattern:
* Informational - Informational
* Comparative - Comparative
* Local - Local
* Transactional - Transactional
Partial answers at scale are **high risk**. Partial answers at scale are **high risk**.
@@ -213,16 +213,16 @@ Scaling pages does **not** lower the bar for quality.
Avoid: Avoid:
* Doorway pages - Doorway pages
* Auto-generated filler - Auto-generated filler
* Near-duplicate content - Near-duplicate content
* Indexing pages with no standalone value - Indexing pages with no standalone value
--- ---
## The 12 Programmatic SEO Playbooks ## The 12 Programmatic SEO Playbooks
*(Strategic patterns, not guaranteed wins)* _(Strategic patterns, not guaranteed wins)_
1. Templates 1. Templates
2. Curation 2. Curation
@@ -245,29 +245,29 @@ Only use playbooks supported by **data + intent + feasibility score**.
### 1. Keyword Pattern Definition ### 1. Keyword Pattern Definition
* Pattern structure - Pattern structure
* Variable set - Variable set
* Estimated combinations - Estimated combinations
* Demand validation - Demand validation
--- ---
### 2. Data Model ### 2. Data Model
* Required fields - Required fields
* Data sources - Data sources
* Update frequency - Update frequency
* Missing-data handling - Missing-data handling
--- ---
### 3. Template Specification ### 3. Template Specification
* Mandatory sections - Mandatory sections
* Conditional logic - Conditional logic
* Unique content mechanisms - Unique content mechanisms
* Internal linking rules - Internal linking rules
* Index / noindex criteria - Index / noindex criteria
--- ---
@@ -275,18 +275,17 @@ Only use playbooks supported by **data + intent + feasibility score**.
### Indexation Rules ### Indexation Rules
* Not all generated pages should be indexed - Not all generated pages should be indexed
* Index only pages with: - Index only pages with:
- Demand
* Demand - Unique value
* Unique value - Complete intent match
* Complete intent match
### Crawl Management ### Crawl Management
* Avoid crawl traps - Avoid crawl traps
* Segment sitemaps by page type - Segment sitemaps by page type
* Monitor indexation rate by pattern - Monitor indexation rate by pattern
--- ---
@@ -294,11 +293,11 @@ Only use playbooks supported by **data + intent + feasibility score**.
### Pre-Index Checklist ### Pre-Index Checklist
* Unique value demonstrated - Unique value demonstrated
* Intent fully satisfied - Intent fully satisfied
* No near-duplicates - No near-duplicates
* Performance acceptable - Performance acceptable
* Canonicals correct - Canonicals correct
--- ---
@@ -306,10 +305,10 @@ Only use playbooks supported by **data + intent + feasibility score**.
If triggered, **halt indexing or roll back**: If triggered, **halt indexing or roll back**:
* High impressions, low engagement at scale - High impressions, low engagement at scale
* Thin content warnings - Thin content warnings
* Index bloat with no traffic - Index bloat with no traffic
* Manual or algorithmic suppression signals - Manual or algorithmic suppression signals
--- ---
@@ -319,36 +318,38 @@ If triggered, **halt indexing or roll back**:
**Feasibility Index** **Feasibility Index**
* Overall Score: XX / 100 - Overall Score: XX / 100
* Verdict: Strong Fit / Moderate Fit / High Risk / Do Not Proceed - Verdict: Strong Fit / Moderate Fit / High Risk / Do Not Proceed
* Category breakdown with brief rationale - Category breakdown with brief rationale
**Opportunity Summary** **Opportunity Summary**
* Keyword pattern - Keyword pattern
* Estimated scale - Estimated scale
* Competition overview - Competition overview
**Page System Design** **Page System Design**
* URL pattern - URL pattern
* Data requirements - Data requirements
* Template outline - Template outline
* Indexation rules - Indexation rules
**Risks & Mitigations** **Risks & Mitigations**
* Thin content risk - Thin content risk
* Data quality risk - Data quality risk
* Crawl/indexation risk - Crawl/indexation risk
--- ---
## Related Skills ## Related Skills
* **seo-audit** – Audit programmatic pages post-launch - **seo-audit** – Audit programmatic pages post-launch
* **schema-markup** – Add structured data to templates - **schema-markup** – Add structured data to templates
* **copywriting** – Improve non-templated sections - **copywriting** – Improve non-templated sections
* **analytics-tracking** – Measure performance and validate value - **analytics-tracking** – Measure performance and validate value
```
``` ```

164
skills/schema-markup/SKILL.md
View File

@@ -1,4 +1,3 @@
```yaml
--- ---
name: schema-markup name: schema-markup
description: > description: >
@@ -9,7 +8,6 @@ description: >
safely according to Google guidelines. safely according to Google guidelines.
allowed-tools: Read, Glob, Grep allowed-tools: Read, Glob, Grep
--- ---
```
--- ---
@@ -20,11 +18,11 @@ You are an expert in **structured data and schema markup** with a focus on
Your responsibility is to: Your responsibility is to:
* Determine **whether schema markup is appropriate** - Determine **whether schema markup is appropriate**
* Identify **which schema types are valid and eligible** - Identify **which schema types are valid and eligible**
* Prevent invalid, misleading, or spammy markup - Prevent invalid, misleading, or spammy markup
* Design **maintainable, correct JSON-LD** - Design **maintainable, correct JSON-LD**
* Avoid over-markup that creates false expectations - Avoid over-markup that creates false expectations
You do **not** guarantee rich results. You do **not** guarantee rich results.
You do **not** add schema that misrepresents content. You do **not** add schema that misrepresents content.
@@ -69,9 +67,9 @@ This is a **diagnostic score**, not a promise of rich results.
#### 1. Content–Schema Alignment (0–25) #### 1. Content–Schema Alignment (0–25)
* Schema reflects **visible, user-facing content** - Schema reflects **visible, user-facing content**
* Marked entities actually exist on the page - Marked entities actually exist on the page
* No hidden or implied content - No hidden or implied content
**Automatic failure** if schema describes content not shown. **Automatic failure** if schema describes content not shown.
@@ -79,41 +77,41 @@ This is a **diagnostic score**, not a promise of rich results.
#### 2. Rich Result Eligibility (0–25) #### 2. Rich Result Eligibility (0–25)
* Schema type is **supported by Google** - Schema type is **supported by Google**
* Page meets documented eligibility requirements - Page meets documented eligibility requirements
* No known disqualifying patterns (e.g. self-serving reviews) - No known disqualifying patterns (e.g. self-serving reviews)
--- ---
#### 3. Data Completeness & Accuracy (0–20) #### 3. Data Completeness & Accuracy (0–20)
* All required properties present - All required properties present
* Values are correct, current, and formatted properly - Values are correct, current, and formatted properly
* No placeholders or fabricated data - No placeholders or fabricated data
--- ---
#### 4. Technical Correctness (0–15) #### 4. Technical Correctness (0–15)
* Valid JSON-LD - Valid JSON-LD
* Correct nesting and types - Correct nesting and types
* No syntax, enum, or formatting errors - No syntax, enum, or formatting errors
--- ---
#### 5. Maintenance & Sustainability (0–10) #### 5. Maintenance & Sustainability (0–10)
* Data can be kept in sync with content - Data can be kept in sync with content
* Updates won’t break schema - Updates won’t break schema
* Suitable for templates if scaled - Suitable for templates if scaled
--- ---
#### 6. Spam / Policy Risk (0–5) #### 6. Spam / Policy Risk (0–5)
* No deceptive intent - No deceptive intent
* No over-markup - No over-markup
* No attempt to game rich results - No attempt to game rich results
--- ---
@@ -136,21 +134,21 @@ If verdict is **Do Not Implement**, stop and explain why.
### 1. Page Type ### 1. Page Type
* What kind of page is this? - What kind of page is this?
* Primary content entity - Primary content entity
* Single-entity vs multi-entity page - Single-entity vs multi-entity page
### 2. Current State ### 2. Current State
* Existing schema present? - Existing schema present?
* Errors or warnings? - Errors or warnings?
* Rich results currently shown? - Rich results currently shown?
### 3. Objective ### 3. Objective
* Which rich result (if any) is targeted? - Which rich result (if any) is targeted?
* Expected benefit (CTR, clarity, trust) - Expected benefit (CTR, clarity, trust)
* Is schema *necessary* to achieve this? - Is schema _necessary_ to achieve this?
--- ---
@@ -158,39 +156,39 @@ If verdict is **Do Not Implement**, stop and explain why.
### 1. Accuracy Over Ambition ### 1. Accuracy Over Ambition
* Schema must match visible content exactly - Schema must match visible content exactly
* Do not “add content for schema” - Do not “add content for schema”
* Remove schema if content is removed - Remove schema if content is removed
--- ---
### 2. Google First, Schema.org Second ### 2. Google First, Schema.org Second
* Follow **Google rich result documentation** - Follow **Google rich result documentation**
* Schema.org allows more than Google supports - Schema.org allows more than Google supports
* Unsupported types provide minimal SEO value - Unsupported types provide minimal SEO value
--- ---
### 3. Minimal, Purposeful Markup ### 3. Minimal, Purposeful Markup
* Add only schema that serves a clear purpose - Add only schema that serves a clear purpose
* Avoid redundant or decorative markup - Avoid redundant or decorative markup
* More schema ≠ better SEO - More schema ≠ better SEO
--- ---
### 4. Continuous Validation ### 4. Continuous Validation
* Validate before deployment - Validate before deployment
* Monitor Search Console enhancements - Monitor Search Console enhancements
* Fix errors promptly - Fix errors promptly
--- ---
## Supported & Common Schema Types ## Supported & Common Schema Types
*(Only implement when eligibility criteria are met.)* _(Only implement when eligibility criteria are met.)_
### Organization ### Organization
@@ -221,9 +219,9 @@ Use for: SaaS apps and tools
Use only when: Use only when:
* Questions and answers are visible - Questions and answers are visible
* Not used for promotional content - Not used for promotional content
* Not user-generated without moderation - Not user-generated without moderation
--- ---
@@ -231,8 +229,8 @@ Use only when:
Use only for: Use only for:
* Genuine step-by-step instructional content - Genuine step-by-step instructional content
* Not marketing funnels - Not marketing funnels
--- ---
@@ -252,9 +250,9 @@ Use for: real, physical business locations
**Strict rules:** **Strict rules:**
* Reviews must be genuine - Reviews must be genuine
* No self-serving reviews - No self-serving reviews
* Ratings must match visible content - Ratings must match visible content
--- ---
@@ -270,9 +268,9 @@ Use `@graph` when representing multiple entities.
Rules: Rules:
* One primary entity per page - One primary entity per page
* Others must relate logically - Others must relate logically
* Avoid conflicting entity definitions - Avoid conflicting entity definitions
--- ---
@@ -280,17 +278,17 @@ Rules:
### Required Tools ### Required Tools
* Google Rich Results Test - Google Rich Results Test
* Schema.org Validator - Schema.org Validator
* Search Console Enhancements - Search Console Enhancements
### Common Failure Patterns ### Common Failure Patterns
* Missing required properties - Missing required properties
* Mismatched values - Mismatched values
* Hidden or fabricated data - Hidden or fabricated data
* Incorrect enum values - Incorrect enum values
* Dates not in ISO 8601 - Dates not in ISO 8601
--- ---
@@ -298,19 +296,19 @@ Rules:
### Static Sites ### Static Sites
* Embed JSON-LD in templates - Embed JSON-LD in templates
* Use includes for reuse - Use includes for reuse
### Frameworks (React / Next.js) ### Frameworks (React / Next.js)
* Server-side rendered JSON-LD - Server-side rendered JSON-LD
* Data serialized directly from source - Data serialized directly from source
### CMS / WordPress ### CMS / WordPress
* Prefer structured plugins - Prefer structured plugins
* Use custom fields for dynamic values - Use custom fields for dynamic values
* Avoid hardcoded schema in themes - Avoid hardcoded schema in themes
--- ---
@@ -318,9 +316,9 @@ Rules:
### Schema Strategy Summary ### Schema Strategy Summary
* Eligibility Index score + verdict - Eligibility Index score + verdict
* Supported schema types - Supported schema types
* Risks and constraints - Risks and constraints
### JSON-LD Implementation ### JSON-LD Implementation
@@ -338,10 +336,10 @@ Where and how to add it
### Validation Checklist ### Validation Checklist
* [ ] Valid JSON-LD - [ ] Valid JSON-LD
* [ ] Passes Rich Results Test - [ ] Passes Rich Results Test
* [ ] Matches visible content - [ ] Matches visible content
* [ ] Meets Google eligibility rules - [ ] Meets Google eligibility rules
--- ---
@@ -357,9 +355,9 @@ Where and how to add it
## Related Skills ## Related Skills
* **seo-audit** – Full SEO review including schema - **seo-audit** – Full SEO review including schema
* **programmatic-seo** – Templated schema at scale - **programmatic-seo** – Templated schema at scale
* **analytics-tracking** – Measure rich result impact - **analytics-tracking** – Measure rich result impact
``` ```

29
skills/seo-fundamentals/SKILL.md
View File

@@ -1,4 +1,3 @@
```yaml
--- ---
name: seo-fundamentals name: seo-fundamentals
description: > description: >
@@ -7,14 +6,13 @@ description: >
*why* SEO works, not how to execute specific optimizations. *why* SEO works, not how to execute specific optimizations.
allowed-tools: Read, Glob, Grep allowed-tools: Read, Glob, Grep
--- ---
```
--- ---
# SEO Fundamentals # SEO Fundamentals
> **Foundational principles for sustainable search visibility.** > **Foundational principles for sustainable search visibility.**
> This skill explains *how search engines evaluate quality*, not tactical shortcuts. > This skill explains _how search engines evaluate quality_, not tactical shortcuts.
--- ---
@@ -46,9 +44,9 @@ Core Web Vitals measure **how users experience a page**, not whether it deserves
**Important context:** **Important context:**
* CWV rarely override poor content - CWV rarely override poor content
* They matter most when content quality is comparable - They matter most when content quality is comparable
* Failing CWV can *hold back* otherwise good pages - Failing CWV can _hold back_ otherwise good pages
--- ---
@@ -125,17 +123,17 @@ Search engines evaluate **output quality**, not authorship method.
### Effective Use ### Effective Use
* AI as a drafting or research assistant - AI as a drafting or research assistant
* Human review for accuracy and clarity - Human review for accuracy and clarity
* Original insights and synthesis - Original insights and synthesis
* Clear accountability - Clear accountability
### Risky Use ### Risky Use
* Publishing unedited AI output - Publishing unedited AI output
* Factual errors or hallucinations - Factual errors or hallucinations
* Thin or duplicated content - Thin or duplicated content
* Keyword-driven text with no value - Keyword-driven text with no value
--- ---
@@ -171,6 +169,5 @@ SEO fundamentals should be validated using **multiple signals**, not single metr
--- ---
> **Key Principle:** > **Key Principle:**
> Sustainable SEO is built on *useful content*, *technical clarity*, and *trust over time*. > Sustainable SEO is built on _useful content_, _technical clarity_, and _trust over time_.
> There are no permanent shortcuts. > There are no permanent shortcuts.