[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-catalyst-calendar":3,"mdc-jih9je-key":33,"related-repo-openai-catalyst-calendar":901,"related-org-openai-catalyst-calendar":1003},{"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},"catalyst-calendar","build public equity catalyst calendars","Use when building public-equity-investing catalyst calendars. Do not use for full event underwriting; use event-driven-analyzer.",{"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},"Finance","finance","tag",{"name":17,"slug":18,"type":15},"Planning","planning",{"name":20,"slug":21,"type":15},"Equity Research","equity-research",4888,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins","2026-08-28T15:09:55.269899",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\u002Fcatalyst-calendar","---\nname: catalyst-calendar\ndescription: Use when building public-equity-investing catalyst calendars. Do not use for full event underwriting; use event-driven-analyzer.\n---\n\n# Catalyst Calendar\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 categories needed for this workflow: `company_filings_ir`, `earnings_transcripts_presentations`, `internal_research`, `portfolio_models_trackers`, and `market_data_estimates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input.\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- `Earnings Transcripts & Events`\n- `Company Filings & IR`\n- `Market Data & Estimates`\n- `Internal Research`\n\n## Internal Support\n\nWhen this workflow needs rendering, evidence\u002Fdata preparation, style, or sector context, route support through the visible `public-equity-investing` router and its bundled internal playbooks. Route workbook or model QA through the visible `model-audit-tieout` workflow.\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 choices. For a substantive single-company 60\u002F90-day catalyst calendar, the workflow default resolves the presentation surface to a polished HTML catalyst calendar unless the user asks for another format, a quick\u002Fno-file answer, or a workbook\u002Ftracker. In that case, do not block on a format question; ask only for unresolved depth, audience\u002Fuse, or focus choices. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt.\n\n## Purpose\nBuild or refresh source-backed Public Equity Investing catalyst calendars. The output should show timing, confidence, thesis relevance, prep work, owner\u002Fstatus, and likely PM decision, not just dates.\n\n## Use \u002F Do Not Use\nUse for single-name, portfolio, sector, earnings, regulatory, clinical, technical, capital-markets, and special-situation catalyst tracking. Use the script for tracker workbooks, CSV\u002FJSON intake, refresh logs, blank templates, or optional ICS export.\n\nDo not use for merger-arb\u002Fspin\u002Ftender probability math; route to `event-driven-analyzer`. Do not use for pure pre-print notes, post-event analysis, model refreshes, thesis updates, risk sizing, or hedge design; route to `earnings-preview`, `earnings-deep-dive`, `equity-model-update`, `thesis-tracker`, or `portfolio-risk-management`.\n\n## Reference Router\n- `..\u002F..\u002Fshared\u002Fhtml-artifact-standard.md`: shared principles for polished, legible, evidence-aware HTML artifacts.\n- `source-and-data-protocol.md`: source hierarchy, stale-date checks, confidence labels, refresh rules.\n- `catalyst-taxonomy-and-fields.md`: event fields, categories, scoring labels.\n- `event-scoring-framework.md`: impact, confidence, controversy, urgency.\n- `pm-action-playbook.md` \u002F `portfolio-pm-playbook.md`: prep actions, thesis checkpoints, clustering, position context.\n- `sector-and-asset-overlays.md`: sector-specific catalyst logic.\n- `output-templates.md` \u002F `pm-review-checklist.md`: delivery formats and QA.\n\n## Workflow\n1. Classify mode: no-context template, partial-context build, refresh, single-company map, portfolio dashboard, single-event brief, or sector sweep.\n2. Set scope: default to next 30\u002F60\u002F90 days plus thesis-critical longer-dated items. Ask only for destructive or blocking choices.\n3. Build rows with exact date or window, source, confidence, status, thesis link, model\u002FKPI line, prep action, owner, and decision implication.\n4. Rank by impact, confidence, controversy, actionability, portfolio relevance, and same-day clustering.\n5. Convert high-priority events into work items, model updates, questions, risk\u002Fsizing reviews, hedge prompts, or post-event follow-up.\n6. Refresh non-destructively: preserve prior rows, append evidence, mark stale\u002Fsuperseded items, and produce a change log.\n7. For a named issuer plus a substantive 60\u002F90-day calendar, default to a polished standalone HTML catalyst calendar when local artifact creation is available unless the user requests another format, a quick\u002Fno-file answer, or a workbook\u002Ftracker. In interactive runs, ask only for unresolved depth, audience\u002Fuse, or focus choices; mention that another format is available as an opt-out without making it a blocking question. In non-interactive runs, apply the HTML catalyst calendar plus full working analysis defaults and disclose those assumptions in the delivery message or accompanying chat summary, not as visible artifact metadata.\n8. For other multi-category calendars, PM monitoring calendars, or requests that ask for earnings plus macro\u002Fregulatory\u002Fcompany-specific catalysts, treat polished standalone HTML as the recommended presentation path and use `..\u002F..\u002Fshared\u002Fdeliverable-intake-policy.md` for materially unresolved format or depth choices.\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: event\u002Fdate verification, source freshness, catalyst impact, probability\u002Ftiming, and follow-up monitoring. Keep this skill as the lead: reconcile conflicts, source labels, assumptions, open items, final QA, and the user-facing answer.\n\n\n## Guardrails\n- Never imply a date is confirmed without reliable evidence.\n- Use windows for guided, estimated, inferred, or street timing; do not turn soft windows into one-day ICS events.\n- Separate facts, assumptions, rumors, restricted\u002Finternal notes, and PM judgments.\n- Do not invent earnings dates, trial readouts, approvals, lockups, merger deadlines, conferences, or policy dates.\n- Surface conflicts and prefer company\u002Fregulator\u002Fexchange sources over aggregators.\n\n## Default Output\nRecommend the full catalyst package: PM summary, top-catalysts table, full catalyst register or clearly scoped subset, prep plan, source\u002Ffreshness notes, refresh change log when relevant, decision implications, and recommended adjacent work.\n\nFor substantive single-company 60\u002F90-day catalyst calendars, default to a concise chat summary plus a polished standalone HTML catalyst calendar when local artifact creation is available. This workflow default resolves presentation format unless the user requests another format, a quick\u002Fno-file answer, or a workbook\u002Ftracker. In interactive runs, ask for unresolved analysis depth and any consequential audience\u002Fuse or focus choice, but do not require the user to confirm HTML before proceeding. In non-interactive runs, default to the HTML catalyst calendar and `Full working analysis`, and state the assumed format and depth in the delivery message or accompanying chat summary rather than in the visible HTML artifact.\n\nIf the user explicitly asks for a standardized dashboard, reusable dashboard template, or structured payload-driven render, route that optional rendering path through `dashboard-builder` and follow its payload and validation contract. `catalyst-calendar` continues to own event selection, timing, confidence, impact, and PM monitoring judgment. Keep JSON\u002FMarkdown\u002FCSV\u002FICS support files behind the HTML artifact unless explicitly requested.\n\nUse a single-event brief or compressed watchlist only when the user explicitly asks for a summary, quick read, one-pager, brief, TL;DR, or one specific event.\n\n## HTML Guidance\n\nFor substantive HTML output, load `..\u002F..\u002Fshared\u002Fhtml-artifact-standard.md` and apply these calendar-specific priorities:\n\n- Use a title that identifies the requested artifact, such as `\u003CCompany> (\u003CTicker>): 90-Day Catalyst Calendar`; do not substitute a generic label such as `Decision Map` for a calendar request.\n- Structure the first read as an investor brief: concise thesis checkpoint, add\u002Fhold\u002Ftrim triggers, then the catalyst schedule. Put the detailed register, preparation queue, and source ledger below that scan layer.\n- Make the catalyst schedule the primary visual object; the reader should reach upcoming dates and timing windows quickly.\n- Before a detailed register table, include a compact month-by-month or time-horizon visual summary of the highest-decision-pressure confirmed dates and inferred windows. Keep it concise: the detailed register should own full explanations, implications, and sourcing.\n- Show confirmed dates distinctly from inferred windows and unscheduled monitoring items.\n- Surface the highest-decision-pressure events prominently, while retaining lower-priority confirmed issuer events in the calendar when they fall inside scope.\n- Include preparation actions and add\u002Fhold\u002Ftrim implications when the user supplies portfolio context.\n- Keep sourcing unobtrusive but auditable, with visible timing confidence and material evidence gaps.\n- A full catalyst register is appropriate for substantive calendars, but do not repeat the same event across overview, register, thesis tests, and prep sections unless each view answers a distinct investment question.\n- Do not surface internal support-contract fields in the HTML artifact; convert relevant evidence gaps and readiness limitations into polished PM-facing prose.\n- Do not show format-selection, intake, or generation-process notes such as `Format assumption` in the HTML artifact; keep any required default disclosure in the delivery message.\n\n## Script Contract\n\n```bash\npython scripts\u002Fcreate_catalyst_calendar_workbook.py --input events.csv --output catalyst_calendar.xlsx --ics catalyst_calendar.ics\npython scripts\u002Fcreate_catalyst_calendar_workbook.py --prior prior_events.csv --input refreshed_events.csv --output refreshed_calendar.xlsx\n```\n\nThe script is a materializer, not a live data provider. It preserves source\u002Fconfidence fields, keeps undated\u002Fwindowed items in review tables, writes refresh changes, and exports ICS entries only for confirmed exact dates.\n\nWorkbook outputs start with a `Cover` tab that serves as the PM dashboard: as-of date, event counts, 30\u002F60\u002F90 day pressure, red\u002Famber urgency, high-impact events, low-confidence events, overdue\u002Fmissing-owner prep, top catalysts, source posture, and workbook map.\n\n## Public Equity PM Judgment Layer\n\nFor substantial catalyst work, load `shared\u002Fpm-judgment-heuristics.md` before finalizing. Audience modes: `long_only_pm`, `long_short_hf`, `sell_side_research`, `etf_index_diligence`, `public_equity_diligence`.\n\nPM catalyst discipline: a catalyst only matters if it can alter estimate path, narrative, multiple, position size, downside, liquidity, or event probability.\n\nRequired PM judgment:\n- Rank by `decision_pressure`, not date proximity alone.\n- Add index\u002FETF and technical catalysts when relevant: index additions\u002Fdeletions, Russell\u002FS&P\u002FMSCI rebalance, ETF reconstitutions, lockups, secondary offerings, buyback windows, blackout windows, passive ownership shifts, and float changes.\n- Separate confirmed dates from inferred windows. Do not export inferred windows as exact calendar events.\n- Group low-impact dates as hygiene unless they are tied to a decision.\n",{"data":34,"body":35},{"name":4,"description":6},{"type":36,"children":37},"root",[38,46,53,60,91,97,148,154,159,200,206,227,233,254,260,265,271,276,325,331,426,432,483,489,494,500,528,534,539,552,572,577,583,595,677,683,782,787,800,806,854,859,864,895],{"type":39,"tag":40,"props":41,"children":42},"element","h1",{"id":4},[43],{"type":44,"value":45},"text","Catalyst Calendar",{"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,118,124,125,131,132,138,140,146],{"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 categories needed for this workflow: ",{"type":39,"tag":67,"props":111,"children":113},{"className":112},[],[114],{"type":44,"value":115},"company_filings_ir",{"type":44,"value":117},", ",{"type":39,"tag":67,"props":119,"children":121},{"className":120},[],[122],{"type":44,"value":123},"earnings_transcripts_presentations",{"type":44,"value":117},{"type":39,"tag":67,"props":126,"children":128},{"className":127},[],[129],{"type":44,"value":130},"internal_research",{"type":44,"value":117},{"type":39,"tag":67,"props":133,"children":135},{"className":134},[],[136],{"type":44,"value":137},"portfolio_models_trackers",{"type":44,"value":139},", and ",{"type":39,"tag":67,"props":141,"children":143},{"className":142},[],[144],{"type":44,"value":145},"market_data_estimates",{"type":44,"value":147},". Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input.",{"type":39,"tag":47,"props":149,"children":151},{"id":150},"relevant-dependency-categories",[152],{"type":44,"value":153},"Relevant Dependency Categories",{"type":39,"tag":61,"props":155,"children":156},{},[157],{"type":44,"value":158},"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":160,"props":161,"children":162},"ul",{},[163,173,182,191],{"type":39,"tag":164,"props":165,"children":166},"li",{},[167],{"type":39,"tag":67,"props":168,"children":170},{"className":169},[],[171],{"type":44,"value":172},"Earnings Transcripts & Events",{"type":39,"tag":164,"props":174,"children":175},{},[176],{"type":39,"tag":67,"props":177,"children":179},{"className":178},[],[180],{"type":44,"value":181},"Company Filings & IR",{"type":39,"tag":164,"props":183,"children":184},{},[185],{"type":39,"tag":67,"props":186,"children":188},{"className":187},[],[189],{"type":44,"value":190},"Market Data & Estimates",{"type":39,"tag":164,"props":192,"children":193},{},[194],{"type":39,"tag":67,"props":195,"children":197},{"className":196},[],[198],{"type":44,"value":199},"Internal Research",{"type":39,"tag":47,"props":201,"children":203},{"id":202},"internal-support",[204],{"type":44,"value":205},"Internal Support",{"type":39,"tag":61,"props":207,"children":208},{},[209,211,217,219,225],{"type":44,"value":210},"When this workflow needs rendering, evidence\u002Fdata preparation, style, or sector context, route support through the visible ",{"type":39,"tag":67,"props":212,"children":214},{"className":213},[],[215],{"type":44,"value":216},"public-equity-investing",{"type":44,"value":218}," router and its bundled internal playbooks. Route workbook or model QA through the visible ",{"type":39,"tag":67,"props":220,"children":222},{"className":221},[],[223],{"type":44,"value":224},"model-audit-tieout",{"type":44,"value":226}," workflow.",{"type":39,"tag":47,"props":228,"children":230},{"id":229},"deliverable-intake",[231],{"type":44,"value":232},"Deliverable Intake",{"type":39,"tag":61,"props":234,"children":235},{},[236,238,244,246,252],{"type":44,"value":237},"Before source gathering or analysis for a new substantive hero deliverable, load ",{"type":39,"tag":67,"props":239,"children":241},{"className":240},[],[242],{"type":44,"value":243},"..\u002F..\u002Fshared\u002Fdeliverable-intake-policy.md",{"type":44,"value":245}," and use its adaptive ",{"type":39,"tag":67,"props":247,"children":249},{"className":248},[],[250],{"type":44,"value":251},"request_user_input",{"type":44,"value":253}," preflight for materially unresolved choices. For a substantive single-company 60\u002F90-day catalyst calendar, the workflow default resolves the presentation surface to a polished HTML catalyst calendar unless the user asks for another format, a quick\u002Fno-file answer, or a workbook\u002Ftracker. In that case, do not block on a format question; ask only for unresolved depth, audience\u002Fuse, or focus choices. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt.",{"type":39,"tag":47,"props":255,"children":257},{"id":256},"purpose",[258],{"type":44,"value":259},"Purpose",{"type":39,"tag":61,"props":261,"children":262},{},[263],{"type":44,"value":264},"Build or refresh source-backed Public Equity Investing catalyst calendars. The output should show timing, confidence, thesis relevance, prep work, owner\u002Fstatus, and likely PM decision, not just dates.",{"type":39,"tag":47,"props":266,"children":268},{"id":267},"use-do-not-use",[269],{"type":44,"value":270},"Use \u002F Do Not Use",{"type":39,"tag":61,"props":272,"children":273},{},[274],{"type":44,"value":275},"Use for single-name, portfolio, sector, earnings, regulatory, clinical, technical, capital-markets, and special-situation catalyst tracking. Use the script for tracker workbooks, CSV\u002FJSON intake, refresh logs, blank templates, or optional ICS export.",{"type":39,"tag":61,"props":277,"children":278},{},[279,281,287,289,295,296,302,303,309,310,316,318,324],{"type":44,"value":280},"Do not use for merger-arb\u002Fspin\u002Ftender probability math; route to ",{"type":39,"tag":67,"props":282,"children":284},{"className":283},[],[285],{"type":44,"value":286},"event-driven-analyzer",{"type":44,"value":288},". Do not use for pure pre-print notes, post-event analysis, model refreshes, thesis updates, risk sizing, or hedge design; route to ",{"type":39,"tag":67,"props":290,"children":292},{"className":291},[],[293],{"type":44,"value":294},"earnings-preview",{"type":44,"value":117},{"type":39,"tag":67,"props":297,"children":299},{"className":298},[],[300],{"type":44,"value":301},"earnings-deep-dive",{"type":44,"value":117},{"type":39,"tag":67,"props":304,"children":306},{"className":305},[],[307],{"type":44,"value":308},"equity-model-update",{"type":44,"value":117},{"type":39,"tag":67,"props":311,"children":313},{"className":312},[],[314],{"type":44,"value":315},"thesis-tracker",{"type":44,"value":317},", or ",{"type":39,"tag":67,"props":319,"children":321},{"className":320},[],[322],{"type":44,"value":323},"portfolio-risk-management",{"type":44,"value":90},{"type":39,"tag":47,"props":326,"children":328},{"id":327},"reference-router",[329],{"type":44,"value":330},"Reference Router",{"type":39,"tag":160,"props":332,"children":333},{},[334,345,356,367,378,397,408],{"type":39,"tag":164,"props":335,"children":336},{},[337,343],{"type":39,"tag":67,"props":338,"children":340},{"className":339},[],[341],{"type":44,"value":342},"..\u002F..\u002Fshared\u002Fhtml-artifact-standard.md",{"type":44,"value":344},": shared principles for polished, legible, evidence-aware HTML artifacts.",{"type":39,"tag":164,"props":346,"children":347},{},[348,354],{"type":39,"tag":67,"props":349,"children":351},{"className":350},[],[352],{"type":44,"value":353},"source-and-data-protocol.md",{"type":44,"value":355},": source hierarchy, stale-date checks, confidence labels, refresh rules.",{"type":39,"tag":164,"props":357,"children":358},{},[359,365],{"type":39,"tag":67,"props":360,"children":362},{"className":361},[],[363],{"type":44,"value":364},"catalyst-taxonomy-and-fields.md",{"type":44,"value":366},": event fields, categories, scoring labels.",{"type":39,"tag":164,"props":368,"children":369},{},[370,376],{"type":39,"tag":67,"props":371,"children":373},{"className":372},[],[374],{"type":44,"value":375},"event-scoring-framework.md",{"type":44,"value":377},": impact, confidence, controversy, urgency.",{"type":39,"tag":164,"props":379,"children":380},{},[381,387,389,395],{"type":39,"tag":67,"props":382,"children":384},{"className":383},[],[385],{"type":44,"value":386},"pm-action-playbook.md",{"type":44,"value":388}," \u002F ",{"type":39,"tag":67,"props":390,"children":392},{"className":391},[],[393],{"type":44,"value":394},"portfolio-pm-playbook.md",{"type":44,"value":396},": prep actions, thesis checkpoints, clustering, position context.",{"type":39,"tag":164,"props":398,"children":399},{},[400,406],{"type":39,"tag":67,"props":401,"children":403},{"className":402},[],[404],{"type":44,"value":405},"sector-and-asset-overlays.md",{"type":44,"value":407},": sector-specific catalyst logic.",{"type":39,"tag":164,"props":409,"children":410},{},[411,417,418,424],{"type":39,"tag":67,"props":412,"children":414},{"className":413},[],[415],{"type":44,"value":416},"output-templates.md",{"type":44,"value":388},{"type":39,"tag":67,"props":419,"children":421},{"className":420},[],[422],{"type":44,"value":423},"pm-review-checklist.md",{"type":44,"value":425},": delivery formats and QA.",{"type":39,"tag":47,"props":427,"children":429},{"id":428},"workflow",[430],{"type":44,"value":431},"Workflow",{"type":39,"tag":433,"props":434,"children":435},"ol",{},[436,441,446,451,456,461,466,471],{"type":39,"tag":164,"props":437,"children":438},{},[439],{"type":44,"value":440},"Classify mode: no-context template, partial-context build, refresh, single-company map, portfolio dashboard, single-event brief, or sector sweep.",{"type":39,"tag":164,"props":442,"children":443},{},[444],{"type":44,"value":445},"Set scope: default to next 30\u002F60\u002F90 days plus thesis-critical longer-dated items. Ask only for destructive or blocking choices.",{"type":39,"tag":164,"props":447,"children":448},{},[449],{"type":44,"value":450},"Build rows with exact date or window, source, confidence, status, thesis link, model\u002FKPI line, prep action, owner, and decision implication.",{"type":39,"tag":164,"props":452,"children":453},{},[454],{"type":44,"value":455},"Rank by impact, confidence, controversy, actionability, portfolio relevance, and same-day clustering.",{"type":39,"tag":164,"props":457,"children":458},{},[459],{"type":44,"value":460},"Convert high-priority events into work items, model updates, questions, risk\u002Fsizing reviews, hedge prompts, or post-event follow-up.",{"type":39,"tag":164,"props":462,"children":463},{},[464],{"type":44,"value":465},"Refresh non-destructively: preserve prior rows, append evidence, mark stale\u002Fsuperseded items, and produce a change log.",{"type":39,"tag":164,"props":467,"children":468},{},[469],{"type":44,"value":470},"For a named issuer plus a substantive 60\u002F90-day calendar, default to a polished standalone HTML catalyst calendar when local artifact creation is available unless the user requests another format, a quick\u002Fno-file answer, or a workbook\u002Ftracker. In interactive runs, ask only for unresolved depth, audience\u002Fuse, or focus choices; mention that another format is available as an opt-out without making it a blocking question. In non-interactive runs, apply the HTML catalyst calendar plus full working analysis defaults and disclose those assumptions in the delivery message or accompanying chat summary, not as visible artifact metadata.",{"type":39,"tag":164,"props":472,"children":473},{},[474,476,481],{"type":44,"value":475},"For other multi-category calendars, PM monitoring calendars, or requests that ask for earnings plus macro\u002Fregulatory\u002Fcompany-specific catalysts, treat polished standalone HTML as the recommended presentation path and use ",{"type":39,"tag":67,"props":477,"children":479},{"className":478},[],[480],{"type":44,"value":243},{"type":44,"value":482}," for materially unresolved format or depth choices.",{"type":39,"tag":47,"props":484,"children":486},{"id":485},"sub-agent-decomposition",[487],{"type":44,"value":488},"Sub-agent decomposition",{"type":39,"tag":61,"props":490,"children":491},{},[492],{"type":44,"value":493},"For complex medium\u002Flarge requests, use sub-agents where available; otherwise emulate the split as named workstreams. Suggested lanes: event\u002Fdate verification, source freshness, catalyst impact, probability\u002Ftiming, and follow-up monitoring. 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":495,"children":497},{"id":496},"guardrails",[498],{"type":44,"value":499},"Guardrails",{"type":39,"tag":160,"props":501,"children":502},{},[503,508,513,518,523],{"type":39,"tag":164,"props":504,"children":505},{},[506],{"type":44,"value":507},"Never imply a date is confirmed without reliable evidence.",{"type":39,"tag":164,"props":509,"children":510},{},[511],{"type":44,"value":512},"Use windows for guided, estimated, inferred, or street timing; do not turn soft windows into one-day ICS events.",{"type":39,"tag":164,"props":514,"children":515},{},[516],{"type":44,"value":517},"Separate facts, assumptions, rumors, restricted\u002Finternal notes, and PM judgments.",{"type":39,"tag":164,"props":519,"children":520},{},[521],{"type":44,"value":522},"Do not invent earnings dates, trial readouts, approvals, lockups, merger deadlines, conferences, or policy dates.",{"type":39,"tag":164,"props":524,"children":525},{},[526],{"type":44,"value":527},"Surface conflicts and prefer company\u002Fregulator\u002Fexchange sources over aggregators.",{"type":39,"tag":47,"props":529,"children":531},{"id":530},"default-output",[532],{"type":44,"value":533},"Default Output",{"type":39,"tag":61,"props":535,"children":536},{},[537],{"type":44,"value":538},"Recommend the full catalyst package: PM summary, top-catalysts table, full catalyst register or clearly scoped subset, prep plan, source\u002Ffreshness notes, refresh change log when relevant, decision implications, and recommended adjacent work.",{"type":39,"tag":61,"props":540,"children":541},{},[542,544,550],{"type":44,"value":543},"For substantive single-company 60\u002F90-day catalyst calendars, default to a concise chat summary plus a polished standalone HTML catalyst calendar when local artifact creation is available. This workflow default resolves presentation format unless the user requests another format, a quick\u002Fno-file answer, or a workbook\u002Ftracker. In interactive runs, ask for unresolved analysis depth and any consequential audience\u002Fuse or focus choice, but do not require the user to confirm HTML before proceeding. In non-interactive runs, default to the HTML catalyst calendar and ",{"type":39,"tag":67,"props":545,"children":547},{"className":546},[],[548],{"type":44,"value":549},"Full working analysis",{"type":44,"value":551},", and state the assumed format and depth in the delivery message or accompanying chat summary rather than in the visible HTML artifact.",{"type":39,"tag":61,"props":553,"children":554},{},[555,557,563,565,570],{"type":44,"value":556},"If the user explicitly asks for a standardized dashboard, reusable dashboard template, or structured payload-driven render, route that optional rendering path through ",{"type":39,"tag":67,"props":558,"children":560},{"className":559},[],[561],{"type":44,"value":562},"dashboard-builder",{"type":44,"value":564}," and follow its payload and validation contract. ",{"type":39,"tag":67,"props":566,"children":568},{"className":567},[],[569],{"type":44,"value":4},{"type":44,"value":571}," continues to own event selection, timing, confidence, impact, and PM monitoring judgment. Keep JSON\u002FMarkdown\u002FCSV\u002FICS support files behind the HTML artifact unless explicitly requested.",{"type":39,"tag":61,"props":573,"children":574},{},[575],{"type":44,"value":576},"Use a single-event brief or compressed watchlist only when the user explicitly asks for a summary, quick read, one-pager, brief, TL;DR, or one specific event.",{"type":39,"tag":47,"props":578,"children":580},{"id":579},"html-guidance",[581],{"type":44,"value":582},"HTML Guidance",{"type":39,"tag":61,"props":584,"children":585},{},[586,588,593],{"type":44,"value":587},"For substantive HTML output, load ",{"type":39,"tag":67,"props":589,"children":591},{"className":590},[],[592],{"type":44,"value":342},{"type":44,"value":594}," and apply these calendar-specific priorities:",{"type":39,"tag":160,"props":596,"children":597},{},[598,619,624,629,634,639,644,649,654,659,664],{"type":39,"tag":164,"props":599,"children":600},{},[601,603,609,611,617],{"type":44,"value":602},"Use a title that identifies the requested artifact, such as ",{"type":39,"tag":67,"props":604,"children":606},{"className":605},[],[607],{"type":44,"value":608},"\u003CCompany> (\u003CTicker>): 90-Day Catalyst Calendar",{"type":44,"value":610},"; do not substitute a generic label such as ",{"type":39,"tag":67,"props":612,"children":614},{"className":613},[],[615],{"type":44,"value":616},"Decision Map",{"type":44,"value":618}," for a calendar request.",{"type":39,"tag":164,"props":620,"children":621},{},[622],{"type":44,"value":623},"Structure the first read as an investor brief: concise thesis checkpoint, add\u002Fhold\u002Ftrim triggers, then the catalyst schedule. Put the detailed register, preparation queue, and source ledger below that scan layer.",{"type":39,"tag":164,"props":625,"children":626},{},[627],{"type":44,"value":628},"Make the catalyst schedule the primary visual object; the reader should reach upcoming dates and timing windows quickly.",{"type":39,"tag":164,"props":630,"children":631},{},[632],{"type":44,"value":633},"Before a detailed register table, include a compact month-by-month or time-horizon visual summary of the highest-decision-pressure confirmed dates and inferred windows. Keep it concise: the detailed register should own full explanations, implications, and sourcing.",{"type":39,"tag":164,"props":635,"children":636},{},[637],{"type":44,"value":638},"Show confirmed dates distinctly from inferred windows and unscheduled monitoring items.",{"type":39,"tag":164,"props":640,"children":641},{},[642],{"type":44,"value":643},"Surface the highest-decision-pressure events prominently, while retaining lower-priority confirmed issuer events in the calendar when they fall inside scope.",{"type":39,"tag":164,"props":645,"children":646},{},[647],{"type":44,"value":648},"Include preparation actions and add\u002Fhold\u002Ftrim implications when the user supplies portfolio context.",{"type":39,"tag":164,"props":650,"children":651},{},[652],{"type":44,"value":653},"Keep sourcing unobtrusive but auditable, with visible timing confidence and material evidence gaps.",{"type":39,"tag":164,"props":655,"children":656},{},[657],{"type":44,"value":658},"A full catalyst register is appropriate for substantive calendars, but do not repeat the same event across overview, register, thesis tests, and prep sections unless each view answers a distinct investment question.",{"type":39,"tag":164,"props":660,"children":661},{},[662],{"type":44,"value":663},"Do not surface internal support-contract fields in the HTML artifact; convert relevant evidence gaps and readiness limitations into polished PM-facing prose.",{"type":39,"tag":164,"props":665,"children":666},{},[667,669,675],{"type":44,"value":668},"Do not show format-selection, intake, or generation-process notes such as ",{"type":39,"tag":67,"props":670,"children":672},{"className":671},[],[673],{"type":44,"value":674},"Format assumption",{"type":44,"value":676}," in the HTML artifact; keep any required default disclosure in the delivery message.",{"type":39,"tag":47,"props":678,"children":680},{"id":679},"script-contract",[681],{"type":44,"value":682},"Script Contract",{"type":39,"tag":684,"props":685,"children":690},"pre",{"className":686,"code":687,"language":688,"meta":689,"style":689},"language-bash shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","python scripts\u002Fcreate_catalyst_calendar_workbook.py --input events.csv --output catalyst_calendar.xlsx --ics catalyst_calendar.ics\npython scripts\u002Fcreate_catalyst_calendar_workbook.py --prior prior_events.csv --input refreshed_events.csv --output refreshed_calendar.xlsx\n","bash","",[691],{"type":39,"tag":67,"props":692,"children":693},{"__ignoreMap":689},[694,742],{"type":39,"tag":695,"props":696,"children":699},"span",{"class":697,"line":698},"line",1,[700,706,712,717,722,727,732,737],{"type":39,"tag":695,"props":701,"children":703},{"style":702},"--shiki-light:#E2931D;--shiki-default:#FFCB6B;--shiki-dark:#FFCB6B",[704],{"type":44,"value":705},"python",{"type":39,"tag":695,"props":707,"children":709},{"style":708},"--shiki-light:#91B859;--shiki-default:#C3E88D;--shiki-dark:#C3E88D",[710],{"type":44,"value":711}," scripts\u002Fcreate_catalyst_calendar_workbook.py",{"type":39,"tag":695,"props":713,"children":714},{"style":708},[715],{"type":44,"value":716}," --input",{"type":39,"tag":695,"props":718,"children":719},{"style":708},[720],{"type":44,"value":721}," events.csv",{"type":39,"tag":695,"props":723,"children":724},{"style":708},[725],{"type":44,"value":726}," --output",{"type":39,"tag":695,"props":728,"children":729},{"style":708},[730],{"type":44,"value":731}," catalyst_calendar.xlsx",{"type":39,"tag":695,"props":733,"children":734},{"style":708},[735],{"type":44,"value":736}," --ics",{"type":39,"tag":695,"props":738,"children":739},{"style":708},[740],{"type":44,"value":741}," catalyst_calendar.ics\n",{"type":39,"tag":695,"props":743,"children":745},{"class":697,"line":744},2,[746,750,754,759,764,768,773,777],{"type":39,"tag":695,"props":747,"children":748},{"style":702},[749],{"type":44,"value":705},{"type":39,"tag":695,"props":751,"children":752},{"style":708},[753],{"type":44,"value":711},{"type":39,"tag":695,"props":755,"children":756},{"style":708},[757],{"type":44,"value":758}," --prior",{"type":39,"tag":695,"props":760,"children":761},{"style":708},[762],{"type":44,"value":763}," prior_events.csv",{"type":39,"tag":695,"props":765,"children":766},{"style":708},[767],{"type":44,"value":716},{"type":39,"tag":695,"props":769,"children":770},{"style":708},[771],{"type":44,"value":772}," refreshed_events.csv",{"type":39,"tag":695,"props":774,"children":775},{"style":708},[776],{"type":44,"value":726},{"type":39,"tag":695,"props":778,"children":779},{"style":708},[780],{"type":44,"value":781}," refreshed_calendar.xlsx\n",{"type":39,"tag":61,"props":783,"children":784},{},[785],{"type":44,"value":786},"The script is a materializer, not a live data provider. It preserves source\u002Fconfidence fields, keeps undated\u002Fwindowed items in review tables, writes refresh changes, and exports ICS entries only for confirmed exact dates.",{"type":39,"tag":61,"props":788,"children":789},{},[790,792,798],{"type":44,"value":791},"Workbook outputs start with a ",{"type":39,"tag":67,"props":793,"children":795},{"className":794},[],[796],{"type":44,"value":797},"Cover",{"type":44,"value":799}," tab that serves as the PM dashboard: as-of date, event counts, 30\u002F60\u002F90 day pressure, red\u002Famber urgency, high-impact events, low-confidence events, overdue\u002Fmissing-owner prep, top catalysts, source posture, and workbook map.",{"type":39,"tag":47,"props":801,"children":803},{"id":802},"public-equity-pm-judgment-layer",[804],{"type":44,"value":805},"Public Equity PM Judgment Layer",{"type":39,"tag":61,"props":807,"children":808},{},[809,811,817,819,825,826,832,833,839,840,846,847,853],{"type":44,"value":810},"For substantial catalyst work, load ",{"type":39,"tag":67,"props":812,"children":814},{"className":813},[],[815],{"type":44,"value":816},"shared\u002Fpm-judgment-heuristics.md",{"type":44,"value":818}," before finalizing. Audience modes: ",{"type":39,"tag":67,"props":820,"children":822},{"className":821},[],[823],{"type":44,"value":824},"long_only_pm",{"type":44,"value":117},{"type":39,"tag":67,"props":827,"children":829},{"className":828},[],[830],{"type":44,"value":831},"long_short_hf",{"type":44,"value":117},{"type":39,"tag":67,"props":834,"children":836},{"className":835},[],[837],{"type":44,"value":838},"sell_side_research",{"type":44,"value":117},{"type":39,"tag":67,"props":841,"children":843},{"className":842},[],[844],{"type":44,"value":845},"etf_index_diligence",{"type":44,"value":117},{"type":39,"tag":67,"props":848,"children":850},{"className":849},[],[851],{"type":44,"value":852},"public_equity_diligence",{"type":44,"value":90},{"type":39,"tag":61,"props":855,"children":856},{},[857],{"type":44,"value":858},"PM catalyst discipline: a catalyst only matters if it can alter estimate path, narrative, multiple, position size, downside, liquidity, or event probability.",{"type":39,"tag":61,"props":860,"children":861},{},[862],{"type":44,"value":863},"Required PM judgment:",{"type":39,"tag":160,"props":865,"children":866},{},[867,880,885,890],{"type":39,"tag":164,"props":868,"children":869},{},[870,872,878],{"type":44,"value":871},"Rank by ",{"type":39,"tag":67,"props":873,"children":875},{"className":874},[],[876],{"type":44,"value":877},"decision_pressure",{"type":44,"value":879},", not date proximity alone.",{"type":39,"tag":164,"props":881,"children":882},{},[883],{"type":44,"value":884},"Add index\u002FETF and technical catalysts when relevant: index additions\u002Fdeletions, Russell\u002FS&P\u002FMSCI rebalance, ETF reconstitutions, lockups, secondary offerings, buyback windows, blackout windows, passive ownership shifts, and float changes.",{"type":39,"tag":164,"props":886,"children":887},{},[888],{"type":44,"value":889},"Separate confirmed dates from inferred windows. Do not export inferred windows as exact calendar events.",{"type":39,"tag":164,"props":891,"children":892},{},[893],{"type":44,"value":894},"Group low-impact dates as hygiene unless they are tied to a decision.",{"type":39,"tag":896,"props":897,"children":898},"style",{},[899],{"type":44,"value":900},"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":902,"total":1002},[903,922,938,950,965,978,990],{"slug":904,"name":904,"fn":905,"description":906,"org":907,"tags":908,"stars":22,"repoUrl":23,"updatedAt":921},"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},[909,912,915,918],{"name":910,"slug":911,"type":15},"Accessibility","accessibility",{"name":913,"slug":914,"type":15},"Charts","charts",{"name":916,"slug":917,"type":15},"Data Visualization","data-visualization",{"name":919,"slug":920,"type":15},"Design","design","2026-06-30T19:00:57.102",{"slug":923,"name":923,"fn":924,"description":925,"org":926,"tags":927,"stars":22,"repoUrl":23,"updatedAt":937},"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},[928,931,934],{"name":929,"slug":930,"type":15},"Creative","creative",{"name":932,"slug":933,"type":15},"Editing","editing",{"name":935,"slug":936,"type":15},"Imaging","imaging","2026-08-28T15:09:11.185865",{"slug":939,"name":939,"fn":940,"description":941,"org":942,"tags":943,"stars":22,"repoUrl":23,"updatedAt":949},"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},[944,945,946],{"name":929,"slug":930,"type":15},{"name":919,"slug":920,"type":15},{"name":947,"slug":948,"type":15},"Graphics","graphics","2026-08-28T15:09:07.42507",{"slug":951,"name":951,"fn":952,"description":953,"org":954,"tags":955,"stars":22,"repoUrl":23,"updatedAt":964},"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},[956,957,958,961],{"name":929,"slug":930,"type":15},{"name":947,"slug":948,"type":15},{"name":959,"slug":960,"type":15},"Marketing","marketing",{"name":962,"slug":963,"type":15},"Social Media","social-media","2026-08-28T15:10:07.282096",{"slug":966,"name":966,"fn":967,"description":968,"org":969,"tags":970,"stars":22,"repoUrl":23,"updatedAt":977},"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},[971,972,973,974],{"name":929,"slug":930,"type":15},{"name":919,"slug":920,"type":15},{"name":947,"slug":948,"type":15},{"name":975,"slug":976,"type":15},"Templates","templates","2026-08-28T15:10:03.050113",{"slug":979,"name":979,"fn":980,"description":981,"org":982,"tags":983,"stars":22,"repoUrl":23,"updatedAt":989},"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},[984,985,986],{"name":929,"slug":930,"type":15},{"name":932,"slug":933,"type":15},{"name":987,"slug":988,"type":15},"Video","video","2026-08-28T15:09:07.765245",{"slug":991,"name":991,"fn":992,"description":993,"org":994,"tags":995,"stars":22,"repoUrl":23,"updatedAt":1001},"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},[996,997,998],{"name":929,"slug":930,"type":15},{"name":935,"slug":936,"type":15},{"name":999,"slug":1000,"type":15},"Photography","photography","2026-08-28T15:09:10.386974",499,{"items":1004,"total":1205},[1005,1026,1049,1066,1082,1101,1120,1134,1150,1164,1176,1189],{"slug":1006,"name":1006,"fn":1007,"description":1008,"org":1009,"tags":1010,"stars":1023,"repoUrl":1024,"updatedAt":1025},"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},[1011,1014,1017,1020],{"name":1012,"slug":1013,"type":15},"Documents","documents",{"name":1015,"slug":1016,"type":15},"Healthcare","healthcare",{"name":1018,"slug":1019,"type":15},"Insurance","insurance",{"name":1021,"slug":1022,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-08-02T05:48:07.395855",{"slug":1027,"name":1027,"fn":1028,"description":1029,"org":1030,"tags":1031,"stars":1046,"repoUrl":1047,"updatedAt":1048},"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},[1032,1035,1037,1040,1043],{"name":1033,"slug":1034,"type":15},".NET","dotnet",{"name":1036,"slug":1027,"type":15},"ASP.NET Core",{"name":1038,"slug":1039,"type":15},"Blazor","blazor",{"name":1041,"slug":1042,"type":15},"C#","csharp",{"name":1044,"slug":1045,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":1050,"name":1050,"fn":1051,"description":1052,"org":1053,"tags":1054,"stars":1046,"repoUrl":1047,"updatedAt":1065},"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},[1055,1058,1061,1064],{"name":1056,"slug":1057,"type":15},"Apps SDK","apps-sdk",{"name":1059,"slug":1060,"type":15},"ChatGPT","chatgpt",{"name":1062,"slug":1063,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":1067,"name":1067,"fn":1068,"description":1069,"org":1070,"tags":1071,"stars":1046,"repoUrl":1047,"updatedAt":1081},"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},[1072,1075,1078],{"name":1073,"slug":1074,"type":15},"API Development","api-development",{"name":1076,"slug":1077,"type":15},"CLI","cli",{"name":1079,"slug":1080,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":1083,"name":1083,"fn":1084,"description":1085,"org":1086,"tags":1087,"stars":1046,"repoUrl":1047,"updatedAt":1100},"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},[1088,1091,1094,1097],{"name":1089,"slug":1090,"type":15},"Cloudflare","cloudflare",{"name":1092,"slug":1093,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":1095,"slug":1096,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":1098,"slug":1099,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":1102,"name":1102,"fn":1103,"description":1104,"org":1105,"tags":1106,"stars":1046,"repoUrl":1047,"updatedAt":1119},"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},[1107,1110,1113,1116],{"name":1108,"slug":1109,"type":15},"Productivity","productivity",{"name":1111,"slug":1112,"type":15},"Project Management","project-management",{"name":1114,"slug":1115,"type":15},"Strategy","strategy",{"name":1117,"slug":1118,"type":15},"Task Management","task-management","2026-05-23T06:17:16.870838",{"slug":1121,"name":1121,"fn":1122,"description":1123,"org":1124,"tags":1125,"stars":1046,"repoUrl":1047,"updatedAt":1133},"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},[1126,1127,1129,1132],{"name":919,"slug":920,"type":15},{"name":1128,"slug":1121,"type":15},"Figma",{"name":1130,"slug":1131,"type":15},"Frontend","frontend",{"name":1062,"slug":1063,"type":15},"2026-04-12T05:06:47.939943",{"slug":1135,"name":1135,"fn":1136,"description":1137,"org":1138,"tags":1139,"stars":1046,"repoUrl":1047,"updatedAt":1149},"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},[1140,1141,1144,1145,1146],{"name":919,"slug":920,"type":15},{"name":1142,"slug":1143,"type":15},"Design System","design-system",{"name":1128,"slug":1121,"type":15},{"name":1130,"slug":1131,"type":15},{"name":1147,"slug":1148,"type":15},"UI Components","ui-components","2026-05-10T05:59:52.971881",{"slug":1151,"name":1151,"fn":1152,"description":1153,"org":1154,"tags":1155,"stars":1046,"repoUrl":1047,"updatedAt":1163},"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},[1156,1157,1158,1161,1162],{"name":919,"slug":920,"type":15},{"name":1142,"slug":1143,"type":15},{"name":1159,"slug":1160,"type":15},"Documentation","documentation",{"name":1128,"slug":1121,"type":15},{"name":1130,"slug":1131,"type":15},"2026-05-16T06:07:47.821474",{"slug":1165,"name":1165,"fn":1166,"description":1167,"org":1168,"tags":1169,"stars":1046,"repoUrl":1047,"updatedAt":1175},"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},[1170,1171,1172,1173,1174],{"name":919,"slug":920,"type":15},{"name":1128,"slug":1121,"type":15},{"name":1130,"slug":1131,"type":15},{"name":1147,"slug":1148,"type":15},{"name":1044,"slug":1045,"type":15},"2026-05-16T06:07:40.583615",{"slug":1177,"name":1177,"fn":1178,"description":1179,"org":1180,"tags":1181,"stars":1046,"repoUrl":1047,"updatedAt":1188},"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},[1182,1185,1186,1187],{"name":1183,"slug":1184,"type":15},"Animation","animation",{"name":1079,"slug":1080,"type":15},{"name":929,"slug":930,"type":15},{"name":919,"slug":920,"type":15},"2026-05-02T05:31:48.48485",{"slug":1190,"name":1190,"fn":1191,"description":1192,"org":1193,"tags":1194,"stars":1046,"repoUrl":1047,"updatedAt":1204},"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},[1195,1196,1197,1200,1203],{"name":929,"slug":930,"type":15},{"name":919,"slug":920,"type":15},{"name":1198,"slug":1199,"type":15},"Image Generation","image-generation",{"name":1201,"slug":1202,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",578]