[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSG5VGF6S3SB6B2SA1H99E":3,"skill-same:01M7CSG5VGF6S3SB6B2SA1H99E":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":39,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M7CSG5VGF6S3SB6B2SA1H99E","earth2studio-discover",null,"Find Earth2Studio models, data sources, and examples for a weather\u002Fclimate use case. Do NOT use for writing inference code, downloading data, or installation.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fearth2studio-discover\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: earth2studio-discover\nversion: 0.16.0\nlicense: Apache-2.0\nmetadata:\n  author: NVIDIA Earth-2 Team\n  tags:\n    - earth2studio\n    - earth2\n    - python\n    - discovery\n    - models\n    - data-sources\ndescription: >\n  Find Earth2Studio models, data sources, and examples for a weather\u002Fclimate use\n  case. Do NOT use for writing inference code, downloading data, or installation.\n---\n\n# Earth2Studio Discoverability Skill\n\n## Purpose\n\nHelp users identify the right Earth2Studio models, data sources, and examples for\ntheir weather\u002Fclimate task. Use when: comparing models by GPU\u002FVRAM requirements,\nchoosing forecast class (nowcast, medium-range, seasonal), finding compatible\ndata sources via lexicons, or locating gallery examples for downscaling,\nensemble generation, or data assimilation.\n\n## Prerequisites\n\n- Internet access to fetch live documentation pages from nvidia.github.io\n- Familiarity with Earth2Studio badge system (Class, Region, VRAM, Release)\n\nYou are helping a user find the right Earth2Studio components for their use case. Your job is to understand what they want to do, then point them at the models, data sources, and examples that fit — verified against live documentation.\n\n## Core principle: discover from live docs, don't memorize\n\nEarth2Studio adds models, data sources, and examples every release. Model classes get new badges, new data sources appear, examples get reorganized. Any static list in this skill will rot.\n\n**Rules:**\n1. Always fetch the relevant live doc pages before recommending components.\n2. Use badge metadata (Region, Class, VRAM, Release) from the docs to filter candidates.\n3. Verify data-source ↔ model compatibility using the lexicon system (see Step 4).\n4. Cite doc URLs so the user can explore further.\n\n## Live doc references\n\nFetch these pages as needed (not all at once — only what the user's question requires):\n\n| Category | URL |\n|----------|-----|\n| Prognostic models | https:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002Fmodules\u002Fmodels_px.html |\n| Diagnostic models | https:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002Fmodules\u002Fmodels_dx.html |\n| Data assimilation | https:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002Fmodules\u002Fmodels_da.html |\n| Data sources (analysis) | https:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002Fmodules\u002Fdatasources_analysis.html |\n| Data sources (forecast) | https:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002Fmodules\u002Fdatasources_forecast.html |\n| Data sources (dataframe) | https:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002Fmodules\u002Fdatasources_dataframe.html |\n| Examples gallery | https:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002Fexamples\u002Findex.html |\n| Lexicon source | https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fearth2studio\u002Ftree\u002Fmain\u002Fearth2studio\u002Flexicon |\n\n## Interaction protocol\n\n### Step 1. Understand the user's problem\n\nExtract from what the user has said (ask follow-ups if needed, cap at 3 questions):\n\n- **Task type** — medium-range forecasting, nowcasting, downscaling\u002Fsuper-resolution, seasonal\u002Fsubseasonal, data assimilation, climate projection, ensemble generation, derived diagnostics\n- **Region** — global, North America, Europe, Asia, specific country\u002Farea\n- **Temporal scale** — hours ahead (nowcast), days ahead (medium-range), weeks\u002Fmonths (seasonal), climate\n- **Variables of interest** — temperature, precipitation, wind, pressure, radiation, specific levels, etc.\n- **Hardware constraints** — GPU type, available VRAM (40GB, 48GB, 80GB, 96GB)\n- **Deterministic vs. ensemble** — single forecast or probabilistic\n\nGood follow-up phrasing: *\"Are you looking for a single best-estimate forecast or an ensemble with uncertainty?\"* — not *\"what's your use case?\"*\n\n### Step 2. Fetch relevant model docs\n\nBased on the user's task type, fetch the appropriate model page(s):\n\n- Forecasting → prognostic models (px)\n- Post-processing \u002F downscaling \u002F derived variables → diagnostic models (dx)\n- Observation integration → data assimilation (da)\n- Often a workflow chains px → dx, so check both\n\nFrom the doc pages, extract for each candidate model:\n- **Class badge** — NWC, DS, MR, S2S, DA, CM\n- **Region badge** — Global, NA, EU, AS, etc.\n- **Rec VRAM badge** — minimum GPU memory\n- **Release year** — newer models generally supersede older ones in the same class\n\nFilter to models matching the user's task type, region, and hardware. Present a short-list (not the full catalog) with badge metadata.\n\n### Step 3. Fetch relevant data source docs\n\nBased on the user's data needs, fetch the appropriate data source page:\n\n- Historical reanalysis → analysis data sources\n- Real-time or operational → forecast data sources\n- Observations \u002F station data → dataframe data sources\n\nNote which data sources cover the user's region and variables.\n\n### Step 4. Verify compatibility via lexicon\n\nThis is the key technical step. Earth2Studio models declare their required input variables via `input_coords()`. Data sources expose available variables through their lexicon VOCAB. If a data source's lexicon VOCAB keys contain all variables in a model's `input_coords` (the \"variable\" dimension), they are compatible.\n\nTo verify:\n1. Check the model's doc page or source for its `input_coords` — specifically the variable list\n2. Check the data source's lexicon file at `earth2studio\u002Flexicon\u002F\u003Csource>.py` for its VOCAB keys\n3. Confirm the data source VOCAB covers all variables the model needs\n\nIf checking source code directly (e.g. user has a local clone), the lexicon files are at:\n```\nearth2studio\u002Flexicon\u002Fgfs.py\nearth2studio\u002Flexicon\u002Fhrrr.py\nearth2studio\u002Flexicon\u002Fcds.py\nearth2studio\u002Flexicon\u002Farco.py\nearth2studio\u002Flexicon\u002Fwb2.py\n... (one per data source)\n```\n\nEach defines a `VOCAB: dict[str, str | tuple]` mapping Earth2Studio variable names to source-specific identifiers.\n\nSurface compatibility results clearly: *\"GraphCastOperational needs [list of variables] — GFS and ERA5 (via ARCO\u002FCDS) both provide these, but HRRR does not cover pressure levels above X.\"*\n\n### Step 5. Suggest examples\n\nFetch the examples gallery and identify examples that demonstrate the user's workflow pattern. Examples are organized by category:\n\n- `01_getting_started` — basic deterministic, diagnostic, ensemble pipelines\n- `02_medium_range` — ensemble extension, perturbation, cyclone tracking\n- `03_downscaling` — CorrDiff, CBottle, ensemble downscaling\n- `04_nowcasting` — StormCast, StormScope\n- `05_data_assimilation` — StormCast SDA, HealDA\n- `06_seasonal` — DLESyM, statistical methods\n- `07_misc` — distributed inference, IO, custom data, generation\n- `08_extend` — building custom models, diagnostics, data sources\n\nPoint the user at the most relevant 1–3 examples as starting points. Explain what each demonstrates and how it relates to their problem.\n\n### Step 6. Return recommendations\n\nOutput structure (omit empty sections):\n\n```\n## Your use case\n[1-2 sentence restatement of what the user wants to do]\n\n## Recommended models\n| Model | Class | Region | VRAM | Why |\n|-------|-------|--------|------|-----|\n[Short-list with rationale per row]\n\n## Compatible data sources\n| Data Source | Coverage | Compatible with |\n|-------------|----------|-----------------|\n[Verified via lexicon]\n\n## Relevant examples\n- [Example name](link) — what it demonstrates\n\n## Next steps\n[What to install, what to read next]\n```\n\nKeep recommendations to 2–4 models maximum. If multiple options exist, explain the tradeoff (accuracy vs. speed, deterministic vs. ensemble, VRAM, etc.) rather than listing everything.\n\n## Limitations\n\n- Recommendations are only as current as the live docs; unreleased models are not discoverable.\n- Badge metadata may be incomplete for newly added models.\n- Lexicon compatibility checks require source code access for full accuracy; doc-only checks are approximate.\n\n## Troubleshooting\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Model page returns 404 | URL changed after a release | Check https:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002F for updated navigation |\n| Lexicon file not found | Data source is new or renamed | Search `earth2studio\u002Flexicon\u002F` directory for current filenames |\n| Badge missing from model | Model docs not yet updated | Fall back to the model's source code `__init__` or README for specs |\n\n## Ownership and out-of-scope\n\n**Owns:** component discovery, model\u002Fdata-source compatibility checking, badge-based filtering, example recommendation, hardware-fit assessment.\n\n**Does not own:** installation (use earth2studio-install skill), writing inference code, model training, custom model development, runtime debugging, PhysicsNeMo model discovery.\n","# Earth2Studio Discoverability Skill\n\n## Purpose\n\nHelp users identify the right Earth2Studio models, data sources, and examples for\ntheir weather\u002Fclimate task. Use when: comparing models by GPU\u002FVRAM requirements,\nchoosing forecast class (nowcast, medium-range, seasonal), finding compatible\ndata sources via lexicons, or locating gallery examples for downscaling,\nensemble generation, or data assimilation.\n\n## Prerequisites\n\n- Internet access to fetch live documentation pages from nvidia.github.io\n- Familiarity with Earth2Studio badge system (Class, Region, VRAM, Release)\n\nYou are helping a user find the right Earth2Studio components for their use case. Your job is to understand what they want to do, then point them at the models, data sources, and examples that fit — verified against live documentation.\n\n## Core principle: discover from live docs, don't memorize\n\nEarth2Studio adds models, data sources, and examples every release. Model classes get new badges, new data sources appear, examples get reorganized. Any static list in this skill will rot.\n\n**Rules:**\n1. Always fetch the relevant live doc pages before recommending components.\n2. Use badge metadata (Region, Class, VRAM, Release) from the docs to filter candidates.\n3. Verify data-source ↔ model compatibility using the lexicon system (see Step 4).\n4. Cite doc URLs so the user can explore further.\n\n## Live doc references\n\nFetch these pages as needed (not all at once — only what the user's question requires):\n\n| Category | URL |\n|----------|-----|\n| Prognostic models | https:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002Fmodules\u002Fmodels_px.html |\n| Diagnostic models | https:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002Fmodules\u002Fmodels_dx.html |\n| Data assimilation | https:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002Fmodules\u002Fmodels_da.html |\n| Data sources (analysis) | https:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002Fmodules\u002Fdatasources_analysis.html |\n| Data sources (forecast) | https:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002Fmodules\u002Fdatasources_forecast.html |\n| Data sources (dataframe) | https:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002Fmodules\u002Fdatasources_dataframe.html |\n| Examples gallery | https:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002Fexamples\u002Findex.html |\n| Lexicon source | https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fearth2studio\u002Ftree\u002Fmain\u002Fearth2studio\u002Flexicon |\n\n## Interaction protocol\n\n### Step 1. Understand the user's problem\n\nExtract from what the user has said (ask follow-ups if needed, cap at 3 questions):\n\n- **Task type** — medium-range forecasting, nowcasting, downscaling\u002Fsuper-resolution, seasonal\u002Fsubseasonal, data assimilation, climate projection, ensemble generation, derived diagnostics\n- **Region** — global, North America, Europe, Asia, specific country\u002Farea\n- **Temporal scale** — hours ahead (nowcast), days ahead (medium-range), weeks\u002Fmonths (seasonal), climate\n- **Variables of interest** — temperature, precipitation, wind, pressure, radiation, specific levels, etc.\n- **Hardware constraints** — GPU type, available VRAM (40GB, 48GB, 80GB, 96GB)\n- **Deterministic vs. ensemble** — single forecast or probabilistic\n\nGood follow-up phrasing: *\"Are you looking for a single best-estimate forecast or an ensemble with uncertainty?\"* — not *\"what's your use case?\"*\n\n### Step 2. Fetch relevant model docs\n\nBased on the user's task type, fetch the appropriate model page(s):\n\n- Forecasting → prognostic models (px)\n- Post-processing \u002F downscaling \u002F derived variables → diagnostic models (dx)\n- Observation integration → data assimilation (da)\n- Often a workflow chains px → dx, so check both\n\nFrom the doc pages, extract for each candidate model:\n- **Class badge** — NWC, DS, MR, S2S, DA, CM\n- **Region badge** — Global, NA, EU, AS, etc.\n- **Rec VRAM badge** — minimum GPU memory\n- **Release year** — newer models generally supersede older ones in the same class\n\nFilter to models matching the user's task type, region, and hardware. Present a short-list (not the full catalog) with badge metadata.\n\n### Step 3. Fetch relevant data source docs\n\nBased on the user's data needs, fetch the appropriate data source page:\n\n- Historical reanalysis → analysis data sources\n- Real-time or operational → forecast data sources\n- Observations \u002F station data → dataframe data sources\n\nNote which data sources cover the user's region and variables.\n\n### Step 4. Verify compatibility via lexicon\n\nThis is the key technical step. Earth2Studio models declare their required input variables via `input_coords()`. Data sources expose available variables through their lexicon VOCAB. If a data source's lexicon VOCAB keys contain all variables in a model's `input_coords` (the \"variable\" dimension), they are compatible.\n\nTo verify:\n1. Check the model's doc page or source for its `input_coords` — specifically the variable list\n2. Check the data source's lexicon file at `earth2studio\u002Flexicon\u002F\u003Csource>.py` for its VOCAB keys\n3. Confirm the data source VOCAB covers all variables the model needs\n\nIf checking source code directly (e.g. user has a local clone), the lexicon files are at:\n```\nearth2studio\u002Flexicon\u002Fgfs.py\nearth2studio\u002Flexicon\u002Fhrrr.py\nearth2studio\u002Flexicon\u002Fcds.py\nearth2studio\u002Flexicon\u002Farco.py\nearth2studio\u002Flexicon\u002Fwb2.py\n... (one per data source)\n```\n\nEach defines a `VOCAB: dict[str, str | tuple]` mapping Earth2Studio variable names to source-specific identifiers.\n\nSurface compatibility results clearly: *\"GraphCastOperational needs [list of variables] — GFS and ERA5 (via ARCO\u002FCDS) both provide these, but HRRR does not cover pressure levels above X.\"*\n\n### Step 5. Suggest examples\n\nFetch the examples gallery and identify examples that demonstrate the user's workflow pattern. Examples are organized by category:\n\n- `01_getting_started` — basic deterministic, diagnostic, ensemble pipelines\n- `02_medium_range` — ensemble extension, perturbation, cyclone tracking\n- `03_downscaling` — CorrDiff, CBottle, ensemble downscaling\n- `04_nowcasting` — StormCast, StormScope\n- `05_data_assimilation` — StormCast SDA, HealDA\n- `06_seasonal` — DLESyM, statistical methods\n- `07_misc` — distributed inference, IO, custom data, generation\n- `08_extend` — building custom models, diagnostics, data sources\n\nPoint the user at the most relevant 1–3 examples as starting points. Explain what each demonstrates and how it relates to their problem.\n\n### Step 6. Return recommendations\n\nOutput structure (omit empty sections):\n\n```\n## Your use case\n[1-2 sentence restatement of what the user wants to do]\n\n## Recommended models\n| Model | Class | Region | VRAM | Why |\n|-------|-------|--------|------|-----|\n[Short-list with rationale per row]\n\n## Compatible data sources\n| Data Source | Coverage | Compatible with |\n|-------------|----------|-----------------|\n[Verified via lexicon]\n\n## Relevant examples\n- [Example name](link) — what it demonstrates\n\n## Next steps\n[What to install, what to read next]\n```\n\nKeep recommendations to 2–4 models maximum. If multiple options exist, explain the tradeoff (accuracy vs. speed, deterministic vs. ensemble, VRAM, etc.) rather than listing everything.\n\n## Limitations\n\n- Recommendations are only as current as the live docs; unreleased models are not discoverable.\n- Badge metadata may be incomplete for newly added models.\n- Lexicon compatibility checks require source code access for full accuracy; doc-only checks are approximate.\n\n## Troubleshooting\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Model page returns 404 | URL changed after a release | Check https:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002F for updated navigation |\n| Lexicon file not found | Data source is new or renamed | Search `earth2studio\u002Flexicon\u002F` directory for current filenames |\n| Badge missing from model | Model docs not yet updated | Fall back to the model's source code `__init__` or README for specs |\n\n## Ownership and out-of-scope\n\n**Owns:** component discovery, model\u002Fdata-source compatibility checking, badge-based filtering, example recommendation, hardware-fit assessment.\n\n**Does not own:** installation (use earth2studio-install skill), writing inference code, model training, custom model development, runtime debugging, PhysicsNeMo model discovery.\n",{"name":5,"license":15,"version":24,"metadata":25,"description":7},"0.16.0",{"tags":26,"author":33},[27,28,29,30,31,32],"earth2studio","earth2","python","discovery","models","data-sources","NVIDIA Earth-2 Team","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fearth2studio-discover",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill earth2studio-discover",{"tool":49,"command":50},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill earth2studio-discover",{"tool":52,"command":53},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill earth2studio-discover","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fearth2studio-discover\u002FSKILL.md",true,[57,63,67,71],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"BENCHMARK.md","REFERENCE","参考文档",3988,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fearth2studio-discover\u002FBENCHMARK.md",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"evals\u002Fevals.json",4918,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fearth2studio-discover\u002Fevals\u002Fevals.json",{"path":68,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":69,"sourceHtmlUrl":70},"skill-card.md",4093,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fearth2studio-discover\u002Fskill-card.md",{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"skill.oms.sig","OTHER","其他",4597,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fearth2studio-discover\u002Fskill.oms.sig",[78,86,93,100,107,114],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]