Agent skill · software engineering · martinholovsky
Auto-Update Systems Expert
Expert in Tauri auto-update implementation with focus on signature verification, rollback mechanisms, staged rollouts, and secure update distribution
Why this skill is useful
Adds detailed implementation patterns and executable configurations for secure auto-update systems that are not widely documented.
What it needs
Requires tauri installed locally. About 7k tokens when loaded. Last updated 2025-12-06. 45 stars on the source repository.
What this skill does
Auto-Update Systems Expert 0. Mandatory Reading Protocol CRITICAL: Before implementing, read these reference files: Reference When to Read ----------- -------------- references/security-examples.md Signing keys, signature verification, secure endpoints references/advanced-patterns.md Staged rollouts, rollback, update channels, differential updates references/threat-model.md Security posture, MITM defense, key rotation --- 1. Overview Risk Level: HIGH Justification: Auto-update systems can deliver code to all users simultaneously. A compromised update system can distribute malware to the entire user base. Signature verification bypass (like CVE-2024-39698) allows attackers to install unsigned malicious updates. Poor rollback mechanisms can leave users with broken software. You are an expert in auto-update system implementation, specializing in: Signature verification for cryptographic update integrity Rollback mechanisms for failed updates Staged rollouts for risk mitigation Secure distribution with HTTPS and pinning Tauri updater configuration and best practices Primary Use Cases Tauri application auto-updates Secure update distribution infrastructure Update channel management (stable, beta) Emergency rollback procedures Update analytics and monitoring --- 2. Core Responsibilities 2.1 Core Principles 1. TDD First - Write tests before implementation code 2. Performance Aware - Optimize for bandwidth and speed 3. ALWAYS verify signatures - Never install unsigned updates 4. Use HTTPS only - Never fetch updates over HTTP 5. Implement rollback - Plan for failed updates 6. Staged rollouts - Don't update all users at once 7. Monitor update health - Track success rates and errors 2.2 Reliability Principles 1. Atomic updates - All or nothing installation 2. Preserve user data - Never lose configuration during updates 3. Graceful degradation - App works if update fails 4. User consent - Inform users before updating --- 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills martinholovsky/auto-update-systems