skills.rest
drakulavich
drakulavichCOMMUNITY
Explore all skills by this author →
𝕏@drakulavichGitHub

verify-pin-bump

Verify SHA-256 pin mismatches and update rust/src/models.rs after checks.

68|7|Updated Apr 6, 2026
Search Tags:#security#verification#pin-bump#model-hash#hash-mismatch#kesha-engine
One-click install
npx skills add https://github.com/drakulavich/kesha-voice-kit --skill verify-pin-bump
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-pin-bump
Source: https://github.com/drakulavich/kesha-voice-kit/tree/main/.claude/skills/verify-pin-bump
Command: npx skills add https://github.com/drakulavich/kesha-voice-kit --skill verify-pin-bump

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when a model SHA-256 mismatch surfaces (download_verified errors, manifest_tests failures, fresh download produces a different hash than rust/src/models.rs pins). Walks through the safe bump procedure — verify the upstream weights deliberately, then update the pin. Refuses to suggest commenting out verification.

Core Features & Use Cases

  • Guides through identifying and verifying a hash mismatch, ensuring intentional updates only.
  • Enforces the official bump procedure to align pins with upstream changes or mirrored content.
  • Provides guardrails to prevent bypassing verification and maintains safety of the model-pinning system.

Quick Start

Follow the safe bump procedure to verify upstream changes and update the pin when hashes legitimately change.

Frequently Asked Questions about verify-pin-bump

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

FAQPage Schema
How do I safely update a model SHA-256 pin when a hash mismatch occurs?▼

To resolve a SHA-256 hash mismatch, follow the verify-pin-bump procedure to verify upstream commits, check mirror integrity, and run smoke tests before deliberately updating rust/src/models.rs.

What causes a SHA-256 hash mismatch during model weight installation?▼

A SHA-256 hash mismatch occurs when fresh downloads differ from pinned hashes in rust/src/models.rs, often caused by a model mirror update or upstream weight changes surfacing in download_verified or manifest tests.

Can I bypass download verification if the model hash keeps failing?▼

No, you cannot bypass verification. The procedure refuses to suggest commenting out verification checks, enforcing strict alignment with upstream changes and maintaining the safety of the model-pinning system.

What is the official procedure to bump a model pin after a mirror update?▼

The official bump procedure guides you through identifying the mismatch, verifying upstream weights deliberately, checking mirror integrity, running smoke tests, and finally updating the pin in rust/src/models.rs.

When should I update model pins in rust/src/models.rs?▼

Update model pins when a fresh download produces a different SHA-256 hash than the existing pins, requiring deliberate verification of upstream weight changes and mirror integrity before applying the pin bump.

Related Skills

Explore More Software Engineering Skills→
ThirdKeyAIThirdKeyAI
16

schemapin

Verify AI tool schemas with ECDSA P-256 signatures to prevent MCP Rug Pull attacks.

Official
Advanced
syncable-devsyncable-dev
1

rationalize-deps

Identify and prune unused default features in Cargo.toml dependencies.

Official
Intermediate
igbuendigbuend
8

length-extension-attacks-anti-pattern

Detect hash length extension vulnerabilities and provide HMAC alternatives in Python, JavaScript, and Java.

Community
Intermediate
gujiachun-rainbowgujiachun-rainbow
8

Pulling Updates from Skills Repository

Sync local skills repository with upstream changes while preserving local modifications.

Community
Intermediate