[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MJFST6CV61MC206V9GR31X":3,"skill-same:01M6MJFST6CV61MC206V9GR31X":78},{"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":27,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":13,"repositoryHtmlUrl":61,"repositoryHomepageUrl":6,"ownerHtmlUrl":62,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":63,"install":64,"resources":77},"01M6MJFST6CV61MC206V9GR31X","seo-audit",null,"When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions \"SEO audit,\" \"technical SEO,\" \"why am I not ranking,\" \"SEO issues,\" \"on-page SEO,\" \"meta tags review,\" or \"SEO health check.\" For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.","JiayiV\u002Fquestion_mixing","JiayiV","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54466889?v=4","01M6JFJYYMRZ3QRGP9339JNQ2K","01M6JFJZ35KB0QVT50NAHPJA7G",0,"MIT","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-marketing-skill-skills-seo-audit-skill-0a51e9ce\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"audit","seo audit","seo","page","for","programmatic","tags","ranking","pages","schema","use","check","technical","review","health","Meta Tags","Meta","issues","diagnose","structured data","2026-11-10 10:12:30",false,"---\nname: \"seo-audit\"\ndescription: When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions \"SEO audit,\" \"technical SEO,\" \"why am I not ranking,\" \"SEO issues,\" \"on-page SEO,\" \"meta tags review,\" or \"SEO health check.\" For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# SEO Audit\n\nYou are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore auditing, understand:\n\n1. **Site Context**\n   - What type of site? (SaaS, e-commerce, blog, etc.)\n   - What's the primary business goal for SEO?\n   - What keywords\u002Ftopics are priorities?\n\n2. **Current State**\n   - Any known issues or concerns?\n   - Current organic traffic level?\n   - Recent changes or migrations?\n\n3. **Scope**\n   - Full site audit or specific pages?\n   - Technical + on-page, or one focus area?\n   - Access to Search Console \u002F analytics?\n\n---\n\n## Audit Framework\n\nThe audit walks three layers — technical (crawl\u002Findexation\u002Fspeed), on-page (titles, headings, internal links, keyword targeting), content (intent match, E-E-A-T, thin\u002Fduplicate pages). Full framework: references\u002Fseo-audit-reference.md.\n\n**Core Web Vitals pass\u002Ffail thresholds** (75th percentile of real-user data; full triage in references\u002Fcwv-thresholds.md):\n\n| Metric | Good | Needs improvement | Poor |\n|---|---|---|---|\n| LCP (Largest Contentful Paint) | ≤ 2.5s | 2.5-4.0s | > 4.0s |\n| INP (Interaction to Next Paint) | ≤ 200ms | 200-500ms | > 500ms |\n| CLS (Cumulative Layout Shift) | ≤ 0.1 | 0.1-0.25 | > 0.25 |\n\n## Tools\n\n| Tool | Invocation | Output |\n|---|---|---|\n| On-page checker | `python3 scripts\u002Fseo_checker.py --file page.html` (or `--url https:\u002F\u002F...`; `--json`) | Scores a single page 0-100: title\u002Fmeta\u002Fheadings\u002Flinks\u002Fimages |\n| Health scorer | `python3 scripts\u002Fseo_health_scorer.py --checks checks.json --industry saas` (no arg = `--demo`; industries: saas\u002Fecommerce\u002Flocal\u002Fpublisher; `--json`) | Weighted 0-100 site health score across 7 categories |\n\nRun `seo_checker.py` on the key templates\u002Fpages during the on-page layer, and `seo_health_scorer.py` on the completed check matrix to produce the audit's headline score.\n\n## Output Format\n\n### Audit Report Structure\n\n**Executive Summary**\n- Overall health assessment — lead with the `seo_health_scorer.py` score and its weakest categories\n- Top 3-5 priority issues\n- Quick wins identified\n\n**Technical SEO Findings**\nFor each issue:\n- **Issue**: What's wrong\n- **Impact**: SEO impact (High\u002FMedium\u002FLow)\n- **Evidence**: How you found it\n- **Fix**: Specific recommendation\n- **Priority**: 1-5 or High\u002FMedium\u002FLow\n\n**On-Page SEO Findings**\nSame format as above\n\n**Content Findings**\nSame format as above\n\n**Prioritized Action Plan**\n1. Critical fixes (blocking indexation\u002Franking)\n2. High-impact improvements\n3. Quick wins (easy, immediate benefit)\n4. Long-term recommendations\n\n---\n\n## References\n\n- [SEO Audit Reference](references\u002Fseo-audit-reference.md): Full audit framework, scoring, and remediation patterns\n- [Core Web Vitals Thresholds](references\u002Fcwv-thresholds.md): LCP\u002FINP\u002FCLS targets and triage rules\n- [E-E-A-T Framework](references\u002Feeat-framework.md): Experience, Expertise, Authoritativeness, Trustworthiness checklist\n- [Schema Types](references\u002Fschema-types.md): Structured data patterns by content type\n\n---\n\n## Tools Referenced\n\n**Free Tools**\n- Google Search Console (essential)\n- Google PageSpeed Insights\n- Bing Webmaster Tools\n- Rich Results Test\n- Mobile-Friendly Test\n- Schema Validator\n\n**Paid Tools** (if available)\n- Screaming Frog\n- Ahrefs \u002F Semrush\n- Sitebulb\n- ContentKing\n\n---\n\n## Task-Specific Questions\n\n1. What pages\u002Fkeywords matter most?\n2. Do you have Search Console access?\n3. Any recent changes or migrations?\n4. Who are your top organic competitors?\n5. What's your current organic traffic baseline?\n\n---\n\n## Related Skills\n\n- **programmatic-seo** — WHEN: user wants to build SEO pages at scale after the audit identifies keyword gaps. WHEN NOT: don't use for diagnosing existing issues; stay in seo-audit mode.\n- **aeo** — WHEN: user wants to optimize for AI answer engines (SGE, Perplexity, ChatGPT) in addition to traditional search. WHEN NOT: don't use for purely technical crawl\u002Findexation issues.\n- **schema-markup** — WHEN: audit reveals missing structured data opportunities (FAQ, HowTo, Product, Review schemas). WHEN NOT: don't use as a standalone fix when core technical SEO is broken.\n- **site-architecture** — WHEN: audit uncovers poor internal linking, orphan pages, or crawl depth issues that need a structural redesign. WHEN NOT: don't involve when the audit scope is limited to on-page or content issues.\n- **content-strategy** — WHEN: audit reveals thin content, keyword gaps, or lack of topical authority requiring a content plan. WHEN NOT: don't use when the problem is purely technical (robots.txt, redirects, speed).\n- **marketing-context** — WHEN: always read first if `.claude\u002Fproduct-marketing-context.md` exists to avoid redundant questions. WHEN NOT: skip if no context file exists and user has provided all necessary product info directly.\n\n---\n\n## Communication\n\nAll audit output follows the **SEO Audit Quality Standard**:\n- Lead with the executive summary (3-5 bullets max)\n- Findings use the Issue \u002F Impact \u002F Evidence \u002F Fix \u002F Priority format consistently\n- Prioritized Action Plan is always the final deliverable section\n- Avoid jargon without explanation; write for a technically-aware but non-SEO-specialist reader\n- Quick wins are called out explicitly and kept separate from high-effort recommendations\n- Never present recommendations without evidence or rationale\n\n---\n\n## Proactive Triggers\n\nAutomatically surface seo-audit recommendations when:\n\n1. **Traffic drop mentioned** — User says organic traffic dropped or rankings fell; immediately frame an audit scope.\n2. **Site migration or redesign** — User mentions a planned or recent URL change, platform switch, or redesign; flag pre\u002Fpost-migration audit needs.\n3. **\"Why isn't my page ranking?\"** — Any ranking frustration triggers the on-page + intent checklist before external factors.\n4. **Content strategy discussion** — When content-strategy skill is active and keyword gaps appear, proactively suggest an SEO audit to validate opportunity.\n5. **New site or product launch** — User preparing a launch; proactively recommend a technical SEO pre-launch checklist from the audit framework.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Executive Summary | Markdown bullets | 3-5 top issues + quick wins, suitable for sharing with stakeholders |\n| Technical SEO Findings | Structured table | Issue \u002F Impact \u002F Evidence \u002F Fix \u002F Priority per finding |\n| On-Page SEO Findings | Structured table | Same format, focused on content and metadata |\n| Prioritized Action Plan | Numbered list | Ordered by impact × effort, grouped into Critical \u002F High \u002F Quick Wins |\n| Keyword Cannibalization Map | Table | Pages competing for same keyword with recommended canonical or redirect actions |\n","# SEO Audit\n\nYou are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore auditing, understand:\n\n1. **Site Context**\n   - What type of site? (SaaS, e-commerce, blog, etc.)\n   - What's the primary business goal for SEO?\n   - What keywords\u002Ftopics are priorities?\n\n2. **Current State**\n   - Any known issues or concerns?\n   - Current organic traffic level?\n   - Recent changes or migrations?\n\n3. **Scope**\n   - Full site audit or specific pages?\n   - Technical + on-page, or one focus area?\n   - Access to Search Console \u002F analytics?\n\n---\n\n## Audit Framework\n\nThe audit walks three layers — technical (crawl\u002Findexation\u002Fspeed), on-page (titles, headings, internal links, keyword targeting), content (intent match, E-E-A-T, thin\u002Fduplicate pages). Full framework: references\u002Fseo-audit-reference.md.\n\n**Core Web Vitals pass\u002Ffail thresholds** (75th percentile of real-user data; full triage in references\u002Fcwv-thresholds.md):\n\n| Metric | Good | Needs improvement | Poor |\n|---|---|---|---|\n| LCP (Largest Contentful Paint) | ≤ 2.5s | 2.5-4.0s | > 4.0s |\n| INP (Interaction to Next Paint) | ≤ 200ms | 200-500ms | > 500ms |\n| CLS (Cumulative Layout Shift) | ≤ 0.1 | 0.1-0.25 | > 0.25 |\n\n## Tools\n\n| Tool | Invocation | Output |\n|---|---|---|\n| On-page checker | `python3 scripts\u002Fseo_checker.py --file page.html` (or `--url https:\u002F\u002F...`; `--json`) | Scores a single page 0-100: title\u002Fmeta\u002Fheadings\u002Flinks\u002Fimages |\n| Health scorer | `python3 scripts\u002Fseo_health_scorer.py --checks checks.json --industry saas` (no arg = `--demo`; industries: saas\u002Fecommerce\u002Flocal\u002Fpublisher; `--json`) | Weighted 0-100 site health score across 7 categories |\n\nRun `seo_checker.py` on the key templates\u002Fpages during the on-page layer, and `seo_health_scorer.py` on the completed check matrix to produce the audit's headline score.\n\n## Output Format\n\n### Audit Report Structure\n\n**Executive Summary**\n- Overall health assessment — lead with the `seo_health_scorer.py` score and its weakest categories\n- Top 3-5 priority issues\n- Quick wins identified\n\n**Technical SEO Findings**\nFor each issue:\n- **Issue**: What's wrong\n- **Impact**: SEO impact (High\u002FMedium\u002FLow)\n- **Evidence**: How you found it\n- **Fix**: Specific recommendation\n- **Priority**: 1-5 or High\u002FMedium\u002FLow\n\n**On-Page SEO Findings**\nSame format as above\n\n**Content Findings**\nSame format as above\n\n**Prioritized Action Plan**\n1. Critical fixes (blocking indexation\u002Franking)\n2. High-impact improvements\n3. Quick wins (easy, immediate benefit)\n4. Long-term recommendations\n\n---\n\n## References\n\n- [SEO Audit Reference](references\u002Fseo-audit-reference.md): Full audit framework, scoring, and remediation patterns\n- [Core Web Vitals Thresholds](references\u002Fcwv-thresholds.md): LCP\u002FINP\u002FCLS targets and triage rules\n- [E-E-A-T Framework](references\u002Feeat-framework.md): Experience, Expertise, Authoritativeness, Trustworthiness checklist\n- [Schema Types](references\u002Fschema-types.md): Structured data patterns by content type\n\n---\n\n## Tools Referenced\n\n**Free Tools**\n- Google Search Console (essential)\n- Google PageSpeed Insights\n- Bing Webmaster Tools\n- Rich Results Test\n- Mobile-Friendly Test\n- Schema Validator\n\n**Paid Tools** (if available)\n- Screaming Frog\n- Ahrefs \u002F Semrush\n- Sitebulb\n- ContentKing\n\n---\n\n## Task-Specific Questions\n\n1. What pages\u002Fkeywords matter most?\n2. Do you have Search Console access?\n3. Any recent changes or migrations?\n4. Who are your top organic competitors?\n5. What's your current organic traffic baseline?\n\n---\n\n## Related Skills\n\n- **programmatic-seo** — WHEN: user wants to build SEO pages at scale after the audit identifies keyword gaps. WHEN NOT: don't use for diagnosing existing issues; stay in seo-audit mode.\n- **aeo** — WHEN: user wants to optimize for AI answer engines (SGE, Perplexity, ChatGPT) in addition to traditional search. WHEN NOT: don't use for purely technical crawl\u002Findexation issues.\n- **schema-markup** — WHEN: audit reveals missing structured data opportunities (FAQ, HowTo, Product, Review schemas). WHEN NOT: don't use as a standalone fix when core technical SEO is broken.\n- **site-architecture** — WHEN: audit uncovers poor internal linking, orphan pages, or crawl depth issues that need a structural redesign. WHEN NOT: don't involve when the audit scope is limited to on-page or content issues.\n- **content-strategy** — WHEN: audit reveals thin content, keyword gaps, or lack of topical authority requiring a content plan. WHEN NOT: don't use when the problem is purely technical (robots.txt, redirects, speed).\n- **marketing-context** — WHEN: always read first if `.claude\u002Fproduct-marketing-context.md` exists to avoid redundant questions. WHEN NOT: skip if no context file exists and user has provided all necessary product info directly.\n\n---\n\n## Communication\n\nAll audit output follows the **SEO Audit Quality Standard**:\n- Lead with the executive summary (3-5 bullets max)\n- Findings use the Issue \u002F Impact \u002F Evidence \u002F Fix \u002F Priority format consistently\n- Prioritized Action Plan is always the final deliverable section\n- Avoid jargon without explanation; write for a technically-aware but non-SEO-specialist reader\n- Quick wins are called out explicitly and kept separate from high-effort recommendations\n- Never present recommendations without evidence or rationale\n\n---\n\n## Proactive Triggers\n\nAutomatically surface seo-audit recommendations when:\n\n1. **Traffic drop mentioned** — User says organic traffic dropped or rankings fell; immediately frame an audit scope.\n2. **Site migration or redesign** — User mentions a planned or recent URL change, platform switch, or redesign; flag pre\u002Fpost-migration audit needs.\n3. **\"Why isn't my page ranking?\"** — Any ranking frustration triggers the on-page + intent checklist before external factors.\n4. **Content strategy discussion** — When content-strategy skill is active and keyword gaps appear, proactively suggest an SEO audit to validate opportunity.\n5. **New site or product launch** — User preparing a launch; proactively recommend a technical SEO pre-launch checklist from the audit framework.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Executive Summary | Markdown bullets | 3-5 top issues + quick wins, suitable for sharing with stakeholders |\n| Technical SEO Findings | Structured table | Issue \u002F Impact \u002F Evidence \u002F Fix \u002F Priority per finding |\n| On-Page SEO Findings | Structured table | Same format, focused on content and metadata |\n| Prioritized Action Plan | Numbered list | Ordered by impact × effort, grouped into Critical \u002F High \u002F Quick Wins |\n| Keyword Cannibalization Map | Table | Pages competing for same keyword with recommended canonical or redirect actions |\n",{"name":5,"license":14,"metadata":53,"description":7},{"author":54,"updated":55,"version":56,"category":57},"Alireza Rezvani",1772755200000,"1.0.0","marketing","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-02-claude-skills-main-marketing-skill-skills-seo-audit-skill-0a51e9ce","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill seo-audit",{"tool":70,"command":71},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill seo-audit",{"tool":73,"command":74},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill seo-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-marketing-skill-skills-seo-audit-skill-0a51e9ce\u002FSKILL.md",true,[],[79,103,131,162,190,222],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":48},"01M6NN9PJS9NHWPDG4QP93BP8F","webmcpify","Make a web app agent-ready — propose a WebMCP tool manifest, integrate, verify in a real browser, heal; unrelated code stays untouched. Use for \"webmcpify\", \"add WebMCP\", or \"expose app actions to AI agents\".","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fwebmcpify\u002FSKILL.md",[],[81,86,87,88,89,90,91,92,93,94,95,96,97,38,98,99,100,101,32,102],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","ready","unrelated","app","scope","webmcp",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":107,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":48},"01M6NN6KZE5RBN6NGHN2WXV1RE","vardoger-analyze","Use when the user asks to personalize the GitHub Copilot CLI assistant, adapt Copilot to their style, use vardoger, or analyze their Copilot CLI conversation history. Reads the local session directory at `~\u002F.copilot\u002Fsession-state\u002F`, extracts recurring preferences and conventions, and writes a fenced personalization block into `~\u002F.copilot\u002Fcopilot-instructions.md`. Runs entirely on the user's machine via the local `vardoger` CLI (`pipx install vardoger`); no network calls and no uploads. Triggers: 'personalize my copilot', 'analyze my copilot history', 'tailor copilot to me', 'run vardoger', 'update my copilot instructions from history', 'make copilot learn my style'.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fvardoger-analyze\u002FSKILL.md",[],[111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130],"vardoger analyze","analyze","directory","cli","github copilot","copilot","run","update","learn","network","my style","install","conversation","me","local","github copilot cli","pipx","my","at","copilot instructions",{"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":143,"publishedAt":48},"01M6NN3CZGQP3XAJ04BM1NNYGT","transloadit-media-processing","Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS\u002FMP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftransloadit-media-processing\u002FSKILL.md",[137,140],{"categoryNo":138,"categoryName":139,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":141,"categoryName":142,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[144,145,146,147,148,149,150,151,152,153,154,155,156,38,157,158,159,160,32,161],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":171,"publishedAt":48},"01M6NN28E92F9GH4WFYQ2H1Y15","terraform-azurerm-set-diff-analyzer","Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attributes) and actual resource changes. Use when reviewing terraform plan output for Azure resources like Application Gateway, Load Balancer, Firewall, Front Door, NSG, and other resources with Set-type attributes that cause spurious diffs due to internal ordering changes.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fterraform-azurerm-set-diff-analyzer\u002FSKILL.md",[168],{"categoryNo":169,"categoryName":170,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[172,173,174,175,176,177,178,179,180,38,181,182,183,184,185,186,187,188,189,32],"terraform","SET","terraform azurerm set diff analyzer","diff","analyzer","diffs","azure","gateway","firewall","only","resource changes","provider","resources","load balancer","attributes","front","load","balancer",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":205,"publishedAt":48},"01M6NN1QMH2TDYWTH3XY3N5XPV","technical-job-search","Use this skill when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV\u002Fresume, writing a cover letter, evaluating a job offer, or drafting a post-interview follow-up email. Do not activate for general career advice unrelated to an active job search action.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-job-search\u002FSKILL.md",[196,199,202],{"categoryNo":197,"categoryName":198,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":200,"categoryName":201,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":203,"categoryName":204,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000038","人力资源",[206,207,208,40,209,210,211,212,112,213,38,214,215,216,217,218,219,220,32,221],"search","Job Search","technical job search","writing","tasks","email","parsing","interview","up","engineer","general","activate","do","task","cv","letter",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":228,"publishedAt":48},"01M6NMZFA67XYS1GS09WT42235","steno-mode","Shorthand-first response compression that cuts ~40% of response tokens while preserving technical precision and exact literals. Use when the user says \"steno mode\", \"shorthand mode\", \"compressed responses\", \"token reduction\", \"brief structured output\", or invokes \u002Fsteno. Supports four compression levels: lite, brief, court, machine. Do not trigger for requests needing polished prose such as onboarding\u002Ftutorial content, stakeholder or customer-facing copy, or teaching-focused explanations.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fsteno-mode\u002FSKILL.md",[],[229,230,231,232,233,40,234,38,218,235,236,237,238,239,240,241,242,243,32,244],"steno mode","mode","customer","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]