[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSZ8AT8KKYY8DXF6A01VH1":3,"skill-same:01M7CSZ8AT8KKYY8DXF6A01VH1":72},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":38,"updatedAt":39,"install":40,"resources":52},"01M7CSZ8AT8KKYY8DXF6A01VH1","seo-content-brief",null,"Generate competitive SEO content briefs with per-section word counts, competitor scoring, keyword density guidance, and page-type templates. Supports both new page briefs and improve-existing-page briefs. Use when user says \"content brief\", \"write a brief\", \"content outline\", \"blog brief\", \"service page brief\", \"brief for\", \"writing brief\", \"content plan\", or \"outline for\".","peterish8\u002Fprats-skill-atlas","peterish8","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F181628466?v=4","01M7CHQAPN6X8D29E2Q8DW4BYF","Prathick Dhanes R","01M7CHQAQ7T42E6D8HH3CZH342",1,"MIT","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fresearch-data\u002Fresearch-seo-and-content\u002Fseo-content-brief\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fresearch-data\u002Fresearch-seo-and-content\u002Fseo-content-brief\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: seo-content-brief\ndescription: >\n  Generate competitive SEO content briefs with per-section word counts,\n  competitor scoring, keyword density guidance, and page-type templates.\n  Supports both new page briefs and improve-existing-page briefs.\n  Use when user says \"content brief\", \"write a brief\", \"content outline\",\n  \"blog brief\", \"service page brief\", \"brief for\", \"writing brief\",\n  \"content plan\", or \"outline for\".\nuser-invocable: true\nargument-hint: \"[url-or-keyword] [page-type]\"\nlicense: MIT\nmetadata:\n  author: puneetindersingh\n  original_author: puneetindersingh\n  version: \"1.0.0\"\n  category: seo\n---\n\n# SEO Content Brief Generator\n\nGenerate research-backed content briefs that help writers produce pages capable of outranking current top results. Briefs include competitor analysis with gap scoring, per-section word count breakdowns, keyword placement rules, and page-type-specific templates.\n\n## Process\n\n### 1. Determine Brief Mode\n\n**Improve mode** (existing page URL provided):\n- Fetch the existing page content and structure\n- Identify what is already strong (keep it)\n- Identify missing, thin, or outdated sections\n- Distinguish \"keep\u002Fstrengthen\" vs \"add new\" sections in the outline\n- Do not recommend a full rewrite when targeted improvements will win\n\n**New page mode** (keyword or topic provided, no existing page):\n- Use the target site's homepage or sitemap for business context only\n- Build the brief from scratch for a new page\n- Focus on competitive gaps the new page can fill\n\n### 2. Fetch Context\n\n- Fetch the target URL or homepage to understand the business\n- Fetch the sitemap to discover all existing pages, categories, and services\n- This context is critical for the Website Relevance Rule (see below)\n\n### 3. Analyse SERPs\n\n- Identify the top 5 ranking pages for the target keyword\n- Filter out non-competitors (Wikipedia, Reddit, Pinterest, Amazon, YouTube, government sites, SEO tool pages, job boards, directories, news aggregators, social platforms). See `references\u002Fexcluded-domains.md` for the full list.\n- Score each real competitor: Depth (1-10), Formatting (1-10), SEO (1-10), UX (1-10)\n- Identify three gap types:\n  - **Topic gaps:** subtopics competitors miss entirely\n  - **Depth gaps:** topics covered but shallow\n  - **Quality gaps:** outdated info, no expert perspective, poor formatting\n- Calculate gap priority: `Impact x Competitive Advantage \u002F Effort`\n\n### 4. Classify Search Intent\n\n- **Informational:** user wants to learn (guides, how-tos, definitions)\n- **Commercial:** user is researching before buying (comparisons, reviews, \"best X\")\n- **Transactional:** user is ready to act (buy, book, enquire, sign up)\n- **Navigational:** user is looking for a specific site or page\n\nIdentify what SERP format Google rewards for this query: long-form guide, listicle, comparison table, landing page, FAQ, video, local pack.\n\n### 5. Build the Brief\n\nApply the page-type template from `references\u002Fpage-type-templates.md`, then customise based on competitor gaps and search intent.\n\n## Critical Rules\n\n### Website Relevance Rule\n\nEvery heading, subtopic, keyword, and FAQ you suggest must be something the target website can credibly write about based on its actual services or products.\n\n- Read the site's homepage and sitemap to understand what it does\n- Do not borrow competitor structure if those sections cover things this site does not offer\n- Before each suggestion, ask: \"Can this website actually deliver on this content?\" If no, remove it.\n\n### Site Structure Coverage Rule\n\nWhen briefing a hub, overview, category, or \"types of\" page:\n- The outline must reference every relevant product category, service, or sub-page that exists on the site\n- Do not invent categories that don't exist, do not leave out categories that do exist\n- Each category should appear as its own section with an internal link suggestion\n- This ensures the page acts as a proper hub linking to all child pages\n\nFor non-hub pages (single service page, blog post), use site structure to suggest relevant internal links but do not force every category into the outline.\n\n### Output Language Rules\n\n- Never mention researcher names, framework names, or tool names in the output (no \"Ben Goodey method\", \"Frase.io formula\", \"Princeton GEO\", \"Clearscope\", \"Backlinko\")\n- These are internal thinking tools only. The output must read as plain, professional advice.\n- Write for a business owner or content writer, not an SEO academic\n\n## Keyword Density and Placement\n\nRead `references\u002Fkeyword-density.md` for the full rules. Summary:\n\n**Primary keyword use:** Use the primary keyword naturally in high-value locations.\n- Do not optimize to a fixed density. Treat density checks as optional internal readability\u002Fstuffing heuristics only.\n- First 1-2 mentions help establish topic context. Diminishing returns after.\n- For a 1,000-word article, avoid forced repetition across headings, body, and alt text.\n\n**Primary keyword must appear in:**\n1. Title tag (near the front)\n2. H1 tag (near the front)\n3. URL slug\n4. Meta description\n5. First paragraph \u002F first 100 words\n6. At least one image alt text\n\n**Primary keyword does NOT need to appear in:**\n- Every H2 or H3 (subtopics carry context naturally if H1 covers it)\n- Every paragraph or section\n\n**Secondary keywords:**\n- 5-8 closely related supporting terms distributed through body content\n- 10-15 broader semantic terms covering related concepts\n- Use in H2-H6 subheadings where natural\n- Synonyms improve readability and do NOT count toward keyword density\n\n**Per-section keyword guidance:** For each section in the outline, specify:\n- Which keyword (primary or secondary) belongs in the heading\n- Whether the body should include the primary keyword or a variation\n- Example: \"Use secondary keyword 'structural drafting services' in H2. Body: mention primary keyword once.\"\n\n**Distribution:** Spread the primary keyword evenly. Do not front-load or cluster in one section.\n\n## Meta Tag Rules\n\n**Title tag:**\n- 50-60 characters (never under 50, never over 60)\n- Primary keyword first, brand name last\n- Separate brand with a pipe or dash (match the site's existing pattern)\n- Lead with outcomes, numbers, or specifics when possible\n\n**Meta description:**\n- 130-150 characters (never under 130, never over 150)\n- Active voice, expand on the title with USPs and specifics\n- End with a call to action\n- No brand name at the end (it's already in the title)\n- No quotes (Google truncates at quotes)\n\n## Information Gain (non-negotiable)\n\nEvery brief must specify EXACTLY what new value this content adds that no current ranking page provides. Must be specific:\n- Proprietary data or original research\n- Case studies with real outcomes\n- Expert quotes or first-hand experience\n- Original synthesis or unique framework\n- NOT \"more detail\" or \"better formatting\"\n\n## E-E-A-T Requirements\n\nList the exact trust signals this content needs:\n- Author credentials and bio relevant to the topic\n- Expert quotes or citations from authoritative sources\n- Cited studies, data, or statistics with dates\n- Last updated date\n- Especially critical for YMYL topics (health, finance, legal, safety)\n\n## Internal Linking\n\n- Suggest 3-5 specific internal link opportunities with anchor text\n- Specify whether the page is a hub (links out to cluster pages) or spoke (links to pillar page)\n- Use the site structure from the sitemap to find real link targets\n\n## Output Format\n\nAlways output in this exact structure:\n\n```\n## Content Brief: [Primary Keyword]\n\n### Search Intent\n[Intent type, SERP format rewarded, target audience and knowledge level. 3-4 lines.]\n\n### Competitor Analysis\n| # | URL | Key H2 Sections | Est. Words | Score | Main Gap |\n|---|-----|-----------------|------------|-------|----------|\n| 1 | ... | ...             | ...        | X\u002F40  | ...      |\n\n### Content Gaps and Opportunities\n[Bullet list: topic gaps, depth gaps, quality gaps with specifics]\n\n### Winning Outline\n\n**H1:** [H1 with primary keyword]\n**URL Slug:** \u002F[slug]\n**Target Word Count:** ~[X] words (competitor avg: ~[X] words)\n\n[Full H2\u002FH3 outline with:\n- Word count per section\n- Content format notes (bullet list, table, definition box, etc.)\n- Featured Snippet targets marked with \"FS target\"\n- Per-section keyword guidance]\n\n### Recommended Meta Tags\n\n**Title**\n[title, 60 chars max]\n\n**Meta Description**\n[description, 150 chars max]\n\n### Unique Angle and Information Gain\n[Specific paragraph: what exact new value this piece adds]\n\n### E-E-A-T Requirements\n[Bullet list of exact trust signals needed]\n\n### Internal Linking Opportunities\n[3-5 suggestions with anchor text and target URL]\n```\n\n## Outline-Only Mode\n\nWhen the user asks for \"just an outline\" or \"content outline\" instead of a full brief, skip the Competitor Analysis table, Content Gaps section, Information Gain section, and E-E-A-T section. Output only:\n\n```\n## Content Outline: [Primary Keyword]\n\n**H1:** [H1 with primary keyword]\n**URL Slug:** \u002F[slug]\n**Target Word Count:** ~[X] words (competitor avg: ~[X] words)\n\n[Full H2\u002FH3 outline with word counts, format notes, FS targets, keyword guidance, and a 1-2 sentence writing note per section]\n```\n\n## DataForSEO Integration (Optional)\n\nIf DataForSEO MCP tools are available, use `serp_organic_live_advanced` for real SERP data and competitor analysis, `kw_data_google_ads_search_volume` for keyword volume, `dataforseo_labs_bulk_keyword_difficulty` for difficulty scores, `dataforseo_labs_search_intent` for intent classification, and `on_page_content_parsing_live` for competitor content extraction.\n\n## Ahrefs Integration (Optional)\n\nIf Ahrefs MCP tools are available, use `keywords-explorer-overview` for keyword volume and difficulty, `serp-overview` for SERP analysis, `site-explorer-organic-keywords` for existing keyword rankings, and `site-explorer-top-pages` for competitor page performance.\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| Target URL unreachable | Report the error. Do not guess page content. Ask the user to verify the URL. |\n| No competitors found after filtering | Broaden the search to include partial-match competitors. Note the thin competitive landscape in the brief. |\n| Sitemap not found | Proceed without site structure context. Note that internal linking suggestions may be incomplete. |\n| Page type not specified | Auto-detect from the keyword intent and SERP format. State the detected type in the brief. |\n| Target word count not specified | Use competitor average as the baseline. Note this in the outline. |\n","# SEO Content Brief Generator\n\nGenerate research-backed content briefs that help writers produce pages capable of outranking current top results. Briefs include competitor analysis with gap scoring, per-section word count breakdowns, keyword placement rules, and page-type-specific templates.\n\n## Process\n\n### 1. Determine Brief Mode\n\n**Improve mode** (existing page URL provided):\n- Fetch the existing page content and structure\n- Identify what is already strong (keep it)\n- Identify missing, thin, or outdated sections\n- Distinguish \"keep\u002Fstrengthen\" vs \"add new\" sections in the outline\n- Do not recommend a full rewrite when targeted improvements will win\n\n**New page mode** (keyword or topic provided, no existing page):\n- Use the target site's homepage or sitemap for business context only\n- Build the brief from scratch for a new page\n- Focus on competitive gaps the new page can fill\n\n### 2. Fetch Context\n\n- Fetch the target URL or homepage to understand the business\n- Fetch the sitemap to discover all existing pages, categories, and services\n- This context is critical for the Website Relevance Rule (see below)\n\n### 3. Analyse SERPs\n\n- Identify the top 5 ranking pages for the target keyword\n- Filter out non-competitors (Wikipedia, Reddit, Pinterest, Amazon, YouTube, government sites, SEO tool pages, job boards, directories, news aggregators, social platforms). See `references\u002Fexcluded-domains.md` for the full list.\n- Score each real competitor: Depth (1-10), Formatting (1-10), SEO (1-10), UX (1-10)\n- Identify three gap types:\n  - **Topic gaps:** subtopics competitors miss entirely\n  - **Depth gaps:** topics covered but shallow\n  - **Quality gaps:** outdated info, no expert perspective, poor formatting\n- Calculate gap priority: `Impact x Competitive Advantage \u002F Effort`\n\n### 4. Classify Search Intent\n\n- **Informational:** user wants to learn (guides, how-tos, definitions)\n- **Commercial:** user is researching before buying (comparisons, reviews, \"best X\")\n- **Transactional:** user is ready to act (buy, book, enquire, sign up)\n- **Navigational:** user is looking for a specific site or page\n\nIdentify what SERP format Google rewards for this query: long-form guide, listicle, comparison table, landing page, FAQ, video, local pack.\n\n### 5. Build the Brief\n\nApply the page-type template from `references\u002Fpage-type-templates.md`, then customise based on competitor gaps and search intent.\n\n## Critical Rules\n\n### Website Relevance Rule\n\nEvery heading, subtopic, keyword, and FAQ you suggest must be something the target website can credibly write about based on its actual services or products.\n\n- Read the site's homepage and sitemap to understand what it does\n- Do not borrow competitor structure if those sections cover things this site does not offer\n- Before each suggestion, ask: \"Can this website actually deliver on this content?\" If no, remove it.\n\n### Site Structure Coverage Rule\n\nWhen briefing a hub, overview, category, or \"types of\" page:\n- The outline must reference every relevant product category, service, or sub-page that exists on the site\n- Do not invent categories that don't exist, do not leave out categories that do exist\n- Each category should appear as its own section with an internal link suggestion\n- This ensures the page acts as a proper hub linking to all child pages\n\nFor non-hub pages (single service page, blog post), use site structure to suggest relevant internal links but do not force every category into the outline.\n\n### Output Language Rules\n\n- Never mention researcher names, framework names, or tool names in the output (no \"Ben Goodey method\", \"Frase.io formula\", \"Princeton GEO\", \"Clearscope\", \"Backlinko\")\n- These are internal thinking tools only. The output must read as plain, professional advice.\n- Write for a business owner or content writer, not an SEO academic\n\n## Keyword Density and Placement\n\nRead `references\u002Fkeyword-density.md` for the full rules. Summary:\n\n**Primary keyword use:** Use the primary keyword naturally in high-value locations.\n- Do not optimize to a fixed density. Treat density checks as optional internal readability\u002Fstuffing heuristics only.\n- First 1-2 mentions help establish topic context. Diminishing returns after.\n- For a 1,000-word article, avoid forced repetition across headings, body, and alt text.\n\n**Primary keyword must appear in:**\n1. Title tag (near the front)\n2. H1 tag (near the front)\n3. URL slug\n4. Meta description\n5. First paragraph \u002F first 100 words\n6. At least one image alt text\n\n**Primary keyword does NOT need to appear in:**\n- Every H2 or H3 (subtopics carry context naturally if H1 covers it)\n- Every paragraph or section\n\n**Secondary keywords:**\n- 5-8 closely related supporting terms distributed through body content\n- 10-15 broader semantic terms covering related concepts\n- Use in H2-H6 subheadings where natural\n- Synonyms improve readability and do NOT count toward keyword density\n\n**Per-section keyword guidance:** For each section in the outline, specify:\n- Which keyword (primary or secondary) belongs in the heading\n- Whether the body should include the primary keyword or a variation\n- Example: \"Use secondary keyword 'structural drafting services' in H2. Body: mention primary keyword once.\"\n\n**Distribution:** Spread the primary keyword evenly. Do not front-load or cluster in one section.\n\n## Meta Tag Rules\n\n**Title tag:**\n- 50-60 characters (never under 50, never over 60)\n- Primary keyword first, brand name last\n- Separate brand with a pipe or dash (match the site's existing pattern)\n- Lead with outcomes, numbers, or specifics when possible\n\n**Meta description:**\n- 130-150 characters (never under 130, never over 150)\n- Active voice, expand on the title with USPs and specifics\n- End with a call to action\n- No brand name at the end (it's already in the title)\n- No quotes (Google truncates at quotes)\n\n## Information Gain (non-negotiable)\n\nEvery brief must specify EXACTLY what new value this content adds that no current ranking page provides. Must be specific:\n- Proprietary data or original research\n- Case studies with real outcomes\n- Expert quotes or first-hand experience\n- Original synthesis or unique framework\n- NOT \"more detail\" or \"better formatting\"\n\n## E-E-A-T Requirements\n\nList the exact trust signals this content needs:\n- Author credentials and bio relevant to the topic\n- Expert quotes or citations from authoritative sources\n- Cited studies, data, or statistics with dates\n- Last updated date\n- Especially critical for YMYL topics (health, finance, legal, safety)\n\n## Internal Linking\n\n- Suggest 3-5 specific internal link opportunities with anchor text\n- Specify whether the page is a hub (links out to cluster pages) or spoke (links to pillar page)\n- Use the site structure from the sitemap to find real link targets\n\n## Output Format\n\nAlways output in this exact structure:\n\n```\n## Content Brief: [Primary Keyword]\n\n### Search Intent\n[Intent type, SERP format rewarded, target audience and knowledge level. 3-4 lines.]\n\n### Competitor Analysis\n| # | URL | Key H2 Sections | Est. Words | Score | Main Gap |\n|---|-----|-----------------|------------|-------|----------|\n| 1 | ... | ...             | ...        | X\u002F40  | ...      |\n\n### Content Gaps and Opportunities\n[Bullet list: topic gaps, depth gaps, quality gaps with specifics]\n\n### Winning Outline\n\n**H1:** [H1 with primary keyword]\n**URL Slug:** \u002F[slug]\n**Target Word Count:** ~[X] words (competitor avg: ~[X] words)\n\n[Full H2\u002FH3 outline with:\n- Word count per section\n- Content format notes (bullet list, table, definition box, etc.)\n- Featured Snippet targets marked with \"FS target\"\n- Per-section keyword guidance]\n\n### Recommended Meta Tags\n\n**Title**\n[title, 60 chars max]\n\n**Meta Description**\n[description, 150 chars max]\n\n### Unique Angle and Information Gain\n[Specific paragraph: what exact new value this piece adds]\n\n### E-E-A-T Requirements\n[Bullet list of exact trust signals needed]\n\n### Internal Linking Opportunities\n[3-5 suggestions with anchor text and target URL]\n```\n\n## Outline-Only Mode\n\nWhen the user asks for \"just an outline\" or \"content outline\" instead of a full brief, skip the Competitor Analysis table, Content Gaps section, Information Gain section, and E-E-A-T section. Output only:\n\n```\n## Content Outline: [Primary Keyword]\n\n**H1:** [H1 with primary keyword]\n**URL Slug:** \u002F[slug]\n**Target Word Count:** ~[X] words (competitor avg: ~[X] words)\n\n[Full H2\u002FH3 outline with word counts, format notes, FS targets, keyword guidance, and a 1-2 sentence writing note per section]\n```\n\n## DataForSEO Integration (Optional)\n\nIf DataForSEO MCP tools are available, use `serp_organic_live_advanced` for real SERP data and competitor analysis, `kw_data_google_ads_search_volume` for keyword volume, `dataforseo_labs_bulk_keyword_difficulty` for difficulty scores, `dataforseo_labs_search_intent` for intent classification, and `on_page_content_parsing_live` for competitor content extraction.\n\n## Ahrefs Integration (Optional)\n\nIf Ahrefs MCP tools are available, use `keywords-explorer-overview` for keyword volume and difficulty, `serp-overview` for SERP analysis, `site-explorer-organic-keywords` for existing keyword rankings, and `site-explorer-top-pages` for competitor page performance.\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| Target URL unreachable | Report the error. Do not guess page content. Ask the user to verify the URL. |\n| No competitors found after filtering | Broaden the search to include partial-match competitors. Note the thin competitive landscape in the brief. |\n| Sitemap not found | Proceed without site structure context. Note that internal linking suggestions may be incomplete. |\n| Page type not specified | Auto-detect from the keyword intent and SERP format. State the detected type in the brief. |\n| Target word count not specified | Use competitor average as the baseline. Note this in the outline. |\n",{"name":5,"license":15,"metadata":25,"description":29,"argument-hint":30,"user-invocable":31},{"author":26,"version":27,"category":28,"original_author":26},"puneetindersingh","1.0.0","seo","Generate competitive SEO content briefs with per-section word counts, competitor scoring, keyword density guidance, and page-type templates. Supports both new page briefs and improve-existing-page briefs. Use when user says \"content brief\", \"write a brief\", \"content outline\", \"blog brief\", \"service page brief\", \"brief for\", \"writing brief\", \"content plan\", or \"outline for\".\n","[url-or-keyword] [page-type]",true,"main","f1bcf88a052c2ccbb297666b33fb820cfd94ac71",".codex\u002Fskills\u002Fresearch-data\u002Fresearch-seo-and-content\u002Fseo-content-brief",0,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas","https:\u002F\u002Fgithub.com\u002Fpeterish8","Building real-world products with clean UI, smart architecture, and privacy in mind. Frontend-focused, full-stack curious.","2026-10-15 19:02:31",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":31},[42,45,48],{"tool":43,"command":44},"npx","npx skills add peterish8\u002Fprats-skill-atlas --skill seo-content-brief",{"tool":46,"command":47},"bunx","bunx skills add peterish8\u002Fprats-skill-atlas --skill seo-content-brief",{"tool":49,"command":50},"pnpm","pnpm dlx skills add peterish8\u002Fprats-skill-atlas --skill seo-content-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fresearch-data\u002Fresearch-seo-and-content\u002Fseo-content-brief\u002FSKILL.md",[53,58,64,68],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",147,{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fexcluded-domains.md","REFERENCE","参考文档",2881,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fresearch-data\u002Fresearch-seo-and-content\u002Fseo-content-brief\u002Freferences\u002Fexcluded-domains.md",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fkeyword-density.md",3134,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fresearch-data\u002Fresearch-seo-and-content\u002Fseo-content-brief\u002Freferences\u002Fkeyword-density.md",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fpage-type-templates.md",7174,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fresearch-data\u002Fresearch-seo-and-content\u002Fseo-content-brief\u002Freferences\u002Fpage-type-templates.md",[73,82,90,98,105,113],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":20},"01M7CTAZW9MHV3RWH2ZEKDQXG9","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftools-utilities\u002Fgeneral-purpose\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftools-utilities\u002Fgeneral-purpose\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":20},"01M7CT8MG7NB1JR67XYZ9EWW3B","seo-audit","Full website SEO audit with parallel subagent delegation. Crawls up to 500 pages, detects business type, delegates to up to 15 specialists (8 always + 7 conditional), generates health score. Use when user says audit, full SEO check, analyze my site, or website health check.","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fseo-audit\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fseo-audit\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":20},"01M7CT87F6GQ0WAD393PKPAGGX","playwright","Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fplaywright\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fplaywright\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":20},"01M7CT809RF90MG98MYEA97D8Z","gsap-performance","Official GSAP skill for performance — prefer transforms, avoid layout thrashing, will-change, batching. Use when optimizing GSAP animations, reducing jank, or when the user asks about animation performance, FPS, or smooth 60fps.","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fgsap-performance\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":20},"01M7CT7Q4VD995JHZMQQFBZZV9","firecrawl-seo-audit","Audit a website's SEO with Firecrawl. Use when the user asks for an SEO audit, metadata and heading review, sitemap\u002Fsite-structure analysis, keyword opportunities, competitor SERP comparison, or prioritized search optimization recommendations.","ISC","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Ffirecrawl-seo-audit\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":20},"01M7CT7JRJFC5RAKJBAP0VS1CV","firecrawl-qa","QA test a live website with Firecrawl browser and scrape evidence. Use when the user wants exploratory QA, form testing, navigation\u002Flink checks, responsive checks, performance observations, bug reports, or a pre-launch quality review.","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Ffirecrawl-qa\u002FSKILL.md",[],[]]