[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FAJCZJP9SWD2MFAHPBEA4P":3,"skill-same:01M7FAJCZJP9SWD2MFAHPBEA4P":62},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":47},"01M7FAJCZJP9SWD2MFAHPBEA4P","training-evaluation",null,"Guides safe MapTR training and chamfer-evaluation command construction, preflight validation, checkpoint handling, reproducibility, and resource-aware recovery.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fmaptr\u002Fsub-skills\u002Ftraining-evaluation\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: training-evaluation\ndescription: \"Guides safe MapTR training and chamfer-evaluation command\n  construction, preflight validation, checkpoint handling, reproducibility, and\n  resource-aware recovery.\"\ndisable-model-invocation: true\nmetadata:\n  disco-role: operating\nlicense: MIT\n---\n\n# MapTR Training And Evaluation\n\nUse this sub-skill to construct and review commands for MapTR training or\nvector-map evaluation. It is deliberately conservative: prove inputs and\nbackend readiness before starting GPU work, prefer dry runs, and never infer\nthat a documented command succeeded on the current system.\n\n## Scope And Evidence Status\n\nThis guidance covers the MapTR `main` behavior represented by commit\n`a6872d8d9670bde17b4b01560f1221f88b443d55`:\n\n- single-process and one-node distributed training;\n- one-node distributed test\u002Fevaluation with the MapTR `chamfer` metric;\n- work directories, seeds, deterministic mode, resume, FP16 configuration,\n  checkpoints, result directories, and failure recovery.\n\nThe project documents Python 3.8, PyTorch 1.9.1 with CUDA 11.1,\n`mmcv-full==1.4.0`, `mmdet==2.14.0`, `mmsegmentation==0.14.1`, the bundled\nmmdetection3d 0.17.2 code, and a compiled GeometryKernelAttention extension.\nThose are **documented compatibility targets**, not proof that a current host\ncan import the plugin or run its CUDA kernels. Full data, checkpoints,\ntraining, evaluation, and the custom extension were not executed while this\nskill was produced.\n\n## Route First\n\n- For nuScenes\u002FAV2 download, conversion, annotation files, and directory\n  layouts, route to `data-preparation`.\n- For architecture selection, BEV\u002Fquery settings, losses, or config authoring,\n  route to `model-configuration`.\n- For image\u002Fvideo rendering, qualitative output, or log plotting, route to\n  `visualization-benchmarking`.\n- Stay here for command semantics, launch sizing, metric selection,\n  checkpoint\u002Foutput behavior, and run-time troubleshooting.\n\n## Required Run Contract\n\nBefore constructing a launch, obtain all of these values. Keep an unknown as a\nstop condition rather than filling it with a guess.\n\n1. **Intent:** train, resume training, or evaluate.\n2. **Config:** exact MapTR config and any `--cfg-options` overrides.\n3. **Data:** dataset family and proof that every configured annotation\u002Fmap file\n   and camera asset exists.\n4. **Weights:** required backbone initialization for a new run, or the exact\n   resume\u002Fevaluation checkpoint.\n5. **Backend:** compatible legacy OpenMMLab stack, CUDA, `mmcv-full` ops, and\n   GeometryKernelAttention import\u002Fbuild evidence.\n6. **Resources:** visible GPU count, memory per GPU, requested process count,\n   storage, wall-time, and scheduler rules.\n7. **Outputs:** unique `--work-dir`, checkpoint retention plan, and evaluation\n   result location.\n8. **Reproducibility:** seed, deterministic policy, final merged config, source\n   revision, and environment inventory.\n\nRead [workflows.md](references\u002Fworkflows.md) for complete gates, commands, and\nexpected observations. Read [cli-reference.md](references\u002Fcli-reference.md)\nbefore adding flags or overrides.\n\n## Safe Command Procedure\n\n### 1. Stop Before Compute\n\nFrom the MapTR project root, run only parser\u002Fconfig checks first:\n\n```bash\npython tools\u002Ftrain.py --help\npython tools\u002Ftest.py --help\npython tools\u002Fmisc\u002Fprint_config.py projects\u002Fconfigs\u002Fmaptr\u002Fmaptr_tiny_r50_24e.py\n```\n\nThe config print should show `plugin=True`, MapTR dataset\u002Fmodel types,\n`evaluation.metric='chamfer'`, and resolved data\u002Fcheckpoint paths. Printing a\nconfig does not import the plugin, read all data, build CUDA extensions, or\nprove training readiness.\n\nDo not proceed when a path is missing, an override is unclear, requested GPUs\nexceed visible GPUs, the config\u002Fcheckpoint pairing is unverified, or a required\nCUDA\u002Fcustom-op probe has not passed.\n\n### 2. Select The Smallest Launch\n\nFor a supported single-process training attempt:\n\n```bash\npython tools\u002Ftrain.py CONFIG.py \\\n  --work-dir work_dirs\u002FRUN_ID \\\n  --gpus 1 --seed 42 --deterministic --launcher none\n```\n\nFor one-node distributed training, use the bundled validator from this\nsub-skill directory. It prints a command by default and starts nothing:\n\n```bash\npython scripts\u002Flaunch_distributed.py train \\\n  --project-root MAPTR_ROOT --config projects\u002Fconfigs\u002Fmaptr\u002FCONFIG.py \\\n  --gpus N -- --work-dir work_dirs\u002FRUN_ID --seed 42\n```\n\nFor evaluation, use the same validator even with one GPU. The checked-in test\nentry point intentionally rejects `--launcher none`:\n\n```bash\npython scripts\u002Flaunch_distributed.py test \\\n  --project-root MAPTR_ROOT --config projects\u002Fconfigs\u002Fmaptr\u002FCONFIG.py \\\n  --checkpoint work_dirs\u002FRUN_ID\u002Fepoch_N.pth --gpus N\n```\n\nThe test command appends `--eval chamfer`. Never substitute the generic\n3D-detection `bbox` launcher for MapTR. The vector-map datasets accept\n`chamfer` and `iou`; project train\u002Feval instructions and MapTR configs use\n`chamfer`.\n\nReview [launch_distributed.py](scripts\u002Flaunch_distributed.py), then add\n`--execute` only after its dry-run output and warnings pass human review.\nExecution can allocate GPUs and run for hours.\n\n### 3. Preserve Run Evidence\n\nA training work directory should receive the merged config, timestamped text\nlog, logger outputs, and checkpoints such as `epoch_1.pth` according to\n`checkpoint_config.interval`. MapTR 24-epoch configs normally evaluate every\ntwo epochs and save every epoch. Confirm actual config values rather than\nassuming those intervals for another config.\n\nChamfer evaluation should print per-class AP at thresholds 0.5, 1.0, and 1.5,\nplus `NuscMap_chamfer\u002FmAP`-style detail keys, and write formatted predictions\nbelow a timestamped `test\u002F\u003Cconfig-name>\u002F` directory. Treat those as expected\nshapes only, not benchmark claims.\n\nRecord the exact command, `CUDA_VISIBLE_DEVICES`, seed, deterministic flag,\nmerged config, checkpoint identity, environment versions, and complete log.\nDo not compare scores from different configs, class maps, point sampling, data\nversions, or checkpoints as if they were equivalent.\n\n## High-Risk Semantics\n\n- `--resume-from` restores training state; a nonexistent path is silently not\n  applied by the training entry point. Validate it before launch.\n- A backbone `pretrained` path initializes a new model; it is not a training\n  resume checkpoint. `load_from` loads weights without promising optimizer and\n  epoch continuity.\n- Most MapTR configs enable static FP16 with `loss_scale=512`. Confirm the\n  merged config and backend support. Do not add a second AMP mechanism.\n- The distributed training wrapper forces deterministic mode. Determinism may\n  reduce speed and does not guarantee bitwise identity across different GPU,\n  driver, CUDA, library, or process-count combinations.\n- `tools\u002Ftest.py --out` is parsed but reaches an intentional assertion instead\n  of dumping predictions. `--show`\u002F`--show-dir` are not forwarded through its\n  distributed test path. Route artifact visualization elsewhere.\n\n## Recovery\n\nUse [troubleshooting.md](references\u002Ftroubleshooting.md) for symptoms, causes,\nrecovery, and explicit stop conditions. In particular:\n\n- `metric bbox is not supported` → replace `--eval bbox` with\n  `--eval chamfer`; do not reinterpret a detector metric as a map metric.\n- eight requested processes with one visible GPU → stop and use `--gpus 1`, or\n  move to a proven eight-GPU host; never oversubscribe silently.\n- resume\u002Fconfig mismatch → stop, locate the config dumped beside the\n  checkpoint, reconcile its model\u002Fdata\u002Fclass\u002Foptimizer\u002Frunner settings, and\n  resume with that config or start a clearly new run.\n\nDo not run merely to discover whether a prerequisite was satisfied. If\nconfiguration, data, checkpoint provenance, backend compatibility, GPU count,\nor budget remains unresolved, return a blocked preflight with the missing\nevidence and the next safe probe.\n","# MapTR Training And Evaluation\n\nUse this sub-skill to construct and review commands for MapTR training or\nvector-map evaluation. It is deliberately conservative: prove inputs and\nbackend readiness before starting GPU work, prefer dry runs, and never infer\nthat a documented command succeeded on the current system.\n\n## Scope And Evidence Status\n\nThis guidance covers the MapTR `main` behavior represented by commit\n`a6872d8d9670bde17b4b01560f1221f88b443d55`:\n\n- single-process and one-node distributed training;\n- one-node distributed test\u002Fevaluation with the MapTR `chamfer` metric;\n- work directories, seeds, deterministic mode, resume, FP16 configuration,\n  checkpoints, result directories, and failure recovery.\n\nThe project documents Python 3.8, PyTorch 1.9.1 with CUDA 11.1,\n`mmcv-full==1.4.0`, `mmdet==2.14.0`, `mmsegmentation==0.14.1`, the bundled\nmmdetection3d 0.17.2 code, and a compiled GeometryKernelAttention extension.\nThose are **documented compatibility targets**, not proof that a current host\ncan import the plugin or run its CUDA kernels. Full data, checkpoints,\ntraining, evaluation, and the custom extension were not executed while this\nskill was produced.\n\n## Route First\n\n- For nuScenes\u002FAV2 download, conversion, annotation files, and directory\n  layouts, route to `data-preparation`.\n- For architecture selection, BEV\u002Fquery settings, losses, or config authoring,\n  route to `model-configuration`.\n- For image\u002Fvideo rendering, qualitative output, or log plotting, route to\n  `visualization-benchmarking`.\n- Stay here for command semantics, launch sizing, metric selection,\n  checkpoint\u002Foutput behavior, and run-time troubleshooting.\n\n## Required Run Contract\n\nBefore constructing a launch, obtain all of these values. Keep an unknown as a\nstop condition rather than filling it with a guess.\n\n1. **Intent:** train, resume training, or evaluate.\n2. **Config:** exact MapTR config and any `--cfg-options` overrides.\n3. **Data:** dataset family and proof that every configured annotation\u002Fmap file\n   and camera asset exists.\n4. **Weights:** required backbone initialization for a new run, or the exact\n   resume\u002Fevaluation checkpoint.\n5. **Backend:** compatible legacy OpenMMLab stack, CUDA, `mmcv-full` ops, and\n   GeometryKernelAttention import\u002Fbuild evidence.\n6. **Resources:** visible GPU count, memory per GPU, requested process count,\n   storage, wall-time, and scheduler rules.\n7. **Outputs:** unique `--work-dir`, checkpoint retention plan, and evaluation\n   result location.\n8. **Reproducibility:** seed, deterministic policy, final merged config, source\n   revision, and environment inventory.\n\nRead [workflows.md](references\u002Fworkflows.md) for complete gates, commands, and\nexpected observations. Read [cli-reference.md](references\u002Fcli-reference.md)\nbefore adding flags or overrides.\n\n## Safe Command Procedure\n\n### 1. Stop Before Compute\n\nFrom the MapTR project root, run only parser\u002Fconfig checks first:\n\n```bash\npython tools\u002Ftrain.py --help\npython tools\u002Ftest.py --help\npython tools\u002Fmisc\u002Fprint_config.py projects\u002Fconfigs\u002Fmaptr\u002Fmaptr_tiny_r50_24e.py\n```\n\nThe config print should show `plugin=True`, MapTR dataset\u002Fmodel types,\n`evaluation.metric='chamfer'`, and resolved data\u002Fcheckpoint paths. Printing a\nconfig does not import the plugin, read all data, build CUDA extensions, or\nprove training readiness.\n\nDo not proceed when a path is missing, an override is unclear, requested GPUs\nexceed visible GPUs, the config\u002Fcheckpoint pairing is unverified, or a required\nCUDA\u002Fcustom-op probe has not passed.\n\n### 2. Select The Smallest Launch\n\nFor a supported single-process training attempt:\n\n```bash\npython tools\u002Ftrain.py CONFIG.py \\\n  --work-dir work_dirs\u002FRUN_ID \\\n  --gpus 1 --seed 42 --deterministic --launcher none\n```\n\nFor one-node distributed training, use the bundled validator from this\nsub-skill directory. It prints a command by default and starts nothing:\n\n```bash\npython scripts\u002Flaunch_distributed.py train \\\n  --project-root MAPTR_ROOT --config projects\u002Fconfigs\u002Fmaptr\u002FCONFIG.py \\\n  --gpus N -- --work-dir work_dirs\u002FRUN_ID --seed 42\n```\n\nFor evaluation, use the same validator even with one GPU. The checked-in test\nentry point intentionally rejects `--launcher none`:\n\n```bash\npython scripts\u002Flaunch_distributed.py test \\\n  --project-root MAPTR_ROOT --config projects\u002Fconfigs\u002Fmaptr\u002FCONFIG.py \\\n  --checkpoint work_dirs\u002FRUN_ID\u002Fepoch_N.pth --gpus N\n```\n\nThe test command appends `--eval chamfer`. Never substitute the generic\n3D-detection `bbox` launcher for MapTR. The vector-map datasets accept\n`chamfer` and `iou`; project train\u002Feval instructions and MapTR configs use\n`chamfer`.\n\nReview [launch_distributed.py](scripts\u002Flaunch_distributed.py), then add\n`--execute` only after its dry-run output and warnings pass human review.\nExecution can allocate GPUs and run for hours.\n\n### 3. Preserve Run Evidence\n\nA training work directory should receive the merged config, timestamped text\nlog, logger outputs, and checkpoints such as `epoch_1.pth` according to\n`checkpoint_config.interval`. MapTR 24-epoch configs normally evaluate every\ntwo epochs and save every epoch. Confirm actual config values rather than\nassuming those intervals for another config.\n\nChamfer evaluation should print per-class AP at thresholds 0.5, 1.0, and 1.5,\nplus `NuscMap_chamfer\u002FmAP`-style detail keys, and write formatted predictions\nbelow a timestamped `test\u002F\u003Cconfig-name>\u002F` directory. Treat those as expected\nshapes only, not benchmark claims.\n\nRecord the exact command, `CUDA_VISIBLE_DEVICES`, seed, deterministic flag,\nmerged config, checkpoint identity, environment versions, and complete log.\nDo not compare scores from different configs, class maps, point sampling, data\nversions, or checkpoints as if they were equivalent.\n\n## High-Risk Semantics\n\n- `--resume-from` restores training state; a nonexistent path is silently not\n  applied by the training entry point. Validate it before launch.\n- A backbone `pretrained` path initializes a new model; it is not a training\n  resume checkpoint. `load_from` loads weights without promising optimizer and\n  epoch continuity.\n- Most MapTR configs enable static FP16 with `loss_scale=512`. Confirm the\n  merged config and backend support. Do not add a second AMP mechanism.\n- The distributed training wrapper forces deterministic mode. Determinism may\n  reduce speed and does not guarantee bitwise identity across different GPU,\n  driver, CUDA, library, or process-count combinations.\n- `tools\u002Ftest.py --out` is parsed but reaches an intentional assertion instead\n  of dumping predictions. `--show`\u002F`--show-dir` are not forwarded through its\n  distributed test path. Route artifact visualization elsewhere.\n\n## Recovery\n\nUse [troubleshooting.md](references\u002Ftroubleshooting.md) for symptoms, causes,\nrecovery, and explicit stop conditions. In particular:\n\n- `metric bbox is not supported` → replace `--eval bbox` with\n  `--eval chamfer`; do not reinterpret a detector metric as a map metric.\n- eight requested processes with one visible GPU → stop and use `--gpus 1`, or\n  move to a proven eight-GPU host; never oversubscribe silently.\n- resume\u002Fconfig mismatch → stop, locate the config dumped beside the\n  checkpoint, reconcile its model\u002Fdata\u002Fclass\u002Foptimizer\u002Frunner settings, and\n  resume with that config or start a clearly new run.\n\nDo not run merely to discover whether a prerequisite was satisfied. If\nconfiguration, data, checkpoint provenance, backend compatibility, GPU count,\nor budget remains unresolved, return a blocked preflight with the missing\nevidence and the next safe probe.\n",{"name":5,"license":15,"metadata":24,"description":7,"disable-model-invocation":26},{"disco-role":25},"operating",true,"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","06-前端与设计\u002Fmaptr\u002Fsub-skills\u002Ftraining-evaluation",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":26},[37,40,43],{"tool":38,"command":39},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill training-evaluation",{"tool":41,"command":42},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill training-evaluation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill training-evaluation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fmaptr\u002Fsub-skills\u002Ftraining-evaluation\u002FSKILL.md",[48,54,58],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fcli-reference.md","REFERENCE","参考文档",8227,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fmaptr\u002Fsub-skills\u002Ftraining-evaluation\u002Freferences\u002Fcli-reference.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Ftroubleshooting.md",10211,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fmaptr\u002Fsub-skills\u002Ftraining-evaluation\u002Freferences\u002Ftroubleshooting.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fworkflows.md",12236,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fmaptr\u002Fsub-skills\u002Ftraining-evaluation\u002Freferences\u002Fworkflows.md",[63,70,75,82,89,96],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":71,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]