[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C2KG01VWJKPDFPKWQ8ZXRY":3,"skill-same:01M6C2KG01VWJKPDFPKWQ8ZXRY":111},{"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":35,"publishedAt":61,"linkOnly":62,"markdownContent":63,"markdownBody":64,"frontMatter":65,"refName":72,"commitSha":73,"skillDirectory":74,"forksCount":14,"repositoryHtmlUrl":75,"repositoryHomepageUrl":6,"ownerHtmlUrl":76,"ownerBlogUrl":6,"ownerDescription":77,"updatedAt":78,"install":79,"resources":91},"01M6C2KG01VWJKPDFPKWQ8ZXRY","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\".","noirelab\u002Flinux-setup","noirelab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142925921?v=4","01M6C29R3FEDGFAXAT0KXY28QX","Kaíque M. Lima","01M6C29R811WX04B0GYHTH1XV6",0,"MIT","https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fclaude\u002Fskills\u002Fseo-content-brief\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fclaude\u002Fskills\u002Fseo-content-brief\u002FSKILL.md",[19,24,27,32],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":25,"categoryName":26,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":28,"categoryName":29,"taxonomyType":30,"taxonomyTypeDesc":31},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",{"categoryNo":33,"categoryName":34,"taxonomyType":30,"taxonomyTypeDesc":31},"01JBSEEDCAT000000000000036","内容创作者",[36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60],"content","seo content brief","brief","seo","content brief","seo content","write","new","when","for","briefs","URL","competitive","blog brief","scoring","use","user","writing","page","blog","Word","plan","improve","templates","generate","2026-11-10 10:12:30",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":66,"description":69,"argument-hint":70,"user-invocable":71},{"author":67,"version":68,"category":39,"original_author":67},"puneetindersingh","1.0.0","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","d8378e461d60315bd1ca8a6e71716df39b6abe4a","configs\u002Fcommon\u002Fclaude\u002Fskills\u002Fseo-content-brief","https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup","https:\u002F\u002Fgithub.com\u002Fnoirelab","Artificial Intelligence Researcher |\r\nComputer Science majoring at UTFPR","2026-11-11 09:12:51",{"source":8,"skillName":5,"commands":80,"prompt":90,"zipAvailable":71},[81,84,87],{"tool":82,"command":83},"npx","npx skills add noirelab\u002Flinux-setup --skill seo-content-brief",{"tool":85,"command":86},"bunx","bunx skills add noirelab\u002Flinux-setup --skill seo-content-brief",{"tool":88,"command":89},"pnpm","pnpm dlx skills add noirelab\u002Flinux-setup --skill seo-content-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fclaude\u002Fskills\u002Fseo-content-brief\u002FSKILL.md",[92,97,103,107],{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",147,{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fexcluded-domains.md","REFERENCE","参考文档",2881,"https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fclaude\u002Fskills\u002Fseo-content-brief\u002Freferences\u002Fexcluded-domains.md",{"path":104,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fkeyword-density.md",3134,"https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fclaude\u002Fskills\u002Fseo-content-brief\u002Freferences\u002Fkeyword-density.md",{"path":108,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fpage-type-templates.md",7174,"https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fclaude\u002Fskills\u002Fseo-content-brief\u002Freferences\u002Fpage-type-templates.md",[112,140,175,201,221,237],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":116,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":123,"publishedAt":61},"01M6C2Q1S6HCS7Y9TBQ2PJ2NAM","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fclaude\u002Fskills\u002Fsynced\u002Ffcfa9261-0073-49cb-8312-19eea68f0c58_391f3767-a35d-4280-81a1-363cd861a8e6\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fclaude\u002Fskills\u002Fsynced\u002Ffcfa9261-0073-49cb-8312-19eea68f0c58_391f3767-a35d-4280-81a1-363cd861a8e6\u002Fskill-creator\u002FSKILL.md",[120],{"categoryNo":121,"categoryName":122,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000023","Skill与智能体开发",[124,125,126,127,128,129,130,131,132,133,58,134,51,135,136,137,45,138,139,44,43],"skill creator","creator","performance","run evals","test","variance analysis","create","run","benchmark","analysis","edit","evals","optimize","existing skill","accuracy","scratch",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":116,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":61},"01M6C2ZRGJ9HN4N9BP24DPNCR4","returns-reverse-logistics","Codified expertise for returns authorization, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management. Informed by returns operations managers with 15+ years experience. Includes grading frameworks, disposition economics, fraud pattern recognition, and vendor recovery processes. Use when handling product returns, reverse logistics, refund decisions, return fraud detection, or warranty claims.","https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fopencode_home\u002Fskills\u002Freturns-reverse-logistics\u002FSKILL.md",[],[147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,51,163,164,165,166,167,168,169,170,171,45,172,173,44,174],"returns","returns reverse logistics","reverse logistics","reverse","github","code","product","https","authorization","detection","fraud","recovery","decisions","management","operations","vendor","claims management","frameworks","fraud detection","pattern","grading","processing","economics","managers","claims","expertise","refund","inspection",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":116,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":61},"01M6C2ZGWSNZGZZQ5VCFWHD2QT","quality-nonconformance","Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments. Includes NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.","https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fopencode_home\u002Fskills\u002Fquality-nonconformance\u002FSKILL.md",[],[182,183,151,184,185,152,186,154,187,188,189,190,133,191,160,51,192,193,194,195,196,197,198,199,45,172,200,44],"quality","quality nonconformance","root cause analysis","interpretation","issues","audit","data","methodology","lifecycle","investigation","fda","across","manufacturing","environments","corrective action","supplier quality management","action","conformance","root cause",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":116,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":207,"publishedAt":61},"01M6C2Z8VQ9AYZYKPZW1KD9DX5","production-scheduling","Codified expertise for production scheduling, job sequencing, line balancing, changeover optimization, and bottleneck resolution in discrete and batch manufacturing. Informed by production schedulers with 15+ years experience. Includes TOC\u002Fdrum-buffer-rope, SMED, OEE analysis, disruption response frameworks, and ERP\u002FMES interaction patterns. Use when scheduling production, resolving bottlenecks, optimizing changeovers, responding to disruptions, or balancing manufacturing lines.","https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fopencode_home\u002Fskills\u002Fproduction-scheduling\u002FSKILL.md",[],[208,209,210,151,152,211,154,212,133,213,214,51,215,216,164,217,218,219,194,220,45,172,44],"Production","production scheduling","scheduling","batch","Optimization","erp","bottleneck","toc","patterns","line","interaction","sequencing","buffer",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":116,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":227,"publishedAt":61},"01M6C2YR01NNN2Z1G18RN7F9MP","logistics-exception-management","Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes. Informed by logistics professionals with 15+ years operational experience. Includes escalation protocols, carrier-specific behaviors, claims procedures, and judgment frameworks. Use when handling shipping exceptions, freight claims, delivery issues, or carrier disputes.","https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fopencode_home\u002Fskills\u002Flogistics-exception-management\u002FSKILL.md",[],[160,228,151,152,229,186,230,154,231,51,164,232,233,234,235,171,45,172,236,44],"logistics exception management","shipping","protocols","escalation","delivery","claude-code","judgment","with","freight",{"skillNo":238,"name":239,"nameZh":6,"description":240,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":116,"licenseFileUrl":6,"sourceHtmlUrl":241,"categories":242,"keywords":243,"publishedAt":61},"01M6C2YC5PXTEJYBJJQZVXPQS0","inventory-demand-planning","Codified expertise for demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation at multi-location retailers. Informed by demand planners with 15+ years experience managing hundreds of SKUs. Includes forecasting method selection, ABC\u002FXYZ analysis, seasonal transition management, and vendor negotiation frameworks. Use when forecasting demand, setting safety stock, planning replenishment, managing promotions, or optimizing inventory levels.","https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fopencode_home\u002Fskills\u002Finventory-demand-planning\u002FSKILL.md",[],[244,245,246,247,151,152,154,248,212,249,133,160,162,250,51,251,164,252,253,254,255,256,45,172,257,44],"planning","inventory","inventory demand planning","demand planning","negotiation","Safety","forecasting","selection","estimation","stock","seasonal","lift","at","transition"]