model-artifact-integration
Skill177 starsChanged 7 days agoApache-2.0View on GitHub
Integrate or replace inference models and engines with verified tensor, preprocessing, runtime, and artifact contracts. Use for ONNX, TensorRT, model assets, precision changes, and target-device deployment.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- agent-evaluationSkill
- algorithm-developmentSkill
- buildSkill
- change-reviewSkill
- container-buildSkill
- engineering-solution-designSkill
- interface-migrationSkill
- issue-localizationSkill
- lintSkill
- long-horizon-developmentSkill
- multi-repo-devSkill
- performance-optimizationSkill
- repository-agent-setupSkill
- simulation-regressionSkill
- test-impact-analysisSkill
- unified-core-runtimeSkill
- vendorSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Read the owning evaluator/adapter and existing model tests.
- Distinctive: line 12
Do not fetch or distribute artifacts without authorization.
- Distinctive: line 20
Check invalid shapes, non-finite results, empty inputs, and failure signaling.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Model Artifact Integration
Procedure
- Read the owning evaluator/adapter and existing model tests. Identify the model's legitimate source, license, checksum, revision, and target runtime. Do not fetch or distribute artifacts without authorization.
- Specify tensor names, shapes, dynamic dimensions, layout, dtype, units, coordinate frames, normalization, preprocessing, and output decoding. Compare training/export semantics with the actual inference implementation.
- Record runtime/compiler, device, precision, optimization profiles, plugins, calibration inputs, and engine build parameters. Do not assume a serialized engine is portable across device or runtime versions.
- Compare a small reference fixture against independently verified outputs. Check invalid shapes, non-finite results, empty inputs, and failure signaling.
- Validate the real target runtime for deployment claims. Use
performance-optimizationfor measured resource claims andsimulation-regressionfor downstream behavioral claims.
Acceptance and failure handling
Separate contract correctness, model quality, target compatibility, and latency evidence. Synthetic plumbing, CPU inference, or engine construction alone does not prove target GPU behavior. Missing device, calibration data, or model rights is a stated boundary, not permission to change precision or substitute assets.
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.

