[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78HWPSS1DMXYVG0HGXK7W8H":3,"skill-same:01M78HWPSS1DMXYVG0HGXK7W8H":74},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":13,"repositoryHtmlUrl":36,"repositoryHomepageUrl":37,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M78HWPSS1DMXYVG0HGXK7W8H","earth2studio-data-fetch",null,"Fetch weather\u002Fclimate data via Earth2Studio data sources for specific variables and times. Do NOT use for inference pipelines, model discovery, or installation.","matheussluzz\u002FZeuZ-Agent","matheussluzz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F209255758?v=4","01M78HKHH1D1ASC9KC9BG583DH","01M78HKHHP6W7XRXQM2SBCAM3R",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmatheussluzz\u002FZeuZ-Agent\u002Fblob\u002Fmain\u002Fcatalog\u002Fbundles\u002Fnvidia\u002Fearth2studio-data-fetch\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: earth2studio-data-fetch\nversion: 0.16.0\nlicense: Apache-2.0\nmetadata:\n  author: NVIDIA Earth-2 Team\n  tags:\n    - earth2studio\n    - earth2\n    - python\n    - data-fetch\n    - weather-data\n    - xarray\ndescription: >\n  Fetch weather\u002Fclimate data via Earth2Studio data sources for specific variables\n  and times. Do NOT use for inference pipelines, model discovery, or installation.\n---\n\n# Earth2Studio Data Fetch Skill\n\n## Purpose\n\nGuide a user through downloading weather\u002Fclimate data via Earth2Studio data source\nAPIs. Identifies compatible sources by checking the lexicon, verifies variable\nsupport, and produces a working fetch script outputting an xarray DataArray.\n\n## Prerequisites\n\n- Earth2Studio installed (`uv pip install earth2studio` or equivalent)\n- Network access to remote data stores (GCS, S3, CDS API, etc.)\n- For CDS-based sources: valid CDS API key configured (`~\u002F.cdsapirc`)\n- Python 3.10+\n\n## Instructions\n\nYou are helping a user download specific weather\u002Fclimate data using\nEarth2Studio's data source APIs. Your job is to identify which data source(s)\ncan provide the requested variables, verify compatibility via the lexicon\nsystem, and produce a working fetch script.\n\n### Core principle: live docs and lexicon are the source of truth\n\nData source APIs, available variables, and the lexicon evolve between releases.\nBefore recommending a data source or writing a fetch script:\n\n1. **Fetch the relevant data source doc page** to confirm the API signature\n   and constructor arguments.\n2. **Check the lexicon** to verify the requested variable is supported by\n   that data source.\n\nLive doc references (fetch only what the user's request requires):\n\n- **Analysis data sources:**\n  \u003Chttps:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002Fmodules\u002Fdatasources_analysis.html>\n- **Forecast data sources:**\n  \u003Chttps:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002Fmodules\u002Fdatasources_forecast.html>\n- **DataFrame data sources:**\n  \u003Chttps:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002Fmodules\u002Fdatasources_dataframe.html>\n- **Lexicon base:**\n  \u003Chttps:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fearth2studio\u002Fblob\u002Fmain\u002Fearth2studio\u002Flexicon\u002Fbase.py>\n- **Lexicon per-source:**\n  \u003Chttps:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fearth2studio\u002Ftree\u002Fmain\u002Fearth2studio\u002Flexicon>\n\n### Interaction protocol\n\n#### Step 1. Understand the user's request\n\nExtract from what the user has said (ask follow-ups if needed, cap at 3\nquestions):\n\n- **Variables** — what do they want? Use Earth2Studio variable names\n  (e.g. `t2m`, `u500`, `z850`, `tp`, `msl`). If the user uses plain language\n  (\"500 hPa geopotential height\"), map it to the E2Studio name by checking\n  the live `base.py` E2STUDIO_VOCAB.\n- **Time** — what date\u002Ftime range? A single timestamp, a range, or multiple\n  discrete times?\n- **Data type** — analysis\u002Freanalysis (historical state) or forecast (lead-time based)?\n- **Lead time** (forecast only) — how far ahead? Which initialization time?\n- **Region** — global or regional (e.g. North America for HRRR)?\n- **Output format** — xarray DataArray (default), save to file (NetCDF\u002FZarr)?\n\n#### Step 2. Identify candidate data sources\n\nBased on the request type, narrow candidates:\n\n**Analysis\u002Freanalysis** (historical state at a specific time):\n\n- Use analysis data source page to identify options\n- Common choices: GFS (operational, recent), HRRR (NA, hourly),\n  IFS\u002FIFS_ENS (ECMWF), ARCO\u002FCDS\u002FWB2ERA5\u002FNCAR_ERA5 (ERA5 reanalysis),\n  GOES\u002FMRMS\u002FJPSS (observational)\n\n**Forecast** (predictions from an initialization time with lead times):\n\n- Use forecast data source page to identify options\n- Common choices: GFS_FX, GEFS_FX, HRRR_FX, IFS_FX, IFS_ENS_FX,\n  AIFS_FX, CFS_FX\n\nKey differentiators to surface:\n\n- **Temporal coverage** — operational sources (GFS, HRRR) have limited\n  history; reanalysis (ERA5 via ARCO\u002FCDS\u002FWB2) goes back decades\n- **Spatial resolution** — HRRR is 3km NA-only; GFS is 0.25° global;\n  WB2ERA5_32x64 is 5.625° global\n- **Update frequency** — some are real-time, some have multi-day lag\n\n#### Step 3. Verify variable support via lexicon\n\nThis is critical. Each data source has a lexicon file that defines which\nE2Studio variables it can provide.\n\nTo verify:\n\n1. Fetch the source's lexicon file from\n   `https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fearth2studio\u002Fblob\u002Fmain\u002Fearth2studio\u002Flexicon\u002F\u003Csource>.py`\n   (e.g. `gfs.py`, `hrrr.py`, `cds.py`, `arco.py`, `wb2.py`)\n2. Check that the user's requested variable(s) appear as keys in the\n   source's `VOCAB` dict\n3. If a variable is NOT in a source's lexicon, that source cannot provide\n   it — try another\n\nThe lexicon VOCAB maps Earth2Studio variable names → source-specific\nidentifiers. If a variable key exists in the VOCAB, the source supports it.\n\nPresent the results clearly: *\"GFS supports `t2m`, `u500`, `z850`. HRRR also\nsupports these but is limited to North America. ARCO (ERA5) supports all\nthree and has data back to 1959.\"*\n\n#### Step 4. Confirm data source selection with user\n\nPresent the viable options with tradeoffs:\n\n| Source | Variables | Coverage | Resolution | Time Range |\n|--------|-----------|----------|------------|------------|\n| ... | ... | ... | ... | ... |\n\nLet the user pick. If there's one obvious choice, recommend it and ask for\nconfirmation.\n\n#### Step 5. Generate fetch script\n\nWrite a Python script that uses the selected data source to fetch the\nrequested data. The script structure depends on whether it's an analysis or\nforecast source.\n\n**Analysis source pattern:**\n\n```python\nimport datetime\nfrom earth2studio.data import \u003CSourceClass>\n\n# Initialize data source\nds = \u003CSourceClass>()\n\n# Fetch data\n# Analysis sources use: ds(time, variable) -> xr.DataArray\ntime = [datetime.datetime(YYYY, M, D, H)]  # or array of times\nvariable = [\"var1\", \"var2\"]  # E2Studio variable names\n\ndata = ds(time, variable)\n```\n\n**Forecast source pattern:**\n\n```python\nimport datetime\nfrom earth2studio.data import \u003CSourceClass>\n\n# Initialize data source\nds = \u003CSourceClass>()\n\n# Forecast sources use: ds(time, lead_time, variable) -> xr.DataArray\ntime = [datetime.datetime(YYYY, M, D, H)]  # initialization time\nlead_time = [datetime.timedelta(hours=H)]   # or array of lead times\nvariable = [\"var1\", \"var2\"]\n\ndata = ds(time, lead_time, variable)\n```\n\nAlways fetch the specific data source's API doc page to confirm the exact\nconstructor arguments and call signature before writing the script — they can\nvary (some need auth tokens, cache paths, specific parameters).\n\nInclude in the script:\n\n- Appropriate imports\n- Clear comments explaining each step\n- How to inspect the result (`print(data)`, `data.shape`, `data.coords`)\n- Optional: saving to file if the user requested it\n\n#### Step 6. Offer next steps\n\nAfter delivering the script, mention:\n\n- How to change variables\u002Ftimes without rewriting the whole thing\n- If they might want to feed this into a model, point them to the\n  discover skill\n- Cache behavior (data is cached locally after first fetch via\n  `EARTH2STUDIO_CACHE`)\n\n### Ownership and out-of-scope\n\n**Owns:** identifying data sources for a user's variable\u002Ftime request,\nverifying variable support via lexicon, generating data fetch scripts,\nexplaining analysis vs. forecast source differences.\n\n**Does not own:** installation (earth2studio-install), model selection\n(earth2studio-discover), inference pipelines, custom data source creation\n(point to extend examples), data source authentication setup beyond what\nthe docs describe.\n\n## Examples\n\nTypical invocation:\n\n> \"I need 500 hPa geopotential height and 2m temperature from ERA5\n> for January 1, 2020 at 00Z.\"\n\nThe skill would:\n\n1. Map plain language → `z500`, `t2m`\n2. Check ARCO\u002FCDS\u002FWB2ERA5 lexicons for support\n3. Recommend ARCO (free, no API key) or CDS (official, needs key)\n4. Generate a fetch script using the selected source\n\n## Limitations\n\n- **Network required** — all data sources fetch from remote stores\n  (GCS, S3, CDS API)\n- **No local file loading** — for local NetCDF\u002FZarr, use\n  `DataArrayFile`\u002F`DataSetFile` directly\n- **One source type per script** — cannot mix analysis and forecast\n  sources in a single call\n- **Variable availability varies** — not all sources provide all\n  variables; always verify via lexicon\n- **Rate limits** — CDS API has queue-based throttling; GCS\u002FS3 sources\n  are generally faster\n\n## Troubleshooting\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| `KeyError: '\u003Cvar>'` | Not in lexicon | Check lexicon; try another source |\n| `FileNotFoundError` \u002F 404 | Time not available | Verify temporal coverage |\n| `CDS API timeout` | Queue congestion | Retry or use ARCO for ERA5 |\n| `ModuleNotFoundError` | Not installed | `uv pip install earth2studio` |\n| Empty DataArray | Time\u002Fvar mismatch | Check datetime and variable name |\n","# Earth2Studio Data Fetch Skill\n\n## Purpose\n\nGuide a user through downloading weather\u002Fclimate data via Earth2Studio data source\nAPIs. Identifies compatible sources by checking the lexicon, verifies variable\nsupport, and produces a working fetch script outputting an xarray DataArray.\n\n## Prerequisites\n\n- Earth2Studio installed (`uv pip install earth2studio` or equivalent)\n- Network access to remote data stores (GCS, S3, CDS API, etc.)\n- For CDS-based sources: valid CDS API key configured (`~\u002F.cdsapirc`)\n- Python 3.10+\n\n## Instructions\n\nYou are helping a user download specific weather\u002Fclimate data using\nEarth2Studio's data source APIs. Your job is to identify which data source(s)\ncan provide the requested variables, verify compatibility via the lexicon\nsystem, and produce a working fetch script.\n\n### Core principle: live docs and lexicon are the source of truth\n\nData source APIs, available variables, and the lexicon evolve between releases.\nBefore recommending a data source or writing a fetch script:\n\n1. **Fetch the relevant data source doc page** to confirm the API signature\n   and constructor arguments.\n2. **Check the lexicon** to verify the requested variable is supported by\n   that data source.\n\nLive doc references (fetch only what the user's request requires):\n\n- **Analysis data sources:**\n  \u003Chttps:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002Fmodules\u002Fdatasources_analysis.html>\n- **Forecast data sources:**\n  \u003Chttps:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002Fmodules\u002Fdatasources_forecast.html>\n- **DataFrame data sources:**\n  \u003Chttps:\u002F\u002Fnvidia.github.io\u002Fearth2studio\u002Fmodules\u002Fdatasources_dataframe.html>\n- **Lexicon base:**\n  \u003Chttps:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fearth2studio\u002Fblob\u002Fmain\u002Fearth2studio\u002Flexicon\u002Fbase.py>\n- **Lexicon per-source:**\n  \u003Chttps:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fearth2studio\u002Ftree\u002Fmain\u002Fearth2studio\u002Flexicon>\n\n### Interaction protocol\n\n#### Step 1. Understand the user's request\n\nExtract from what the user has said (ask follow-ups if needed, cap at 3\nquestions):\n\n- **Variables** — what do they want? Use Earth2Studio variable names\n  (e.g. `t2m`, `u500`, `z850`, `tp`, `msl`). If the user uses plain language\n  (\"500 hPa geopotential height\"), map it to the E2Studio name by checking\n  the live `base.py` E2STUDIO_VOCAB.\n- **Time** — what date\u002Ftime range? A single timestamp, a range, or multiple\n  discrete times?\n- **Data type** — analysis\u002Freanalysis (historical state) or forecast (lead-time based)?\n- **Lead time** (forecast only) — how far ahead? Which initialization time?\n- **Region** — global or regional (e.g. North America for HRRR)?\n- **Output format** — xarray DataArray (default), save to file (NetCDF\u002FZarr)?\n\n#### Step 2. Identify candidate data sources\n\nBased on the request type, narrow candidates:\n\n**Analysis\u002Freanalysis** (historical state at a specific time):\n\n- Use analysis data source page to identify options\n- Common choices: GFS (operational, recent), HRRR (NA, hourly),\n  IFS\u002FIFS_ENS (ECMWF), ARCO\u002FCDS\u002FWB2ERA5\u002FNCAR_ERA5 (ERA5 reanalysis),\n  GOES\u002FMRMS\u002FJPSS (observational)\n\n**Forecast** (predictions from an initialization time with lead times):\n\n- Use forecast data source page to identify options\n- Common choices: GFS_FX, GEFS_FX, HRRR_FX, IFS_FX, IFS_ENS_FX,\n  AIFS_FX, CFS_FX\n\nKey differentiators to surface:\n\n- **Temporal coverage** — operational sources (GFS, HRRR) have limited\n  history; reanalysis (ERA5 via ARCO\u002FCDS\u002FWB2) goes back decades\n- **Spatial resolution** — HRRR is 3km NA-only; GFS is 0.25° global;\n  WB2ERA5_32x64 is 5.625° global\n- **Update frequency** — some are real-time, some have multi-day lag\n\n#### Step 3. Verify variable support via lexicon\n\nThis is critical. Each data source has a lexicon file that defines which\nE2Studio variables it can provide.\n\nTo verify:\n\n1. Fetch the source's lexicon file from\n   `https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fearth2studio\u002Fblob\u002Fmain\u002Fearth2studio\u002Flexicon\u002F\u003Csource>.py`\n   (e.g. `gfs.py`, `hrrr.py`, `cds.py`, `arco.py`, `wb2.py`)\n2. Check that the user's requested variable(s) appear as keys in the\n   source's `VOCAB` dict\n3. If a variable is NOT in a source's lexicon, that source cannot provide\n   it — try another\n\nThe lexicon VOCAB maps Earth2Studio variable names → source-specific\nidentifiers. If a variable key exists in the VOCAB, the source supports it.\n\nPresent the results clearly: *\"GFS supports `t2m`, `u500`, `z850`. HRRR also\nsupports these but is limited to North America. ARCO (ERA5) supports all\nthree and has data back to 1959.\"*\n\n#### Step 4. Confirm data source selection with user\n\nPresent the viable options with tradeoffs:\n\n| Source | Variables | Coverage | Resolution | Time Range |\n|--------|-----------|----------|------------|------------|\n| ... | ... | ... | ... | ... |\n\nLet the user pick. If there's one obvious choice, recommend it and ask for\nconfirmation.\n\n#### Step 5. Generate fetch script\n\nWrite a Python script that uses the selected data source to fetch the\nrequested data. The script structure depends on whether it's an analysis or\nforecast source.\n\n**Analysis source pattern:**\n\n```python\nimport datetime\nfrom earth2studio.data import \u003CSourceClass>\n\n# Initialize data source\nds = \u003CSourceClass>()\n\n# Fetch data\n# Analysis sources use: ds(time, variable) -> xr.DataArray\ntime = [datetime.datetime(YYYY, M, D, H)]  # or array of times\nvariable = [\"var1\", \"var2\"]  # E2Studio variable names\n\ndata = ds(time, variable)\n```\n\n**Forecast source pattern:**\n\n```python\nimport datetime\nfrom earth2studio.data import \u003CSourceClass>\n\n# Initialize data source\nds = \u003CSourceClass>()\n\n# Forecast sources use: ds(time, lead_time, variable) -> xr.DataArray\ntime = [datetime.datetime(YYYY, M, D, H)]  # initialization time\nlead_time = [datetime.timedelta(hours=H)]   # or array of lead times\nvariable = [\"var1\", \"var2\"]\n\ndata = ds(time, lead_time, variable)\n```\n\nAlways fetch the specific data source's API doc page to confirm the exact\nconstructor arguments and call signature before writing the script — they can\nvary (some need auth tokens, cache paths, specific parameters).\n\nInclude in the script:\n\n- Appropriate imports\n- Clear comments explaining each step\n- How to inspect the result (`print(data)`, `data.shape`, `data.coords`)\n- Optional: saving to file if the user requested it\n\n#### Step 6. Offer next steps\n\nAfter delivering the script, mention:\n\n- How to change variables\u002Ftimes without rewriting the whole thing\n- If they might want to feed this into a model, point them to the\n  discover skill\n- Cache behavior (data is cached locally after first fetch via\n  `EARTH2STUDIO_CACHE`)\n\n### Ownership and out-of-scope\n\n**Owns:** identifying data sources for a user's variable\u002Ftime request,\nverifying variable support via lexicon, generating data fetch scripts,\nexplaining analysis vs. forecast source differences.\n\n**Does not own:** installation (earth2studio-install), model selection\n(earth2studio-discover), inference pipelines, custom data source creation\n(point to extend examples), data source authentication setup beyond what\nthe docs describe.\n\n## Examples\n\nTypical invocation:\n\n> \"I need 500 hPa geopotential height and 2m temperature from ERA5\n> for January 1, 2020 at 00Z.\"\n\nThe skill would:\n\n1. Map plain language → `z500`, `t2m`\n2. Check ARCO\u002FCDS\u002FWB2ERA5 lexicons for support\n3. Recommend ARCO (free, no API key) or CDS (official, needs key)\n4. Generate a fetch script using the selected source\n\n## Limitations\n\n- **Network required** — all data sources fetch from remote stores\n  (GCS, S3, CDS API)\n- **No local file loading** — for local NetCDF\u002FZarr, use\n  `DataArrayFile`\u002F`DataSetFile` directly\n- **One source type per script** — cannot mix analysis and forecast\n  sources in a single call\n- **Variable availability varies** — not all sources provide all\n  variables; always verify via lexicon\n- **Rate limits** — CDS API has queue-based throttling; GCS\u002FS3 sources\n  are generally faster\n\n## Troubleshooting\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| `KeyError: '\u003Cvar>'` | Not in lexicon | Check lexicon; try another source |\n| `FileNotFoundError` \u002F 404 | Time not available | Verify temporal coverage |\n| `CDS API timeout` | Queue congestion | Retry or use ARCO for ERA5 |\n| `ModuleNotFoundError` | Not installed | `uv pip install earth2studio` |\n| Empty DataArray | Time\u002Fvar mismatch | Check datetime and variable name |\n",{"name":5,"license":14,"version":23,"metadata":24,"description":7},"0.16.0",{"tags":25,"author":32},[26,27,28,29,30,31],"earth2studio","earth2","python","data-fetch","weather-data","xarray","NVIDIA Earth-2 Team","main","fc4f2c7759ae400c66cd38656db70ead882a0d08","catalog\u002Fbundles\u002Fnvidia\u002Fearth2studio-data-fetch","https:\u002F\u002Fgithub.com\u002Fmatheussluzz\u002FZeuZ-Agent","https:\u002F\u002Fgithub.com\u002Fmatheussluzz\u002FZeuZ-Agent#readme","https:\u002F\u002Fgithub.com\u002Fmatheussluzz","2026-08-27 05:21:51",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add matheussluzz\u002FZeuZ-Agent --skill earth2studio-data-fetch",{"tool":46,"command":47},"bunx","bunx skills add matheussluzz\u002FZeuZ-Agent --skill earth2studio-data-fetch",{"tool":49,"command":50},"pnpm","pnpm dlx skills add matheussluzz\u002FZeuZ-Agent --skill earth2studio-data-fetch","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmatheussluzz\u002FZeuZ-Agent\u002Fblob\u002Fmain\u002Fcatalog\u002Fbundles\u002Fnvidia\u002Fearth2studio-data-fetch\u002FSKILL.md",true,[54,60,64,70],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"BENCHMARK.md","REFERENCE","参考文档",3702,"https:\u002F\u002Fgithub.com\u002Fmatheussluzz\u002FZeuZ-Agent\u002Fblob\u002Fmain\u002Fcatalog\u002Fbundles\u002Fnvidia\u002Fearth2studio-data-fetch\u002FBENCHMARK.md",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"skill-card.md",3953,"https:\u002F\u002Fgithub.com\u002Fmatheussluzz\u002FZeuZ-Agent\u002Fblob\u002Fmain\u002Fcatalog\u002Fbundles\u002Fnvidia\u002Fearth2studio-data-fetch\u002Fskill-card.md",{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"skill.oms.sig","OTHER","其他",5329,"https:\u002F\u002Fgithub.com\u002Fmatheussluzz\u002FZeuZ-Agent\u002Fblob\u002Fmain\u002Fcatalog\u002Fbundles\u002Fnvidia\u002Fearth2studio-data-fetch\u002Fskill.oms.sig",{"path":71,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":72,"sourceHtmlUrl":73},"zeuz.manifest.yaml",172,"https:\u002F\u002Fgithub.com\u002Fmatheussluzz\u002FZeuZ-Agent\u002Fblob\u002Fmain\u002Fcatalog\u002Fbundles\u002Fnvidia\u002Fearth2studio-data-fetch\u002Fzeuz.manifest.yaml",[75,83,90,97,104,111],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M78JQ2R0QR8H2Z6662RFX804","gamma","Fixture skill gamma for discovery benchmarks.","MIT","https:\u002F\u002Fgithub.com\u002Fmatheussluzz\u002FZeuZ-Agent\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fskill-registry-mini\u002Fskills\u002Fgamma\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M78JQ1KCVZ15APZG3FFF29K0","beta","Fixture skill beta for discovery benchmarks.","https:\u002F\u002Fgithub.com\u002Fmatheussluzz\u002FZeuZ-Agent\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fskill-registry-mini\u002Fskills\u002Fbeta\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M78JQ0FJTK4Q9JKZMX9SVSEN","alpha","Fixture skill alpha for discovery benchmarks.","https:\u002F\u002Fgithub.com\u002Fmatheussluzz\u002FZeuZ-Agent\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fskill-registry-mini\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M78JPYVYPY7R8QS10KADQPWE","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fmatheussluzz\u002FZeuZ-Agent\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":18},"01M78JPVYHB88RF5ATZVGX84RR","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fmatheussluzz\u002FZeuZ-Agent\u002Fblob\u002Fmain\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":18},"01M78JPSSWNTZW89DWGJTX7716","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Fmatheussluzz\u002FZeuZ-Agent\u002Fblob\u002Fmain\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]