llm-update-downloads

Update URLs and SHA256 checksums in requirements.json for LLM model downloads.

4|3|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/Arm-Examples/LLM-Runner --skill llm-update-downloads
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llm-update-downloads
Source: https://github.com/Arm-Examples/LLM-Runner/tree/main/skills/llm-update-downloads
Command: npx skills add https://github.com/Arm-Examples/LLM-Runner --skill llm-update-downloads

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of managing external model and tool downloads by updating their URLs and checksums in a central manifest file, ensuring deterministic and secure retrieval.

Core Features & Use Cases

  • Manifest Management: Updates scripts/py/requirements.json with new or refreshed download URLs and SHA256 checksums.
  • Integrity Validation: Allows for optional validation of download logic and hash integrity.
  • Use Case: When adding a new LLM model to the project, use this Skill to add its download URL and expected SHA256 hash to the requirements.json file, ensuring it can be reliably downloaded and verified later.

Quick Start

Update the download manifest for the new model by editing scripts/py/requirements.json.

Frequently Asked Questions about llm-update-downloads

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

FAQPage Schema
How do I update download URLs and checksums for LLM models in a requirements manifest?

To update download URLs and checksums for LLM models, you modify the central requirements.json manifest file with the new resource links and SHA256 hashes. This ensures deterministic retrieval and integrity validation for external dependencies.

What is a download manifest for LLM tools and when do I need one?

A download manifest for LLM tools is a central JSON configuration file that stores external resource URLs and SHA256 checksums. You need it to ensure secure, verifiable, and deterministic retrieval of build artifacts and model dependencies.

How do I add a new LLM model to a project and ensure its download is verified?

To add a new LLM model and verify its download, you add the model's download URL and expected SHA256 hash to the requirements.json file. This centralizes dependency management and enables integrity validation during retrieval.

Can I validate download logic and hash integrity for external dependencies?

Yes, you can validate download logic and hash integrity for external dependencies. By updating the requirements.json manifest with accurate SHA256 checksums, the system verifies that downloaded build artifacts match expected hashes.

Does updating download manifests require any external dependencies?

No, updating download manifests does not require external dependencies. The process involves modifying the central requirements.json file directly to manage URLs and SHA256 checksums for LLM models and tools.

What are the limitations of using a central JSON file for download integrity validation?

The limitation of using a central JSON file for download integrity validation is that it primarily supports deterministic downloads and SHA256 hash verification, without handling complex dynamic URL generation or multi-factor authentication for resource retrieval.