[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MEEBJNAHCB3CCB6PSEBP5G":3,"skill-same:01M6MEEBJNAHCB3CCB6PSEBP5G":107},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":66,"commitSha":67,"skillDirectory":68,"forksCount":69,"repositoryHtmlUrl":70,"repositoryHomepageUrl":71,"ownerHtmlUrl":72,"ownerBlogUrl":73,"ownerDescription":74,"updatedAt":75,"install":76,"resources":88},"01M6MEEBJNAHCB3CCB6PSEBP5G","seo-sxo",null,"Search Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says \"SXO\", \"search experience\", \"page type mismatch\", \"SERP analysis\", \"user story\", \"persona scoring\", \"why isn't my page ranking\", \"intent mismatch\", or \"wireframe\".","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1571,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favalonreset\u002Fseo-dungeon\u002Fskills\u002Fseo-sxo\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"seo sxo","seo","sxo","when","for","user stories","my","google","analyzing","why","intent","signals","perspectives","scoring","analysis","URL","persona","challenge","ranking","serp analysis","search","user story","2026-11-10 10:12:30",false,"---\nname: seo-sxo\ndescription: >\n  Search Experience Optimization: reads Google SERPs backwards to detect page-type\n  mismatches, derives user stories from search intent signals, and scores pages\n  from multiple persona perspectives. Identifies why well-optimized pages fail\n  to rank by analyzing what Google rewards for each keyword. Use when user says\n  \"SXO\", \"search experience\", \"page type mismatch\", \"SERP analysis\", \"user story\",\n  \"persona scoring\", \"why isn't my page ranking\", \"intent mismatch\", or \"wireframe\".\nuser-invocable: true\nargument-hint: \"\u003Curl> [keyword]\"\nlicense: MIT\nmetadata:\n  author: AgriciDaniel\n  original_author: \"Florian Schmitz (Pro Hub Challenge)\"\n  version: \"2.2.7\"\n  category: seo\n---\n\n# Search Experience Optimization (SXO)\n\nSXO bridges the gap between SEO (what Google rewards) and UX (what users need).\nTraditional SEO audits check technical health. SXO asks: \"Does this page deserve\nto rank for this keyword based on what Google is actually rewarding in the SERP?\"\n\n## Core Insight\n\nA page can score 95\u002F100 on technical SEO and still fail to rank because it is the\n**wrong page type** for the keyword. If Google shows 8 product pages and 2 comparison\npages for your keyword, your blog post will never break through -- no matter how\nwell-optimized it is.\n\n## Commands\n\n| Command | Purpose |\n|---------|---------|\n| `\u002Fseo sxo \u003Curl>` | Full SXO analysis (auto-detect keyword from page) |\n| `\u002Fseo sxo \u003Curl> \u003Ckeyword>` | Full SXO analysis for a specific keyword |\n| `\u002Fseo sxo wireframe \u003Curl>` | Generate IST\u002FSOLL wireframe with concrete placeholders |\n| `\u002Fseo sxo personas \u003Curl>` | Persona-only scoring (skip SERP analysis) |\n\n## Execution Pipeline\n\n### Step 1: Target Acquisition\n\n1. Fetch the target URL via `claude-seo run render_page.py \u003CURL> --mode auto` (SPA-aware and SSRF-safe)\n2. Parse with `claude-seo run parse_html.py \u003CURL>` to extract: title, H1, meta description,\n   headings hierarchy, word count, schema markup, CTAs, media elements\n3. If no keyword provided, extract primary keyword from title tag + H1 overlap\n4. Validate keyword is non-empty before proceeding\n\n### Step 2: SERP Backwards Analysis\n\nRead `references\u002Fpage-type-taxonomy.md` for classification rules.\n\n1. Search Google for the target keyword (WebSearch)\n2. For each of the top 10 organic results, record:\n   - URL and domain authority tier (brand \u002F niche authority \u002F unknown)\n   - Page type (classify using taxonomy)\n   - Content format (long-form, listicle, how-to, comparison, tool, video)\n   - Word count estimate (from snippet length and page structure)\n   - Schema types present (from currently supported SERP features; exclude FAQ\u002FHowTo)\n   - Media signals (video carousel, image pack, thumbnail presence)\n3. Record SERP features present:\n   - Featured snippet (paragraph \u002F list \u002F table \u002F video)\n   - People Also Ask (extract all visible questions)\n   - Ads (top and bottom -- count and analyze ad copy themes)\n   - Related searches (extract all)\n   - Knowledge panel \u002F local pack \u002F shopping results\n   - AI Overview presence and source types\n4. Calculate SERP consensus:\n   - Dominant page type (>60% = strong consensus, 40-60% = mixed, \u003C40% = fragmented)\n   - Content depth expectations (average word count tier)\n   - Schema expectation (most common structured data types)\n   - Media expectations (video required? images critical?)\n\n### Step 3: Page-Type Mismatch Detection\n\nThis is the core SXO insight. Compare target page type against SERP consensus.\n\n**Mismatch severity levels:**\n\n| Target Type | SERP Expects | Severity | Recommendation |\n|-------------|-------------|----------|----------------|\n| Blog Post | Product Pages | CRITICAL | Create dedicated product page |\n| Blog Post | Comparison | HIGH | Restructure as comparison with matrix |\n| Product | Informational | HIGH | Add educational content layer |\n| Landing Page | Tool\u002FCalculator | HIGH | Build interactive tool component |\n| Service Page | Local Results | MEDIUM | Add location signals + local schema |\n| Any type match | - | ALIGNED | Focus on content depth and UX |\n\n**Classification rules:**\n- Classify target page using `references\u002Fpage-type-taxonomy.md`\n- Classify each SERP result using the same taxonomy\n- Flag mismatch if target type differs from SERP dominant type\n- If SERP is fragmented (no dominant type), note opportunity for differentiation\n\n### Step 4: User Story Derivation\n\nRead `references\u002Fuser-story-framework.md` for the full framework.\n\nFrom SERP signals, derive user stories:\n\n1. **PAA questions** reveal knowledge gaps and concerns\n2. **Ad copy themes** reveal commercial triggers and value propositions\n3. **Related searches** reveal the search journey (what comes before\u002Fafter)\n4. **Featured snippet format** reveals the expected answer structure\n5. **AI Overview** reveals what Google considers the definitive answer\n\nFor each signal cluster, generate a user story:\n```\nAs a [persona derived from signal],\nI want to [goal derived from query intent],\nbecause [emotional driver from ad copy \u002F PAA tone],\nbut I'm blocked by [barrier derived from PAA questions \u002F related searches].\n```\n\nGenerate 3-5 user stories covering the primary intent angles.\n\n### Step 5: Gap Analysis\n\nCompare the target page against SERP expectations across 7 dimensions:\n\n| Dimension | What to Compare | Score |\n|-----------|----------------|-------|\n| Page Type | Target type vs SERP dominant type | 0-15 |\n| Content Depth | Word count, heading depth, topic coverage | 0-15 |\n| UX Signals | CTA clarity, above-fold content, mobile layout | 0-15 |\n| Schema Markup | Present vs expected structured data types | 0-15 |\n| Media Richness | Images, video, interactive elements vs SERP norm | 0-15 |\n| Authority Signals | E-E-A-T markers, social proof, credentials | 0-15 |\n| Freshness | Last updated, date signals, content recency | 0-10 |\n\n**Total: 0-100 SXO Gap Score** (lower = larger gap, higher = better alignment)\n\n### Step 6: Persona-Based Scoring\n\nRead `references\u002Fpersona-scoring.md` for methodology.\n\n1. Derive 4-7 personas from SERP intent signals:\n   - Cluster PAA questions by theme\n   - Segment ad copy by target audience\n   - Map related searches to journey stages\n2. For each persona, score the target page on 4 dimensions (25 pts each):\n   - **Relevance**: Does the page address this persona's need?\n   - **Clarity**: Can this persona find their answer within 10 seconds?\n   - **Trust**: Are there adequate trust signals for this persona?\n   - **Action**: Is there a clear next step for this persona?\n3. Output persona cards with scores and specific improvement recommendations\n4. Sort recommendations by weakest persona first (biggest opportunity)\n\n### Step 7: Wireframe Generation (Optional)\n\nOnly execute when `\u002Fseo sxo wireframe` is invoked.\n\nRead `references\u002Fwireframe-templates.md` for templates.\n\n1. Generate IST (current state) wireframe from parsed page structure\n2. Generate SOLL (target state) wireframe based on:\n   - SERP consensus page type\n   - Gap analysis findings\n   - Persona scoring weaknesses\n3. Use ultra-concrete placeholders:\n   - NOT: \"Add a CTA here\"\n   - YES: \"Add pricing CTA with annual savings badge below hero, linking to \u002Fpricing#enterprise\"\n4. Output as semantic HTML section outline with annotations\n\n## DataForSEO Integration\n\nIf DataForSEO credentials or optional tools are available:\n\n1. **Before any API call**, run cost estimate and confirm with user\n2. Use `serp_organic_live_advanced` for precise SERP data (positions, features, snippets)\n3. Use `kw_data_google_ads_search_volume` for search volume and competition metrics\n4. Fall back to WebSearch if DataForSEO unavailable -- note reduced precision in output\n\n## SXO Score vs SEO Health Score\n\nThe SXO score is **separate** from the main SEO Health Score.\n\n- SEO Health Score = technical compliance (crawlability, speed, schema, etc.)\n- SXO Gap Score = alignment between page and SERP expectations\n- A page can score 95 SEO + 30 SXO = technically perfect but strategically misaligned\n- Both scores should be reported together when both are available\n\n## Cross-Skill References\n\n| Finding | Hand Off To |\n|---------|-------------|\n| E-E-A-T gaps in persona scoring | `\u002Fseo content` for deep E-E-A-T audit |\n| Missing schema types | `\u002Fseo schema` for generation |\n| Local intent detected in SERP | `\u002Fseo local` for GBP analysis |\n| Content depth gaps | `\u002Fseo page` for deep page analysis |\n| Technical issues found during fetch | `\u002Fseo technical` for full audit |\n| Image\u002Fmedia gaps | `\u002Fseo images` for optimization |\n\n## Output Format\n\n### Full SXO Analysis\n\n```\n## SXO Analysis: [URL]\n### Target Keyword: [keyword]\n\n### 1. SERP Landscape\n- Dominant page type: [type] ([confidence]% consensus)\n- SERP features: [list]\n- Content depth norm: [word count range]\n- Schema expectation: [types]\n\n### 2. Page-Type Alignment\n- Your page type: [type]\n- SERP expects: [type]\n- Verdict: [ALIGNED | MISMATCH (severity)]\n- Impact: [explanation]\n\n### 3. User Stories (derived from SERP signals)\n[3-5 user stories with source signals]\n\n### 4. Gap Analysis (SXO Score: XX\u002F100)\n[7-dimension breakdown table]\n\n### 5. Persona Scores\n[4-7 persona cards with 4-dimension scores]\n\n### 6. Priority Actions\n[Ranked list: fix mismatch first, then weakest persona gaps]\n\n### 7. Limitations\n[What could not be assessed, data source notes]\n```\n\n## Error Handling\n\n| Error | Action |\n|-------|--------|\n| URL fetch fails | Report error, suggest checking URL accessibility |\n| No keyword provided or detected | Ask user to provide target keyword |\n| WebSearch returns \u003C5 results | Proceed with available data, note limited sample |\n| SERP has no organic results (all ads) | Note highly commercial SERP, analyze ad copy only |\n| Target page is JavaScript-rendered | Note limitation, use available HTML content |\n| DataForSEO cost exceeds threshold | Fall back to WebSearch, notify user |\n\n## Quality Checklist\n\nBefore delivering results, verify:\n- [ ] Target URL was fetched via `claude-seo run render_page.py \u003CURL> --mode auto` (not raw curl\u002Ffetch)\n- [ ] Page type classification uses taxonomy from references\n- [ ] At least 5 SERP results were analyzed\n- [ ] User stories cite specific SERP signals as evidence\n- [ ] Persona scores include concrete improvement suggestions\n- [ ] SXO score is clearly labeled as separate from SEO Health Score\n- [ ] Limitations section is present and honest\n- [ ] Cross-skill recommendations are included where relevant\n","# Search Experience Optimization (SXO)\n\nSXO bridges the gap between SEO (what Google rewards) and UX (what users need).\nTraditional SEO audits check technical health. SXO asks: \"Does this page deserve\nto rank for this keyword based on what Google is actually rewarding in the SERP?\"\n\n## Core Insight\n\nA page can score 95\u002F100 on technical SEO and still fail to rank because it is the\n**wrong page type** for the keyword. If Google shows 8 product pages and 2 comparison\npages for your keyword, your blog post will never break through -- no matter how\nwell-optimized it is.\n\n## Commands\n\n| Command | Purpose |\n|---------|---------|\n| `\u002Fseo sxo \u003Curl>` | Full SXO analysis (auto-detect keyword from page) |\n| `\u002Fseo sxo \u003Curl> \u003Ckeyword>` | Full SXO analysis for a specific keyword |\n| `\u002Fseo sxo wireframe \u003Curl>` | Generate IST\u002FSOLL wireframe with concrete placeholders |\n| `\u002Fseo sxo personas \u003Curl>` | Persona-only scoring (skip SERP analysis) |\n\n## Execution Pipeline\n\n### Step 1: Target Acquisition\n\n1. Fetch the target URL via `claude-seo run render_page.py \u003CURL> --mode auto` (SPA-aware and SSRF-safe)\n2. Parse with `claude-seo run parse_html.py \u003CURL>` to extract: title, H1, meta description,\n   headings hierarchy, word count, schema markup, CTAs, media elements\n3. If no keyword provided, extract primary keyword from title tag + H1 overlap\n4. Validate keyword is non-empty before proceeding\n\n### Step 2: SERP Backwards Analysis\n\nRead `references\u002Fpage-type-taxonomy.md` for classification rules.\n\n1. Search Google for the target keyword (WebSearch)\n2. For each of the top 10 organic results, record:\n   - URL and domain authority tier (brand \u002F niche authority \u002F unknown)\n   - Page type (classify using taxonomy)\n   - Content format (long-form, listicle, how-to, comparison, tool, video)\n   - Word count estimate (from snippet length and page structure)\n   - Schema types present (from currently supported SERP features; exclude FAQ\u002FHowTo)\n   - Media signals (video carousel, image pack, thumbnail presence)\n3. Record SERP features present:\n   - Featured snippet (paragraph \u002F list \u002F table \u002F video)\n   - People Also Ask (extract all visible questions)\n   - Ads (top and bottom -- count and analyze ad copy themes)\n   - Related searches (extract all)\n   - Knowledge panel \u002F local pack \u002F shopping results\n   - AI Overview presence and source types\n4. Calculate SERP consensus:\n   - Dominant page type (>60% = strong consensus, 40-60% = mixed, \u003C40% = fragmented)\n   - Content depth expectations (average word count tier)\n   - Schema expectation (most common structured data types)\n   - Media expectations (video required? images critical?)\n\n### Step 3: Page-Type Mismatch Detection\n\nThis is the core SXO insight. Compare target page type against SERP consensus.\n\n**Mismatch severity levels:**\n\n| Target Type | SERP Expects | Severity | Recommendation |\n|-------------|-------------|----------|----------------|\n| Blog Post | Product Pages | CRITICAL | Create dedicated product page |\n| Blog Post | Comparison | HIGH | Restructure as comparison with matrix |\n| Product | Informational | HIGH | Add educational content layer |\n| Landing Page | Tool\u002FCalculator | HIGH | Build interactive tool component |\n| Service Page | Local Results | MEDIUM | Add location signals + local schema |\n| Any type match | - | ALIGNED | Focus on content depth and UX |\n\n**Classification rules:**\n- Classify target page using `references\u002Fpage-type-taxonomy.md`\n- Classify each SERP result using the same taxonomy\n- Flag mismatch if target type differs from SERP dominant type\n- If SERP is fragmented (no dominant type), note opportunity for differentiation\n\n### Step 4: User Story Derivation\n\nRead `references\u002Fuser-story-framework.md` for the full framework.\n\nFrom SERP signals, derive user stories:\n\n1. **PAA questions** reveal knowledge gaps and concerns\n2. **Ad copy themes** reveal commercial triggers and value propositions\n3. **Related searches** reveal the search journey (what comes before\u002Fafter)\n4. **Featured snippet format** reveals the expected answer structure\n5. **AI Overview** reveals what Google considers the definitive answer\n\nFor each signal cluster, generate a user story:\n```\nAs a [persona derived from signal],\nI want to [goal derived from query intent],\nbecause [emotional driver from ad copy \u002F PAA tone],\nbut I'm blocked by [barrier derived from PAA questions \u002F related searches].\n```\n\nGenerate 3-5 user stories covering the primary intent angles.\n\n### Step 5: Gap Analysis\n\nCompare the target page against SERP expectations across 7 dimensions:\n\n| Dimension | What to Compare | Score |\n|-----------|----------------|-------|\n| Page Type | Target type vs SERP dominant type | 0-15 |\n| Content Depth | Word count, heading depth, topic coverage | 0-15 |\n| UX Signals | CTA clarity, above-fold content, mobile layout | 0-15 |\n| Schema Markup | Present vs expected structured data types | 0-15 |\n| Media Richness | Images, video, interactive elements vs SERP norm | 0-15 |\n| Authority Signals | E-E-A-T markers, social proof, credentials | 0-15 |\n| Freshness | Last updated, date signals, content recency | 0-10 |\n\n**Total: 0-100 SXO Gap Score** (lower = larger gap, higher = better alignment)\n\n### Step 6: Persona-Based Scoring\n\nRead `references\u002Fpersona-scoring.md` for methodology.\n\n1. Derive 4-7 personas from SERP intent signals:\n   - Cluster PAA questions by theme\n   - Segment ad copy by target audience\n   - Map related searches to journey stages\n2. For each persona, score the target page on 4 dimensions (25 pts each):\n   - **Relevance**: Does the page address this persona's need?\n   - **Clarity**: Can this persona find their answer within 10 seconds?\n   - **Trust**: Are there adequate trust signals for this persona?\n   - **Action**: Is there a clear next step for this persona?\n3. Output persona cards with scores and specific improvement recommendations\n4. Sort recommendations by weakest persona first (biggest opportunity)\n\n### Step 7: Wireframe Generation (Optional)\n\nOnly execute when `\u002Fseo sxo wireframe` is invoked.\n\nRead `references\u002Fwireframe-templates.md` for templates.\n\n1. Generate IST (current state) wireframe from parsed page structure\n2. Generate SOLL (target state) wireframe based on:\n   - SERP consensus page type\n   - Gap analysis findings\n   - Persona scoring weaknesses\n3. Use ultra-concrete placeholders:\n   - NOT: \"Add a CTA here\"\n   - YES: \"Add pricing CTA with annual savings badge below hero, linking to \u002Fpricing#enterprise\"\n4. Output as semantic HTML section outline with annotations\n\n## DataForSEO Integration\n\nIf DataForSEO credentials or optional tools are available:\n\n1. **Before any API call**, run cost estimate and confirm with user\n2. Use `serp_organic_live_advanced` for precise SERP data (positions, features, snippets)\n3. Use `kw_data_google_ads_search_volume` for search volume and competition metrics\n4. Fall back to WebSearch if DataForSEO unavailable -- note reduced precision in output\n\n## SXO Score vs SEO Health Score\n\nThe SXO score is **separate** from the main SEO Health Score.\n\n- SEO Health Score = technical compliance (crawlability, speed, schema, etc.)\n- SXO Gap Score = alignment between page and SERP expectations\n- A page can score 95 SEO + 30 SXO = technically perfect but strategically misaligned\n- Both scores should be reported together when both are available\n\n## Cross-Skill References\n\n| Finding | Hand Off To |\n|---------|-------------|\n| E-E-A-T gaps in persona scoring | `\u002Fseo content` for deep E-E-A-T audit |\n| Missing schema types | `\u002Fseo schema` for generation |\n| Local intent detected in SERP | `\u002Fseo local` for GBP analysis |\n| Content depth gaps | `\u002Fseo page` for deep page analysis |\n| Technical issues found during fetch | `\u002Fseo technical` for full audit |\n| Image\u002Fmedia gaps | `\u002Fseo images` for optimization |\n\n## Output Format\n\n### Full SXO Analysis\n\n```\n## SXO Analysis: [URL]\n### Target Keyword: [keyword]\n\n### 1. SERP Landscape\n- Dominant page type: [type] ([confidence]% consensus)\n- SERP features: [list]\n- Content depth norm: [word count range]\n- Schema expectation: [types]\n\n### 2. Page-Type Alignment\n- Your page type: [type]\n- SERP expects: [type]\n- Verdict: [ALIGNED | MISMATCH (severity)]\n- Impact: [explanation]\n\n### 3. User Stories (derived from SERP signals)\n[3-5 user stories with source signals]\n\n### 4. Gap Analysis (SXO Score: XX\u002F100)\n[7-dimension breakdown table]\n\n### 5. Persona Scores\n[4-7 persona cards with 4-dimension scores]\n\n### 6. Priority Actions\n[Ranked list: fix mismatch first, then weakest persona gaps]\n\n### 7. Limitations\n[What could not be assessed, data source notes]\n```\n\n## Error Handling\n\n| Error | Action |\n|-------|--------|\n| URL fetch fails | Report error, suggest checking URL accessibility |\n| No keyword provided or detected | Ask user to provide target keyword |\n| WebSearch returns \u003C5 results | Proceed with available data, note limited sample |\n| SERP has no organic results (all ads) | Note highly commercial SERP, analyze ad copy only |\n| Target page is JavaScript-rendered | Note limitation, use available HTML content |\n| DataForSEO cost exceeds threshold | Fall back to WebSearch, notify user |\n\n## Quality Checklist\n\nBefore delivering results, verify:\n- [ ] Target URL was fetched via `claude-seo run render_page.py \u003CURL> --mode auto` (not raw curl\u002Ffetch)\n- [ ] Page type classification uses taxonomy from references\n- [ ] At least 5 SERP results were analyzed\n- [ ] User stories cite specific SERP signals as evidence\n- [ ] Persona scores include concrete improvement suggestions\n- [ ] SXO score is clearly labeled as separate from SEO Health Score\n- [ ] Limitations section is present and honest\n- [ ] Cross-skill recommendations are included where relevant\n",{"name":5,"license":15,"metadata":59,"description":63,"argument-hint":64,"user-invocable":65},{"author":60,"version":61,"category":33,"original_author":62},"AgriciDaniel","2.2.7","Florian Schmitz (Pro Hub Challenge)","Search Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says \"SXO\", \"search experience\", \"page type mismatch\", \"SERP analysis\", \"user story\", \"persona scoring\", \"why isn't my page ranking\", \"intent mismatch\", or \"wireframe\".\n","\u003Curl> [keyword]",true,"main","40706766fd37c03ca624f5206741fef55dd2a684","plugins\u002Favalonreset\u002Fseo-dungeon\u002Fskills\u002Fseo-sxo",490,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 02:12:02",{"source":8,"skillName":5,"commands":77,"prompt":87,"zipAvailable":65},[78,81,84],{"tool":79,"command":80},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill seo-sxo",{"tool":82,"command":83},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill seo-sxo",{"tool":85,"command":86},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill seo-sxo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favalonreset\u002Fseo-dungeon\u002Fskills\u002Fseo-sxo\u002FSKILL.md",[89,95,99,103],{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fpage-type-taxonomy.md","REFERENCE","参考文档",7382,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favalonreset\u002Fseo-dungeon\u002Fskills\u002Fseo-sxo\u002Freferences\u002Fpage-type-taxonomy.md",{"path":96,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fpersona-scoring.md",6353,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favalonreset\u002Fseo-dungeon\u002Fskills\u002Fseo-sxo\u002Freferences\u002Fpersona-scoring.md",{"path":100,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fuser-story-framework.md",5694,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favalonreset\u002Fseo-dungeon\u002Fskills\u002Fseo-sxo\u002Freferences\u002Fuser-story-framework.md",{"path":104,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fwireframe-templates.md",6493,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favalonreset\u002Fseo-dungeon\u002Fskills\u002Fseo-sxo\u002Freferences\u002Fwireframe-templates.md",[108,117,124,131,156,181],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":116},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":116},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":116},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":54},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[52,138,139,140,141,142,143,144,145,146,147,35,148,149,150,151,152,153,154,155],"deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":54},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[163,164,165,151,166,167,168,169,170,171,172,173,174,175,142,176,177,178,179,180],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":196,"publishedAt":54},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[187,190,193],{"categoryNo":188,"categoryName":189,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":191,"categoryName":192,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":194,"categoryName":195,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[183,47,197,198,199,200,201,177,202,143,203,204,205,206,35,207,208,209,210,211],"Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]