[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6RW0214XGYQ89B4TZWC9HKP":3,"skill-same:01M6RW0214XGYQ89B4TZWC9HKP":90},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":13,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":62,"install":63,"resources":75},"01M6RW0214XGYQ89B4TZWC9HKP","quarkus-patterns",null,"Quarkus 3.x LTS architecture patterns with Camel for messaging, RESTful API design, CDI services, data access with Panache, and async processing. Use for Java Quarkus backend work with event-driven architectures.","sakamoto-family-smile\u002Fagent_monorepo","sakamoto-family-smile","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F132812403?v=4","01M6RTAT3H8PMWX5SJ65KP3VYF","01M6RTAV321WB5RAHCWTZMX5CV",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fquarkus-patterns\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"quarkus patterns","patterns","quarkus","work","for","with","event","processing","architectures","async","use","design","access","api","architecture patterns","data","services","messaging","java","architecture","2026-11-10 10:12:30",false,"---\nname: seo-content-brief\ndescription: 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\".\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 density:** 0.5% to 2.0% of total word count.\n- Above 2% requires review. Above 3% risks keyword stuffing penalties.\n- First 1-2 mentions carry the most SEO weight. Diminishing returns after.\n- For a 1,000-word article at 1-2%: roughly 10-20 total appearances including 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_google_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 density:** 0.5% to 2.0% of total word count.\n- Above 2% requires review. Above 3% risks keyword stuffing penalties.\n- First 1-2 mentions carry the most SEO weight. Diminishing returns after.\n- For a 1,000-word article at 1-2%: roughly 10-20 total appearances including 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_google_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":48,"license":49,"metadata":50,"description":54,"argument-hint":55,"user_invocable":56},"seo-content-brief","MIT",{"author":51,"version":52,"category":53,"original_author":51},"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\".","[url-or-keyword] [page-type]",true,"main","60a901a00f46e71601f58727cb5661f8d3fb6d24",".claude\u002Fskills\u002Fecc\u002Fquarkus-patterns","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile","2026-11-08 20:29:14",{"source":8,"skillName":48,"commands":64,"prompt":74,"zipAvailable":56},[65,68,71],{"tool":66,"command":67},"npx","npx skills add sakamoto-family-smile\u002Fagent_monorepo --skill seo-content-brief",{"tool":69,"command":70},"bunx","bunx skills add sakamoto-family-smile\u002Fagent_monorepo --skill seo-content-brief",{"tool":72,"command":73},"pnpm","pnpm dlx skills add sakamoto-family-smile\u002Fagent_monorepo --skill seo-content-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fquarkus-patterns\u002FSKILL.md",[76,82,86],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fexcluded-domains.md","REFERENCE","参考文档",2881,"https:\u002F\u002Fgithub.com\u002Fshenxingy\u002FClade\u002Fblob\u002Fmain\u002Fconfigs\u002Fskills\u002Fseo-content-brief\u002Freferences\u002Fexcluded-domains.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fkeyword-density.md",3097,"https:\u002F\u002Fgithub.com\u002Fshenxingy\u002FClade\u002Fblob\u002Fmain\u002Fconfigs\u002Fskills\u002Fseo-content-brief\u002Freferences\u002Fkeyword-density.md",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fpage-type-templates.md",6712,"https:\u002F\u002Fgithub.com\u002Fshenxingy\u002FClade\u002Fblob\u002Fmain\u002Fconfigs\u002Fskills\u002Fseo-content-brief\u002Freferences\u002Fpage-type-templates.md",[91,123,131,151,174,197],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":103,"publishedAt":43},"01M6RW50THEFSKK42YNR8XFZA1","remotion-video-creation","Best practices for Remotion - Video creation in React. 29 domain-specific rules covering 3D, animations, audio, captions, charts, transitions, and more.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fremotion-video-creation\u002FSKILL.md",[97,100],{"categoryNo":98,"categoryName":99,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":101,"categoryName":102,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",[104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,27],"Video","remotion video","remotion video creation","creation","Remotion","Charts","Captions","Audio","3D","Composition","Animation","best practices","more","animations","domain-specific","domain","three","Rules","Lottie",{"skillNo":124,"name":125,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":43},"01M6VCJ23NPECPSZJKGY691F75","hotcook-recipes","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fhotcook-agent\u002Fdata\u002Fskills\u002Fhotcook-recipes\u002FSKILL.md",[],[129,130],"hotcook recipes","recipes",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":145,"publishedAt":43},"01M6VCHHE00X5XHSDRD1KH1BW2","code-helper","Code review and assistance skill","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fagent-system-2\u002Fskills\u002Fcode-helper\u002Fskill.md",[137,140],{"categoryNo":138,"categoryName":139,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":141,"categoryName":142,"taxonomyType":143,"taxonomyTypeDesc":144},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[146,147,148,149,150],"code helper","helper","code","code review","review",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":163,"publishedAt":43},"01M6VCH3Q31A20H6SQ1H0J7JB2","research-assistant","Web research assistant skill using Brave Search MCP","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fagent-system-1\u002Fskills\u002Fresearch-assistant\u002Fskill.md",[157,160],{"categoryNo":158,"categoryName":159,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":161,"categoryName":162,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[164,165,166,167,168,169,170,171,172,173],"research assistant","research","assistant","MCP","web","search","brave search","web research","brave","web research assistant",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":182,"publishedAt":43},"01M6VCGZZGPNVJSCZ1JTMNZAHY","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fx-api\u002FSKILL.md",[180,181],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":141,"categoryName":142,"taxonomyType":143,"taxonomyTypeDesc":144},[183,36,28,184,185,186,27,187,188,189,190,191,24,192,193,33,194,195,169,196],"x api","when","limits","rate","threads","reading","native","posting","platform","api integration","twitter","auth","analytics","OAuth",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":204,"publishedAt":43},"01M6VCGVX6DGB1FKTA53QBBCQB","workspace-surface-audit","Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fworkspace-surface-audit\u002FSKILL.md",[203],{"categoryNo":161,"categoryName":162,"taxonomyType":20,"taxonomyTypeDesc":21},[205,206,207,208,167,209,210,148,211,212,213,214,33,215,216,217,218,189,219,184],"workspace surface audit","workspace","audit","hooks","workflows","connectors","capabilities","harness","repo","environment","up","harness setup","active","env","value"]