ml-prior-art-survey

Surveys ML model, dataset, and benchmark registries to produce a validated build-vs-buy option register.

1|1|Updated May 24, 2026
One-click install
npx skills add https://github.com/bm629/agent-skills --skill ml-prior-art-survey-bm629
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ml-prior-art-survey
Source: https://github.com/bm629/agent-skills/tree/main/skills/ml-prior-art-survey
Command: npx skills add https://github.com/bm629/agent-skills --skill ml-prior-art-survey-bm629

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, jsonschema, and includes scripts (resource) and references (resource) components.

What problem does it solve? Teams routinely choose an ML architecture — call an API, fine-tune, or train from scratch — before checking what the published corpus already offers. This Skill gathers that evidence systematically: it searches model registries, dataset corpora, evaluation tables, pricing catalogues, and safety evaluations, records every query as run, and distills the findings into an adoption-ladder decision register. ## Core Features & Use Cases - Vocabulary map: Mints a search protocol across eight axes (task, modality, domain terms, benchmarks, datasets, methods, runtime formats, harm categories) with per-angle applicability verdicts. - Recorded search angles: Executes one of nine search angles across sources like HuggingFace, arXiv, OpenML, and vendor catalogues, logging every query verbatim with coverage cells and sanitization status. - Extract records and option register: Deep-reads admitted artifacts into schema-validated YAML records, then synthesizes an option register whose spine is an adoption ladder — the first admissible rung with every higher rung explained by the artifact that failed. - Use Case: Before committing to fine-tuning a model for a document-classification feature, run this Skill to survey hosted APIs, open-weights models, and benchmarks, producing a validated register that justifies the cheapest admissible option with citations. ## Quick Start Use ml-prior-art-survey to survey existing models and datasets for our text-classification feature and produce an option register before we decide between an API and fine-tuning.

Frequently Asked Questions about ml-prior-art-survey

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I survey existing ML models before choosing an architecture?

Run the vocabulary-map procedure first to mint search terms across eight axes, then execute the applicable search angles against registries like HuggingFace and arXiv. Each admitted artifact gets a deep-read extract record, and synthesis produces an option register ranking API, open-weights, fine-tune, and from-scratch options.

What sources does an ML prior-art survey cover?

The survey covers model registries, dataset and training corpora, published evaluation tables, preprint listings, hosted-inference catalogues and pricing, training-cost figures, safety evaluations, serving benchmarks, and on-device runtime formats. Each source's URL, access status, and fallback is recorded in a source registry.

How do I validate the survey output files?

Run the bundled validator with uv: python scripts/validate_ml_prior_art.py followed by the mode (keyword-map, search, extract, or synthesis) and the file path. The synthesis check requires --extracts pointing at the extract records directory, and the artifact must validate with exit code 0.

Does the survey handle sources that are rate-limited or gated?

Yes. Coverage cells distinguish reached, gated, rate-limited, unreachable, superseded, and not-attempted statuses, each with a recorded cause. A 429 from a shared academic pool is treated as a normal operating condition, never as a searched zero.

When should I not use a systematic ML prior-art survey?

Skip it when the project has no ML involvement or the architecture is already fixed by external constraint. The survey exists to inform the build-vs-buy decision before it is made; running it after the decision only documents a choice already locked in.