--- name: ad-accuracy-debug-a3537d1b373f description: > Debug AutoDeploy accuracy regressions vs a reference score (PyTorch backend or published baseline). Use when an AutoDeploy model's eval score is significantly below the reference and the root cause is unknown. license: Apache-2.0 tags: - tensorrt-llm - autodeploy - accuracy - debugging - evaluation metadata: author: NVIDIA Corporation --- # AutoDeploy Accuracy Debugging ## Where this skill applies This file is part of **trtllm-agent-toolkit**. Paths such as `tensorrt_llm/`, `tests/`, and `examples/auto_deploy/` are relative to a **TensorRT-LLM source checkout** on the user's machine, not the plugin repository. ## Related skills in this plugin - `trtllm-agent-toolkit:ad-graph-dump` — inspect per-transform FX graph snapshots when Phase 2 suggests a transform was applied incorrectly or is corrupting activations. - `trtllm-agent-toolkit:ad-conf-check` — verify that precision or config settings (FP8, sharding, chunked prefill, etc.) were actually applied at runtime before attributing an accuracy gap to a kernel or weight bug. **Input:** model name, failing accuracy score, reference score, eval task (e.g. MMLU, GSM8K). **Output:** identified root cause, minimal reproducer, and a code fix. ## Situation Assessment Before debugging, confirm: 1. **What is the reference score?** Is it from the PyTorch backend test, a published leaderboard, or set manually? 2. **How large is the gap?** A 1-2% gap may be within statistical noise; a 5%+ gap is a real bug. 3. **Is the eval framework itself suspect?** Run the same eval on the PyTorch backend to validate the harness before blaming AutoDeploy. ## Abbreviations - **AD** — AutoDeploy, TRT-LLM with `_autodeploy` backend - **PT** — PyTorch, TRT-LLM with `pytorch` backend (manual deployment) ## Phase 0 — Validate the Test Harness Run the equivalent PyTorch backend test on the same model and same eval task. If PT also fails or scores lower than expected, the issue is in the eval framework (prompt format, chat template, sampling params), not AD-specific. Key things to verify in the eval harness: - **Prompt format / `apply_chat_template`**: does the evaluator send raw prompts or apply a chat template? The relationship is two-sided for reasoning/chat models: - Applying `apply_chat_template` to a concatenated few-shot prompt (without `fewshot_as_multiturn`) collapses the examples into a malformed single turn and can produce 0% accuracy. - Omitting `apply_chat_template` for a chat-first model can be equally wrong. For chat models on few-shot benchmarks, consider whether `apply_chat_template=True` paired with `fewshot_as_multiturn=True` is appropriate — the latter turns each few-shot example into an explicit user/assistant exchange before the template is applied. (Reference: Qwen3.5-MoE accuracy fix in `test_llm_api_autodeploy.py`.) - **`max_output_len` for generation tasks**: for benchmarks where the model must generate a full reasoning chain before the answer (e.g. GSM8K with a reasoning model), the default `MAX_OUTPUT_LEN` may truncate the response before the final answer is reached. Consider patching it up (e.g. 512) if outputs appear cut off. This is distinct from capping `max_tokens` for classification tasks like MMLU where you want to *prevent* long generations. - **`max_tokens` for classification tasks**: must be capped (e.g. 2 for MMLU) to prevent the model generating a full reasoning chain. - **Dataset path**: confirm `LLM_MODELS_ROOT` is set correctly and the dataset directory exists. If PT passes: the harness is fine. Proceed to Phase 1. ## Phase 1 — Quick Diagnostic with a Small Sample Write a standalone diagnostic script that: 1. Loads the AD model directly via `from tensorrt_llm._torch.auto_deploy import LLM as AutoDeployLLM` 2. Reproduces the **exact** prompt format the evaluator uses (not a simplified variant), including few-shot examples if any 3. Runs ~50-100 samples 4. Prints per-sample `(ref, output, correct)` and overall accuracy **Critical:** reproduce the evaluator's exact prompt format. Deviating — for example, using a 0-shot prompt when the evaluator uses 5-shot — can cause thinking models to produce "Okay" or other meta-responses instead of the expected answer, making results uninterpretable. Verify the first printed prompt matches what the evaluator sends. Typical evaluator sources: - `tensorrt_llm/evaluate/mmlu.py` — 5-shot format with dev examples - `tensorrt_llm/evaluate/gsm8k.py` — few-shot with CoT references - `tests/integration/defs/accuracy/accuracy_core.py` — `MAX_INPUT_LEN`, `MAX_OUTPUT_LEN`, `NUM_SAMPLES` per task ## Phase 2 — Classify the Error Pattern From the diagnostic output, determine what the model is generating: | Output Pattern | Likely Root Cause | |---|---| | Coherent but consistently wrong letter / answer | Numerical accuracy bug (attention, FP8 kernel, weight corruption) | | Generates meta-text ("The user wants...", "The answer is...", "Let me think...") | Prompt format issue — model not primed to answer directly | | Outputs empty string or EOS immediately | KV cache garbage (uninitialized cache, scale overflow), or `end_id` matching first token | | Completely random tokens / gibberish | Transformation applied incorrectly, load hook missing or applied twice, corrupted weights | | Correct on easy subjects, wrong on hard subjects | Subtle numerical precision bug (FP8 kernel mismatch, attention scale wrong) | | NaN in logits, especially on prefill | FX graph transform produced a node without shape metadata — enable `AD_DUMP_GRAPHS_DIR` and look for nodes missing `meta["val"]`; often caused by an opaque Python closure inside a transform | | Passes at `world_size=1`, fails at `world_size>1` | Sharding bug — see Phase 4c | ## Phase 3 — Configuration Isolation Narrow down which part of the setup is responsible by reducing the environment to its simplest form, then re-enabling components one at a time until the regression reappears. **Step 1 — Strip to a minimal configuration:** Where feasible, reduce complexity along each axis, re-running the Phase 1 diagnostic after each change: - Remove sharding or reduce to TP=1 / single GPU - Disable multi-streaming - Disable non-default transform passes in the YAML config (`enabled: false`) - **Revert to `torch-simple` `compile_backend`**: AutoDeploy currently supports two backends — `torch-cudagraph` (CUDA graphs, the typical production setting) and `torch-simple` (no CUDA graphs, significantly slower). If the model is configured with `torch-cudagraph`, revert to `torch-simple` and check whether the accuracy issue persists. Note the slower throughput will make the validation loop take longer. If accuracy recovers at `torch-simple`, CUDA graph capture or replay is the suspect. If the issue disappears when a component is removed, that component is the suspect — note it and proceed to Step 2 targeting it. If the issue persists even at minimal config, the bug is in a core path (weight loading, attention, KV cache) — proceed to Phase 4. **Step 2 — Re-enable one component at a time:** Starting from the stripped-down configuration that still reproduces the issue, re-enable the suspected components individually — one per diagnostic run. Stop as soon as accuracy drops: the last re-enabled component is the offending pass or backend. Carry this finding into Phase 4 to investigate the root cause. ## Phase 4 — Root Cause Investigation > This phase contains targeted investigation paths for known root-cause categories. Add > model-specific or error-pattern-specific steps here as they are discovered. ### 4a — Quantized Model Accuracy If the failing model is quantized (e.g. FP8, NVFP4), first verify whether the issue is in the quantization itself or in the quantized kernel path: **Step 1 — Test an unquantized baseline.** Ask the user for an unquantized (BF16/FP16) version of the same model. Run the Phase 1 diagnostic against it with an identical configuration (same `compile_backend`, same TP, same eval format). - If the unquantized model **also fails**: the bug is not quantization-related — the issue is in a transform pass, attention implementation, or weight loading. Continue with Phase 3 isolation against the unquantized model. - If the unquantized model **passes**: the accuracy gap is introduced by quantization or the quantized kernel path. Proceed to Step 2. **Step 2 — Suspect classification.** When quantization is confirmed as the source, the likely causes are (in rough order of severity): | Suspect | Symptom | How to isolate | |---|---|---| | Missing scale during dequantization | Near-zero or astronomically large logits; catastrophic accuracy loss (≈ random chance or worse) | Log a few raw logits; they will be wildly out of range | | Inverted scale (multiplied instead of divided, or vice versa) | Similarly catastrophic; outputs plausible tokens but systematically wrong | Same logit inspection; compare scale values in the checkpoint vs what the kernel receives | | Incorrect block-scale computation | Major but not catastrophic degradation; typically 5–20% below unquantized reference | Compare per-block scales against a reference quantizer on a few weight tensors | | `.to(dtype)` used instead of `.view(dtype)` for packed format reinterpretation | Wrong scale or weight values without an error — `.to()` converts values numerically while `.view()` reinterprets the raw bits | Grep the quantization transform for `.to(` on quantized weight/scale tensors of packed types (FP4, FP8); the intent is bit-level reinterpretation, which requires `.view()` | | Quantized kernel bug (wrong accumulation, wrong cast) | Non-catastrophic; may be input-dependent or shape-dependent | Step 3 below | **Step 3 — Isolate quantized kernels via fake quantization.** AutoDeploy's transform pipeline has a built-in fake-quantization path that implements exactly Q→DQ→high-precision-matmul. Understanding the two stages helps: - **Stage 1 (`pattern_matcher`)**: Replaces `nn.Linear` nodes with `torch.ops.auto_deploy.torch_fake_quant_fp8_linear` / `torch_fake_quant_nvfp4_linear` etc. These ops quantize the input, immediately dequantize both input and weight back to BF16/FP16, then run a standard `torch.matmul`. Scales are exercised but all arithmetic is in high precision. Implementation: `tensorrt_llm/_torch/auto_deploy/custom_ops/quantization/torch_quant.py`, lines 178–286. - **Stage 2 (`post_load_fusion`)**: `fuse_fp8_linear`, `fuse_nvfp4_linear`, and `fuse_finegrained_fp8_linear` transforms **replace** the fake-quant ops with optimized low-precision kernels. This is where a kernel bug would be introduced. To run inference in fake-quantization mode (bypassing the low-precision kernels), add the following to the YAML config file the test is already using (passed via `--config` or `--extra_llm_api_options`): ```yaml transforms: fuse_fp8_linear: enabled: false fuse_nvfp4_linear: enabled: false fuse_finegrained_fp8_linear: enabled: false # For MoE models also add: fuse_fp8_moe: enabled: false fuse_finegrained_fp8_moe: enabled: false fuse_nvfp4_moe: enabled: false ``` If there is no existing config file, create one with only the above content and pass it via `--extra_llm_api_options /path/to/fake_quant_debug.yaml`. The `transforms` key maps directly to `LlmArgs.transforms`; any transform not listed inherits its default from `tensorrt_llm/_torch/auto_deploy/config/default.yaml`. If accuracy recovers with fake quantization, the quantized kernel (not the scales) is the bug. If accuracy is still wrong, the scales or weight data are the likely culprit. ### 4b — Kernel Wrapper Hardcoded Assumptions **Symptom:** coherent but systematically wrong output on one specific model family (or one model variant within a family), while a structurally similar model is fine. **Root cause pattern:** The C++ kernel or its Python wrapper has a constant where it should read from the model config or from the actual tensor. Two common forms: - **Config value hardcoded**: a kernel wrapper assumes a default value instead of reading it from the HF config loaded at runtime. - **Tensor stride/shape hardcoded**: a C++ kernel assumes a specific memory layout that differs from what AutoDeploy actually passes. The kernel then reads the wrong memory locations silently. **How to investigate:** 1. Identify which kernel is dispatched for the failing op (search for the op's Python entry point in `tensorrt_llm/_torch/auto_deploy/`). 2. Compare every constant or default in the kernel wrapper call against the corresponding field in the model's HF config (`config.json`). Flag any value that is not read from the config. 3. For stride bugs: print the actual strides of the tensors being passed to the kernel and compare against what the kernel expects (check the C++ kernel source for stride assumptions or parameters). 4. If a mismatch is found, the fix is to pass the config or tensor property as an explicit parameter rather than using a hardcoded constant. ### 4c — Sharding-Related Accuracy (world_size > 1) **First step:** reproduce the issue at `world_size=1`. If accuracy recovers, the bug is in the sharding path. If it fails at `world_size=1` too, sharding is not the cause — return to Phase 3. To run at `world_size=1`, set `world_size: 1` in the model's YAML config or pass `--extra_llm_api_options` with `world_size: 1`. **Known sharding bug patterns (check in order):** | Suspect | Symptom | How to isolate | |---|---|---| | Wrong allreduce strategy | Non-deterministic or rank-dependent outputs; may appear only at TP≥4 | Set `allreduce_strategy: NCCL` in the sharding transform config; the `AUTO` default has caused correctness issues in the past | | Double `all_reduce` in MoE | MoE output doubled in magnitude; accuracy catastrophic | Inspect the exported graph; there should be exactly one `all_reduce` after the sum of routed and shared expert outputs, not one per branch | | Head reshape with wrong stride after TP | Attention output garbage at TP>1, correct at TP=1 | Reshapes that use concrete head counts from `torch.export` become wrong after TP splits the head dimension; these must use `torch.ops.auto_deploy.view` with `tp_scaled_dim` | | Sharding a projection that must not be sharded | Dim-1 gating projections or latent projections sharded → wrong results | Check `tp_mode` on small-output projections (e.g. MoE router, MLA latent q_a/kv_a); they must be `"none"` | | Nested parameter deletion breaking weight loading | Some weights missing after sharding, silently defaulting to zero or random | If sharding deletes parent module params and child params are looked up by the old path, the load hook may silently skip them | **Validating a sharding fix:** If model size permits, run it at `world_size=1` (baseline), then `world_size=2`, then the target `world_size`. If accuracy is correct at TP=1 and TP=2 but wrong at TP=8, the bug is likely a head-count divisibility assumption (head dim must be divisible by the TP degree). If it is wrong at all TP>1, it is a structural sharding bug (missing allreduce, wrong split point, wrong stride). ## Phase 5 — Per-Subject / Per-Category Breakdown When the overall score is lower than expected but not catastrophically wrong, look at per-subject or per-category breakdowns in the eval logs. Patterns to look for: | Pattern | Implication | |---|---| | All subjects uniformly ~N% below reference | Uniform precision loss — suspect FP8 kernel or attention scale | | Specific subjects near 25% (random chance for 4-choice MCQ) | Those subjects have a systematic error — suspect subject length or chunked prefill | | Easy subjects correct, hard subjects wrong | Near-decision-boundary sensitivity — suspect subtle numerical error | | Subject-correlated errors | Prompt-length correlation — verify truncation behavior | For MCQ tasks like MMLU, random chance is 25%. Subjects scoring 25-35% may be genuinely hard for the model even in the PT backend — verify against PT per-subject scores before concluding an AD-specific bug. ## Phase 6 — Iterative Ablation Once a hypothesis is formed, verify it by toggling one change at a time and re-running the diagnostic (50-100 samples is sufficient for 5%+ gaps). Each ablation should be a separate diagnostic run. Do not batch multiple hypotheses in one run — it makes results ambiguous. ## Anti-Patterns - **Do not use 0-shot prompts to diagnose a 5-shot evaluator.** Meta-responses ("Okay", "The answer is...") from a 0-shot run are a prompt-format artifact, not an AD inference bug. - **Do not invoke `torchrun` for AD tests.** The AD LLM API spawns MPI workers internally; `torchrun` adds a second layer of distributed init that deadlocks. - **Do not override `LLM_MODELS_ROOT`.** If it is already set in the environment (CI sets it to `/path/to/llm-models`), unsetting or overriding it breaks dataset lookups. Check `echo $LLM_MODELS_ROOT` before assuming it needs to be set. - **Do not lower the reference threshold as a "fix."** The reference value must be validated against the PT backend before being accepted. If PT also fails, re-examine the harness, not the threshold. - **Do not apply the same load hook twice.** If a hook converts interleaved → NeoX, applying it again corrupts the weights (it is not idempotent). Check the git log for reverts/restores before adding a hook that might already exist elsewhere in the call chain. ## Keeping This Skill Up to Date Whenever this skill is used and the debugging session uncovers a new root cause or error pattern that is not yet described here, update the skill before closing the session. **Where to add new findings:** - **Phase 2 — Classify the Error Pattern**: add a new row to the table if the session revealed a symptom → root cause mapping that is not already listed. Keep the "Output Pattern" column observable (something visible in diagnostic output), and the "Likely Root Cause" column actionable (points to a concrete next step or Phase 4 subsection). - **Phase 4 — Root Cause Investigation**: add the investigation steps under the most fitting existing subsection (4a quantization, 4b kernel wrapper assumptions, 4c sharding). If the finding does not fit any existing subsection, create a new one numbered sequentially (4d, 4e, …). Each subsection should follow the same structure: symptom, root cause pattern, and a numbered investigation procedure. **What is worth capturing:** - A root cause that is not already represented in Phase 4. - A symptom pattern that allows earlier classification (Phase 2). - A configuration or environment condition that reproduces or masks the bug (Phase 3). - A new anti-pattern discovered during the session. **What is not worth capturing:** - Model-specific quirks with no generalization potential. - Findings that duplicate what is already written. - Workarounds that paper over a bug rather than identifying it. --- Source attribution: yo-steven Original project: https://github.com/yo-steven/skills-exploration-20260522/blob/6e1127ffb7690aa8038b172d0ae7cc720754870d/skills/TensorRT-LLM/ad-accuracy-debug/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice SPDX-License-Identifier: Apache-2.0 AND CC-BY-4.0 Copyright (c) 2026 NVIDIA Corporation This project is licensed under a dual license: - Apache License 2.0 (for code and configuration) - Creative Commons Attribution 4.0 International (CC BY 4.0) (for documentation) You may use the contents of this repository under the terms of either license, or both, as applicable to the type of content. ================================================================================ Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS ================================================================================ Creative Commons Attribution 4.0 International License (CC BY 4.0) https://creativecommons.org/licenses/by/4.0/ You are free to: Share — copy and redistribute the material in any medium or format for any purpose, even commercially. Adapt — remix, transform, and build upon the material for any purpose, even commercially. The licensor cannot revoke these freedoms as long as you follow the license terms. Under the following terms: Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits. Notices: You do not have to comply with the license for elements of the material in the public domain or where your use is permitted by an applicable exception or limitation. No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as publicity, privacy, or moral rights may limit how you use the material. For the full legal text, see: https://creativecommons.org/licenses/by/4.0/legalcode # Mega AI Hub resource metadata Creator / publisher: yo-steven Original project: https://github.com/yo-steven/skills-exploration-20260522/blob/6e1127ffb7690aa8038b172d0ae7cc720754870d/skills/TensorRT-LLM/ad-accuracy-debug/SKILL.md Attribution basis: Source repository record Fields of work: Data & Analytics, Development & Engineering Roles: Data Scientist, ML / AI Engineer, QA / Test Engineer Specialties: API, Testing Tools: Pytorch, Tensorrt Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 29cf45629237557fecb682be5e4dab5e5faf88f40f005f8a415b0613251ad44c