Compute the NegativePredictiveValue metric — provided by torchmetrics. Use when the user has predictions and ground-truth and needs to compute NegativePredictiveValue, or asks how to score with NegativePredictiveValue.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add qhjqhj00/research-skills-pool --skill negativepredictivevalue --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Negativepredictivevalue?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/qhjqhj00-negativepredictivevalue)More formats (shields.io, HTML) on the badges page.
---
name: negativepredictivevalue
description: Compute the NegativePredictiveValue metric — provided by torchmetrics. Use when the user has predictions and ground-truth and needs to compute NegativePredictiveValue, or asks how to score with NegativePredictiveValue.
metadata:
skill_kind: metric
source_lib: torchmetrics
import_path: torchmetrics.NegativePredictiveValue
source: library_introspection
---
# negativepredictivevalue
> Metric `NegativePredictiveValue` from `torchmetrics` (torchmetrics.NegativePredictiveValue)
## When to invoke this skill
The user has predictions + ground truth and asks to evaluate with NegativePredictiveValue, or
mentions `torchmetrics.NegativePredictiveValue` directly, or wants the standard torchmetrics implementation.
## Reference signature
```python
from torchmetrics import NegativePredictiveValue
# NegativePredictiveValue(task: Literal['binary', 'multiclass', 'multilabel'], threshold: float = 0.5, num_classes: Optional[int] = None, num_labels: Optional[int] = None, average: Optional[Literal['micro', 'macro', 'weighted', 'none']] = 'micro', multidim_average: Optional[Literal['global', 'samplewise']] = 'global', top_k: Optional[int] = 1, ignore_index: Optional[int] = None, validate_args: bool = True, **kwargs: Any) -> torchmetrics.metric.Metric
```
## Library docstring
```
Compute `Negative Predictive Value`_.
.. math:: \text{Negative Predictive Value} = \frac{\text{TN}}{\text{TN} + \text{FN}}
Where :math:`\text{TN}` and :math:`\text{FN}` represent the number of true negatives and false negatives
respectively. The metric is only proper defined when :math:`\text{TP} + \text{FN} \neq 0`. If this case is
encountered for any class/label, the metric for that class/label will be set to 0 and the overall metric may
therefore be affected in turn.
This function is a simple wrapper to get the task specific versions of this metric, which is done by setting the
``task`` argument to either ``'binary'``, ``'multiclass'`` or ``'multilabel'``. See the documentation of
:class:`~torchmetrics.classification.BinaryNegativePredictiveValue`,
:class:`~torchmetrics.classification.MulticlassNegativePredictiveValue`
and :class:`~torchmetrics.classification.MultilabelNegativePredictiveValue` for the specific details of each
argument influence and examples.
Legacy Example:
>>> from torch import tensor
>>> preds = tensor([2, 0, 2, 1])
>>> target = tensor([1, 1, 2, 0])
>>> nvp = NegativePredictiveValue(task="multiclass", average='macro', num_classes=3)
>>> nvp(preds, target)
tensor(0.6667)
>>> nvp = NegativePredictiveValue(task="multiclass", average='micro', num_classes=3)
>>> nvp(preds, target)
tensor(0.6250)
```
## Quick recipe
```python
import torchmetrics as _m
score = _m.NegativePredictiveValue(y_true, y_pred)
```
## Don'ts
- Don't reimplement when the library version handles edge cases (NaN, ties, empty inputs) better than a hand-rolled formula.
- Always check the library version's argument order — sklearn is `(y_true, y_pred)` while torchmetrics is `(preds, target)`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!