Evaluates few-shot image classification models on semantically coherent versus uniformly sampled tasks. It probes the model's ability to generalize from limited support examples to query images across varying class coarseness and scale (5-way vs 100-way). Use when the user wants to benchmark on tieredImageNet, Danish Fungi 2020, or asks about evaluating this task. Reports Top-1 accuracy.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add qhjqhj00/research-skills-pool --skill few-shot-image-classification-eval --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Few Shot Image Classification Eval?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/qhjqhj00-few-shot-image-classification-eval)More formats (shields.io, HTML) on the badges page.
---
name: few-shot-image-classification-eval
description: Evaluates few-shot image classification models on semantically coherent versus uniformly sampled tasks. It probes the model's ability to generalize from limited support examples to query images across varying class coarseness and scale (5-way vs 100-way). Use when the user wants to benchmark on tieredImageNet, Danish Fungi 2020, or asks about evaluating this task. Reports Top-1 accuracy.
metadata:
skill_kind: dataset_eval
source_arxiv: 2205.05155
bibtex_key: bennequin2022fewshot
confidence: high
---
# few-shot-image-classification-eval
> Few-Shot Image Classification Benchmarks are Too Far From Reality: Build Back Better with Semantic Task Sampling — Bennequin et al. (2022) (arXiv:2205.05155, 2022)
## What this evaluates
Evaluates few-shot image classification models on semantically coherent versus uniformly sampled tasks. It probes the model's ability to generalize from limited support examples to query images across varying class coarseness and scale (5-way vs 100-way).
## Datasets
- **tieredImageNet** — total ?; splits: test (5000)
- **Danish Fungi 2020** — total ?; splits: test (5000)
## Metrics
- `Top-1 accuracy` **(primary)** — range: percent
- Fraction of correctly classified query images across all tasks in the testbed, multiplied by 100.
- `Top-5 accuracy` — range: percent
- Fraction of query images where the true class is among the top 5 predicted classes, multiplied by 100.
## Input / output format
**Input**: Support set images (N-way K-shot) and query set images (10 queries per class) for each episodic few-shot task.
**Output**: Predicted class label for each query image.
## Scoring recipe
```python
correct = 0
total = 0
for task in testbed:
for query_img in task.query_images:
pred = model.predict(query_img, task.support_images)
if pred == query_img.label:
correct += 1
total += 1
return (correct / total) * 100
```
## Common pitfalls
- Tasks are sampled episodically (5000 tasks per testbed), not evaluated on a single static split.
- 100-way tasks on DF20 yield very low top-1 accuracy (<10%), so top-5 must be reported to assess performance meaningfully.
- Semantic coarsity (WordNet distance) heavily influences difficulty; uniform sampling masks this correlation.
## Evidence (verbatim from paper)
> We built two testbeds with uniform class sampling (1-shot and 5-shot), and two testbeds (1-shot and 5-shot) with semantic task sampling... We upsampled 10000 tasks, then we removed all duplicate tasks and downsampled them to 5000 tasks. All tasks present 10 queries per class. Results for tieredImageNet are shown in Tables 1 and 2. The immediate observation that we can make is that our benchmark better-tieredImageNet is much more challenging than uniform task sampling, with a performance drop of 12 to 15% in top-1 accuracy for all settings and methods.
## Citation
```bibtex
@misc{bennequin2022fewshot,
title={Few-Shot Image Classification Benchmarks are Too Far From Reality: Build Back Better with Semantic Task Sampling},
author={Bennequin et al. (2022)},
year={2022},
note={arXiv:2205.05155}
}
```
- arXiv: 2205.05155
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!