[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BJX0AV1KX8CWH66B320HFV":3,"skill-same:01M7BJX0AV1KX8CWH66B320HFV":71},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":33,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7BJX0AV1KX8CWH66B320HFV","mcore-testing",null,"Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.","YYC-Cube\u002FYYC3-AI-Agent-Archive","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79K9J2WD44BBY4662XKNZRB",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Fskills-hub\u002Fai-ml\u002Fnvidia-skills\u002Fskills\u002Fmcore-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mcore-testing\ndescription: Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.\ncategory: development-code\nversion: 1.0.0\nlicense: Apache-2.0\nwhen_to_use: Adding or running a unit or functional test; understanding the test layout; writing a recipe YAML; downloading or updating golden values; reproducing a test failure locally; 'how do I add a test', 'run unit tests', 'pytest fails', 'test layout', 'golden values', 'recipe YAML', 'marker filter'.\nmetadata:\n  author: Philip Petrakian \u003Cppetrakian@nvidia.com>\n---\n\n# Testing Guide\n\n---\n\n## Answer-First Testing Facts\n\nFor questions about disabling tests without deleting them:\n\n- Functional recipe entries stay in YAML; disable by suffixing scope with\n  `-broken`, for example `scope: [mr-github]` -> `scope: [mr-github-broken]`.\n- Unit-test skips use pytest markers instead: `@pytest.mark.flaky_in_dev` skips\n  in the default dev environment, and `@pytest.mark.flaky` skips in LTS.\n- Do not delete the test case or recipe entry when the goal is discoverability\n  and easy re-enable.\n\n---\n\n## Test Layout\n\n```text\ntests\u002F\n├── unit_tests\u002F          # pytest, 1 node × 8 GPUs, torch.distributed runner\n├── functional_tests\u002F    # end-to-end shell + training scripts\n│   └── test_cases\u002F\n│       └── {model}\u002F{test_case}\u002F\n│           ├── model_config.yaml          # training args\n│           └── golden_values_{env}_{platform}.json\n└── test_utils\u002F\n    ├── recipes\u002F\n    │   ├── h100\u002F        # YAML recipes for H100 jobs\n    │   └── gb200\u002F       # YAML recipes for GB200 jobs\n    └── python_scripts\u002F  # helpers (recipe_parser, golden-value download, …)\n```\n\n---\n\n## How Tests Execute\n\nThe GitHub Actions runner invokes `launch_nemo_run_workload.py`, which uses\n**nemo-run** to launch a `DockerExecutor` container. The repo is bind-mounted\nat `\u002Fopt\u002Fmegatron-lm`; training data is mounted at `\u002Fmnt\u002Fartifacts`.\n\n**Unit tests** are dispatched through `torch.distributed.run`:\n\n- Ranks 0 and 3 are tee-d to stdout; all other ranks write only to log files.\n- Per-rank log files land at `{assets_dir}\u002Flogs\u002F1\u002F` and are uploaded as a\n  GitHub artifact after the run.\n\n**Functional tests** are driven by\n`tests\u002Ffunctional_tests\u002Fshell_test_utils\u002Frun_ci_test.sh`. Only rank 0 runs the\npytest validation step; training output from all ranks is uploaded as an artifact.\n\n**Flaky-failure auto-retry**: `launch_nemo_run_workload.py` retries up to\n**3 times** for known transient patterns (NCCL timeout, ECC error, segfault,\nHuggingFace connectivity, …) before declaring a genuine failure.\n\n---\n\n## Recipe YAML Structure\n\nRecipes live in `tests\u002Ftest_utils\u002Frecipes\u002F` and are parsed by\n`tests\u002Ftest_utils\u002Fpython_scripts\u002Frecipe_parser.py`. Each file expands a\ncartesian `products` block into individual workload specs:\n\n```yaml\ntype: basic\nformat_version: 1\nmaintainers: [mcore]\nloggers: [stdout]\nspec:\n  name: \"{test_case}_{environment}_{platforms}\"\n  model: gpt              # maps to tests\u002Ffunctional_tests\u002Ftest_cases\u002F{model}\u002F\n  build: mcore-pyt-{environment}\n  nodes: 1\n  gpus: 8\n  n_repeat: 5\n  platforms: dgx_h100\n  time_limit: 1800\n  script_setup: |\n    ...\n  script: |-\n    bash tests\u002Ffunctional_tests\u002Fshell_test_utils\u002Frun_ci_test.sh ...\nproducts:\n  - test_case: [my_test]\n    products:\n      - environment: [dev, lts]\n        scope: [mr-github]\n        platforms: [dgx_h100]\n```\n\nKey runtime placeholders: `{assets_dir}`, `{artifacts_dir}`, `{test_case}`,\n`{environment}`, `{platforms}`, `{n_repeat}`.\n\n### Disabling a Test Without Deleting It\n\nTo temporarily disable a test case in a recipe YAML, suffix its `scope` value\nwith `-broken` — **do not delete the entry**:\n\n```yaml\n# before (test runs in CI)\nscope: [mr-github]\n\n# after (test is skipped; entry preserved for easy re-enable)\nscope: [mr-github-broken]\n```\n\n---\n\n## Running Unit Tests Locally\n\nAll unit tests initialize a `torch.distributed` group, so every invocation\nrequires GPU access and must go through `torch.distributed.run`:\n\n```bash\n# Full suite\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests\n\n# Single file\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests\u002Fmodels\u002Ftest_gpt_model.py\n\n# Single test\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests\u002Fmodels\u002Ftest_gpt_model.py::TestGPTModel::test_constructor\n\n# Filter by name substring\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests -k optimizer\n```\n\n### Marker filters\n\n```bash\n# Exclude flaky tests during development\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests -m \"not flaky and not flaky_in_dev\"\n\n# Include experimental tests\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests --experimental\n```\n\n### CI parity\n\nUse `tests\u002Funit_tests\u002Frun_ci_test.sh` to reproduce a CI bucket failure exactly.\nFor ad-hoc runs, prefer the direct `torch.distributed.run` invocations above.\n\n### Gotchas\n\n- `pyproject.toml` sets `addopts = --durations=15 -s -rA` — stdout is not\n  captured (`-s`), so ranks interleave during multi-rank runs. Override with\n  `--capture=fd` when debugging a specific rank.\n- `tests\u002Funit_tests\u002Fconftest.py` looks for test data under `\u002Fopt\u002Fdata` and\n  attempts a download if missing. Supply it manually or skip data-dependent\n  tests when running outside the canonical container.\n\n---\n\n## Adding a Unit Test\n\n1. Create `tests\u002Funit_tests\u002F\u003Ccategory>\u002Ftest_\u003Cname>.py`.\n2. Use fixtures from `tests\u002Funit_tests\u002Fconftest.py`.\n3. Apply markers as needed:\n   - `@pytest.mark.internal` — skipped on `legacy` tag\n   - `@pytest.mark.flaky_in_dev` — skipped in `dev` environment (CI default; use this to disable a flaky test without blocking the standard pipeline)\n   - `@pytest.mark.flaky` — skipped in `lts` environment\n   - `@pytest.mark.experimental` — `latest` tag only\n4. Verify locally (see Running Unit Tests Locally above).\n5. If the test needs a dedicated CI bucket, add an entry to\n   `tests\u002Ftest_utils\u002Frecipes\u002Fh100\u002Funit-tests.yaml`.\n\n---\n\n## Adding a Functional \u002F Integration Test\n\n1. Create `tests\u002Ffunctional_tests\u002Ftest_cases\u002F\u003Cmodel>\u002F\u003Ctest_name>\u002F`.\n2. Write `model_config.yaml` with `MODEL_ARGS`, `ENV_VARS`, and `TEST_TYPE`.\n3. Add a YAML recipe under `tests\u002Ftest_utils\u002Frecipes\u002Fh100\u002F` (and `gb200\u002F` if\n   needed). Required fields: `scope`, `environment`, `platform`, `n_repeat`,\n   `time_limit`.\n4. Push the PR, add the label **\"Run functional tests\"** to trigger a full run.\n5. After a successful run, download golden values:\n\n   ```bash\n   python tests\u002Ftest_utils\u002Fpython_scripts\u002Fdownload_golden_values.py \\\n     --source github --pipeline-id \u003Crun-id>\n   ```\n\n6. Commit the downloaded golden values.\n\n---\n\n## Common Pitfalls\n\n| Problem | Cause | Fix |\n|---------|-------|-----|\n| Test passes locally but fails in CI | Different environment or data path | Check `DATA_PATH`, `DATA_CACHE_PATH`, and the `environment` tag (`dev` vs `lts`) |\n| Golden value mismatch after a code change | Numerical regression | Download new golden values via `download_golden_values.py` after a clean run |\n| `cicd-integration-tests-gb200` not triggered | GB200 jobs require maintainer status | Ask a maintainer to trigger, or add the `Run functional tests` label |\n","# Testing Guide\n\n---\n\n## Answer-First Testing Facts\n\nFor questions about disabling tests without deleting them:\n\n- Functional recipe entries stay in YAML; disable by suffixing scope with\n  `-broken`, for example `scope: [mr-github]` -> `scope: [mr-github-broken]`.\n- Unit-test skips use pytest markers instead: `@pytest.mark.flaky_in_dev` skips\n  in the default dev environment, and `@pytest.mark.flaky` skips in LTS.\n- Do not delete the test case or recipe entry when the goal is discoverability\n  and easy re-enable.\n\n---\n\n## Test Layout\n\n```text\ntests\u002F\n├── unit_tests\u002F          # pytest, 1 node × 8 GPUs, torch.distributed runner\n├── functional_tests\u002F    # end-to-end shell + training scripts\n│   └── test_cases\u002F\n│       └── {model}\u002F{test_case}\u002F\n│           ├── model_config.yaml          # training args\n│           └── golden_values_{env}_{platform}.json\n└── test_utils\u002F\n    ├── recipes\u002F\n    │   ├── h100\u002F        # YAML recipes for H100 jobs\n    │   └── gb200\u002F       # YAML recipes for GB200 jobs\n    └── python_scripts\u002F  # helpers (recipe_parser, golden-value download, …)\n```\n\n---\n\n## How Tests Execute\n\nThe GitHub Actions runner invokes `launch_nemo_run_workload.py`, which uses\n**nemo-run** to launch a `DockerExecutor` container. The repo is bind-mounted\nat `\u002Fopt\u002Fmegatron-lm`; training data is mounted at `\u002Fmnt\u002Fartifacts`.\n\n**Unit tests** are dispatched through `torch.distributed.run`:\n\n- Ranks 0 and 3 are tee-d to stdout; all other ranks write only to log files.\n- Per-rank log files land at `{assets_dir}\u002Flogs\u002F1\u002F` and are uploaded as a\n  GitHub artifact after the run.\n\n**Functional tests** are driven by\n`tests\u002Ffunctional_tests\u002Fshell_test_utils\u002Frun_ci_test.sh`. Only rank 0 runs the\npytest validation step; training output from all ranks is uploaded as an artifact.\n\n**Flaky-failure auto-retry**: `launch_nemo_run_workload.py` retries up to\n**3 times** for known transient patterns (NCCL timeout, ECC error, segfault,\nHuggingFace connectivity, …) before declaring a genuine failure.\n\n---\n\n## Recipe YAML Structure\n\nRecipes live in `tests\u002Ftest_utils\u002Frecipes\u002F` and are parsed by\n`tests\u002Ftest_utils\u002Fpython_scripts\u002Frecipe_parser.py`. Each file expands a\ncartesian `products` block into individual workload specs:\n\n```yaml\ntype: basic\nformat_version: 1\nmaintainers: [mcore]\nloggers: [stdout]\nspec:\n  name: \"{test_case}_{environment}_{platforms}\"\n  model: gpt              # maps to tests\u002Ffunctional_tests\u002Ftest_cases\u002F{model}\u002F\n  build: mcore-pyt-{environment}\n  nodes: 1\n  gpus: 8\n  n_repeat: 5\n  platforms: dgx_h100\n  time_limit: 1800\n  script_setup: |\n    ...\n  script: |-\n    bash tests\u002Ffunctional_tests\u002Fshell_test_utils\u002Frun_ci_test.sh ...\nproducts:\n  - test_case: [my_test]\n    products:\n      - environment: [dev, lts]\n        scope: [mr-github]\n        platforms: [dgx_h100]\n```\n\nKey runtime placeholders: `{assets_dir}`, `{artifacts_dir}`, `{test_case}`,\n`{environment}`, `{platforms}`, `{n_repeat}`.\n\n### Disabling a Test Without Deleting It\n\nTo temporarily disable a test case in a recipe YAML, suffix its `scope` value\nwith `-broken` — **do not delete the entry**:\n\n```yaml\n# before (test runs in CI)\nscope: [mr-github]\n\n# after (test is skipped; entry preserved for easy re-enable)\nscope: [mr-github-broken]\n```\n\n---\n\n## Running Unit Tests Locally\n\nAll unit tests initialize a `torch.distributed` group, so every invocation\nrequires GPU access and must go through `torch.distributed.run`:\n\n```bash\n# Full suite\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests\n\n# Single file\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests\u002Fmodels\u002Ftest_gpt_model.py\n\n# Single test\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests\u002Fmodels\u002Ftest_gpt_model.py::TestGPTModel::test_constructor\n\n# Filter by name substring\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests -k optimizer\n```\n\n### Marker filters\n\n```bash\n# Exclude flaky tests during development\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests -m \"not flaky and not flaky_in_dev\"\n\n# Include experimental tests\nuv run python -m torch.distributed.run --nproc-per-node 8 -m pytest -q \\\n  tests\u002Funit_tests --experimental\n```\n\n### CI parity\n\nUse `tests\u002Funit_tests\u002Frun_ci_test.sh` to reproduce a CI bucket failure exactly.\nFor ad-hoc runs, prefer the direct `torch.distributed.run` invocations above.\n\n### Gotchas\n\n- `pyproject.toml` sets `addopts = --durations=15 -s -rA` — stdout is not\n  captured (`-s`), so ranks interleave during multi-rank runs. Override with\n  `--capture=fd` when debugging a specific rank.\n- `tests\u002Funit_tests\u002Fconftest.py` looks for test data under `\u002Fopt\u002Fdata` and\n  attempts a download if missing. Supply it manually or skip data-dependent\n  tests when running outside the canonical container.\n\n---\n\n## Adding a Unit Test\n\n1. Create `tests\u002Funit_tests\u002F\u003Ccategory>\u002Ftest_\u003Cname>.py`.\n2. Use fixtures from `tests\u002Funit_tests\u002Fconftest.py`.\n3. Apply markers as needed:\n   - `@pytest.mark.internal` — skipped on `legacy` tag\n   - `@pytest.mark.flaky_in_dev` — skipped in `dev` environment (CI default; use this to disable a flaky test without blocking the standard pipeline)\n   - `@pytest.mark.flaky` — skipped in `lts` environment\n   - `@pytest.mark.experimental` — `latest` tag only\n4. Verify locally (see Running Unit Tests Locally above).\n5. If the test needs a dedicated CI bucket, add an entry to\n   `tests\u002Ftest_utils\u002Frecipes\u002Fh100\u002Funit-tests.yaml`.\n\n---\n\n## Adding a Functional \u002F Integration Test\n\n1. Create `tests\u002Ffunctional_tests\u002Ftest_cases\u002F\u003Cmodel>\u002F\u003Ctest_name>\u002F`.\n2. Write `model_config.yaml` with `MODEL_ARGS`, `ENV_VARS`, and `TEST_TYPE`.\n3. Add a YAML recipe under `tests\u002Ftest_utils\u002Frecipes\u002Fh100\u002F` (and `gb200\u002F` if\n   needed). Required fields: `scope`, `environment`, `platform`, `n_repeat`,\n   `time_limit`.\n4. Push the PR, add the label **\"Run functional tests\"** to trigger a full run.\n5. After a successful run, download golden values:\n\n   ```bash\n   python tests\u002Ftest_utils\u002Fpython_scripts\u002Fdownload_golden_values.py \\\n     --source github --pipeline-id \u003Crun-id>\n   ```\n\n6. Commit the downloaded golden values.\n\n---\n\n## Common Pitfalls\n\n| Problem | Cause | Fix |\n|---------|-------|-----|\n| Test passes locally but fails in CI | Different environment or data path | Check `DATA_PATH`, `DATA_CACHE_PATH`, and the `environment` tag (`dev` vs `lts`) |\n| Golden value mismatch after a code change | Numerical regression | Download new golden values via `download_golden_values.py` after a clean run |\n| `cicd-integration-tests-gb200` not triggered | GB200 jobs require maintainer status | Ask a maintainer to trigger, or add the `Run functional tests` label |\n",{"name":5,"license":15,"version":24,"category":25,"metadata":26,"description":7,"when_to_use":28},"1.0.0","development-code",{"author":27},"Philip Petrakian \u003Cppetrakian@nvidia.com>","Adding or running a unit or functional test; understanding the test layout; writing a recipe YAML; downloading or updating golden values; reproducing a test failure locally; 'how do I add a test', 'run unit tests', 'pytest fails', 'test layout', 'golden values', 'recipe YAML', 'marker filter'.","main","d591030ef9fb1bbcebed3454aa5c2dcb8d608f69","skills-hub\u002Fai-ml\u002Fnvidia-skills\u002Fskills\u002Fmcore-testing","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive","https:\u002F\u002Fai-agent.yyc3.vip\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-13 22:26:14",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add YYC-Cube\u002FYYC3-AI-Agent-Archive --skill mcore-testing",{"tool":43,"command":44},"bunx","bunx skills add YYC-Cube\u002FYYC3-AI-Agent-Archive --skill mcore-testing",{"tool":46,"command":47},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-AI-Agent-Archive --skill mcore-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Fskills-hub\u002Fai-ml\u002Fnvidia-skills\u002Fskills\u002Fmcore-testing\u002FSKILL.md",true,[51,57,61,65],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"BENCHMARK.md","REFERENCE","参考文档",2747,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Fskills-hub\u002Fai-ml\u002Fnvidia-skills\u002Fskills\u002Fmcore-testing\u002FBENCHMARK.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"evals\u002Fevals.json",3,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Fskills-hub\u002Fai-ml\u002Fnvidia-skills\u002Fskills\u002Fmcore-testing\u002Fevals\u002Fevals.json",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"skill-card.md",2533,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Fskills-hub\u002Fai-ml\u002Fnvidia-skills\u002Fskills\u002Fmcore-testing\u002Fskill-card.md",{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"skill.oms.sig","OTHER","其他",4585,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Fskills-hub\u002Fai-ml\u002Fnvidia-skills\u002Fskills\u002Fmcore-testing\u002Fskill.oms.sig",[72,80,87,94,101,109],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7BTB92RE8MT5YE706QBNDTQ","yingmi-skill","当用户需要查询基金、策略、公告、财经资讯，做资产配置、组合诊断、风险回测、现金流分析，或生成图表、PDF 时，优先使用本 Skill 获取真实数据与可执行能力。","MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Ftools-hub\u002Fcode-ide\u002Fskills-marketplace\u002Fskills\u002Fyingmi-skill\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7BT7ZYR091HPJYEFNWVTEJJ","web-access","所有联网操作必须通过此 skill 处理，包括：搜索、网页抓取、登录后操作、网络交互等。","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Ftools-hub\u002Fcode-ide\u002Fskills-marketplace\u002Fskills\u002Fweb-access\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7BT4NKS0DNP8A53M1BGGZR2","tencentmap-map-assistant","腾讯位置服务·地图助手 Skill，一句自然语言调用腾讯地图全套能力，无需开发者账号、开箱即用。提供 AI 旅游攻略、地点搜索（含评分\u002F人均\u002F营业时间）、关键词提示、路线规划（驾车\u002F步行\u002F公交\u002F骑行）、地址解析与逆解析、行政区划、IP 定位、距离计算、天气查询，并可将行程或多 POI 渲染成网页地图。涉及找地点、规划路线、旅游行程、查天气、坐标转换等出行场景时使用。","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Ftools-hub\u002Fcode-ide\u002Fskills-marketplace\u002Fskills\u002Ftencentmap-map-assistant\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7BSWKV1T5XYYRGV4W4JP88C","skill-scanner","Scan any agent skill for security risks before you install or use it. Powered by Tencent Zhuque Lab A.I.G (AI-Infra-Guard). 100% local static analysis — no file contents or credentials leave your device. Compatible with CodeBuddy, Cursor, Windsurf, Claude Code, OpenClaw and more. Triggers on: 这个 skill 安全吗, skill 安全扫描, 检查 skill 安全, audit skill, scan skill, check skill safety, analyze skill, inspect skill, verify skill, skill security, skill supply chain. Do NOT trigger for general agent usage, full system health checks, project debugging, or normal development.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Ftools-hub\u002Fcode-ide\u002Fskills-marketplace\u002Fskills\u002Fskill-scanner\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7BSWGTCFW7F123S4BM4XY6W","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends agent capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Ftools-hub\u002Fcode-ide\u002Fskills-marketplace\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Ftools-hub\u002Fcode-ide\u002Fskills-marketplace\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M7BSVV4DH8JK2ZMQSCW25VCD","shader-dev","Comprehensive GLSL shader techniques for creating stunning visual effects — ray marching, SDF modeling, fluid simulation, particle systems, procedural generation, lighting, post-processing, and more.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-AI-Agent-Archive\u002Fblob\u002Fmain\u002Ftools-hub\u002Fcode-ide\u002Fskills-marketplace\u002Fskills\u002Fshader-dev\u002FSKILL.md",[],[]]