accuracy-improvement-loop
Skill8 starsChanged 4 months agoMITView on GitHub
Use when an existing model's results are disappointing and the user wants higher accuracy - 'accuracy is still too low', 'improve/boost the model', 'why is it bad', 'make it better than the paper', 'combine methods to beat SOTA'. Diagnoses the real bottleneck first (error analysis, learning curves, leakage, saliency), then researches the specific gap, synthesizes a principled combination of techniques from the literature, and ranks next levers by expected impact - with honest ceilings, not magic promises.
In this repository22 other files it gives its agents.
- data-rigor-and-leakageSkill
- dataset-profilingSkill
- deployment-explainabilitySkill
- domain-3dSkill
- domain-anomaly-detectionSkill
- domain-audio-speechSkill
- domain-computer-visionSkill
- domain-generativeSkill
- domain-graphSkill
- domain-medical-imagingSkill
- domain-multimodalSkill
- domain-nlp-llmSkill
- domain-recommenderSkill
- domain-reinforcement-learningSkill
- domain-tabularSkill
- domain-time-seriesSkill
- domain-videoSkill
- literature-reviewSkill
- ml-research-methodologySkill
- notebook-deliverySkill
- rigorous-evaluationSkill
- training-optimizationSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Do NOT throw random tricks at the model.
- Very specific: line 31
Verify with rigorous-evaluation.
- Distinctive: line 34
Every dataset has a realistic ceiling.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Accuracy-Improvement Loop
Do NOT throw random tricks at the model. Diagnose, research the gap, combine principled fixes, verify. This is the loop a professional runs to push toward (and recognize) the ceiling.
Step 1 - Diagnose the bottleneck (evidence, not guesses)
- Re-audit leakage FIRST (
data-rigor-and-leakage). A suspicious jump/drop is often a split problem. Fixing leakage may lower the number - that is success, because it was fake. - Learning curves: train loss down but val loss up means overfitting; both flat or low means underfitting or a data problem; unstable means an LR, batch, or BatchNorm issue.
- Error analysis: inspect the confusion matrix and the actual misclassified samples. What do the errors have in common?
- Saliency check (Grad-CAM): is the model attending to the signal or to an artifact (background, labels, muscle/border, watermark, spurious correlation)? Fix the data/preprocessing if so.
- Per-branch/per-model check: in fusion/ensembles, is one component dragging the rest down?
Step 2 - Research the specific gap
Invoke literature-review / paper-researcher targeted at the diagnosed problem (e.g., "small-lesion whole-image classification", "fusion gradient dilution", "class imbalance long-tail"), not the generic task. Extract techniques that address this failure mode.
Step 3 - Synthesize a principled combination
Combine the best-evidenced techniques that target the bottleneck - this is how you "beat existing work": a grounded combination, not one silver bullet. Common high-impact levers (pick by diagnosis):
- Data/signal: higher input resolution, better ROI/region focus, artifact removal, cleaner labels, stronger domain-appropriate augmentation, more/balanced data (incl. synthesis only if justified).
- Architecture: stronger/more-suitable backbone for this dataset (not just the trendiest); attention (CBAM/self-attention); multi-scale features; multi-view/multi-input; feature-fusion done right - gated fusion + deep supervision / auxiliary per-branch losses to beat gradient dilution when a weak branch drags a fusion.
- Training: discriminative LR, better schedule, regularization retuned to the diagnosis, longer training, EMA/SWA, self-distillation, patch-pretraining then whole-image.
- Inference/aggregation: TTA, calibrated thresholds, ensembles (soft-voting / weighted-by-val / stacking) - output-level fusion is often the cheapest real gain.
- Weakly-supervised localization (e.g., GMIC-style) when lesions/objects are tiny in a large input - often both more accurate and gives free saliency.
Step 4 - Rank, run, verify
- Rank candidate levers by expected impact vs cost; try the biggest first (usually data/resolution/leakage, then architecture).
- Change one lever at a time where feasible so you know what worked.
- Verify with
rigorous-evaluation; keep only what improves validation honestly.
Honesty (the professor standard)
- Every dataset has a realistic ceiling. State it. Do not promise to beat leaky 99% papers.
- Know when you have hit diminishing returns - and say so, instead of chasing noise.
- A defensible, reproducible gain > a fragile record that won't survive review.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

