[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-build-competitive-brief":3,"mdc-kokq0y-key":36,"related-repo-openai-build-competitive-brief":1577,"related-org-openai-build-competitive-brief":1680},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":25,"repoUrl":26,"updatedAt":27,"license":28,"forks":29,"topics":30,"repo":31,"sourceUrl":34,"mdContent":35},"build-competitive-brief","build competitive briefs and battlecards","Use when the user wants a competitor or vendor comparison, market-landscape analysis, battlecard, objection package, positioning brief, or account-specific competitive view. Produce an evidence-backed comparison, guidance, and brief, using supplied materials, connected research, and public evidence when appropriate.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"openai","OpenAI","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fopenai.png",[12,16,19,22],{"name":13,"slug":14,"type":15},"Research","research","tag",{"name":17,"slug":18,"type":15},"Competitive Intelligence","competitive-intelligence",{"name":20,"slug":21,"type":15},"Marketing","marketing",{"name":23,"slug":24,"type":15},"Sales","sales",427,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Frole-specific-plugins","2026-07-01T07:54:13.073252",null,65,[],{"repoUrl":26,"stars":25,"forks":29,"topics":32,"description":33},[],"Role-specific Codex plugin templates","https:\u002F\u002Fgithub.com\u002Fopenai\u002Frole-specific-plugins\u002Ftree\u002FHEAD\u002Fplugins\u002Fsales\u002Fskills\u002Fbuild-competitive-brief","---\nname: build-competitive-brief\ndescription: \"Use when the user wants a competitor or vendor comparison, market-landscape analysis, battlecard, objection package, positioning brief, or account-specific competitive view. Produce an evidence-backed comparison, guidance, and brief, using supplied materials, connected research, and public evidence when appropriate.\"\n---\n\n# Build Competitive Brief\n\nCreate a seller-ready competitive brief that separates verified facts from field signal and inference. Default to a self-contained HTML artifact plus a concise chat readout; use chat or Markdown only when the user explicitly asks for it. This skill owns research, synthesis, and the brief artifact, not external posting or CRM writes.\n\n## Common Skill Instructions\n\nMANDATORY: If not already in context, read and adhere closely to plugins\u002Fsales\u002Fskills\u002Findex\u002FSKILL.md## Cross-Skill Best Practices.\n\n## Key Dependency Categories\n\nUse the categories that materially apply to the request; do not broaden a search merely because a source is available.\n\n- ~~CRM for account, opportunity, contact, ownership, known competitor, and active-deal truth\n- ~~Knowledge & Files for battlecards, competitive docs, account plans, product positioning, proof points, and prior briefs\n- ~~Internal Messaging for recent field signals, account-team observations, objection examples, and source-of-truth routing when internal context matters\n- ~~Meeting Transcripts for prior objections, competitor mentions, buyer language, decisions, and commitments\n- ~~Sales Intelligence only when it sharpens competitor discovery, company context, or a concrete evidence gap\n\nUse public research for current public competitor facts. Prefer official product, pricing, launch, customer-story, investor, and regulatory sources; use secondary coverage only when primary sources are insufficient.\n\n## Reference Loading\n\n`SKILL.md` owns the normal research flow, HTML-by-default behavior, and evidence guardrails. Load references only when their extra detail matters:\n\n- Use [references\u002Frequest-schema.yaml](references\u002Frequest-schema.yaml) for structured input, mode normalization, or matrix bounds.\n- Use [references\u002Fsource-priority.md](references\u002Fsource-priority.md) when source conflict, authority order, or public-proof downgrade behavior is ambiguous.\n- Use [references\u002Foutput-contract.md](references\u002Foutput-contract.md) for exact section order, compressed brief variants, or machine-readable compatibility.\n\n## Terms\n\n- **Battlecard:** a compact seller guide for how to position against a competitor, including where they win, where they are weaker, and what to say.\n- **Defensive prep:** preparation for a competitor that may be relevant even when there is not enough evidence to say the competitor is active in the live deal.\n\n## Workflow Guidance\n\n### 1. Resolve the comparison anchor\n\n- Require one useful anchor: named competitor(s), a named account or deal with competitor context, or a clear product, workflow, segment, or market category to compare.\n- Preserve the user's exact seller, competitor, account, and objection wording. Infer the seller from the prompt or provided material only when credible; otherwise ask one targeted question.\n- When the user gives a clear product, workflow, segment, or market category but no competitor names, discover likely competitors from seller context, buyer context, product scope, maintained competitive material, and public evidence. Keep the discovered set focused and label uncertainty.\n- User confirmation is required for any required anchor inferred from sources rather than provided by the user.\n- If the anchor is ambiguous, do a bounded candidate pass before asking: at most three source reads, only enough to offer up to five concrete candidates with one-line rationale.\n- When a company-like name could be a competitor or customer, use a bounded ~~CRM check when available. If it resolves to a customer and the user did not clearly name it as a competitor, treat it as account context or ask the user to choose.\n- Do not gather broad enrichment before the user confirms an inferred required anchor.\n\n### 2. Gather evidence in authority order\n\nUse this order unless the user specifies a narrower lane:\n\n1. User-provided notes, decks, transcripts, prior briefs, and linked material\n2. ~~Knowledge & Files competitive docs, battlecards, account plans, and positioning\n3. ~~CRM for named account or deal truth\n4. ~~Meeting Transcripts and ~~Internal Messaging when they materially change the talk track\n5. Official public competitor and seller sources\n6. Investor, regulatory, or other primary public materials\n7. ~~Sales Intelligence and reputable secondary coverage for a specific remaining gap\n\n- Do not let generic web research replace stronger user or internal material.\n- Establish a seller baseline from seller-controlled sources when the seller is known: positioning, product lines, target segments, customer proof, recent launches, and comparison language.\n- Validate claims about current positioning, launches, pricing, partnerships, and public proof with public primary sources.\n- For competitor-only runs, seek multiple distinct evidence units when available. For account-scoped runs, add account evidence when the user supplied it or a connected source can fetch it narrowly.\n- Treat internal field signals as directional unless corroborated by account evidence, maintained docs, or public proof.\n- For each important source, extract a concrete evidence unit: what is claimed, what is confirmed, why buyers may care, how to counter or reframe, and what not to overclaim.\n- Cite material claims with clickable links when available. If a lane is unavailable, stale, thin, or conflicting, say so and continue with the strongest remaining evidence.\n\n### 3. Build dossiers before synthesis\n\nFor each in-scope competitor, capture the relevant available facts:\n\n- profile, target market, and what they sell\n- positioning and buyer appeal\n- pricing or pricing talk track only when supported\n- recent launches, releases, partnerships, or public proof\n- where they win and where the seller can separate\n- likely objections, discovery questions, talk tracks, and landmines\n\nDo not collapse competitors into one generic story. Keep distinct evidence and uncertainty for each.\n\n### 4. Add account context carefully\n\n- When an account is named, use user-provided account notes first and ~~CRM for account and opportunity truth.\n- Use ~~Knowledge & Files, ~~Meeting Transcripts, or ~~Internal Messaging selectively when they sharpen the live account implication.\n- Do not let public research or generic field chatter invent account status, competitor presence, or deal posture.\n- If there is no direct evidence that a competitor is active in the deal, label the account section Defensive prep.\n\n### 5. Synthesize the seller response\n\n- Default to brief; use objections, positioning, or account_overlay when the request calls for a narrower shape.\n- Compare at most five competitors in one matrix unless the user explicitly asks for more.\n- For 1-v-1, use Area | Seller | Competitor | Readout. For 1-v-many, use Area | Seller read | Status | Main pressure.\n- Use statuses such as Lead, Pressure from [Competitor], Mixed, and Not determined; do not force a winner when evidence does not support one.\n- Keep the tone factual and calm. Include what to say, what to clarify, proof to use, and what not to overclaim; avoid a feature bakeoff unless requested.\n- The package should answer what each competitor is doing, where they are dangerous, why they win, why they lose, how to compete, and what the seller or strategist should say next.\n\nExample 1-v-1 row:\n\n| Area | MyCompany | Competitor Alpha | Readout |\n| --- | --- | --- | --- |\n| Deployment fit | Strong for governed enterprise rollout | Strong for fast team-level adoption | Mixed; clarify buyer governance needs |\n\nExample 1-v-many row:\n\n| Area | MyCompany read | Status | Main pressure |\n| --- | --- | --- | --- |\n| Buyer simplicity | Strong if the buyer values one accountable platform | Pressure from Competitor Beta | Competitor Beta may look simpler for a narrow departmental use case |\n\n### 6. Create and verify the artifact\n\n- Default output: create a self-contained UTF-8 HTML brief with inline CSS and no external assets, then provide a concise chat summary. If the user explicitly asks for chat, plain text, or Markdown only, skip HTML and render the same substance in chat.\n- Use a user-provided destination when supplied. Otherwise write a sanitized-seller-compintel-date.html file in the current workspace; use a safe temporary directory when a workspace file would be inappropriate. Ask before overwriting an existing user-visible file.\n- Use a restrained, neutral, deck-inspired layout unless the user supplies brand conventions. Do not hardcode a company palette, logo, product name, or visual system.\n- Include top-level sections or tabs: Overview, Competitors, Guidance, and Sources.\n- Useful generic tooltip or card labels include Trigger, Discovery questions, Positioning, Verified signals, Where they win, Where the seller can separate, Why this works, Proof, Use when, and Landmine \u002F do not say.\n- Sources must show clickable provenance, evidence limitations, and which dependency categories were used, unavailable, or not relevant.\n- Read the generated file back and verify the required sections, source provenance, and embedded styling are present. When a browser or Playwright-style renderer is available, render it once and fix blank pages, broken layout, unreadable contrast, or missing CSS before returning the link.\n- Return the clickable artifact link first, followed by a short readout and a useful next-step offer. Do not narrate HTML mechanics in ordinary user-facing copy.\n\n### Next Step Options\n\nAfter the first output, offer the most relevant follow-up from the options below. Offer one clear transition, not a menu. Suggest ONLY these unless you are very confident another option is more useful:\n- Add an account-specific overlay that separates confirmed deal evidence from defensive prep.\n- Create an objections-only or positioning-only version for the immediate seller need.\n- Prepare a meeting brief using the competitive risks and discovery questions.\n- Draft a concise internal enablement or account-team update for review.\n- Check whether a matching weekly automation already reruns this `build-competitive-brief` skill for the same competitor, product, category, or account scope; if none exists, offer to create one that gives the seller a reusable competitive digest.\n- Close the smallest material competitive evidence gap.\n\nNext steps to avoid:\n- Sending, posting, or turning unsupported competitor claims into customer-facing assertions.\n\n### Automation Offer Guard\n\nFor durable competitor, category, product, or account-specific competitive scopes, a weekly competitive digest is the preferred automation offer when the user would benefit from reusable field intelligence rather than a one-off battlecard. Frame the value in sales language: what changed in the competitive landscape, why buyers may care, where the seller can separate, what to say, what to clarify, and what not to overclaim.\n\nThe automation must be a scheduled rerun of this skill, not a separate custom research digest. When creating or describing the automation, make the prompt call this skill directly and preserve the same competitive scope and mode:\n\n```text\nUse the Sales `build-competitive-brief` skill.\nRerun it weekly for the same competitive scope: [competitor, product, workflow, category, segment, region, or account].\nReturn the standard competitive brief output, including source posture and landmines.\n\nseller_company_name: \"[seller company when known]\"\nproduct_scope: \"[same product scope]\"\nworkflow_scope: \"[same workflow or buyer problem]\"\ncompetitor_scope: \"[same competitor category or market category]\"\ncompetitor_names: [same named competitors when used]\naccount_name: \"[same account when account-specific]\"\nmode: \"[brief, objections, positioning, or account_overlay]\"\nknown_objections: [same recurring objections when used]\n```\n\nFor broad category or product scopes where named competitors are discovered by the skill, keep the stable scope in the plain-language prompt text and let this skill resolve likely competitors using its normal comparison-anchor guidance. Do not offer this automation for a narrow one-time objection, meeting-specific prep, or sparse evidence gap unless the user clearly wants a recurring competitive watch.\n\nThe recurring output should follow this skill's competitive brief contract: context, seller baseline, competitive landscape summary, competitor snapshots, comparison takeaways, response strategy, what not to overclaim, and sources. Keep it read-only; it may recommend talk tracks, discovery questions, proof, and internal updates for review, but must not post, send, share, or turn unsupported competitor claims into customer-facing assertions unless the user separately asks and approves.\n\nBefore offering the weekly competitive digest, check whether the user already has a matching local automation installed. Inspect local automation records under `$CODEX_HOME\u002Fautomations\u002F*\u002Fautomation.toml`, or `~\u002F.codex\u002Fautomations\u002F*\u002Fautomation.toml` when `CODEX_HOME` is unset, and match by name, prompt, skill name, cadence, competitor, product, category, segment, account, mode, known objections, or other stable scope details. Treat active and paused matches as already installed.\n\n- If a matching automation exists, do not suggest creating another one. Continue with the next most relevant non-automation follow-up.\n- If no matching automation exists, end with one clear offer to check\u002Fcreate a weekly rerun of `build-competitive-brief` for the same scope. Describe the recurring output as a seller-ready competitive digest with what changed, why it matters, what to say, proof to use, and landmines to avoid. Do not create or update the automation until the user explicitly agrees.\n- If the automation surface is unavailable, do not mention tool details; offer to help set up a recurring competitive digest when automations are available.\n\n## Modes\n\n- brief — default; canonical competitive brief, matrix, response guidance, and sources\n- objections — buyer objections, proof points, discovery questions, talk tracks, and do-not-say guidance\n- positioning — comparison framing, danger zones, differentiators, and response strategy\n- account_overlay — account-specific implications, clearly separating confirmed deal evidence from defensive prep\n- chat_or_markdown_only — same evidence contract without an HTML artifact, only when explicitly requested\n\n## Output Format\n\nFor the HTML artifact and Markdown-only fallback, preserve this content contract:\n\n```md\n# [Seller] Competitive Brief\n\n## Context\n[Scope, buyer\u002Faccount context, mode, and evidence posture]\n\n## Seller Baseline\n[Seller positioning and relevant proof]\n\n## Competitive Landscape Summary\n[What matters most and why]\n\n## Competitor Snapshot\n### [Competitor]\n- **What they claim:** [Grounded claim]\n- **What is confirmed:** [Evidence-backed fact]\n- **Why buyers may care:** [Buyer appeal]\n- **Where they win:** [Supported strength]\n- **Where we can separate:** [Supported response]\n- **Landmine \u002F do not say:** [Overclaim to avoid]\n\n## Comparison Matrix Takeaways\n[Matrix plus the few implications that change seller behavior]\n\n## Response Strategy\n- **Say:** [Talk track]\n- **Clarify:** [Discovery question]\n- **Prove:** [Evidence]\n\n## What Not To Overclaim\n- [Uncertainty, conflict, or unsupported claim]\n\n## Sources\n- [Clickable source + what it supported]\n- [Dependency category status and material gaps]\n\n{Follow the instructions and output format\u002Fconditions in [Limitations and Improvements](..\u002Findex\u002FSKILL.md#limitations-and-improvements)}\n\n{Follow the instructions and output format\u002Fconditions in [Next Steps](..\u002Findex\u002FSKILL.md#4-next-steps)}\n```\n\nAdd Account Implications for account_overlay, and label unsupported competitor presence as Defensive prep.\n\n## Example Prompts\n\n- `Build a competitive brief for MyCompany vs Competitor Alpha.`\n- `Create a battlecard for MyCompany against Competitor Alpha and Competitor Beta in financial services.`\n- `Compare MyCompany's enterprise workflow platform against the top three alternatives for regulated buyers.`\n- `Build an account-specific defensive prep brief for ExampleCorp where Competitor Alpha may be in the deal.`\n- `Create a shareable HTML competitive brief for MyCompany vs Competitor Alpha.`\n\n## Rules\n\n- Never fabricate competitor capabilities, pricing, customer proof, account posture, or source links.\n- Keep facts, field signals, and inference visibly separate.\n- If evidence is sparse, narrow the brief and name the smallest evidence gaps that would improve it.\n- Do not post, send, share, or update systems from this workflow unless the user later explicitly requests a separate supported action.\n- Always cite material source-backed claims with hyperlinks when useful links are available.\n",{"data":37,"body":38},{"name":4,"description":6},{"type":39,"children":40},"root",[41,49,55,62,67,73,78,108,113,119,131,169,175,199,205,212,250,256,261,300,338,344,349,382,387,393,416,422,463,468,529,534,588,594,637,643,648,688,693,701,707,712,717,729,734,739,768,793,799,827,833,838,1478,1483,1489,1537,1543,1571],{"type":42,"tag":43,"props":44,"children":45},"element","h1",{"id":4},[46],{"type":47,"value":48},"text","Build Competitive Brief",{"type":42,"tag":50,"props":51,"children":52},"p",{},[53],{"type":47,"value":54},"Create a seller-ready competitive brief that separates verified facts from field signal and inference. Default to a self-contained HTML artifact plus a concise chat readout; use chat or Markdown only when the user explicitly asks for it. This skill owns research, synthesis, and the brief artifact, not external posting or CRM writes.",{"type":42,"tag":56,"props":57,"children":59},"h2",{"id":58},"common-skill-instructions",[60],{"type":47,"value":61},"Common Skill Instructions",{"type":42,"tag":50,"props":63,"children":64},{},[65],{"type":47,"value":66},"MANDATORY: If not already in context, read and adhere closely to plugins\u002Fsales\u002Fskills\u002Findex\u002FSKILL.md## Cross-Skill Best Practices.",{"type":42,"tag":56,"props":68,"children":70},{"id":69},"key-dependency-categories",[71],{"type":47,"value":72},"Key Dependency Categories",{"type":42,"tag":50,"props":74,"children":75},{},[76],{"type":47,"value":77},"Use the categories that materially apply to the request; do not broaden a search merely because a source is available.",{"type":42,"tag":79,"props":80,"children":81},"ul",{},[82,88,93,98,103],{"type":42,"tag":83,"props":84,"children":85},"li",{},[86],{"type":47,"value":87},"~~CRM for account, opportunity, contact, ownership, known competitor, and active-deal truth",{"type":42,"tag":83,"props":89,"children":90},{},[91],{"type":47,"value":92},"~~Knowledge & Files for battlecards, competitive docs, account plans, product positioning, proof points, and prior briefs",{"type":42,"tag":83,"props":94,"children":95},{},[96],{"type":47,"value":97},"~~Internal Messaging for recent field signals, account-team observations, objection examples, and source-of-truth routing when internal context matters",{"type":42,"tag":83,"props":99,"children":100},{},[101],{"type":47,"value":102},"~~Meeting Transcripts for prior objections, competitor mentions, buyer language, decisions, and commitments",{"type":42,"tag":83,"props":104,"children":105},{},[106],{"type":47,"value":107},"~~Sales Intelligence only when it sharpens competitor discovery, company context, or a concrete evidence gap",{"type":42,"tag":50,"props":109,"children":110},{},[111],{"type":47,"value":112},"Use public research for current public competitor facts. Prefer official product, pricing, launch, customer-story, investor, and regulatory sources; use secondary coverage only when primary sources are insufficient.",{"type":42,"tag":56,"props":114,"children":116},{"id":115},"reference-loading",[117],{"type":47,"value":118},"Reference Loading",{"type":42,"tag":50,"props":120,"children":121},{},[122,129],{"type":42,"tag":123,"props":124,"children":126},"code",{"className":125},[],[127],{"type":47,"value":128},"SKILL.md",{"type":47,"value":130}," owns the normal research flow, HTML-by-default behavior, and evidence guardrails. Load references only when their extra detail matters:",{"type":42,"tag":79,"props":132,"children":133},{},[134,147,158],{"type":42,"tag":83,"props":135,"children":136},{},[137,139,145],{"type":47,"value":138},"Use ",{"type":42,"tag":140,"props":141,"children":143},"a",{"href":142},"references\u002Frequest-schema.yaml",[144],{"type":47,"value":142},{"type":47,"value":146}," for structured input, mode normalization, or matrix bounds.",{"type":42,"tag":83,"props":148,"children":149},{},[150,151,156],{"type":47,"value":138},{"type":42,"tag":140,"props":152,"children":154},{"href":153},"references\u002Fsource-priority.md",[155],{"type":47,"value":153},{"type":47,"value":157}," when source conflict, authority order, or public-proof downgrade behavior is ambiguous.",{"type":42,"tag":83,"props":159,"children":160},{},[161,162,167],{"type":47,"value":138},{"type":42,"tag":140,"props":163,"children":165},{"href":164},"references\u002Foutput-contract.md",[166],{"type":47,"value":164},{"type":47,"value":168}," for exact section order, compressed brief variants, or machine-readable compatibility.",{"type":42,"tag":56,"props":170,"children":172},{"id":171},"terms",[173],{"type":47,"value":174},"Terms",{"type":42,"tag":79,"props":176,"children":177},{},[178,189],{"type":42,"tag":83,"props":179,"children":180},{},[181,187],{"type":42,"tag":182,"props":183,"children":184},"strong",{},[185],{"type":47,"value":186},"Battlecard:",{"type":47,"value":188}," a compact seller guide for how to position against a competitor, including where they win, where they are weaker, and what to say.",{"type":42,"tag":83,"props":190,"children":191},{},[192,197],{"type":42,"tag":182,"props":193,"children":194},{},[195],{"type":47,"value":196},"Defensive prep:",{"type":47,"value":198}," preparation for a competitor that may be relevant even when there is not enough evidence to say the competitor is active in the live deal.",{"type":42,"tag":56,"props":200,"children":202},{"id":201},"workflow-guidance",[203],{"type":47,"value":204},"Workflow Guidance",{"type":42,"tag":206,"props":207,"children":209},"h3",{"id":208},"_1-resolve-the-comparison-anchor",[210],{"type":47,"value":211},"1. Resolve the comparison anchor",{"type":42,"tag":79,"props":213,"children":214},{},[215,220,225,230,235,240,245],{"type":42,"tag":83,"props":216,"children":217},{},[218],{"type":47,"value":219},"Require one useful anchor: named competitor(s), a named account or deal with competitor context, or a clear product, workflow, segment, or market category to compare.",{"type":42,"tag":83,"props":221,"children":222},{},[223],{"type":47,"value":224},"Preserve the user's exact seller, competitor, account, and objection wording. Infer the seller from the prompt or provided material only when credible; otherwise ask one targeted question.",{"type":42,"tag":83,"props":226,"children":227},{},[228],{"type":47,"value":229},"When the user gives a clear product, workflow, segment, or market category but no competitor names, discover likely competitors from seller context, buyer context, product scope, maintained competitive material, and public evidence. Keep the discovered set focused and label uncertainty.",{"type":42,"tag":83,"props":231,"children":232},{},[233],{"type":47,"value":234},"User confirmation is required for any required anchor inferred from sources rather than provided by the user.",{"type":42,"tag":83,"props":236,"children":237},{},[238],{"type":47,"value":239},"If the anchor is ambiguous, do a bounded candidate pass before asking: at most three source reads, only enough to offer up to five concrete candidates with one-line rationale.",{"type":42,"tag":83,"props":241,"children":242},{},[243],{"type":47,"value":244},"When a company-like name could be a competitor or customer, use a bounded ~~CRM check when available. If it resolves to a customer and the user did not clearly name it as a competitor, treat it as account context or ask the user to choose.",{"type":42,"tag":83,"props":246,"children":247},{},[248],{"type":47,"value":249},"Do not gather broad enrichment before the user confirms an inferred required anchor.",{"type":42,"tag":206,"props":251,"children":253},{"id":252},"_2-gather-evidence-in-authority-order",[254],{"type":47,"value":255},"2. Gather evidence in authority order",{"type":42,"tag":50,"props":257,"children":258},{},[259],{"type":47,"value":260},"Use this order unless the user specifies a narrower lane:",{"type":42,"tag":262,"props":263,"children":264},"ol",{},[265,270,275,280,285,290,295],{"type":42,"tag":83,"props":266,"children":267},{},[268],{"type":47,"value":269},"User-provided notes, decks, transcripts, prior briefs, and linked material",{"type":42,"tag":83,"props":271,"children":272},{},[273],{"type":47,"value":274},"~~Knowledge & Files competitive docs, battlecards, account plans, and positioning",{"type":42,"tag":83,"props":276,"children":277},{},[278],{"type":47,"value":279},"~~CRM for named account or deal truth",{"type":42,"tag":83,"props":281,"children":282},{},[283],{"type":47,"value":284},"~~Meeting Transcripts and ~~Internal Messaging when they materially change the talk track",{"type":42,"tag":83,"props":286,"children":287},{},[288],{"type":47,"value":289},"Official public competitor and seller sources",{"type":42,"tag":83,"props":291,"children":292},{},[293],{"type":47,"value":294},"Investor, regulatory, or other primary public materials",{"type":42,"tag":83,"props":296,"children":297},{},[298],{"type":47,"value":299},"~~Sales Intelligence and reputable secondary coverage for a specific remaining gap",{"type":42,"tag":79,"props":301,"children":302},{},[303,308,313,318,323,328,333],{"type":42,"tag":83,"props":304,"children":305},{},[306],{"type":47,"value":307},"Do not let generic web research replace stronger user or internal material.",{"type":42,"tag":83,"props":309,"children":310},{},[311],{"type":47,"value":312},"Establish a seller baseline from seller-controlled sources when the seller is known: positioning, product lines, target segments, customer proof, recent launches, and comparison language.",{"type":42,"tag":83,"props":314,"children":315},{},[316],{"type":47,"value":317},"Validate claims about current positioning, launches, pricing, partnerships, and public proof with public primary sources.",{"type":42,"tag":83,"props":319,"children":320},{},[321],{"type":47,"value":322},"For competitor-only runs, seek multiple distinct evidence units when available. For account-scoped runs, add account evidence when the user supplied it or a connected source can fetch it narrowly.",{"type":42,"tag":83,"props":324,"children":325},{},[326],{"type":47,"value":327},"Treat internal field signals as directional unless corroborated by account evidence, maintained docs, or public proof.",{"type":42,"tag":83,"props":329,"children":330},{},[331],{"type":47,"value":332},"For each important source, extract a concrete evidence unit: what is claimed, what is confirmed, why buyers may care, how to counter or reframe, and what not to overclaim.",{"type":42,"tag":83,"props":334,"children":335},{},[336],{"type":47,"value":337},"Cite material claims with clickable links when available. If a lane is unavailable, stale, thin, or conflicting, say so and continue with the strongest remaining evidence.",{"type":42,"tag":206,"props":339,"children":341},{"id":340},"_3-build-dossiers-before-synthesis",[342],{"type":47,"value":343},"3. Build dossiers before synthesis",{"type":42,"tag":50,"props":345,"children":346},{},[347],{"type":47,"value":348},"For each in-scope competitor, capture the relevant available facts:",{"type":42,"tag":79,"props":350,"children":351},{},[352,357,362,367,372,377],{"type":42,"tag":83,"props":353,"children":354},{},[355],{"type":47,"value":356},"profile, target market, and what they sell",{"type":42,"tag":83,"props":358,"children":359},{},[360],{"type":47,"value":361},"positioning and buyer appeal",{"type":42,"tag":83,"props":363,"children":364},{},[365],{"type":47,"value":366},"pricing or pricing talk track only when supported",{"type":42,"tag":83,"props":368,"children":369},{},[370],{"type":47,"value":371},"recent launches, releases, partnerships, or public proof",{"type":42,"tag":83,"props":373,"children":374},{},[375],{"type":47,"value":376},"where they win and where the seller can separate",{"type":42,"tag":83,"props":378,"children":379},{},[380],{"type":47,"value":381},"likely objections, discovery questions, talk tracks, and landmines",{"type":42,"tag":50,"props":383,"children":384},{},[385],{"type":47,"value":386},"Do not collapse competitors into one generic story. Keep distinct evidence and uncertainty for each.",{"type":42,"tag":206,"props":388,"children":390},{"id":389},"_4-add-account-context-carefully",[391],{"type":47,"value":392},"4. Add account context carefully",{"type":42,"tag":79,"props":394,"children":395},{},[396,401,406,411],{"type":42,"tag":83,"props":397,"children":398},{},[399],{"type":47,"value":400},"When an account is named, use user-provided account notes first and ~~CRM for account and opportunity truth.",{"type":42,"tag":83,"props":402,"children":403},{},[404],{"type":47,"value":405},"Use ~~Knowledge & Files, ~~Meeting Transcripts, or ~~Internal Messaging selectively when they sharpen the live account implication.",{"type":42,"tag":83,"props":407,"children":408},{},[409],{"type":47,"value":410},"Do not let public research or generic field chatter invent account status, competitor presence, or deal posture.",{"type":42,"tag":83,"props":412,"children":413},{},[414],{"type":47,"value":415},"If there is no direct evidence that a competitor is active in the deal, label the account section Defensive prep.",{"type":42,"tag":206,"props":417,"children":419},{"id":418},"_5-synthesize-the-seller-response",[420],{"type":47,"value":421},"5. Synthesize the seller response",{"type":42,"tag":79,"props":423,"children":424},{},[425,430,435,440,453,458],{"type":42,"tag":83,"props":426,"children":427},{},[428],{"type":47,"value":429},"Default to brief; use objections, positioning, or account_overlay when the request calls for a narrower shape.",{"type":42,"tag":83,"props":431,"children":432},{},[433],{"type":47,"value":434},"Compare at most five competitors in one matrix unless the user explicitly asks for more.",{"type":42,"tag":83,"props":436,"children":437},{},[438],{"type":47,"value":439},"For 1-v-1, use Area | Seller | Competitor | Readout. For 1-v-many, use Area | Seller read | Status | Main pressure.",{"type":42,"tag":83,"props":441,"children":442},{},[443,445,451],{"type":47,"value":444},"Use statuses such as Lead, Pressure from ",{"type":42,"tag":446,"props":447,"children":448},"span",{},[449],{"type":47,"value":450},"Competitor",{"type":47,"value":452},", Mixed, and Not determined; do not force a winner when evidence does not support one.",{"type":42,"tag":83,"props":454,"children":455},{},[456],{"type":47,"value":457},"Keep the tone factual and calm. Include what to say, what to clarify, proof to use, and what not to overclaim; avoid a feature bakeoff unless requested.",{"type":42,"tag":83,"props":459,"children":460},{},[461],{"type":47,"value":462},"The package should answer what each competitor is doing, where they are dangerous, why they win, why they lose, how to compete, and what the seller or strategist should say next.",{"type":42,"tag":50,"props":464,"children":465},{},[466],{"type":47,"value":467},"Example 1-v-1 row:",{"type":42,"tag":469,"props":470,"children":471},"table",{},[472,501],{"type":42,"tag":473,"props":474,"children":475},"thead",{},[476],{"type":42,"tag":477,"props":478,"children":479},"tr",{},[480,486,491,496],{"type":42,"tag":481,"props":482,"children":483},"th",{},[484],{"type":47,"value":485},"Area",{"type":42,"tag":481,"props":487,"children":488},{},[489],{"type":47,"value":490},"MyCompany",{"type":42,"tag":481,"props":492,"children":493},{},[494],{"type":47,"value":495},"Competitor Alpha",{"type":42,"tag":481,"props":497,"children":498},{},[499],{"type":47,"value":500},"Readout",{"type":42,"tag":502,"props":503,"children":504},"tbody",{},[505],{"type":42,"tag":477,"props":506,"children":507},{},[508,514,519,524],{"type":42,"tag":509,"props":510,"children":511},"td",{},[512],{"type":47,"value":513},"Deployment fit",{"type":42,"tag":509,"props":515,"children":516},{},[517],{"type":47,"value":518},"Strong for governed enterprise rollout",{"type":42,"tag":509,"props":520,"children":521},{},[522],{"type":47,"value":523},"Strong for fast team-level adoption",{"type":42,"tag":509,"props":525,"children":526},{},[527],{"type":47,"value":528},"Mixed; clarify buyer governance needs",{"type":42,"tag":50,"props":530,"children":531},{},[532],{"type":47,"value":533},"Example 1-v-many row:",{"type":42,"tag":469,"props":535,"children":536},{},[537,562],{"type":42,"tag":473,"props":538,"children":539},{},[540],{"type":42,"tag":477,"props":541,"children":542},{},[543,547,552,557],{"type":42,"tag":481,"props":544,"children":545},{},[546],{"type":47,"value":485},{"type":42,"tag":481,"props":548,"children":549},{},[550],{"type":47,"value":551},"MyCompany read",{"type":42,"tag":481,"props":553,"children":554},{},[555],{"type":47,"value":556},"Status",{"type":42,"tag":481,"props":558,"children":559},{},[560],{"type":47,"value":561},"Main pressure",{"type":42,"tag":502,"props":563,"children":564},{},[565],{"type":42,"tag":477,"props":566,"children":567},{},[568,573,578,583],{"type":42,"tag":509,"props":569,"children":570},{},[571],{"type":47,"value":572},"Buyer simplicity",{"type":42,"tag":509,"props":574,"children":575},{},[576],{"type":47,"value":577},"Strong if the buyer values one accountable platform",{"type":42,"tag":509,"props":579,"children":580},{},[581],{"type":47,"value":582},"Pressure from Competitor Beta",{"type":42,"tag":509,"props":584,"children":585},{},[586],{"type":47,"value":587},"Competitor Beta may look simpler for a narrow departmental use case",{"type":42,"tag":206,"props":589,"children":591},{"id":590},"_6-create-and-verify-the-artifact",[592],{"type":47,"value":593},"6. Create and verify the artifact",{"type":42,"tag":79,"props":595,"children":596},{},[597,602,607,612,617,622,627,632],{"type":42,"tag":83,"props":598,"children":599},{},[600],{"type":47,"value":601},"Default output: create a self-contained UTF-8 HTML brief with inline CSS and no external assets, then provide a concise chat summary. If the user explicitly asks for chat, plain text, or Markdown only, skip HTML and render the same substance in chat.",{"type":42,"tag":83,"props":603,"children":604},{},[605],{"type":47,"value":606},"Use a user-provided destination when supplied. Otherwise write a sanitized-seller-compintel-date.html file in the current workspace; use a safe temporary directory when a workspace file would be inappropriate. Ask before overwriting an existing user-visible file.",{"type":42,"tag":83,"props":608,"children":609},{},[610],{"type":47,"value":611},"Use a restrained, neutral, deck-inspired layout unless the user supplies brand conventions. Do not hardcode a company palette, logo, product name, or visual system.",{"type":42,"tag":83,"props":613,"children":614},{},[615],{"type":47,"value":616},"Include top-level sections or tabs: Overview, Competitors, Guidance, and Sources.",{"type":42,"tag":83,"props":618,"children":619},{},[620],{"type":47,"value":621},"Useful generic tooltip or card labels include Trigger, Discovery questions, Positioning, Verified signals, Where they win, Where the seller can separate, Why this works, Proof, Use when, and Landmine \u002F do not say.",{"type":42,"tag":83,"props":623,"children":624},{},[625],{"type":47,"value":626},"Sources must show clickable provenance, evidence limitations, and which dependency categories were used, unavailable, or not relevant.",{"type":42,"tag":83,"props":628,"children":629},{},[630],{"type":47,"value":631},"Read the generated file back and verify the required sections, source provenance, and embedded styling are present. When a browser or Playwright-style renderer is available, render it once and fix blank pages, broken layout, unreadable contrast, or missing CSS before returning the link.",{"type":42,"tag":83,"props":633,"children":634},{},[635],{"type":47,"value":636},"Return the clickable artifact link first, followed by a short readout and a useful next-step offer. Do not narrate HTML mechanics in ordinary user-facing copy.",{"type":42,"tag":206,"props":638,"children":640},{"id":639},"next-step-options",[641],{"type":47,"value":642},"Next Step Options",{"type":42,"tag":50,"props":644,"children":645},{},[646],{"type":47,"value":647},"After the first output, offer the most relevant follow-up from the options below. Offer one clear transition, not a menu. Suggest ONLY these unless you are very confident another option is more useful:",{"type":42,"tag":79,"props":649,"children":650},{},[651,656,661,666,671,683],{"type":42,"tag":83,"props":652,"children":653},{},[654],{"type":47,"value":655},"Add an account-specific overlay that separates confirmed deal evidence from defensive prep.",{"type":42,"tag":83,"props":657,"children":658},{},[659],{"type":47,"value":660},"Create an objections-only or positioning-only version for the immediate seller need.",{"type":42,"tag":83,"props":662,"children":663},{},[664],{"type":47,"value":665},"Prepare a meeting brief using the competitive risks and discovery questions.",{"type":42,"tag":83,"props":667,"children":668},{},[669],{"type":47,"value":670},"Draft a concise internal enablement or account-team update for review.",{"type":42,"tag":83,"props":672,"children":673},{},[674,676,681],{"type":47,"value":675},"Check whether a matching weekly automation already reruns this ",{"type":42,"tag":123,"props":677,"children":679},{"className":678},[],[680],{"type":47,"value":4},{"type":47,"value":682}," skill for the same competitor, product, category, or account scope; if none exists, offer to create one that gives the seller a reusable competitive digest.",{"type":42,"tag":83,"props":684,"children":685},{},[686],{"type":47,"value":687},"Close the smallest material competitive evidence gap.",{"type":42,"tag":50,"props":689,"children":690},{},[691],{"type":47,"value":692},"Next steps to avoid:",{"type":42,"tag":79,"props":694,"children":695},{},[696],{"type":42,"tag":83,"props":697,"children":698},{},[699],{"type":47,"value":700},"Sending, posting, or turning unsupported competitor claims into customer-facing assertions.",{"type":42,"tag":206,"props":702,"children":704},{"id":703},"automation-offer-guard",[705],{"type":47,"value":706},"Automation Offer Guard",{"type":42,"tag":50,"props":708,"children":709},{},[710],{"type":47,"value":711},"For durable competitor, category, product, or account-specific competitive scopes, a weekly competitive digest is the preferred automation offer when the user would benefit from reusable field intelligence rather than a one-off battlecard. Frame the value in sales language: what changed in the competitive landscape, why buyers may care, where the seller can separate, what to say, what to clarify, and what not to overclaim.",{"type":42,"tag":50,"props":713,"children":714},{},[715],{"type":47,"value":716},"The automation must be a scheduled rerun of this skill, not a separate custom research digest. When creating or describing the automation, make the prompt call this skill directly and preserve the same competitive scope and mode:",{"type":42,"tag":718,"props":719,"children":724},"pre",{"className":720,"code":722,"language":47,"meta":723},[721],"language-text","Use the Sales `build-competitive-brief` skill.\nRerun it weekly for the same competitive scope: [competitor, product, workflow, category, segment, region, or account].\nReturn the standard competitive brief output, including source posture and landmines.\n\nseller_company_name: \"[seller company when known]\"\nproduct_scope: \"[same product scope]\"\nworkflow_scope: \"[same workflow or buyer problem]\"\ncompetitor_scope: \"[same competitor category or market category]\"\ncompetitor_names: [same named competitors when used]\naccount_name: \"[same account when account-specific]\"\nmode: \"[brief, objections, positioning, or account_overlay]\"\nknown_objections: [same recurring objections when used]\n","",[725],{"type":42,"tag":123,"props":726,"children":727},{"__ignoreMap":723},[728],{"type":47,"value":722},{"type":42,"tag":50,"props":730,"children":731},{},[732],{"type":47,"value":733},"For broad category or product scopes where named competitors are discovered by the skill, keep the stable scope in the plain-language prompt text and let this skill resolve likely competitors using its normal comparison-anchor guidance. Do not offer this automation for a narrow one-time objection, meeting-specific prep, or sparse evidence gap unless the user clearly wants a recurring competitive watch.",{"type":42,"tag":50,"props":735,"children":736},{},[737],{"type":47,"value":738},"The recurring output should follow this skill's competitive brief contract: context, seller baseline, competitive landscape summary, competitor snapshots, comparison takeaways, response strategy, what not to overclaim, and sources. Keep it read-only; it may recommend talk tracks, discovery questions, proof, and internal updates for review, but must not post, send, share, or turn unsupported competitor claims into customer-facing assertions unless the user separately asks and approves.",{"type":42,"tag":50,"props":740,"children":741},{},[742,744,750,752,758,760,766],{"type":47,"value":743},"Before offering the weekly competitive digest, check whether the user already has a matching local automation installed. Inspect local automation records under ",{"type":42,"tag":123,"props":745,"children":747},{"className":746},[],[748],{"type":47,"value":749},"$CODEX_HOME\u002Fautomations\u002F*\u002Fautomation.toml",{"type":47,"value":751},", or ",{"type":42,"tag":123,"props":753,"children":755},{"className":754},[],[756],{"type":47,"value":757},"~\u002F.codex\u002Fautomations\u002F*\u002Fautomation.toml",{"type":47,"value":759}," when ",{"type":42,"tag":123,"props":761,"children":763},{"className":762},[],[764],{"type":47,"value":765},"CODEX_HOME",{"type":47,"value":767}," is unset, and match by name, prompt, skill name, cadence, competitor, product, category, segment, account, mode, known objections, or other stable scope details. Treat active and paused matches as already installed.",{"type":42,"tag":79,"props":769,"children":770},{},[771,776,788],{"type":42,"tag":83,"props":772,"children":773},{},[774],{"type":47,"value":775},"If a matching automation exists, do not suggest creating another one. Continue with the next most relevant non-automation follow-up.",{"type":42,"tag":83,"props":777,"children":778},{},[779,781,786],{"type":47,"value":780},"If no matching automation exists, end with one clear offer to check\u002Fcreate a weekly rerun of ",{"type":42,"tag":123,"props":782,"children":784},{"className":783},[],[785],{"type":47,"value":4},{"type":47,"value":787}," for the same scope. Describe the recurring output as a seller-ready competitive digest with what changed, why it matters, what to say, proof to use, and landmines to avoid. Do not create or update the automation until the user explicitly agrees.",{"type":42,"tag":83,"props":789,"children":790},{},[791],{"type":47,"value":792},"If the automation surface is unavailable, do not mention tool details; offer to help set up a recurring competitive digest when automations are available.",{"type":42,"tag":56,"props":794,"children":796},{"id":795},"modes",[797],{"type":47,"value":798},"Modes",{"type":42,"tag":79,"props":800,"children":801},{},[802,807,812,817,822],{"type":42,"tag":83,"props":803,"children":804},{},[805],{"type":47,"value":806},"brief — default; canonical competitive brief, matrix, response guidance, and sources",{"type":42,"tag":83,"props":808,"children":809},{},[810],{"type":47,"value":811},"objections — buyer objections, proof points, discovery questions, talk tracks, and do-not-say guidance",{"type":42,"tag":83,"props":813,"children":814},{},[815],{"type":47,"value":816},"positioning — comparison framing, danger zones, differentiators, and response strategy",{"type":42,"tag":83,"props":818,"children":819},{},[820],{"type":47,"value":821},"account_overlay — account-specific implications, clearly separating confirmed deal evidence from defensive prep",{"type":42,"tag":83,"props":823,"children":824},{},[825],{"type":47,"value":826},"chat_or_markdown_only — same evidence contract without an HTML artifact, only when explicitly requested",{"type":42,"tag":56,"props":828,"children":830},{"id":829},"output-format",[831],{"type":47,"value":832},"Output Format",{"type":42,"tag":50,"props":834,"children":835},{},[836],{"type":47,"value":837},"For the HTML artifact and Markdown-only fallback, preserve this content contract:",{"type":42,"tag":718,"props":839,"children":843},{"className":840,"code":841,"language":842,"meta":723,"style":723},"language-md shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","# [Seller] Competitive Brief\n\n## Context\n[Scope, buyer\u002Faccount context, mode, and evidence posture]\n\n## Seller Baseline\n[Seller positioning and relevant proof]\n\n## Competitive Landscape Summary\n[What matters most and why]\n\n## Competitor Snapshot\n### [Competitor]\n- **What they claim:** [Grounded claim]\n- **What is confirmed:** [Evidence-backed fact]\n- **Why buyers may care:** [Buyer appeal]\n- **Where they win:** [Supported strength]\n- **Where we can separate:** [Supported response]\n- **Landmine \u002F do not say:** [Overclaim to avoid]\n\n## Comparison Matrix Takeaways\n[Matrix plus the few implications that change seller behavior]\n\n## Response Strategy\n- **Say:** [Talk track]\n- **Clarify:** [Discovery question]\n- **Prove:** [Evidence]\n\n## What Not To Overclaim\n- [Uncertainty, conflict, or unsupported claim]\n\n## Sources\n- [Clickable source + what it supported]\n- [Dependency category status and material gaps]\n\n{Follow the instructions and output format\u002Fconditions in [Limitations and Improvements](..\u002Findex\u002FSKILL.md#limitations-and-improvements)}\n\n{Follow the instructions and output format\u002Fconditions in [Next Steps](..\u002Findex\u002FSKILL.md#4-next-steps)}\n","md",[844],{"type":42,"tag":123,"props":845,"children":846},{"__ignoreMap":723},[847,875,885,899,909,917,930,939,947,960,969,977,990,1008,1039,1065,1091,1117,1143,1169,1177,1190,1199,1207,1220,1246,1272,1307,1315,1328,1341,1349,1362,1375,1388,1396,1436,1444],{"type":42,"tag":446,"props":848,"children":851},{"class":849,"line":850},"line",1,[852,858,864,869],{"type":42,"tag":446,"props":853,"children":855},{"style":854},"--shiki-light:#39ADB5;--shiki-default:#89DDFF;--shiki-dark:#89DDFF",[856],{"type":47,"value":857},"# [",{"type":42,"tag":446,"props":859,"children":861},{"style":860},"--shiki-light:#91B859;--shiki-default:#C3E88D;--shiki-dark:#C3E88D",[862],{"type":47,"value":863},"Seller",{"type":42,"tag":446,"props":865,"children":866},{"style":854},[867],{"type":47,"value":868},"]",{"type":42,"tag":446,"props":870,"children":872},{"style":871},"--shiki-light:#E2931D;--shiki-default:#FFCB6B;--shiki-dark:#FFCB6B",[873],{"type":47,"value":874}," Competitive Brief\n",{"type":42,"tag":446,"props":876,"children":878},{"class":849,"line":877},2,[879],{"type":42,"tag":446,"props":880,"children":882},{"emptyLinePlaceholder":881},true,[883],{"type":47,"value":884},"\n",{"type":42,"tag":446,"props":886,"children":888},{"class":849,"line":887},3,[889,894],{"type":42,"tag":446,"props":890,"children":891},{"style":854},[892],{"type":47,"value":893},"## ",{"type":42,"tag":446,"props":895,"children":896},{"style":871},[897],{"type":47,"value":898},"Context\n",{"type":42,"tag":446,"props":900,"children":902},{"class":849,"line":901},4,[903],{"type":42,"tag":446,"props":904,"children":906},{"style":905},"--shiki-light:#90A4AE;--shiki-default:#EEFFFF;--shiki-dark:#BABED8",[907],{"type":47,"value":908},"[Scope, buyer\u002Faccount context, mode, and evidence posture]\n",{"type":42,"tag":446,"props":910,"children":912},{"class":849,"line":911},5,[913],{"type":42,"tag":446,"props":914,"children":915},{"emptyLinePlaceholder":881},[916],{"type":47,"value":884},{"type":42,"tag":446,"props":918,"children":920},{"class":849,"line":919},6,[921,925],{"type":42,"tag":446,"props":922,"children":923},{"style":854},[924],{"type":47,"value":893},{"type":42,"tag":446,"props":926,"children":927},{"style":871},[928],{"type":47,"value":929},"Seller Baseline\n",{"type":42,"tag":446,"props":931,"children":933},{"class":849,"line":932},7,[934],{"type":42,"tag":446,"props":935,"children":936},{"style":905},[937],{"type":47,"value":938},"[Seller positioning and relevant proof]\n",{"type":42,"tag":446,"props":940,"children":942},{"class":849,"line":941},8,[943],{"type":42,"tag":446,"props":944,"children":945},{"emptyLinePlaceholder":881},[946],{"type":47,"value":884},{"type":42,"tag":446,"props":948,"children":950},{"class":849,"line":949},9,[951,955],{"type":42,"tag":446,"props":952,"children":953},{"style":854},[954],{"type":47,"value":893},{"type":42,"tag":446,"props":956,"children":957},{"style":871},[958],{"type":47,"value":959},"Competitive Landscape Summary\n",{"type":42,"tag":446,"props":961,"children":963},{"class":849,"line":962},10,[964],{"type":42,"tag":446,"props":965,"children":966},{"style":905},[967],{"type":47,"value":968},"[What matters most and why]\n",{"type":42,"tag":446,"props":970,"children":972},{"class":849,"line":971},11,[973],{"type":42,"tag":446,"props":974,"children":975},{"emptyLinePlaceholder":881},[976],{"type":47,"value":884},{"type":42,"tag":446,"props":978,"children":980},{"class":849,"line":979},12,[981,985],{"type":42,"tag":446,"props":982,"children":983},{"style":854},[984],{"type":47,"value":893},{"type":42,"tag":446,"props":986,"children":987},{"style":871},[988],{"type":47,"value":989},"Competitor Snapshot\n",{"type":42,"tag":446,"props":991,"children":993},{"class":849,"line":992},13,[994,999,1003],{"type":42,"tag":446,"props":995,"children":996},{"style":854},[997],{"type":47,"value":998},"### [",{"type":42,"tag":446,"props":1000,"children":1001},{"style":860},[1002],{"type":47,"value":450},{"type":42,"tag":446,"props":1004,"children":1005},{"style":854},[1006],{"type":47,"value":1007},"]\n",{"type":42,"tag":446,"props":1009,"children":1011},{"class":849,"line":1010},14,[1012,1017,1023,1029,1034],{"type":42,"tag":446,"props":1013,"children":1014},{"style":854},[1015],{"type":47,"value":1016},"-",{"type":42,"tag":446,"props":1018,"children":1020},{"style":1019},"--shiki-light:#39ADB5;--shiki-light-font-weight:bold;--shiki-default:#89DDFF;--shiki-default-font-weight:bold;--shiki-dark:#89DDFF;--shiki-dark-font-weight:bold",[1021],{"type":47,"value":1022}," **",{"type":42,"tag":446,"props":1024,"children":1026},{"style":1025},"--shiki-light:#E53935;--shiki-light-font-weight:bold;--shiki-default:#F07178;--shiki-default-font-weight:bold;--shiki-dark:#F07178;--shiki-dark-font-weight:bold",[1027],{"type":47,"value":1028},"What they claim:",{"type":42,"tag":446,"props":1030,"children":1031},{"style":1019},[1032],{"type":47,"value":1033},"**",{"type":42,"tag":446,"props":1035,"children":1036},{"style":905},[1037],{"type":47,"value":1038}," [Grounded claim]\n",{"type":42,"tag":446,"props":1040,"children":1042},{"class":849,"line":1041},15,[1043,1047,1051,1056,1060],{"type":42,"tag":446,"props":1044,"children":1045},{"style":854},[1046],{"type":47,"value":1016},{"type":42,"tag":446,"props":1048,"children":1049},{"style":1019},[1050],{"type":47,"value":1022},{"type":42,"tag":446,"props":1052,"children":1053},{"style":1025},[1054],{"type":47,"value":1055},"What is confirmed:",{"type":42,"tag":446,"props":1057,"children":1058},{"style":1019},[1059],{"type":47,"value":1033},{"type":42,"tag":446,"props":1061,"children":1062},{"style":905},[1063],{"type":47,"value":1064}," [Evidence-backed fact]\n",{"type":42,"tag":446,"props":1066,"children":1068},{"class":849,"line":1067},16,[1069,1073,1077,1082,1086],{"type":42,"tag":446,"props":1070,"children":1071},{"style":854},[1072],{"type":47,"value":1016},{"type":42,"tag":446,"props":1074,"children":1075},{"style":1019},[1076],{"type":47,"value":1022},{"type":42,"tag":446,"props":1078,"children":1079},{"style":1025},[1080],{"type":47,"value":1081},"Why buyers may care:",{"type":42,"tag":446,"props":1083,"children":1084},{"style":1019},[1085],{"type":47,"value":1033},{"type":42,"tag":446,"props":1087,"children":1088},{"style":905},[1089],{"type":47,"value":1090}," [Buyer appeal]\n",{"type":42,"tag":446,"props":1092,"children":1094},{"class":849,"line":1093},17,[1095,1099,1103,1108,1112],{"type":42,"tag":446,"props":1096,"children":1097},{"style":854},[1098],{"type":47,"value":1016},{"type":42,"tag":446,"props":1100,"children":1101},{"style":1019},[1102],{"type":47,"value":1022},{"type":42,"tag":446,"props":1104,"children":1105},{"style":1025},[1106],{"type":47,"value":1107},"Where they win:",{"type":42,"tag":446,"props":1109,"children":1110},{"style":1019},[1111],{"type":47,"value":1033},{"type":42,"tag":446,"props":1113,"children":1114},{"style":905},[1115],{"type":47,"value":1116}," [Supported strength]\n",{"type":42,"tag":446,"props":1118,"children":1120},{"class":849,"line":1119},18,[1121,1125,1129,1134,1138],{"type":42,"tag":446,"props":1122,"children":1123},{"style":854},[1124],{"type":47,"value":1016},{"type":42,"tag":446,"props":1126,"children":1127},{"style":1019},[1128],{"type":47,"value":1022},{"type":42,"tag":446,"props":1130,"children":1131},{"style":1025},[1132],{"type":47,"value":1133},"Where we can separate:",{"type":42,"tag":446,"props":1135,"children":1136},{"style":1019},[1137],{"type":47,"value":1033},{"type":42,"tag":446,"props":1139,"children":1140},{"style":905},[1141],{"type":47,"value":1142}," [Supported response]\n",{"type":42,"tag":446,"props":1144,"children":1146},{"class":849,"line":1145},19,[1147,1151,1155,1160,1164],{"type":42,"tag":446,"props":1148,"children":1149},{"style":854},[1150],{"type":47,"value":1016},{"type":42,"tag":446,"props":1152,"children":1153},{"style":1019},[1154],{"type":47,"value":1022},{"type":42,"tag":446,"props":1156,"children":1157},{"style":1025},[1158],{"type":47,"value":1159},"Landmine \u002F do not say:",{"type":42,"tag":446,"props":1161,"children":1162},{"style":1019},[1163],{"type":47,"value":1033},{"type":42,"tag":446,"props":1165,"children":1166},{"style":905},[1167],{"type":47,"value":1168}," [Overclaim to avoid]\n",{"type":42,"tag":446,"props":1170,"children":1172},{"class":849,"line":1171},20,[1173],{"type":42,"tag":446,"props":1174,"children":1175},{"emptyLinePlaceholder":881},[1176],{"type":47,"value":884},{"type":42,"tag":446,"props":1178,"children":1180},{"class":849,"line":1179},21,[1181,1185],{"type":42,"tag":446,"props":1182,"children":1183},{"style":854},[1184],{"type":47,"value":893},{"type":42,"tag":446,"props":1186,"children":1187},{"style":871},[1188],{"type":47,"value":1189},"Comparison Matrix Takeaways\n",{"type":42,"tag":446,"props":1191,"children":1193},{"class":849,"line":1192},22,[1194],{"type":42,"tag":446,"props":1195,"children":1196},{"style":905},[1197],{"type":47,"value":1198},"[Matrix plus the few implications that change seller behavior]\n",{"type":42,"tag":446,"props":1200,"children":1202},{"class":849,"line":1201},23,[1203],{"type":42,"tag":446,"props":1204,"children":1205},{"emptyLinePlaceholder":881},[1206],{"type":47,"value":884},{"type":42,"tag":446,"props":1208,"children":1210},{"class":849,"line":1209},24,[1211,1215],{"type":42,"tag":446,"props":1212,"children":1213},{"style":854},[1214],{"type":47,"value":893},{"type":42,"tag":446,"props":1216,"children":1217},{"style":871},[1218],{"type":47,"value":1219},"Response Strategy\n",{"type":42,"tag":446,"props":1221,"children":1223},{"class":849,"line":1222},25,[1224,1228,1232,1237,1241],{"type":42,"tag":446,"props":1225,"children":1226},{"style":854},[1227],{"type":47,"value":1016},{"type":42,"tag":446,"props":1229,"children":1230},{"style":1019},[1231],{"type":47,"value":1022},{"type":42,"tag":446,"props":1233,"children":1234},{"style":1025},[1235],{"type":47,"value":1236},"Say:",{"type":42,"tag":446,"props":1238,"children":1239},{"style":1019},[1240],{"type":47,"value":1033},{"type":42,"tag":446,"props":1242,"children":1243},{"style":905},[1244],{"type":47,"value":1245}," [Talk track]\n",{"type":42,"tag":446,"props":1247,"children":1249},{"class":849,"line":1248},26,[1250,1254,1258,1263,1267],{"type":42,"tag":446,"props":1251,"children":1252},{"style":854},[1253],{"type":47,"value":1016},{"type":42,"tag":446,"props":1255,"children":1256},{"style":1019},[1257],{"type":47,"value":1022},{"type":42,"tag":446,"props":1259,"children":1260},{"style":1025},[1261],{"type":47,"value":1262},"Clarify:",{"type":42,"tag":446,"props":1264,"children":1265},{"style":1019},[1266],{"type":47,"value":1033},{"type":42,"tag":446,"props":1268,"children":1269},{"style":905},[1270],{"type":47,"value":1271}," [Discovery question]\n",{"type":42,"tag":446,"props":1273,"children":1275},{"class":849,"line":1274},27,[1276,1280,1284,1289,1293,1298,1303],{"type":42,"tag":446,"props":1277,"children":1278},{"style":854},[1279],{"type":47,"value":1016},{"type":42,"tag":446,"props":1281,"children":1282},{"style":1019},[1283],{"type":47,"value":1022},{"type":42,"tag":446,"props":1285,"children":1286},{"style":1025},[1287],{"type":47,"value":1288},"Prove:",{"type":42,"tag":446,"props":1290,"children":1291},{"style":1019},[1292],{"type":47,"value":1033},{"type":42,"tag":446,"props":1294,"children":1295},{"style":854},[1296],{"type":47,"value":1297}," [",{"type":42,"tag":446,"props":1299,"children":1300},{"style":860},[1301],{"type":47,"value":1302},"Evidence",{"type":42,"tag":446,"props":1304,"children":1305},{"style":854},[1306],{"type":47,"value":1007},{"type":42,"tag":446,"props":1308,"children":1310},{"class":849,"line":1309},28,[1311],{"type":42,"tag":446,"props":1312,"children":1313},{"emptyLinePlaceholder":881},[1314],{"type":47,"value":884},{"type":42,"tag":446,"props":1316,"children":1318},{"class":849,"line":1317},29,[1319,1323],{"type":42,"tag":446,"props":1320,"children":1321},{"style":854},[1322],{"type":47,"value":893},{"type":42,"tag":446,"props":1324,"children":1325},{"style":871},[1326],{"type":47,"value":1327},"What Not To Overclaim\n",{"type":42,"tag":446,"props":1329,"children":1331},{"class":849,"line":1330},30,[1332,1336],{"type":42,"tag":446,"props":1333,"children":1334},{"style":854},[1335],{"type":47,"value":1016},{"type":42,"tag":446,"props":1337,"children":1338},{"style":905},[1339],{"type":47,"value":1340}," [Uncertainty, conflict, or unsupported claim]\n",{"type":42,"tag":446,"props":1342,"children":1344},{"class":849,"line":1343},31,[1345],{"type":42,"tag":446,"props":1346,"children":1347},{"emptyLinePlaceholder":881},[1348],{"type":47,"value":884},{"type":42,"tag":446,"props":1350,"children":1352},{"class":849,"line":1351},32,[1353,1357],{"type":42,"tag":446,"props":1354,"children":1355},{"style":854},[1356],{"type":47,"value":893},{"type":42,"tag":446,"props":1358,"children":1359},{"style":871},[1360],{"type":47,"value":1361},"Sources\n",{"type":42,"tag":446,"props":1363,"children":1365},{"class":849,"line":1364},33,[1366,1370],{"type":42,"tag":446,"props":1367,"children":1368},{"style":854},[1369],{"type":47,"value":1016},{"type":42,"tag":446,"props":1371,"children":1372},{"style":905},[1373],{"type":47,"value":1374}," [Clickable source + what it supported]\n",{"type":42,"tag":446,"props":1376,"children":1378},{"class":849,"line":1377},34,[1379,1383],{"type":42,"tag":446,"props":1380,"children":1381},{"style":854},[1382],{"type":47,"value":1016},{"type":42,"tag":446,"props":1384,"children":1385},{"style":905},[1386],{"type":47,"value":1387}," [Dependency category status and material gaps]\n",{"type":42,"tag":446,"props":1389,"children":1391},{"class":849,"line":1390},35,[1392],{"type":42,"tag":446,"props":1393,"children":1394},{"emptyLinePlaceholder":881},[1395],{"type":47,"value":884},{"type":42,"tag":446,"props":1397,"children":1399},{"class":849,"line":1398},36,[1400,1405,1410,1415,1420,1426,1431],{"type":42,"tag":446,"props":1401,"children":1402},{"style":905},[1403],{"type":47,"value":1404},"{Follow the instructions and output format\u002Fconditions in ",{"type":42,"tag":446,"props":1406,"children":1407},{"style":854},[1408],{"type":47,"value":1409},"[",{"type":42,"tag":446,"props":1411,"children":1412},{"style":860},[1413],{"type":47,"value":1414},"Limitations and Improvements",{"type":42,"tag":446,"props":1416,"children":1417},{"style":854},[1418],{"type":47,"value":1419},"](",{"type":42,"tag":446,"props":1421,"children":1423},{"style":1422},"--shiki-light:#E53935;--shiki-light-text-decoration:underline;--shiki-default:#F07178;--shiki-default-text-decoration:underline;--shiki-dark:#F07178;--shiki-dark-text-decoration:underline",[1424],{"type":47,"value":1425},"..\u002Findex\u002FSKILL.md#limitations-and-improvements",{"type":42,"tag":446,"props":1427,"children":1428},{"style":854},[1429],{"type":47,"value":1430},")",{"type":42,"tag":446,"props":1432,"children":1433},{"style":905},[1434],{"type":47,"value":1435},"}\n",{"type":42,"tag":446,"props":1437,"children":1439},{"class":849,"line":1438},37,[1440],{"type":42,"tag":446,"props":1441,"children":1442},{"emptyLinePlaceholder":881},[1443],{"type":47,"value":884},{"type":42,"tag":446,"props":1445,"children":1447},{"class":849,"line":1446},38,[1448,1452,1456,1461,1465,1470,1474],{"type":42,"tag":446,"props":1449,"children":1450},{"style":905},[1451],{"type":47,"value":1404},{"type":42,"tag":446,"props":1453,"children":1454},{"style":854},[1455],{"type":47,"value":1409},{"type":42,"tag":446,"props":1457,"children":1458},{"style":860},[1459],{"type":47,"value":1460},"Next Steps",{"type":42,"tag":446,"props":1462,"children":1463},{"style":854},[1464],{"type":47,"value":1419},{"type":42,"tag":446,"props":1466,"children":1467},{"style":1422},[1468],{"type":47,"value":1469},"..\u002Findex\u002FSKILL.md#4-next-steps",{"type":42,"tag":446,"props":1471,"children":1472},{"style":854},[1473],{"type":47,"value":1430},{"type":42,"tag":446,"props":1475,"children":1476},{"style":905},[1477],{"type":47,"value":1435},{"type":42,"tag":50,"props":1479,"children":1480},{},[1481],{"type":47,"value":1482},"Add Account Implications for account_overlay, and label unsupported competitor presence as Defensive prep.",{"type":42,"tag":56,"props":1484,"children":1486},{"id":1485},"example-prompts",[1487],{"type":47,"value":1488},"Example Prompts",{"type":42,"tag":79,"props":1490,"children":1491},{},[1492,1501,1510,1519,1528],{"type":42,"tag":83,"props":1493,"children":1494},{},[1495],{"type":42,"tag":123,"props":1496,"children":1498},{"className":1497},[],[1499],{"type":47,"value":1500},"Build a competitive brief for MyCompany vs Competitor Alpha.",{"type":42,"tag":83,"props":1502,"children":1503},{},[1504],{"type":42,"tag":123,"props":1505,"children":1507},{"className":1506},[],[1508],{"type":47,"value":1509},"Create a battlecard for MyCompany against Competitor Alpha and Competitor Beta in financial services.",{"type":42,"tag":83,"props":1511,"children":1512},{},[1513],{"type":42,"tag":123,"props":1514,"children":1516},{"className":1515},[],[1517],{"type":47,"value":1518},"Compare MyCompany's enterprise workflow platform against the top three alternatives for regulated buyers.",{"type":42,"tag":83,"props":1520,"children":1521},{},[1522],{"type":42,"tag":123,"props":1523,"children":1525},{"className":1524},[],[1526],{"type":47,"value":1527},"Build an account-specific defensive prep brief for ExampleCorp where Competitor Alpha may be in the deal.",{"type":42,"tag":83,"props":1529,"children":1530},{},[1531],{"type":42,"tag":123,"props":1532,"children":1534},{"className":1533},[],[1535],{"type":47,"value":1536},"Create a shareable HTML competitive brief for MyCompany vs Competitor Alpha.",{"type":42,"tag":56,"props":1538,"children":1540},{"id":1539},"rules",[1541],{"type":47,"value":1542},"Rules",{"type":42,"tag":79,"props":1544,"children":1545},{},[1546,1551,1556,1561,1566],{"type":42,"tag":83,"props":1547,"children":1548},{},[1549],{"type":47,"value":1550},"Never fabricate competitor capabilities, pricing, customer proof, account posture, or source links.",{"type":42,"tag":83,"props":1552,"children":1553},{},[1554],{"type":47,"value":1555},"Keep facts, field signals, and inference visibly separate.",{"type":42,"tag":83,"props":1557,"children":1558},{},[1559],{"type":47,"value":1560},"If evidence is sparse, narrow the brief and name the smallest evidence gaps that would improve it.",{"type":42,"tag":83,"props":1562,"children":1563},{},[1564],{"type":47,"value":1565},"Do not post, send, share, or update systems from this workflow unless the user later explicitly requests a separate supported action.",{"type":42,"tag":83,"props":1567,"children":1568},{},[1569],{"type":47,"value":1570},"Always cite material source-backed claims with hyperlinks when useful links are available.",{"type":42,"tag":1572,"props":1573,"children":1574},"style",{},[1575],{"type":47,"value":1576},"html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"items":1578,"total":1679},[1579,1594,1610,1623,1639,1655,1672],{"slug":1580,"name":1580,"fn":1581,"description":1582,"org":1583,"tags":1584,"stars":25,"repoUrl":26,"updatedAt":1593},"analyze-account-signals","analyze account signals for sales intelligence","Use when the user wants to know what changed with one account, monitor an owner portfolio or watchlist, or rank accounts needing attention from recent evidence. Produce an evidence-backed account brief or bounded watchlist summary with recommended actions.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1585,1588,1591,1592],{"name":1586,"slug":1587,"type":15},"Analytics","analytics",{"name":1589,"slug":1590,"type":15},"CRM","crm",{"name":13,"slug":14,"type":15},{"name":23,"slug":24,"type":15},"2026-07-01T07:54:11.79288",{"slug":1595,"name":1595,"fn":1596,"description":1597,"org":1598,"tags":1599,"stars":25,"repoUrl":26,"updatedAt":1609},"analyze-data-quality","assess data quality for analysis","Assess whether structured data, query results, dashboards, or analytical evidence are trustworthy enough to use. Use when the task is to check data quality, reconcile conflicting sources or metric definitions, or decide whether evidence is safe to cite.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1600,1603,1606],{"name":1601,"slug":1602,"type":15},"Audit","audit",{"name":1604,"slug":1605,"type":15},"Data Engineering","data-engineering",{"name":1607,"slug":1608,"type":15},"Data Quality","data-quality","2026-07-01T07:55:01.146961",{"slug":1611,"name":1611,"fn":1612,"description":1613,"org":1614,"tags":1615,"stars":25,"repoUrl":26,"updatedAt":1622},"answers-ask-user-input","request missing context from users","Use when a small amount of missing context would materially improve the answer and tappable options plus a free-text answer can gather it efficiently.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1616,1619],{"name":1617,"slug":1618,"type":15},"Communications","communications",{"name":1620,"slug":1621,"type":15},"Productivity","productivity","2026-07-14T05:43:36.096323",{"slug":1624,"name":1624,"fn":1625,"description":1626,"org":1627,"tags":1628,"stars":25,"repoUrl":26,"updatedAt":1638},"apollo","prospect and enrich leads with Apollo","Use only when a focused Sales workflow has selected a present and connected Apollo connector, or the user explicitly asks for Apollo prospecting, enrichment, Company Details, records, sequences, or outbound planning. Apply Apollo v2-specific behavior only after verifying app version 2.0.0 or later.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1629,1631,1634,1637],{"name":1630,"slug":1624,"type":15},"Apollo",{"name":1632,"slug":1633,"type":15},"Lead Enrichment","lead-enrichment",{"name":1635,"slug":1636,"type":15},"Prospecting","prospecting",{"name":23,"slug":24,"type":15},"2026-07-14T05:43:34.800076",{"slug":1602,"name":1602,"fn":1640,"description":1641,"org":1642,"tags":1643,"stars":25,"repoUrl":26,"updatedAt":1654},"audit product flows and user journeys","Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1644,1645,1648,1651],{"name":1601,"slug":1602,"type":15},{"name":1646,"slug":1647,"type":15},"Design","design",{"name":1649,"slug":1650,"type":15},"Product Management","product-management",{"name":1652,"slug":1653,"type":15},"UX Design","ux-design","2026-07-01T07:54:30.613428",{"slug":1656,"name":1656,"fn":1657,"description":1658,"org":1659,"tags":1660,"stars":25,"repoUrl":26,"updatedAt":1671},"build-business-case","build customer-led business cases and ROI","Review commercial proposals and build customer-led business cases, ROI or value models, pricing or investment rationales, executive summaries, and customer-ready value stories tied to a customer, workflow, initiative, or decision.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1661,1664,1667,1670],{"name":1662,"slug":1663,"type":15},"Content Creation","content-creation",{"name":1665,"slug":1666,"type":15},"Finance","finance",{"name":1668,"slug":1669,"type":15},"Financial Modeling","financial-modeling",{"name":23,"slug":24,"type":15},"2026-07-01T07:54:02.779003",{"slug":4,"name":4,"fn":5,"description":6,"org":1673,"tags":1674,"stars":25,"repoUrl":26,"updatedAt":27},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1675,1676,1677,1678],{"name":17,"slug":18,"type":15},{"name":20,"slug":21,"type":15},{"name":13,"slug":14,"type":15},{"name":23,"slug":24,"type":15},43,{"items":1681,"total":1882},[1682,1703,1726,1743,1759,1778,1795,1809,1825,1839,1851,1866],{"slug":1683,"name":1683,"fn":1684,"description":1685,"org":1686,"tags":1687,"stars":1700,"repoUrl":1701,"updatedAt":1702},"prior-auth-packet-builder","build healthcare prior authorization packets","Build a concise prior authorization packet from local case files and payer policy docs.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1688,1691,1694,1697],{"name":1689,"slug":1690,"type":15},"Documents","documents",{"name":1692,"slug":1693,"type":15},"Healthcare","healthcare",{"name":1695,"slug":1696,"type":15},"Insurance","insurance",{"name":1698,"slug":1699,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":1704,"name":1704,"fn":1705,"description":1706,"org":1707,"tags":1708,"stars":1723,"repoUrl":1724,"updatedAt":1725},"aspnet-core","build ASP.NET Core web applications","Build, review, refactor, or architect ASP.NET Core web applications using current official guidance for .NET web development. Use when working on Blazor Web Apps, Razor Pages, MVC, Minimal APIs, controller-based Web APIs, SignalR, gRPC, middleware, dependency injection, configuration, authentication, authorization, testing, performance, deployment, or ASP.NET Core upgrades.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1709,1712,1714,1717,1720],{"name":1710,"slug":1711,"type":15},".NET","dotnet",{"name":1713,"slug":1704,"type":15},"ASP.NET Core",{"name":1715,"slug":1716,"type":15},"Blazor","blazor",{"name":1718,"slug":1719,"type":15},"C#","csharp",{"name":1721,"slug":1722,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":1727,"name":1727,"fn":1728,"description":1729,"org":1730,"tags":1731,"stars":1723,"repoUrl":1724,"updatedAt":1742},"chatgpt-apps","build ChatGPT Apps SDK applications","Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications that combine an MCP server and widget UI. Use when Codex needs to design tools, register UI resources, wire the MCP Apps bridge or ChatGPT compatibility APIs, apply Apps SDK metadata or CSP or domain settings, or produce a docs-aligned project scaffold. Prefer a docs-first workflow by invoking the openai-docs skill or OpenAI developer docs MCP tools before generating code.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1732,1735,1738,1741],{"name":1733,"slug":1734,"type":15},"Apps SDK","apps-sdk",{"name":1736,"slug":1737,"type":15},"ChatGPT","chatgpt",{"name":1739,"slug":1740,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":1744,"name":1744,"fn":1745,"description":1746,"org":1747,"tags":1748,"stars":1723,"repoUrl":1724,"updatedAt":1758},"cli-creator","build CLIs from API docs","Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user wants Codex to create a command-line tool that can run from any repo, expose composable read\u002Fwrite commands, return stable JSON, manage auth, and pair with a companion skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1749,1752,1755],{"name":1750,"slug":1751,"type":15},"API Development","api-development",{"name":1753,"slug":1754,"type":15},"CLI","cli",{"name":1756,"slug":1757,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":1760,"name":1760,"fn":1761,"description":1762,"org":1763,"tags":1764,"stars":1723,"repoUrl":1724,"updatedAt":1777},"cloudflare-deploy","deploy projects to Cloudflare","Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1765,1768,1771,1774],{"name":1766,"slug":1767,"type":15},"Cloudflare","cloudflare",{"name":1769,"slug":1770,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":1772,"slug":1773,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":1775,"slug":1776,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":1779,"name":1779,"fn":1780,"description":1781,"org":1782,"tags":1783,"stars":1723,"repoUrl":1724,"updatedAt":1794},"define-goal","define and set measurable project goals","Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy intention into a quantitative outcome. Use this skill for goal creation and goal refinement only; it does not manage durable snapshots, decision logs, or long-running execution artifacts.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1784,1785,1788,1791],{"name":1620,"slug":1621,"type":15},{"name":1786,"slug":1787,"type":15},"Project Management","project-management",{"name":1789,"slug":1790,"type":15},"Strategy","strategy",{"name":1792,"slug":1793,"type":15},"Task Management","task-management","2026-05-23T06:17:16.870838",{"slug":1796,"name":1796,"fn":1797,"description":1798,"org":1799,"tags":1800,"stars":1723,"repoUrl":1724,"updatedAt":1808},"figma","translate Figma designs into code","Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1801,1802,1804,1807],{"name":1646,"slug":1647,"type":15},{"name":1803,"slug":1796,"type":15},"Figma",{"name":1805,"slug":1806,"type":15},"Frontend","frontend",{"name":1739,"slug":1740,"type":15},"2026-04-12T05:06:47.939943",{"slug":1810,"name":1810,"fn":1811,"description":1812,"org":1813,"tags":1814,"stars":1723,"repoUrl":1724,"updatedAt":1824},"figma-code-connect-components","connect Figma designs to code components","Connects Figma design components to code components using Code Connect mapping tools. Use when user says \"code connect\", \"connect this component to code\", \"map this component\", \"link component to code\", \"create code connect mapping\", or wants to establish mappings between Figma designs and code implementations. For canvas writes via `use_figma`, use `figma-use`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1815,1816,1819,1820,1821],{"name":1646,"slug":1647,"type":15},{"name":1817,"slug":1818,"type":15},"Design System","design-system",{"name":1803,"slug":1796,"type":15},{"name":1805,"slug":1806,"type":15},{"name":1822,"slug":1823,"type":15},"UI Components","ui-components","2026-05-10T05:59:52.971881",{"slug":1826,"name":1826,"fn":1827,"description":1828,"org":1829,"tags":1830,"stars":1723,"repoUrl":1724,"updatedAt":1838},"figma-create-design-system-rules","generate design system rules from Figma","Generates custom design system rules for the user's codebase. Use when user says \"create design system rules\", \"generate rules for my project\", \"set up design rules\", \"customize design system guidelines\", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1831,1832,1833,1836,1837],{"name":1646,"slug":1647,"type":15},{"name":1817,"slug":1818,"type":15},{"name":1834,"slug":1835,"type":15},"Documentation","documentation",{"name":1803,"slug":1796,"type":15},{"name":1805,"slug":1806,"type":15},"2026-05-16T06:07:47.821474",{"slug":1840,"name":1840,"fn":1841,"description":1842,"org":1843,"tags":1844,"stars":1723,"repoUrl":1724,"updatedAt":1850},"figma-implement-design","translate Figma designs into application code","Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions \"implement design\", \"generate code\", \"implement component\", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via `use_figma`, use `figma-use`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1845,1846,1847,1848,1849],{"name":1646,"slug":1647,"type":15},{"name":1803,"slug":1796,"type":15},{"name":1805,"slug":1806,"type":15},{"name":1822,"slug":1823,"type":15},{"name":1721,"slug":1722,"type":15},"2026-05-16T06:07:40.583615",{"slug":1852,"name":1852,"fn":1853,"description":1854,"org":1855,"tags":1856,"stars":1723,"repoUrl":1724,"updatedAt":1865},"hatch-pet","create animated pets for Codex","Create, repair, validate, visually QA, and package Codex-compatible animated pets and pet spritesheets from character art, generated images, company or prospect brand cues, or visual references. Use when a user wants a lightweight-worker Codex pet workflow, a non-pixel custom pet style, a prospect or company mascot pet, or a full 8x9 animated pet atlas with transparent unused cells, QA contact sheets, and pet.json packaging. This skill composes the installed $imagegen system skill for visual generation and uses bundled scripts for deterministic spritesheet assembly.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1857,1860,1861,1864],{"name":1858,"slug":1859,"type":15},"Animation","animation",{"name":1756,"slug":1757,"type":15},{"name":1862,"slug":1863,"type":15},"Creative","creative",{"name":1646,"slug":1647,"type":15},"2026-05-02T05:31:48.48485",{"slug":1867,"name":1867,"fn":1868,"description":1869,"org":1870,"tags":1871,"stars":1723,"repoUrl":1724,"updatedAt":1881},"imagegen","generate and edit raster images","Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG\u002Fvector\u002Fcode-native assets, extending an established icon or logo system, or building the visual directly in HTML\u002FCSS\u002Fcanvas.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1872,1873,1874,1877,1880],{"name":1862,"slug":1863,"type":15},{"name":1646,"slug":1647,"type":15},{"name":1875,"slug":1876,"type":15},"Image Generation","image-generation",{"name":1878,"slug":1879,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675]