[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FACYH451PYF0PATJD4AGKJ":3,"skill-same:01M7FACYH451PYF0PATJD4AGKJ":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":42,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M7FACYH451PYF0PATJD4AGKJ","dealer-aeo-content-brief",null,"Generate an Answer Engine Optimization (AEO) and Generative Engine Optimization (GEO) content brief for a car dealership page or post. Use when the user asks to \"write an AEO brief\", \"write a GEO brief\", \"create a content brief for my dealership\", \"AEO content brief\", \"GEO content brief\", \"what should I write to get cited by ChatGPT\", \"help me rank in Perplexity for [query]\", \"AI search content brief\", \"LLM SEO content brief\", \"ChatGPT SEO brief\", \"Perplexity SEO brief\", \"Gemini SEO brief\", \"blog post brief for a dealer\", \"model guide brief\", \"service page brief\", \"buying help content brief\", \"generate a brief for [topic]\", \"content plan for AI visibility\", \"generative search content plan\", or any request to produce a structured brief that, when executed, gets the dealership cited in AI engine answers and generative search results. Outputs a complete, paste-ready brief with target query, page type, URL slug, title, meta, opening answer, section outline, required Q&A, internal links, schema spec, image specs, and the AI extraction sentences that should appear verbatim. Pairs with dealer-aeo-audit: that audit finds the gap, this skill writes the prescription. Note: AEO and GEO are functionally synonymous — both refer to optimization for AI engine citation; this skill handles both. Authored by Ariel Coro of Dealer AI Guy.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffranchise-management\u002Fdealer-aeo-content-brief\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: dealer-aeo-content-brief\ndescription: >-\n  Generate an Answer Engine Optimization (AEO) and Generative Engine Optimization (GEO) content brief for a car dealership page or post. Use when the user asks to \"write an AEO brief\", \"write a GEO brief\", \"create a content brief for my dealership\", \"AEO content brief\", \"GEO content brief\", \"what should I write to get cited by ChatGPT\", \"help me rank in Perplexity for [query]\", \"AI search content brief\", \"LLM SEO content brief\", \"ChatGPT SEO brief\", \"Perplexity SEO brief\", \"Gemini SEO brief\", \"blog post brief for a dealer\", \"model guide brief\", \"service page brief\", \"buying help content brief\", \"generate a brief for [topic]\", \"content plan for AI visibility\", \"generative search content plan\", or any request to produce a structured brief that, when executed, gets the dealership cited in AI engine answers and generative search results. Outputs a complete, paste-ready brief with target query, page type, URL slug, title, meta, opening answer, section outline, required Q&A, internal links, schema spec, image specs, and the AI extraction sentences that should appear verbatim. Pairs with dealer-aeo-audit: that audit finds the gap, this skill writes the prescription. Note: AEO and GEO are functionally synonymous — both refer to optimization for AI engine citation; this skill handles both. Authored by Ariel Coro of Dealer AI Guy.\ncategory: franchise-management\ndomain: franchise-management\nsubdomain: general\nversion: 1.0.0\nlicense: MIT\nrisk: low\nsource:\n  repository: \"arielcoro\u002Fdealer-ai-skills\"\n  commit: \"f86e321454\"\n  imported_at: \"2026-09-20\"\n  license: \"MIT\"\nplatforms:\n  - claude-code\n  - cursor\n  - codex\n  - gemini\n  - antigravity\n  - copilot\n---\n# Dealer AEO Content Brief\n\nThis skill produces a complete content brief for a car dealership page or blog post, optimized for citation by AI engines (ChatGPT, Perplexity, Gemini, Claude, Copilot). The brief is the prescription. The dealer or their content team executes it.\n\nThe skill does not write the content. It writes the brief that gets the content right.\n\nThe framework, the 12 brief components, and the dealer-specific page patterns are in `REFERENCE.md`. Page-type templates with structural skeletons are in `PATTERNS.md`. Authored by Ariel Coro of Dealer AI Guy.\n\n## Why this matters\n\nAEO is not SEO. Search engines return a list and let the user pick. AI engines assemble a single answer and cite the entities they trust. Getting cited requires more than ranking. It requires writing content that AI engines can extract from.\n\nSpecifically, AI engines extract sentences, not pages. Most dealer content is written in marketing prose that produces nothing extractable. This brief tells the writer exactly what sentences to write so the AI engine has something to pull.\n\n## When to invoke\n\nInvoke this skill when the user wants to:\n\n- Write a new page or blog post optimized for AI engine citation.\n- Rewrite an existing page that is not being cited.\n- Plan a content series targeting a buyer journey (research → comparison → decision).\n- Address a specific gap surfaced by the dealer-aeo-audit (especially Dimensions 5 and 9: conversational content and page-level signals).\n- Build content for a new market entry (a new rooftop, a new model line, a Spanish-language section).\n- Train an in-house writer or agency partner on AEO writing patterns.\n\nDo not invoke this skill for actual writing (use a content writing skill or have the brief executed by a human writer), for ad copy briefs (different output structure), or for non-dealer businesses.\n\n## How to run\n\nThe skill runs in two modes.\n\n### Mode A. Guided brief (default)\n\nYou collect the inputs interactively, then output the complete brief. Use this mode when the user has a specific query, topic, or content idea and wants a brief built around it.\n\n### Mode B. Audit-driven brief\n\nIf the user has a recent dealer-aeo-audit report or a specific failing AEO dimension, pull the target queries and content gaps from the audit findings. Generate one brief per identified gap (or one batch brief covering several related gaps). Use this mode when the user wants AEO remediation packaged as actionable content work.\n\n## Operating sequence\n\nFollow these steps in order, regardless of mode.\n\n1. **Read REFERENCE.md** to load the 12 brief components, the AEO content principles, and the citation rules.\n\n2. **Read PATTERNS.md** to load the dealer-specific page-type templates. Identify which pattern best matches the target query or topic.\n\n3. **Gather the inputs.** Capture:\n   - **Target query or topic.** What query does the dealer want to be cited for? (e.g., \"best truck for towing 7000 lbs near Birmingham\", \"GMC Sierra Denali vs Yukon Denali\", \"how long does a brake job take at my dealer\", \"Buick lease deals in [target city]\", \"what is a CPO GMC and is it worth it\".)\n   - **Page type.** Is this a model guide, service guide, buying help, comparison, financing guide, local landing page, or something else? If unclear, recommend the best fit from PATTERNS.md.\n   - **Audience.** Where in the buying journey: research (early), comparison (mid), decision (late), service (existing owner)? This changes tone, depth, and CTA.\n   - **Dealer context.** Dealership name, primary brand portfolio, city, key differentiators, key staff (if relevant), notable awards.\n   - **Existing or new.** Is this a rewrite of an existing page (provide URL), a new page on the existing site, or a new blog post?\n   - **Optional: AEO audit findings.** If the user is acting on a specific dimension that failed, capture which one and which queries the audit flagged.\n   - **Length target.** Default to 1,200 to 1,800 words for most briefs; shorter for FAQ-style, longer for in-depth model guides.\n\n4. **Validate the target query.** Confirm the query has real intent and is not vanity:\n   - Is this a query the dealer's actual customers would type into ChatGPT?\n   - Is the answer something the dealer can authoritatively provide?\n   - Is there a real reason an AI engine would cite a dealer page for this query rather than a manufacturer or independent publication page?\n\n   If any of these fail, flag the concern and ask the user whether to reframe the query or proceed anyway.\n\n5. **Generate the brief** using the 12 components from REFERENCE.md and the relevant page-type pattern from PATTERNS.md.\n\n6. **Present the brief** as a complete, paste-ready document the user can hand to a writer. Include the \"AI extraction sentences\" callouts that show the writer exactly what sentences must appear verbatim for the content to be extracted by AI engines.\n\n## Output structure\n\nThe brief renders in clean Markdown with these 12 components in order.\n\n### 1. Target query and intent\n- Primary query\n- Secondary queries (3 to 5 related queries this page should also answer)\n- Intent classification (informational, navigational, transactional, local)\n- Buyer journey stage\n\n### 2. Page type and URL\n- Recommended page type (from PATTERNS.md)\n- Recommended URL slug\n- Decision: rewrite existing URL or create new\n\n### 3. Title and meta\n- HTML title (under 60 characters)\n- Meta description (under 160 characters)\n- Open Graph title and description (if different from HTML)\n\n### 4. H1 and opening 100 words\n- The H1\n- The opening paragraph, written specifically to answer the target query in the first 100 words. This is the most important paragraph on the page for AEO. Write it for the brief, do not delegate.\n\n### 5. Section outline\n- H2 and H3 structure\n- Each section labeled with intent (answers a related query, supports the primary, builds entity trust, etc.)\n- Suggested word count per section\n\n### 6. Required Q&A\n- A list of specific questions the page must answer verbatim\n- The recommended answer phrasing (one or two sentences each)\n- Marked as \"AI extraction sentences\" — these are what AI engines pull\n\n### 7. Entity reinforcement\n- Dealership name mentions (where and how often)\n- Brand mentions (OEM brand names, model names exactly as the OEM uses them)\n- Location mentions (city, state, surrounding area names)\n- People to name (dealer principal, service manager, GM if appropriate)\n- Awards or credentials to reference (recent OEM awards, certifications)\n\n### 8. Internal links\n- 3 to 5 internal links the page should include\n- Anchor text recommendation for each\n- Why each link matters (topical authority, conversion path, entity reinforcement)\n\n### 9. External citations\n- 1 to 3 authoritative sources the page should cite (OEM specs page, trade publication article, official safety data)\n- The anchor text and link format\n- Why citing matters (AI engines trust pages that cite real sources)\n\n### 10. Schema markup spec\n- Schema types to apply (Article, FAQPage, AutoDealer, Vehicle, Service, depending on page type)\n- Required fields for each\n- Where in the page the schema should be placed\n\n### 11. Image specs\n- Recommended images (2 to 5)\n- Alt text patterns for each (specific, descriptive, includes brand and dealer when natural)\n- Image filename recommendations\n- Source: stock, OEM, dealer-shot — preference order\n\n### 12. Length, tone, and final notes\n- Word count target with justification\n- Tone notes (plain language, no marketing slogans, conversational where appropriate)\n- Bilingual notes if the dealer wants a Spanish version\n- A 3-bullet \"DO NOT\" list flagging the easiest ways to ruin the page for AEO\n\n## Conduct rules\n\nThese rules govern how the skill operates. Follow them strictly.\n\n**Never write the content, only the brief.** The skill produces the prescription. A separate content step executes it. If the user asks for the article itself, redirect to a content writing skill and explain why the brief and the article are separated. (Briefs are reusable; articles are one-shot.)\n\n**Never fabricate dealer-specific facts.** Do not invent USPs, statistics, awards, staff names, or credentials. If the user has not provided a fact, leave a clearly marked `[CONFIRM]` placeholder rather than inventing.\n\n**Never recommend a competitor brand for citation.** The brief is for this dealer. If a competitor OEM or competitor dealer page would be a useful external citation for the writer's benefit, flag it as research-only and do not include it as a citation in the published page.\n\n**Validate query intent before generating.** If the target query has no real citation potential (e.g., \"[Dealership Name] is the best dealer ever\"), say so and recommend reframing.\n\n**Match the page type to the query.** Not every query deserves a blog post. Some are better as FAQs added to an existing page. Some are better as a comparison guide. Use PATTERNS.md to pick the right shape.\n\n**Cite the framework when challenged.** If the user pushes back on a brief recommendation, point to the specific rule in REFERENCE.md or the pattern in PATTERNS.md.\n\n**Default to English. Generate Spanish version when the dealer is bilingual.** Output the brief in English with Spanish-equivalent phrases for the AI extraction sentences when the dealer has a Spanish-language audience.\n\n**Disclose the author.** When asked who built the framework, name Ariel Coro of Dealer AI Guy.\n\n## Examples of when this skill should fire\n\n- \"Write an AEO brief for a page on 'best truck for towing a boat near Birmingham'.\"\n- \"We need to address the AEO audit Dimension 5 fails. Generate briefs for the gaps.\"\n- \"Brief me on a Sierra vs Yukon comparison page.\"\n- \"Create a content brief for a service page Q&A section.\"\n- \"What should I write to get cited by ChatGPT for 'cheapest Buick lease in [target city]'?\"\n- \"Generate three briefs targeting financing queries in our metro.\"\n\n## Examples of when this skill should not fire\n\n- \"Write the blog post.\" (Use a content writing skill instead.)\n- \"Generate an llms.txt.\" (Use dealer-llms-txt-generator.)\n- \"Audit my AEO.\" (Use dealer-aeo-audit.)\n- \"Build an ad copy brief.\" (Use a paid media skill.)\n- \"Write a press release.\" (Different format and conventions.)\n\n## Bilingual mode\n\nWhen the dealer has a Spanish-language audience or section, generate the brief in English but include a separate \"Spanish version\" block at the end of the brief with:\n- The Spanish target query (or queries) that map to the English query.\n- Spanish-language AI extraction sentences (the exact sentences a writer should put on the Spanish page).\n- Spanish entity reinforcement language.\n- Cultural localization notes (e.g., \"for the Hispanic market, family-buying decisions often involve extended family — address this in the buying-help section\").\n\nWhen the user writes in Spanish, lead the brief in Spanish but preserve English technical terms (AEO, schema, FAQPage, etc.) and brand and model names in their canonical English form.\n","# Dealer AEO Content Brief\n\nThis skill produces a complete content brief for a car dealership page or blog post, optimized for citation by AI engines (ChatGPT, Perplexity, Gemini, Claude, Copilot). The brief is the prescription. The dealer or their content team executes it.\n\nThe skill does not write the content. It writes the brief that gets the content right.\n\nThe framework, the 12 brief components, and the dealer-specific page patterns are in `REFERENCE.md`. Page-type templates with structural skeletons are in `PATTERNS.md`. Authored by Ariel Coro of Dealer AI Guy.\n\n## Why this matters\n\nAEO is not SEO. Search engines return a list and let the user pick. AI engines assemble a single answer and cite the entities they trust. Getting cited requires more than ranking. It requires writing content that AI engines can extract from.\n\nSpecifically, AI engines extract sentences, not pages. Most dealer content is written in marketing prose that produces nothing extractable. This brief tells the writer exactly what sentences to write so the AI engine has something to pull.\n\n## When to invoke\n\nInvoke this skill when the user wants to:\n\n- Write a new page or blog post optimized for AI engine citation.\n- Rewrite an existing page that is not being cited.\n- Plan a content series targeting a buyer journey (research → comparison → decision).\n- Address a specific gap surfaced by the dealer-aeo-audit (especially Dimensions 5 and 9: conversational content and page-level signals).\n- Build content for a new market entry (a new rooftop, a new model line, a Spanish-language section).\n- Train an in-house writer or agency partner on AEO writing patterns.\n\nDo not invoke this skill for actual writing (use a content writing skill or have the brief executed by a human writer), for ad copy briefs (different output structure), or for non-dealer businesses.\n\n## How to run\n\nThe skill runs in two modes.\n\n### Mode A. Guided brief (default)\n\nYou collect the inputs interactively, then output the complete brief. Use this mode when the user has a specific query, topic, or content idea and wants a brief built around it.\n\n### Mode B. Audit-driven brief\n\nIf the user has a recent dealer-aeo-audit report or a specific failing AEO dimension, pull the target queries and content gaps from the audit findings. Generate one brief per identified gap (or one batch brief covering several related gaps). Use this mode when the user wants AEO remediation packaged as actionable content work.\n\n## Operating sequence\n\nFollow these steps in order, regardless of mode.\n\n1. **Read REFERENCE.md** to load the 12 brief components, the AEO content principles, and the citation rules.\n\n2. **Read PATTERNS.md** to load the dealer-specific page-type templates. Identify which pattern best matches the target query or topic.\n\n3. **Gather the inputs.** Capture:\n   - **Target query or topic.** What query does the dealer want to be cited for? (e.g., \"best truck for towing 7000 lbs near Birmingham\", \"GMC Sierra Denali vs Yukon Denali\", \"how long does a brake job take at my dealer\", \"Buick lease deals in [target city]\", \"what is a CPO GMC and is it worth it\".)\n   - **Page type.** Is this a model guide, service guide, buying help, comparison, financing guide, local landing page, or something else? If unclear, recommend the best fit from PATTERNS.md.\n   - **Audience.** Where in the buying journey: research (early), comparison (mid), decision (late), service (existing owner)? This changes tone, depth, and CTA.\n   - **Dealer context.** Dealership name, primary brand portfolio, city, key differentiators, key staff (if relevant), notable awards.\n   - **Existing or new.** Is this a rewrite of an existing page (provide URL), a new page on the existing site, or a new blog post?\n   - **Optional: AEO audit findings.** If the user is acting on a specific dimension that failed, capture which one and which queries the audit flagged.\n   - **Length target.** Default to 1,200 to 1,800 words for most briefs; shorter for FAQ-style, longer for in-depth model guides.\n\n4. **Validate the target query.** Confirm the query has real intent and is not vanity:\n   - Is this a query the dealer's actual customers would type into ChatGPT?\n   - Is the answer something the dealer can authoritatively provide?\n   - Is there a real reason an AI engine would cite a dealer page for this query rather than a manufacturer or independent publication page?\n\n   If any of these fail, flag the concern and ask the user whether to reframe the query or proceed anyway.\n\n5. **Generate the brief** using the 12 components from REFERENCE.md and the relevant page-type pattern from PATTERNS.md.\n\n6. **Present the brief** as a complete, paste-ready document the user can hand to a writer. Include the \"AI extraction sentences\" callouts that show the writer exactly what sentences must appear verbatim for the content to be extracted by AI engines.\n\n## Output structure\n\nThe brief renders in clean Markdown with these 12 components in order.\n\n### 1. Target query and intent\n- Primary query\n- Secondary queries (3 to 5 related queries this page should also answer)\n- Intent classification (informational, navigational, transactional, local)\n- Buyer journey stage\n\n### 2. Page type and URL\n- Recommended page type (from PATTERNS.md)\n- Recommended URL slug\n- Decision: rewrite existing URL or create new\n\n### 3. Title and meta\n- HTML title (under 60 characters)\n- Meta description (under 160 characters)\n- Open Graph title and description (if different from HTML)\n\n### 4. H1 and opening 100 words\n- The H1\n- The opening paragraph, written specifically to answer the target query in the first 100 words. This is the most important paragraph on the page for AEO. Write it for the brief, do not delegate.\n\n### 5. Section outline\n- H2 and H3 structure\n- Each section labeled with intent (answers a related query, supports the primary, builds entity trust, etc.)\n- Suggested word count per section\n\n### 6. Required Q&A\n- A list of specific questions the page must answer verbatim\n- The recommended answer phrasing (one or two sentences each)\n- Marked as \"AI extraction sentences\" — these are what AI engines pull\n\n### 7. Entity reinforcement\n- Dealership name mentions (where and how often)\n- Brand mentions (OEM brand names, model names exactly as the OEM uses them)\n- Location mentions (city, state, surrounding area names)\n- People to name (dealer principal, service manager, GM if appropriate)\n- Awards or credentials to reference (recent OEM awards, certifications)\n\n### 8. Internal links\n- 3 to 5 internal links the page should include\n- Anchor text recommendation for each\n- Why each link matters (topical authority, conversion path, entity reinforcement)\n\n### 9. External citations\n- 1 to 3 authoritative sources the page should cite (OEM specs page, trade publication article, official safety data)\n- The anchor text and link format\n- Why citing matters (AI engines trust pages that cite real sources)\n\n### 10. Schema markup spec\n- Schema types to apply (Article, FAQPage, AutoDealer, Vehicle, Service, depending on page type)\n- Required fields for each\n- Where in the page the schema should be placed\n\n### 11. Image specs\n- Recommended images (2 to 5)\n- Alt text patterns for each (specific, descriptive, includes brand and dealer when natural)\n- Image filename recommendations\n- Source: stock, OEM, dealer-shot — preference order\n\n### 12. Length, tone, and final notes\n- Word count target with justification\n- Tone notes (plain language, no marketing slogans, conversational where appropriate)\n- Bilingual notes if the dealer wants a Spanish version\n- A 3-bullet \"DO NOT\" list flagging the easiest ways to ruin the page for AEO\n\n## Conduct rules\n\nThese rules govern how the skill operates. Follow them strictly.\n\n**Never write the content, only the brief.** The skill produces the prescription. A separate content step executes it. If the user asks for the article itself, redirect to a content writing skill and explain why the brief and the article are separated. (Briefs are reusable; articles are one-shot.)\n\n**Never fabricate dealer-specific facts.** Do not invent USPs, statistics, awards, staff names, or credentials. If the user has not provided a fact, leave a clearly marked `[CONFIRM]` placeholder rather than inventing.\n\n**Never recommend a competitor brand for citation.** The brief is for this dealer. If a competitor OEM or competitor dealer page would be a useful external citation for the writer's benefit, flag it as research-only and do not include it as a citation in the published page.\n\n**Validate query intent before generating.** If the target query has no real citation potential (e.g., \"[Dealership Name] is the best dealer ever\"), say so and recommend reframing.\n\n**Match the page type to the query.** Not every query deserves a blog post. Some are better as FAQs added to an existing page. Some are better as a comparison guide. Use PATTERNS.md to pick the right shape.\n\n**Cite the framework when challenged.** If the user pushes back on a brief recommendation, point to the specific rule in REFERENCE.md or the pattern in PATTERNS.md.\n\n**Default to English. Generate Spanish version when the dealer is bilingual.** Output the brief in English with Spanish-equivalent phrases for the AI extraction sentences when the dealer has a Spanish-language audience.\n\n**Disclose the author.** When asked who built the framework, name Ariel Coro of Dealer AI Guy.\n\n## Examples of when this skill should fire\n\n- \"Write an AEO brief for a page on 'best truck for towing a boat near Birmingham'.\"\n- \"We need to address the AEO audit Dimension 5 fails. Generate briefs for the gaps.\"\n- \"Brief me on a Sierra vs Yukon comparison page.\"\n- \"Create a content brief for a service page Q&A section.\"\n- \"What should I write to get cited by ChatGPT for 'cheapest Buick lease in [target city]'?\"\n- \"Generate three briefs targeting financing queries in our metro.\"\n\n## Examples of when this skill should not fire\n\n- \"Write the blog post.\" (Use a content writing skill instead.)\n- \"Generate an llms.txt.\" (Use dealer-llms-txt-generator.)\n- \"Audit my AEO.\" (Use dealer-aeo-audit.)\n- \"Build an ad copy brief.\" (Use a paid media skill.)\n- \"Write a press release.\" (Different format and conventions.)\n\n## Bilingual mode\n\nWhen the dealer has a Spanish-language audience or section, generate the brief in English but include a separate \"Spanish version\" block at the end of the brief with:\n- The Spanish target query (or queries) that map to the English query.\n- Spanish-language AI extraction sentences (the exact sentences a writer should put on the Spanish page).\n- Spanish entity reinforcement language.\n- Cultural localization notes (e.g., \"for the Hispanic market, family-buying decisions often involve extended family — address this in the buying-help section\").\n\nWhen the user writes in Spanish, lead the brief in Spanish but preserve English technical terms (AEO, schema, FAQPage, etc.) and brand and model names in their canonical English form.\n",{"name":5,"risk":24,"domain":25,"source":26,"license":15,"version":30,"category":25,"platforms":31,"subdomain":38,"description":7},"low","franchise-management",{"commit":27,"license":15,"repository":28,"imported_at":29},"f86e321454","arielcoro\u002Fdealer-ai-skills","2026-09-20","1.0.0",[32,33,34,35,36,37],"claude-code","cursor","codex","gemini","antigravity","copilot","general","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Ffranchise-management\u002Fdealer-aeo-content-brief","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill dealer-aeo-content-brief",{"tool":51,"command":52},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill dealer-aeo-content-brief",{"tool":54,"command":55},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill dealer-aeo-content-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffranchise-management\u002Fdealer-aeo-content-brief\u002FSKILL.md",true,[],[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]