[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-meeting-prep":3,"mdc-2vznlc-key":33,"related-org-openai-meeting-prep":941,"related-repo-openai-meeting-prep":1148},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":22,"repoUrl":23,"updatedAt":24,"license":25,"forks":26,"topics":27,"repo":28,"sourceUrl":31,"mdContent":32},"meeting-prep","create public equity meeting prep briefs","Use when creating Public Equity Investing meeting prep briefs. Do not use for private diligence, IB, FP&A, legal, or scheduling-only tasks.",{"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],{"name":13,"slug":14,"type":15},"Research","research","tag",{"name":17,"slug":18,"type":15},"Finance","finance",{"name":20,"slug":21,"type":15},"Equity Research","equity-research",4888,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins","2026-08-28T15:09:16.406482",null,661,[],{"repoUrl":23,"stars":22,"forks":26,"topics":29,"description":30},[],"OpenAI Plugins","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Ftree\u002FHEAD\u002Fplugins\u002Fpublic-equity-investing\u002Fskills\u002Fmeeting-prep","---\nname: meeting-prep\ndescription: Use when creating Public Equity Investing meeting prep briefs. Do not use for private diligence, IB, FP&A, legal, or scheduling-only tasks.\n---\n\n# Meeting Prep\n\n## Skill Configuration\n\n### Common Skill Instructions\n\nMANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `..\u002Fpublic-equity-investing\u002FSKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `..\u002F..\u002Fshared\u002Fplugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `..\u002Fuser-context\u002FSKILL.md`.\n\n### Source Resolution\n\nLoad `..\u002F..\u002Fshared\u002Fworkflow-source-resolution.md`. Resolve only the catalogued source categories needed for the current meeting. Prefer a user-named source first, then one available app, connector, file, export, or pasted input that satisfies the category. Attempt the smallest useful native read only when the workflow needs that source. If a route needs auth, connection, or setup, state the practical limitation and continue from prompt context, active artifacts, pasted or exported material, and public sources when the meeting brief can still be useful. Do not inspect unrelated source categories, run broad source setup, write connector readiness, or create, read, migrate, or update `category-state.json`.\n\nThe runtime source categories below cover the catalogued Public Equity Investing sources. Use `references\u002Fcontext-and-sources.md` for the broader evidence hierarchy, including optional meeting-logistics connectors.\n\n### Workflow Sources\n\nWhen this skill uses a source category, use it for the following information. These are semantic source categories, not fixed connector names.\n\n- `company_filings_ir`: filings, IR materials, and reported financials needed for the meeting baseline.\n- `earnings_transcripts_presentations`: transcripts, presentations, events, and recent management commentary needed for question planning.\n- `internal_research`: internal notes, expert context, and team discussions when they materially improve the meeting plan.\n- `portfolio_models_trackers`: portfolio context, watchlists, models, and thesis trackers only when they materially change the investor stance or follow-up.\n- `market_data_estimates`: market data, consensus, estimates, and ownership only when they materially change the investor stance or questions.\n\n## Relevant Dependency Categories\n\nThese are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.\n\n- `Internal Research`\n- `Company Filings & IR`\n- `Earnings Transcripts & Events`\n- `Portfolio Models & Trackers`\n- `Market Data & Estimates`\n\n## Deliverable Intake\n\nBefore source gathering or analysis for a new substantive hero deliverable, load `..\u002F..\u002Fshared\u002Fdeliverable-intake-policy.md` and use its adaptive `request_user_input` preflight for materially unresolved format, depth, audience\u002Fuse, or focus choices. For a substantive reusable meeting-prep packet or explicit HTML meeting brief, the default resolves the presentation surface to a polished standalone HTML live-meeting brief unless the user requests another surface, a quick\u002Fno-file answer, or a standardized dashboard. In interactive runs, ask only remaining material choices such as depth, audience\u002Fuse, meeting type, or focus; in non-interactive runs, default to the HTML live-meeting brief and `Full working analysis` while disclosing those assumptions outside the artifact. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt.\n\n## Mission\n\nCreate decision-useful Public Equity Investing meeting readiness: what to ask first, what to listen for, how to follow up if the answer is evasive, what not to say, what evidence to request, what decisions to drive, and what follow-ups to send. For a live meeting, the prep sheet is a conversation tool, not a general research report.\n\nDefault prep bundle:\n\n1. meeting objective, investor stance, and compact verified baseline;\n2. conversation flow: opening frame, lead question, pressure-test, and close;\n3. three or four must-ask questions ranked by decision impact, with listen-fors and evasive-answer follow-ups;\n4. compact must-know context, time-permitting questions, and evidence requests;\n5. likely pushbacks, compliance boundaries, and what not to ask or say;\n6. follow-up\u002Faction tracker;\n7. source log and material open gaps.\n\nPreserve existing briefs, decks, memos, spreadsheets, trackers, and notes. Add new outputs, comments, suggested edits, speaker notes, or change logs unless the user explicitly asks to modify the original.\n\nUse chat for quick prep. For a substantive reusable prep packet or explicit HTML meeting brief, produce a polished standalone HTML live-meeting brief following `..\u002F..\u002Fshared\u002Fhtml-artifact-standard.md`; let the meeting type and decision needed determine the hierarchy. Keep background research proportional to its utility in the conversation: do not turn meeting prep into an earnings deep dive, tearsheet, or initiation report merely because HTML space is available.\n\nUse `dashboard-builder` only when the user explicitly asks for a standardized dashboard, reusable dashboard template, or structured payload-driven render. For that optional route, use `references\u002FDASHBOARD_PACK.md`: `meeting-prep` owns the meeting objective, context, question sequencing, evidence requests, pushbacks, and follow-up logic; `dashboard-builder` owns the standardized shell\u002Frendering\u002FQA. Build a `public_equity_investing_dashboard.v1` payload as an internal renderer input, and keep JSON\u002FMarkdown\u002FCSV support files behind the HTML dashboard unless explicitly requested.\n\n## Public Equity Investing Boundary\n\nUse this skill for meetings tied to public securities, listed issuers, equity-risk credit signals, event-driven situations, sector research, PM\u002Frisk reviews, earnings, investor days, conferences, expert calls, and public-equity-investing client or committee discussions. Route credit-instrument, creditworthiness, covenant, recovery, restructuring, and debt-security meetings to Credit Markets.\n\nDo not use this skill as the lead owner for private-markets diligence, investment-banking pitch or process meetings, corporate FP&A or operating-cadence meetings, legal\u002Fregulatory\u002Fcontract meetings, or scheduling-only tasks.\n\nIf the user asks for those non-local workflows, route to the appropriate plugin\u002Ftool when available or state that the workflow is non-local to Public Equity Investing.\n\n## Workflow\n\n1. **Determine mode.** Build from scratch, refresh existing prep, turn analysis into call prep, prepare for a specific meeting, prepare follow-ups, or review\u002Fupgrade an existing prep packet.\n2. **Infer audience and meeting type.** Management\u002FIR, issuer, PM, client, committee, expert, earnings, investor day, credit, risk, portfolio review, model review, catalyst prep, or research kickoff. Load `references\u002Fmeeting-type-playbooks.md` when needed.\n3. **Build context pack.** Start with the prompt and active artifacts. Use runtime apps\u002Fconnectors only when they are actually callable. Do not imply calendar, email, Slack, Drive, market-data, or research connectors are available if they are not.\n4. **Handle sparse context.** With no context, produce starter prep plus data request list. With partial context, label assumptions and prioritize decision-changing gaps. With full context, produce tailored questions, evidence requests, likely responses, and follow-ups. Do not reproduce a long issuer or earnings background unless it changes the meeting plan.\n5. **Compose with local skills.** Use source, tearsheet, memo, style, QC, scenario, audit, model, earnings, event, risk, hedge, thesis, or sector skills when meeting prep depends on their domain. Use Credit Markets as a handoff for credit-first meeting prep.\n6. **Create brief.** State why the meeting matters now, what decision\u002Finformation is needed, what is known\u002Fassumed, the must-ask questions in meeting order, what to listen for, what follow-up to use if an answer remains qualitative or evasive, evidence requests, pushbacks, and action items.\n7. **Prepare follow-ups if post-meeting.** Capture decisions, new facts, changed assumptions, open questions, evidence requests, commitments, owners, dates, dependencies, and draft follow-up language if useful.\n\n## First-Class Meeting Modes\n\nSupport these modes explicitly: `management_ir`, `expert_call`, `pm_internal_review`, `investment_committee`, `client_update`, `sell_side_call`, `earnings_call`, `investor_day`, `portfolio_watchlist_review`, `model_review`, `research_kickoff`, and `post_meeting_follow_up`.\n\nFor every mode, rank questions by decision impact, include what not to ask or say, identify evidence requests, anticipate likely pushbacks, and assign follow-up actions. For a finite live conversation, make three or four questions the must-ask set and place additional questions in an `If Time Permits` block. Tie every must-ask question to an estimate, valuation, thesis, catalyst, sizing, or monitoring consequence. The senior PM layer should press on what would change the view, what evidence is missing, what answer would be evasive, what the market already knows, and what should route to a model, memo, thesis tracker, sizing review, or Credit Markets handoff.\n\n## HTML Guidance\n\nFor a substantive standalone HTML meeting brief, load `..\u002F..\u002Fshared\u002Fhtml-artifact-standard.md` and apply these meeting-specific requirements:\n\n- Make the live conversation plan the primary visual object. Lead with the meeting objective, one-sentence investor stance, core decision or information gap, and a compact disclosed baseline.\n- Place a compact `Conversation Flow` block immediately after the opening stance\u002Fbaseline and before detailed question cards or extended background. It should show the opening frame, lead question, pressure-test, and close\u002Fevidence request at a glance.\n- For `management_ir`, `sell_side_call`, `expert_call`, `earnings_call`, or `investor_day`, display three or four must-ask questions after the conversation flow and before extended background. For each, show `Why it matters`, `Listen for`, `If evasive`, and `Model \u002F thesis implication` or the closest decision consequence.\n- Keep each must-ask subfield concise enough for live use: generally one short sentence, and no more than two short sentences where material nuance would otherwise be lost.\n- Put secondary questions in a compact `If Time Permits` block. Do not render a long list of equally weighted question cards.\n- Keep the disclosed baseline short: usually four or five facts or metrics that make the questions intelligible. Detailed historical tables, scenario work, and extended industry context belong only when they change a live question or follow-up.\n- Include a usable conversation-flow block before detailed questions: opening frame, first question, productive follow-up if management remains qualitative, and closing evidence request or next public disclosure to monitor.\n- Keep the compliance boundary visible for external meetings: public-disclosure-only posture, prohibited asks, and clean ways to restate questions without seeking material nonpublic information.\n- Give the headline, stance box, baseline, and question plan distinct jobs. Do not repeat the same conclusion across several visible panels.\n- Keep citations traceable but readable: do not fragment company names, product names, periods, dates, numeric ranges, or metric labels into separately linked tokens.\n- Visually inspect local HTML via local headless-browser screenshots, not the in-app Browser plugin, and iterate on hierarchy, density, clipping, citation rendering, and whether the must-ask questions are quickly usable in a live meeting.\n\n## When To Invoke Support\n\nLoad `shared\u002Fsupport-layer-routing-contract.md` when support services are needed. Use `financial-source-of-truth` for verified facts, claims, citations, and source gaps; use `company-tearsheet`, `financials-normalizer`, or `excel-data-cleaner` for issuer\u002Ftable prep; use `deck-report-qc` for pre-read\u002Fcirculation review; use `style-guide-adapter` only after substantive prep is locked. Support artifacts stay secondary to the live-meeting brief or optional standardized dashboard.\n\n## Sub-agent decomposition\n\nFor complex medium\u002Flarge requests, use sub-agents where available; otherwise emulate the split as named workstreams. Suggested lanes: source pack, company and market context, key questions, risk flags, and follow-up tracker. Keep this skill as the lead: reconcile conflicts, source labels, assumptions, open items, final QA, and the user-facing answer.\n\n\n## Quality Bar\n\nThe objective is explicit, the brief is usable during the meeting, facts and assumptions are separated, material source gaps are visible, must-ask questions are sequenced by decision impact, evasive-answer follow-ups and decision consequences are clear, evidence requests are specific, likely objections are covered, action items have owner\u002Ftiming where available, and no source artifact is modified or deleted without permission.\n\n## Reference Map\n\n- `references\u002Fcontext-and-sources.md`: source hierarchy and optional connector behavior. Treat connectors as optional runtime inputs.\n- `references\u002Fmeeting-type-playbooks.md`: persona and meeting-type modules.\n- `references\u002Fquestion-and-evidence-bank.md`: question and evidence-request patterns.\n- `references\u002Ffollow-up-and-action-tracking.md`: debrief and tracker fields.\n- `references\u002Foutput-templates.md`: standard brief formats.\n- `references\u002Fsafety-and-integrations.md`: non-destructive editing and circulation rules.\n",{"data":34,"body":35},{"name":4,"description":6},{"type":36,"children":37},"root",[38,46,53,60,91,97,117,130,136,141,201,207,212,260,266,295,301,306,311,350,355,368,411,417,422,427,432,438,520,526,617,630,636,648,782,788,846,852,857,863,868,874],{"type":39,"tag":40,"props":41,"children":42},"element","h1",{"id":4},[43],{"type":44,"value":45},"text","Meeting Prep",{"type":39,"tag":47,"props":48,"children":50},"h2",{"id":49},"skill-configuration",[51],{"type":44,"value":52},"Skill Configuration",{"type":39,"tag":54,"props":55,"children":57},"h3",{"id":56},"common-skill-instructions",[58],{"type":44,"value":59},"Common Skill Instructions",{"type":39,"tag":61,"props":62,"children":63},"p",{},[64,66,73,75,81,83,89],{"type":44,"value":65},"MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in ",{"type":39,"tag":67,"props":68,"children":70},"code",{"className":69},[],[71],{"type":44,"value":72},"..\u002Fpublic-equity-investing\u002FSKILL.md## Cross-Skill Runtime Contract",{"type":44,"value":74},". Then check the router skill map and ",{"type":39,"tag":67,"props":76,"children":78},{"className":77},[],[79],{"type":44,"value":80},"..\u002F..\u002Fshared\u002Fplugin-routing-playbook.md",{"type":44,"value":82}," for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to ",{"type":39,"tag":67,"props":84,"children":86},{"className":85},[],[87],{"type":44,"value":88},"..\u002Fuser-context\u002FSKILL.md",{"type":44,"value":90},".",{"type":39,"tag":54,"props":92,"children":94},{"id":93},"source-resolution",[95],{"type":44,"value":96},"Source Resolution",{"type":39,"tag":61,"props":98,"children":99},{},[100,102,108,110,116],{"type":44,"value":101},"Load ",{"type":39,"tag":67,"props":103,"children":105},{"className":104},[],[106],{"type":44,"value":107},"..\u002F..\u002Fshared\u002Fworkflow-source-resolution.md",{"type":44,"value":109},". Resolve only the catalogued source categories needed for the current meeting. Prefer a user-named source first, then one available app, connector, file, export, or pasted input that satisfies the category. Attempt the smallest useful native read only when the workflow needs that source. If a route needs auth, connection, or setup, state the practical limitation and continue from prompt context, active artifacts, pasted or exported material, and public sources when the meeting brief can still be useful. Do not inspect unrelated source categories, run broad source setup, write connector readiness, or create, read, migrate, or update ",{"type":39,"tag":67,"props":111,"children":113},{"className":112},[],[114],{"type":44,"value":115},"category-state.json",{"type":44,"value":90},{"type":39,"tag":61,"props":118,"children":119},{},[120,122,128],{"type":44,"value":121},"The runtime source categories below cover the catalogued Public Equity Investing sources. Use ",{"type":39,"tag":67,"props":123,"children":125},{"className":124},[],[126],{"type":44,"value":127},"references\u002Fcontext-and-sources.md",{"type":44,"value":129}," for the broader evidence hierarchy, including optional meeting-logistics connectors.",{"type":39,"tag":54,"props":131,"children":133},{"id":132},"workflow-sources",[134],{"type":44,"value":135},"Workflow Sources",{"type":39,"tag":61,"props":137,"children":138},{},[139],{"type":44,"value":140},"When this skill uses a source category, use it for the following information. These are semantic source categories, not fixed connector names.",{"type":39,"tag":142,"props":143,"children":144},"ul",{},[145,157,168,179,190],{"type":39,"tag":146,"props":147,"children":148},"li",{},[149,155],{"type":39,"tag":67,"props":150,"children":152},{"className":151},[],[153],{"type":44,"value":154},"company_filings_ir",{"type":44,"value":156},": filings, IR materials, and reported financials needed for the meeting baseline.",{"type":39,"tag":146,"props":158,"children":159},{},[160,166],{"type":39,"tag":67,"props":161,"children":163},{"className":162},[],[164],{"type":44,"value":165},"earnings_transcripts_presentations",{"type":44,"value":167},": transcripts, presentations, events, and recent management commentary needed for question planning.",{"type":39,"tag":146,"props":169,"children":170},{},[171,177],{"type":39,"tag":67,"props":172,"children":174},{"className":173},[],[175],{"type":44,"value":176},"internal_research",{"type":44,"value":178},": internal notes, expert context, and team discussions when they materially improve the meeting plan.",{"type":39,"tag":146,"props":180,"children":181},{},[182,188],{"type":39,"tag":67,"props":183,"children":185},{"className":184},[],[186],{"type":44,"value":187},"portfolio_models_trackers",{"type":44,"value":189},": portfolio context, watchlists, models, and thesis trackers only when they materially change the investor stance or follow-up.",{"type":39,"tag":146,"props":191,"children":192},{},[193,199],{"type":39,"tag":67,"props":194,"children":196},{"className":195},[],[197],{"type":44,"value":198},"market_data_estimates",{"type":44,"value":200},": market data, consensus, estimates, and ownership only when they materially change the investor stance or questions.",{"type":39,"tag":47,"props":202,"children":204},{"id":203},"relevant-dependency-categories",[205],{"type":44,"value":206},"Relevant Dependency Categories",{"type":39,"tag":61,"props":208,"children":209},{},[210],{"type":44,"value":211},"These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.",{"type":39,"tag":142,"props":213,"children":214},{},[215,224,233,242,251],{"type":39,"tag":146,"props":216,"children":217},{},[218],{"type":39,"tag":67,"props":219,"children":221},{"className":220},[],[222],{"type":44,"value":223},"Internal Research",{"type":39,"tag":146,"props":225,"children":226},{},[227],{"type":39,"tag":67,"props":228,"children":230},{"className":229},[],[231],{"type":44,"value":232},"Company Filings & IR",{"type":39,"tag":146,"props":234,"children":235},{},[236],{"type":39,"tag":67,"props":237,"children":239},{"className":238},[],[240],{"type":44,"value":241},"Earnings Transcripts & Events",{"type":39,"tag":146,"props":243,"children":244},{},[245],{"type":39,"tag":67,"props":246,"children":248},{"className":247},[],[249],{"type":44,"value":250},"Portfolio Models & Trackers",{"type":39,"tag":146,"props":252,"children":253},{},[254],{"type":39,"tag":67,"props":255,"children":257},{"className":256},[],[258],{"type":44,"value":259},"Market Data & Estimates",{"type":39,"tag":47,"props":261,"children":263},{"id":262},"deliverable-intake",[264],{"type":44,"value":265},"Deliverable Intake",{"type":39,"tag":61,"props":267,"children":268},{},[269,271,277,279,285,287,293],{"type":44,"value":270},"Before source gathering or analysis for a new substantive hero deliverable, load ",{"type":39,"tag":67,"props":272,"children":274},{"className":273},[],[275],{"type":44,"value":276},"..\u002F..\u002Fshared\u002Fdeliverable-intake-policy.md",{"type":44,"value":278}," and use its adaptive ",{"type":39,"tag":67,"props":280,"children":282},{"className":281},[],[283],{"type":44,"value":284},"request_user_input",{"type":44,"value":286}," preflight for materially unresolved format, depth, audience\u002Fuse, or focus choices. For a substantive reusable meeting-prep packet or explicit HTML meeting brief, the default resolves the presentation surface to a polished standalone HTML live-meeting brief unless the user requests another surface, a quick\u002Fno-file answer, or a standardized dashboard. In interactive runs, ask only remaining material choices such as depth, audience\u002Fuse, meeting type, or focus; in non-interactive runs, default to the HTML live-meeting brief and ",{"type":39,"tag":67,"props":288,"children":290},{"className":289},[],[291],{"type":44,"value":292},"Full working analysis",{"type":44,"value":294}," while disclosing those assumptions outside the artifact. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt.",{"type":39,"tag":47,"props":296,"children":298},{"id":297},"mission",[299],{"type":44,"value":300},"Mission",{"type":39,"tag":61,"props":302,"children":303},{},[304],{"type":44,"value":305},"Create decision-useful Public Equity Investing meeting readiness: what to ask first, what to listen for, how to follow up if the answer is evasive, what not to say, what evidence to request, what decisions to drive, and what follow-ups to send. For a live meeting, the prep sheet is a conversation tool, not a general research report.",{"type":39,"tag":61,"props":307,"children":308},{},[309],{"type":44,"value":310},"Default prep bundle:",{"type":39,"tag":312,"props":313,"children":314},"ol",{},[315,320,325,330,335,340,345],{"type":39,"tag":146,"props":316,"children":317},{},[318],{"type":44,"value":319},"meeting objective, investor stance, and compact verified baseline;",{"type":39,"tag":146,"props":321,"children":322},{},[323],{"type":44,"value":324},"conversation flow: opening frame, lead question, pressure-test, and close;",{"type":39,"tag":146,"props":326,"children":327},{},[328],{"type":44,"value":329},"three or four must-ask questions ranked by decision impact, with listen-fors and evasive-answer follow-ups;",{"type":39,"tag":146,"props":331,"children":332},{},[333],{"type":44,"value":334},"compact must-know context, time-permitting questions, and evidence requests;",{"type":39,"tag":146,"props":336,"children":337},{},[338],{"type":44,"value":339},"likely pushbacks, compliance boundaries, and what not to ask or say;",{"type":39,"tag":146,"props":341,"children":342},{},[343],{"type":44,"value":344},"follow-up\u002Faction tracker;",{"type":39,"tag":146,"props":346,"children":347},{},[348],{"type":44,"value":349},"source log and material open gaps.",{"type":39,"tag":61,"props":351,"children":352},{},[353],{"type":44,"value":354},"Preserve existing briefs, decks, memos, spreadsheets, trackers, and notes. Add new outputs, comments, suggested edits, speaker notes, or change logs unless the user explicitly asks to modify the original.",{"type":39,"tag":61,"props":356,"children":357},{},[358,360,366],{"type":44,"value":359},"Use chat for quick prep. For a substantive reusable prep packet or explicit HTML meeting brief, produce a polished standalone HTML live-meeting brief following ",{"type":39,"tag":67,"props":361,"children":363},{"className":362},[],[364],{"type":44,"value":365},"..\u002F..\u002Fshared\u002Fhtml-artifact-standard.md",{"type":44,"value":367},"; let the meeting type and decision needed determine the hierarchy. Keep background research proportional to its utility in the conversation: do not turn meeting prep into an earnings deep dive, tearsheet, or initiation report merely because HTML space is available.",{"type":39,"tag":61,"props":369,"children":370},{},[371,373,379,381,387,389,394,396,401,403,409],{"type":44,"value":372},"Use ",{"type":39,"tag":67,"props":374,"children":376},{"className":375},[],[377],{"type":44,"value":378},"dashboard-builder",{"type":44,"value":380}," only when the user explicitly asks for a standardized dashboard, reusable dashboard template, or structured payload-driven render. For that optional route, use ",{"type":39,"tag":67,"props":382,"children":384},{"className":383},[],[385],{"type":44,"value":386},"references\u002FDASHBOARD_PACK.md",{"type":44,"value":388},": ",{"type":39,"tag":67,"props":390,"children":392},{"className":391},[],[393],{"type":44,"value":4},{"type":44,"value":395}," owns the meeting objective, context, question sequencing, evidence requests, pushbacks, and follow-up logic; ",{"type":39,"tag":67,"props":397,"children":399},{"className":398},[],[400],{"type":44,"value":378},{"type":44,"value":402}," owns the standardized shell\u002Frendering\u002FQA. Build a ",{"type":39,"tag":67,"props":404,"children":406},{"className":405},[],[407],{"type":44,"value":408},"public_equity_investing_dashboard.v1",{"type":44,"value":410}," payload as an internal renderer input, and keep JSON\u002FMarkdown\u002FCSV support files behind the HTML dashboard unless explicitly requested.",{"type":39,"tag":47,"props":412,"children":414},{"id":413},"public-equity-investing-boundary",[415],{"type":44,"value":416},"Public Equity Investing Boundary",{"type":39,"tag":61,"props":418,"children":419},{},[420],{"type":44,"value":421},"Use this skill for meetings tied to public securities, listed issuers, equity-risk credit signals, event-driven situations, sector research, PM\u002Frisk reviews, earnings, investor days, conferences, expert calls, and public-equity-investing client or committee discussions. Route credit-instrument, creditworthiness, covenant, recovery, restructuring, and debt-security meetings to Credit Markets.",{"type":39,"tag":61,"props":423,"children":424},{},[425],{"type":44,"value":426},"Do not use this skill as the lead owner for private-markets diligence, investment-banking pitch or process meetings, corporate FP&A or operating-cadence meetings, legal\u002Fregulatory\u002Fcontract meetings, or scheduling-only tasks.",{"type":39,"tag":61,"props":428,"children":429},{},[430],{"type":44,"value":431},"If the user asks for those non-local workflows, route to the appropriate plugin\u002Ftool when available or state that the workflow is non-local to Public Equity Investing.",{"type":39,"tag":47,"props":433,"children":435},{"id":434},"workflow",[436],{"type":44,"value":437},"Workflow",{"type":39,"tag":312,"props":439,"children":440},{},[441,452,470,480,490,500,510],{"type":39,"tag":146,"props":442,"children":443},{},[444,450],{"type":39,"tag":445,"props":446,"children":447},"strong",{},[448],{"type":44,"value":449},"Determine mode.",{"type":44,"value":451}," Build from scratch, refresh existing prep, turn analysis into call prep, prepare for a specific meeting, prepare follow-ups, or review\u002Fupgrade an existing prep packet.",{"type":39,"tag":146,"props":453,"children":454},{},[455,460,462,468],{"type":39,"tag":445,"props":456,"children":457},{},[458],{"type":44,"value":459},"Infer audience and meeting type.",{"type":44,"value":461}," Management\u002FIR, issuer, PM, client, committee, expert, earnings, investor day, credit, risk, portfolio review, model review, catalyst prep, or research kickoff. Load ",{"type":39,"tag":67,"props":463,"children":465},{"className":464},[],[466],{"type":44,"value":467},"references\u002Fmeeting-type-playbooks.md",{"type":44,"value":469}," when needed.",{"type":39,"tag":146,"props":471,"children":472},{},[473,478],{"type":39,"tag":445,"props":474,"children":475},{},[476],{"type":44,"value":477},"Build context pack.",{"type":44,"value":479}," Start with the prompt and active artifacts. Use runtime apps\u002Fconnectors only when they are actually callable. Do not imply calendar, email, Slack, Drive, market-data, or research connectors are available if they are not.",{"type":39,"tag":146,"props":481,"children":482},{},[483,488],{"type":39,"tag":445,"props":484,"children":485},{},[486],{"type":44,"value":487},"Handle sparse context.",{"type":44,"value":489}," With no context, produce starter prep plus data request list. With partial context, label assumptions and prioritize decision-changing gaps. With full context, produce tailored questions, evidence requests, likely responses, and follow-ups. Do not reproduce a long issuer or earnings background unless it changes the meeting plan.",{"type":39,"tag":146,"props":491,"children":492},{},[493,498],{"type":39,"tag":445,"props":494,"children":495},{},[496],{"type":44,"value":497},"Compose with local skills.",{"type":44,"value":499}," Use source, tearsheet, memo, style, QC, scenario, audit, model, earnings, event, risk, hedge, thesis, or sector skills when meeting prep depends on their domain. Use Credit Markets as a handoff for credit-first meeting prep.",{"type":39,"tag":146,"props":501,"children":502},{},[503,508],{"type":39,"tag":445,"props":504,"children":505},{},[506],{"type":44,"value":507},"Create brief.",{"type":44,"value":509}," State why the meeting matters now, what decision\u002Finformation is needed, what is known\u002Fassumed, the must-ask questions in meeting order, what to listen for, what follow-up to use if an answer remains qualitative or evasive, evidence requests, pushbacks, and action items.",{"type":39,"tag":146,"props":511,"children":512},{},[513,518],{"type":39,"tag":445,"props":514,"children":515},{},[516],{"type":44,"value":517},"Prepare follow-ups if post-meeting.",{"type":44,"value":519}," Capture decisions, new facts, changed assumptions, open questions, evidence requests, commitments, owners, dates, dependencies, and draft follow-up language if useful.",{"type":39,"tag":47,"props":521,"children":523},{"id":522},"first-class-meeting-modes",[524],{"type":44,"value":525},"First-Class Meeting Modes",{"type":39,"tag":61,"props":527,"children":528},{},[529,531,537,539,545,546,552,553,559,560,566,567,573,574,580,581,587,588,594,595,601,602,608,610,616],{"type":44,"value":530},"Support these modes explicitly: ",{"type":39,"tag":67,"props":532,"children":534},{"className":533},[],[535],{"type":44,"value":536},"management_ir",{"type":44,"value":538},", ",{"type":39,"tag":67,"props":540,"children":542},{"className":541},[],[543],{"type":44,"value":544},"expert_call",{"type":44,"value":538},{"type":39,"tag":67,"props":547,"children":549},{"className":548},[],[550],{"type":44,"value":551},"pm_internal_review",{"type":44,"value":538},{"type":39,"tag":67,"props":554,"children":556},{"className":555},[],[557],{"type":44,"value":558},"investment_committee",{"type":44,"value":538},{"type":39,"tag":67,"props":561,"children":563},{"className":562},[],[564],{"type":44,"value":565},"client_update",{"type":44,"value":538},{"type":39,"tag":67,"props":568,"children":570},{"className":569},[],[571],{"type":44,"value":572},"sell_side_call",{"type":44,"value":538},{"type":39,"tag":67,"props":575,"children":577},{"className":576},[],[578],{"type":44,"value":579},"earnings_call",{"type":44,"value":538},{"type":39,"tag":67,"props":582,"children":584},{"className":583},[],[585],{"type":44,"value":586},"investor_day",{"type":44,"value":538},{"type":39,"tag":67,"props":589,"children":591},{"className":590},[],[592],{"type":44,"value":593},"portfolio_watchlist_review",{"type":44,"value":538},{"type":39,"tag":67,"props":596,"children":598},{"className":597},[],[599],{"type":44,"value":600},"model_review",{"type":44,"value":538},{"type":39,"tag":67,"props":603,"children":605},{"className":604},[],[606],{"type":44,"value":607},"research_kickoff",{"type":44,"value":609},", and ",{"type":39,"tag":67,"props":611,"children":613},{"className":612},[],[614],{"type":44,"value":615},"post_meeting_follow_up",{"type":44,"value":90},{"type":39,"tag":61,"props":618,"children":619},{},[620,622,628],{"type":44,"value":621},"For every mode, rank questions by decision impact, include what not to ask or say, identify evidence requests, anticipate likely pushbacks, and assign follow-up actions. For a finite live conversation, make three or four questions the must-ask set and place additional questions in an ",{"type":39,"tag":67,"props":623,"children":625},{"className":624},[],[626],{"type":44,"value":627},"If Time Permits",{"type":44,"value":629}," block. Tie every must-ask question to an estimate, valuation, thesis, catalyst, sizing, or monitoring consequence. The senior PM layer should press on what would change the view, what evidence is missing, what answer would be evasive, what the market already knows, and what should route to a model, memo, thesis tracker, sizing review, or Credit Markets handoff.",{"type":39,"tag":47,"props":631,"children":633},{"id":632},"html-guidance",[634],{"type":44,"value":635},"HTML Guidance",{"type":39,"tag":61,"props":637,"children":638},{},[639,641,646],{"type":44,"value":640},"For a substantive standalone HTML meeting brief, load ",{"type":39,"tag":67,"props":642,"children":644},{"className":643},[],[645],{"type":44,"value":365},{"type":44,"value":647}," and apply these meeting-specific requirements:",{"type":39,"tag":142,"props":649,"children":650},{},[651,656,669,735,740,752,757,762,767,772,777],{"type":39,"tag":146,"props":652,"children":653},{},[654],{"type":44,"value":655},"Make the live conversation plan the primary visual object. Lead with the meeting objective, one-sentence investor stance, core decision or information gap, and a compact disclosed baseline.",{"type":39,"tag":146,"props":657,"children":658},{},[659,661,667],{"type":44,"value":660},"Place a compact ",{"type":39,"tag":67,"props":662,"children":664},{"className":663},[],[665],{"type":44,"value":666},"Conversation Flow",{"type":44,"value":668}," block immediately after the opening stance\u002Fbaseline and before detailed question cards or extended background. It should show the opening frame, lead question, pressure-test, and close\u002Fevidence request at a glance.",{"type":39,"tag":146,"props":670,"children":671},{},[672,674,679,680,685,686,691,692,697,699,704,706,712,713,719,720,726,727,733],{"type":44,"value":673},"For ",{"type":39,"tag":67,"props":675,"children":677},{"className":676},[],[678],{"type":44,"value":536},{"type":44,"value":538},{"type":39,"tag":67,"props":681,"children":683},{"className":682},[],[684],{"type":44,"value":572},{"type":44,"value":538},{"type":39,"tag":67,"props":687,"children":689},{"className":688},[],[690],{"type":44,"value":544},{"type":44,"value":538},{"type":39,"tag":67,"props":693,"children":695},{"className":694},[],[696],{"type":44,"value":579},{"type":44,"value":698},", or ",{"type":39,"tag":67,"props":700,"children":702},{"className":701},[],[703],{"type":44,"value":586},{"type":44,"value":705},", display three or four must-ask questions after the conversation flow and before extended background. For each, show ",{"type":39,"tag":67,"props":707,"children":709},{"className":708},[],[710],{"type":44,"value":711},"Why it matters",{"type":44,"value":538},{"type":39,"tag":67,"props":714,"children":716},{"className":715},[],[717],{"type":44,"value":718},"Listen for",{"type":44,"value":538},{"type":39,"tag":67,"props":721,"children":723},{"className":722},[],[724],{"type":44,"value":725},"If evasive",{"type":44,"value":609},{"type":39,"tag":67,"props":728,"children":730},{"className":729},[],[731],{"type":44,"value":732},"Model \u002F thesis implication",{"type":44,"value":734}," or the closest decision consequence.",{"type":39,"tag":146,"props":736,"children":737},{},[738],{"type":44,"value":739},"Keep each must-ask subfield concise enough for live use: generally one short sentence, and no more than two short sentences where material nuance would otherwise be lost.",{"type":39,"tag":146,"props":741,"children":742},{},[743,745,750],{"type":44,"value":744},"Put secondary questions in a compact ",{"type":39,"tag":67,"props":746,"children":748},{"className":747},[],[749],{"type":44,"value":627},{"type":44,"value":751}," block. Do not render a long list of equally weighted question cards.",{"type":39,"tag":146,"props":753,"children":754},{},[755],{"type":44,"value":756},"Keep the disclosed baseline short: usually four or five facts or metrics that make the questions intelligible. Detailed historical tables, scenario work, and extended industry context belong only when they change a live question or follow-up.",{"type":39,"tag":146,"props":758,"children":759},{},[760],{"type":44,"value":761},"Include a usable conversation-flow block before detailed questions: opening frame, first question, productive follow-up if management remains qualitative, and closing evidence request or next public disclosure to monitor.",{"type":39,"tag":146,"props":763,"children":764},{},[765],{"type":44,"value":766},"Keep the compliance boundary visible for external meetings: public-disclosure-only posture, prohibited asks, and clean ways to restate questions without seeking material nonpublic information.",{"type":39,"tag":146,"props":768,"children":769},{},[770],{"type":44,"value":771},"Give the headline, stance box, baseline, and question plan distinct jobs. Do not repeat the same conclusion across several visible panels.",{"type":39,"tag":146,"props":773,"children":774},{},[775],{"type":44,"value":776},"Keep citations traceable but readable: do not fragment company names, product names, periods, dates, numeric ranges, or metric labels into separately linked tokens.",{"type":39,"tag":146,"props":778,"children":779},{},[780],{"type":44,"value":781},"Visually inspect local HTML via local headless-browser screenshots, not the in-app Browser plugin, and iterate on hierarchy, density, clipping, citation rendering, and whether the must-ask questions are quickly usable in a live meeting.",{"type":39,"tag":47,"props":783,"children":785},{"id":784},"when-to-invoke-support",[786],{"type":44,"value":787},"When To Invoke Support",{"type":39,"tag":61,"props":789,"children":790},{},[791,792,798,800,806,808,814,815,821,822,828,830,836,838,844],{"type":44,"value":101},{"type":39,"tag":67,"props":793,"children":795},{"className":794},[],[796],{"type":44,"value":797},"shared\u002Fsupport-layer-routing-contract.md",{"type":44,"value":799}," when support services are needed. Use ",{"type":39,"tag":67,"props":801,"children":803},{"className":802},[],[804],{"type":44,"value":805},"financial-source-of-truth",{"type":44,"value":807}," for verified facts, claims, citations, and source gaps; use ",{"type":39,"tag":67,"props":809,"children":811},{"className":810},[],[812],{"type":44,"value":813},"company-tearsheet",{"type":44,"value":538},{"type":39,"tag":67,"props":816,"children":818},{"className":817},[],[819],{"type":44,"value":820},"financials-normalizer",{"type":44,"value":698},{"type":39,"tag":67,"props":823,"children":825},{"className":824},[],[826],{"type":44,"value":827},"excel-data-cleaner",{"type":44,"value":829}," for issuer\u002Ftable prep; use ",{"type":39,"tag":67,"props":831,"children":833},{"className":832},[],[834],{"type":44,"value":835},"deck-report-qc",{"type":44,"value":837}," for pre-read\u002Fcirculation review; use ",{"type":39,"tag":67,"props":839,"children":841},{"className":840},[],[842],{"type":44,"value":843},"style-guide-adapter",{"type":44,"value":845}," only after substantive prep is locked. Support artifacts stay secondary to the live-meeting brief or optional standardized dashboard.",{"type":39,"tag":47,"props":847,"children":849},{"id":848},"sub-agent-decomposition",[850],{"type":44,"value":851},"Sub-agent decomposition",{"type":39,"tag":61,"props":853,"children":854},{},[855],{"type":44,"value":856},"For complex medium\u002Flarge requests, use sub-agents where available; otherwise emulate the split as named workstreams. Suggested lanes: source pack, company and market context, key questions, risk flags, and follow-up tracker. Keep this skill as the lead: reconcile conflicts, source labels, assumptions, open items, final QA, and the user-facing answer.",{"type":39,"tag":47,"props":858,"children":860},{"id":859},"quality-bar",[861],{"type":44,"value":862},"Quality Bar",{"type":39,"tag":61,"props":864,"children":865},{},[866],{"type":44,"value":867},"The objective is explicit, the brief is usable during the meeting, facts and assumptions are separated, material source gaps are visible, must-ask questions are sequenced by decision impact, evasive-answer follow-ups and decision consequences are clear, evidence requests are specific, likely objections are covered, action items have owner\u002Ftiming where available, and no source artifact is modified or deleted without permission.",{"type":39,"tag":47,"props":869,"children":871},{"id":870},"reference-map",[872],{"type":44,"value":873},"Reference Map",{"type":39,"tag":142,"props":875,"children":876},{},[877,887,897,908,919,930],{"type":39,"tag":146,"props":878,"children":879},{},[880,885],{"type":39,"tag":67,"props":881,"children":883},{"className":882},[],[884],{"type":44,"value":127},{"type":44,"value":886},": source hierarchy and optional connector behavior. Treat connectors as optional runtime inputs.",{"type":39,"tag":146,"props":888,"children":889},{},[890,895],{"type":39,"tag":67,"props":891,"children":893},{"className":892},[],[894],{"type":44,"value":467},{"type":44,"value":896},": persona and meeting-type modules.",{"type":39,"tag":146,"props":898,"children":899},{},[900,906],{"type":39,"tag":67,"props":901,"children":903},{"className":902},[],[904],{"type":44,"value":905},"references\u002Fquestion-and-evidence-bank.md",{"type":44,"value":907},": question and evidence-request patterns.",{"type":39,"tag":146,"props":909,"children":910},{},[911,917],{"type":39,"tag":67,"props":912,"children":914},{"className":913},[],[915],{"type":44,"value":916},"references\u002Ffollow-up-and-action-tracking.md",{"type":44,"value":918},": debrief and tracker fields.",{"type":39,"tag":146,"props":920,"children":921},{},[922,928],{"type":39,"tag":67,"props":923,"children":925},{"className":924},[],[926],{"type":44,"value":927},"references\u002Foutput-templates.md",{"type":44,"value":929},": standard brief formats.",{"type":39,"tag":146,"props":931,"children":932},{},[933,939],{"type":39,"tag":67,"props":934,"children":936},{"className":935},[],[937],{"type":44,"value":938},"references\u002Fsafety-and-integrations.md",{"type":44,"value":940},": non-destructive editing and circulation rules.",{"items":942,"total":1147},[943,964,987,1004,1020,1039,1058,1074,1090,1104,1116,1131],{"slug":944,"name":944,"fn":945,"description":946,"org":947,"tags":948,"stars":961,"repoUrl":962,"updatedAt":963},"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},[949,952,955,958],{"name":950,"slug":951,"type":15},"Documents","documents",{"name":953,"slug":954,"type":15},"Healthcare","healthcare",{"name":956,"slug":957,"type":15},"Insurance","insurance",{"name":959,"slug":960,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-08-02T05:48:07.395855",{"slug":965,"name":965,"fn":966,"description":967,"org":968,"tags":969,"stars":984,"repoUrl":985,"updatedAt":986},"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},[970,973,975,978,981],{"name":971,"slug":972,"type":15},".NET","dotnet",{"name":974,"slug":965,"type":15},"ASP.NET Core",{"name":976,"slug":977,"type":15},"Blazor","blazor",{"name":979,"slug":980,"type":15},"C#","csharp",{"name":982,"slug":983,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":988,"name":988,"fn":989,"description":990,"org":991,"tags":992,"stars":984,"repoUrl":985,"updatedAt":1003},"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},[993,996,999,1002],{"name":994,"slug":995,"type":15},"Apps SDK","apps-sdk",{"name":997,"slug":998,"type":15},"ChatGPT","chatgpt",{"name":1000,"slug":1001,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":1005,"name":1005,"fn":1006,"description":1007,"org":1008,"tags":1009,"stars":984,"repoUrl":985,"updatedAt":1019},"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},[1010,1013,1016],{"name":1011,"slug":1012,"type":15},"API Development","api-development",{"name":1014,"slug":1015,"type":15},"CLI","cli",{"name":1017,"slug":1018,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":1021,"name":1021,"fn":1022,"description":1023,"org":1024,"tags":1025,"stars":984,"repoUrl":985,"updatedAt":1038},"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},[1026,1029,1032,1035],{"name":1027,"slug":1028,"type":15},"Cloudflare","cloudflare",{"name":1030,"slug":1031,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":1033,"slug":1034,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":1036,"slug":1037,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":1040,"name":1040,"fn":1041,"description":1042,"org":1043,"tags":1044,"stars":984,"repoUrl":985,"updatedAt":1057},"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},[1045,1048,1051,1054],{"name":1046,"slug":1047,"type":15},"Productivity","productivity",{"name":1049,"slug":1050,"type":15},"Project Management","project-management",{"name":1052,"slug":1053,"type":15},"Strategy","strategy",{"name":1055,"slug":1056,"type":15},"Task Management","task-management","2026-05-23T06:17:16.870838",{"slug":1059,"name":1059,"fn":1060,"description":1061,"org":1062,"tags":1063,"stars":984,"repoUrl":985,"updatedAt":1073},"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},[1064,1067,1069,1072],{"name":1065,"slug":1066,"type":15},"Design","design",{"name":1068,"slug":1059,"type":15},"Figma",{"name":1070,"slug":1071,"type":15},"Frontend","frontend",{"name":1000,"slug":1001,"type":15},"2026-04-12T05:06:47.939943",{"slug":1075,"name":1075,"fn":1076,"description":1077,"org":1078,"tags":1079,"stars":984,"repoUrl":985,"updatedAt":1089},"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},[1080,1081,1084,1085,1086],{"name":1065,"slug":1066,"type":15},{"name":1082,"slug":1083,"type":15},"Design System","design-system",{"name":1068,"slug":1059,"type":15},{"name":1070,"slug":1071,"type":15},{"name":1087,"slug":1088,"type":15},"UI Components","ui-components","2026-05-10T05:59:52.971881",{"slug":1091,"name":1091,"fn":1092,"description":1093,"org":1094,"tags":1095,"stars":984,"repoUrl":985,"updatedAt":1103},"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},[1096,1097,1098,1101,1102],{"name":1065,"slug":1066,"type":15},{"name":1082,"slug":1083,"type":15},{"name":1099,"slug":1100,"type":15},"Documentation","documentation",{"name":1068,"slug":1059,"type":15},{"name":1070,"slug":1071,"type":15},"2026-05-16T06:07:47.821474",{"slug":1105,"name":1105,"fn":1106,"description":1107,"org":1108,"tags":1109,"stars":984,"repoUrl":985,"updatedAt":1115},"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},[1110,1111,1112,1113,1114],{"name":1065,"slug":1066,"type":15},{"name":1068,"slug":1059,"type":15},{"name":1070,"slug":1071,"type":15},{"name":1087,"slug":1088,"type":15},{"name":982,"slug":983,"type":15},"2026-05-16T06:07:40.583615",{"slug":1117,"name":1117,"fn":1118,"description":1119,"org":1120,"tags":1121,"stars":984,"repoUrl":985,"updatedAt":1130},"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},[1122,1125,1126,1129],{"name":1123,"slug":1124,"type":15},"Animation","animation",{"name":1017,"slug":1018,"type":15},{"name":1127,"slug":1128,"type":15},"Creative","creative",{"name":1065,"slug":1066,"type":15},"2026-05-02T05:31:48.48485",{"slug":1132,"name":1132,"fn":1133,"description":1134,"org":1135,"tags":1136,"stars":984,"repoUrl":985,"updatedAt":1146},"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},[1137,1138,1139,1142,1145],{"name":1127,"slug":1128,"type":15},{"name":1065,"slug":1066,"type":15},{"name":1140,"slug":1141,"type":15},"Image Generation","image-generation",{"name":1143,"slug":1144,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",578,{"items":1149,"total":1245},[1150,1167,1181,1193,1208,1221,1233],{"slug":1151,"name":1151,"fn":1152,"description":1153,"org":1154,"tags":1155,"stars":22,"repoUrl":23,"updatedAt":1166},"accessibility-and-inclusive-visualization","make data visualizations accessible","Make data visualizations accessible and inclusive. Use when the user needs chart or diagram accessibility guidance, text alternatives for complex visuals, color and contrast review, keyboard support, reduced-motion behavior for animation or parallax, or an accessibility QA workflow for exported figures, UML-like diagrams, and dashboards.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1156,1159,1162,1165],{"name":1157,"slug":1158,"type":15},"Accessibility","accessibility",{"name":1160,"slug":1161,"type":15},"Charts","charts",{"name":1163,"slug":1164,"type":15},"Data Visualization","data-visualization",{"name":1065,"slug":1066,"type":15},"2026-06-30T19:00:57.102",{"slug":1168,"name":1168,"fn":1169,"description":1170,"org":1171,"tags":1172,"stars":22,"repoUrl":23,"updatedAt":1180},"adobe-batch-edit-photos","apply consistent photo adjustments","Apply consistent photo adjustments across a set of images so they look like they were edited together. Use this skill whenever the user says \"make my photos look cohesive\", \"give all these the same style\", \"apply a warm and golden feel to all of these\", \"make this cinematic\", \"match the look across my photos\", \"edit all my travel photos the same way\", \"batch edit these\", \"make these consistent\", \"fix my phone photos\", or uploads a folder of photos and wants a unified, polished result. Also triggers for requests like \"apply a preset to all of these\", \"make these look professional\", or \"they were shot in mixed lighting — can you fix them all\". Outputs direct final image URLs plus an in-chat preview grid and optional Firefly Board link. Access: 🔐 Signed-In required | Gen AI: ❌\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1173,1174,1177],{"name":1127,"slug":1128,"type":15},{"name":1175,"slug":1176,"type":15},"Editing","editing",{"name":1178,"slug":1179,"type":15},"Imaging","imaging","2026-08-28T15:09:11.185865",{"slug":1182,"name":1182,"fn":1183,"description":1184,"org":1185,"tags":1186,"stars":22,"repoUrl":23,"updatedAt":1192},"adobe-create-mockups","create product and scene mockups","Use when a user wants to see their logo, design, or sketch on a product or scene mockup — mugs, t-shirts, business cards, hats, phone screens, posters, billboards, or similar. Triggers on \"create mockups\", \"show my logo on products\", or any logo upload with a request to visualize it on items. Access: 🔐 Signed-In required | Gen AI: ✅ Adobe Firefly via `image_generate` used for design creation, sketch polishing, and mockup scene generation\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1187,1188,1189],{"name":1127,"slug":1128,"type":15},{"name":1065,"slug":1066,"type":15},{"name":1190,"slug":1191,"type":15},"Graphics","graphics","2026-08-28T15:09:07.42507",{"slug":1194,"name":1194,"fn":1195,"description":1196,"org":1197,"tags":1198,"stars":22,"repoUrl":23,"updatedAt":1207},"adobe-create-social-variations","export platform-ready social media assets","Resize, crop, or export any image or video into platform-ready social media assets using Adobe Creative Cloud tools. Use this skill when a user wants to prepare a photo, image, or video for one or more social platforms — Instagram, TikTok, LinkedIn, Facebook, YouTube, Snapchat, Pinterest, Threads, or X\u002FTwitter. Triggers on: \"prepare my image for Instagram\", \"resize for TikTok\", \"get this ready to post\", \"make versions for all platforms\", \"social media sizes\", \"crop for stories\", \"export for LinkedIn\", \"resize my video for social\", \"make social media assets\", or any request to adapt a photo or video for specific platforms. Handles subject-aware cropping, AI canvas expansion, test previews before full runs, and same-ratio video resizing.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1199,1200,1201,1204],{"name":1127,"slug":1128,"type":15},{"name":1190,"slug":1191,"type":15},{"name":1202,"slug":1203,"type":15},"Marketing","marketing",{"name":1205,"slug":1206,"type":15},"Social Media","social-media","2026-08-28T15:10:07.282096",{"slug":1209,"name":1209,"fn":1210,"description":1211,"org":1212,"tags":1213,"stars":22,"repoUrl":23,"updatedAt":1220},"adobe-design-from-template","create visual designs from templates","Create any visual design using Adobe Express templates — flyers, posters, social media posts (Instagram, Facebook, LinkedIn), business cards, invitations, greeting cards, resumes, cover letters, brochures, newsletters, certificates, presentations, YouTube thumbnails, email headers, logos, menus, and labels. Use this skill whenever the user wants to make, design, or build any visual — even if they just say \"make me a flyer\", \"design a poster\", \"I need something for Instagram\", \"create an event invite\", or \"make a business card\". Also handles browsing templates, editing text, replacing images, changing backgrounds, animating, and exporting designs. Access: 🔐 Signed-In required | Gen AI: ❌ by default — image replacement only where the surface permits generative AI (e.g. Codex); none on Claude\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1214,1215,1216,1217],{"name":1127,"slug":1128,"type":15},{"name":1065,"slug":1066,"type":15},{"name":1190,"slug":1191,"type":15},{"name":1218,"slug":1219,"type":15},"Templates","templates","2026-08-28T15:10:03.050113",{"slug":1222,"name":1222,"fn":1223,"description":1224,"org":1225,"tags":1226,"stars":22,"repoUrl":23,"updatedAt":1232},"adobe-edit-quick-cut","create video sizzle reels","Create a punchy sizzle reel from a video using Adobe Quick Cut. Use this skill whenever a user wants to cut, trim, or shorten a video into highlights — including phrases like \"make a sizzle reel\", \"make a highlight reel\", \"quick cut this\", \"cut the best parts\", \"shorten this video\", \"make a highlight clip\", \"summarize this video visually\", or any request to produce a shorter edited version of a video. Use this skill for Quick Cut requests before suggesting manual editing in Premiere. Requires the user to upload a video file.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1227,1228,1229],{"name":1127,"slug":1128,"type":15},{"name":1175,"slug":1176,"type":15},{"name":1230,"slug":1231,"type":15},"Video","video","2026-08-28T15:09:07.765245",{"slug":1234,"name":1234,"fn":1235,"description":1236,"org":1237,"tags":1238,"stars":22,"repoUrl":23,"updatedAt":1244},"adobe-retouch-portraits","batch retouch portrait photos","Bulk-retouch a folder of portrait photos using Adobe tools — designed for wedding photographers and event photographers who need fast, walk-away batch processing. Use this skill when the user says \"retouch my photos\", \"batch process these portraits\", \"process my wedding photos\", \"clean up this folder of images\", \"run my headshots through Adobe\", or uploads\u002Fselects a folder of photos and wants them polished and ready to review. Automatically applies auto-straighten, auto-tone, and auto-light to every image. Outputs a preview grid and download folder. Access: 🔐 Signed-In required | Gen AI: ❌ by default — optional background-only cleanup only where the surface permits generative AI (e.g. Codex); none on Claude\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1239,1240,1241],{"name":1127,"slug":1128,"type":15},{"name":1178,"slug":1179,"type":15},{"name":1242,"slug":1243,"type":15},"Photography","photography","2026-08-28T15:09:10.386974",499]