Auto Updater

Purpose

The Auto Updater skill manages automatic updates for ClawdBot and its skills. It monitors ClawdHub for new skill versions, applies updates to the local installation, tracks version history, notifies administrators of updates, and provides rollback capabilities to recover from problematic updates.

Triggers

Use this skill when:

Checking for Available Updates - Scan ClawdHub for new skill versions
Updating Skills - Apply available updates from ClawdHub to local skills
Managing Skill Versions - Track and manage versions of installed skills
Rolling Back Updates - Restore previous skill versions if issues arise
Monitoring Version Changes - Track what changed between versions
Automating Skill Maintenance - Scheduled update checks and installation

Capabilities

1. ClawdHub Integration

Query ClawdHub for available skill updates
Check version compatibility with current ClawdBot installation
Retrieve skill metadata, changelog, and dependencies
Authenticate with ClawdHub API for private skill updates

2. Update Detection

Compare installed skill versions against ClawdHub versions
Identify major, minor, and patch version updates
Flag breaking changes and deprecations
Detect security updates and critical patches

3. Automated Installation

Download skill updates from ClawdHub
Verify package integrity and signatures
Install updates with dependency resolution
Handle skill hot-reloading without bot restart

4. Version Tracking

Maintain version history for all skills
Log installation timestamps and sources
Track update source (ClawdHub, GitHub, local)
Store changelog information locally

5. Update Notifications

Notify administrators of available updates
Alert on successful installations
Report on failed updates with error details
Optional Telegram notifications for monitoring

6. Rollback Capability

Restore previous skill versions
Maintain version history for rollback operations
Handle rollback validation and testing
Document rollback reasons and timestamp

7. Safety Features

Dry-run mode to preview updates before installation
Backup current skill state before updates
Automatic rollback on critical failures
Dependency validation before installation

How to Use

Check for Updates

Check for available skill updates from ClawdHub

List all available updates for ClawdBot skills

Show what's new in the latest skill versions

Install Updates

Update all skills to the latest versions

Update the 'market-analyst' skill to version 2.1.0

Install updates with a dry-run to preview changes

View Version History

Show version history for the 'auto-updater' skill

What skill versions are currently installed?

Compare versions of 'content-research-writer' across all installations

Rollback Updates

Rollback 'market-analyst' to the previous version

Restore all skills to the versions from January 15th

Show rollback options for the 'page-cro' skill

Track Changes

Show what changed between versions of 'copywriting'

What dependencies are needed for skill version 2.5.0?

Is there a breaking change in the latest 'design-and-refine' update?

Schedule Automated Updates

Check for updates every Monday at 9 AM

Auto-update all non-major version changes

Enable notifications for critical security updates only

Examples

Example 1: Checking for Available Updates

User: "Check for available skill updates from ClawdHub"

Auto-Updater Response:

✓ Checking ClawdHub for updates...

Available Updates: 7 skills have new versions

┌─ market-analyst (1.2.0 → 2.0.0) [MAJOR]
│  • Enhanced crypto market analysis
│  • New prediction market integration
│  • Breaking: Kalshi API endpoint changed
│
├─ content-research-writer (1.5.2 → 1.5.3) [PATCH]
│  • Fixed citation formatting
│  • Improved source deduplication
│
└─ copywriting (2.1.0 → 2.2.0) [MINOR]
   • New A/B test copy variants
   • Improved psychology integration
   • Backward compatible

Ready to install? Run: "Update all skills to the latest versions"

Example 2: Installing Updates with Dry-Run

User: "Install updates with a dry-run to preview changes"

Auto-Updater Response:

DRY RUN MODE: Preview only, no changes will be made

Installing Updates (Preview):
✓ market-analyst 1.2.0 → 2.0.0
  - 145 KB additional size
  - 3 new dependencies (kalshi-api, polygon-data, market-sync)
  - Config migration required: update API endpoints

✓ content-research-writer 1.5.2 → 1.5.3
  - 8 KB reduction
  - No new dependencies
  - No breaking changes

✓ copywriting 2.1.0 → 2.2.0
  - 32 KB additional size
  - 1 new dependency (ab-test-validator)
  - Config update recommended: new copywriting presets

Total size change: +169 KB
Install time estimate: 12 seconds
Estimated restart required: No

Proceed with actual installation? (Dry-run successful)

Example 3: Rollback Operations

User: "Rollback 'market-analyst' to the previous version"

Auto-Updater Response:

Rolling back market-analyst...

Current version: 2.0.0 (installed Jan 20, 2026)
Reverting to: 1.2.0 (installed Jan 10, 2026)

✓ Backed up current version
✓ Downloaded previous version
✓ Verified package integrity
✓ Restored skill files
✓ Restored configuration
✓ Cleared cache

Rollback complete! market-analyst is now at version 1.2.0

Changes reverted:
- Kalshi market integration removed
- Removed 3 dependencies
- Configuration reset to v1.2.0 defaults

Note: Please review your market-analyst usage. The Kalshi integration is no longer available.

Example 4: Version History

User: "Show version history for the 'auto-updater' skill"

Auto-Updater Response:

Version History: auto-updater

1.0.0 (Current)
├─ Installed: Jan 20, 2026 at 09:15 AM
├─ Source: ClawdHub
├─ Status: Active
└─ Notable: Initial release with all core features

0.9.0-beta
├─ Installed: Jan 12, 2026 at 02:30 PM
├─ Source: ClawdHub (beta channel)
└─ Status: Superseded (rolled back Jan 20)

0.8.0
├─ Installed: Dec 28, 2025 at 06:00 AM
├─ Source: GitHub
└─ Status: Archived

Available Upgrades: None
Available Downgrades: 0.9.0-beta, 0.8.0

Example 5: Tracking Changes Between Versions

User: "Show what changed between versions of 'copywriting'"

Auto-Updater Response:

Change Summary: copywriting 2.1.0 → 2.2.0

Breaking Changes: None ✓
Deprecations: None ✓

New Features:
+ A/B test copy variant generator
+ Psychology-based headline optimizer
+ Social proof integration
+ Multi-tone voice presets

Improvements:
~ Faster processing (15% improvement)
~ Better emoji handling
~ Improved CTR predictions
~ Enhanced marketing psychology integration

Bug Fixes:
- Fixed comma placement in long sentences
- Corrected spelling in marketing psychology terms
- Resolved encoding issues with special characters

Dependencies Added:
+ ab-test-validator (^1.2.0)

Configuration Changes:
• New config key: copywriting.psychology_weight (default: 0.5)
• New config key: copywriting.ab_test_variants (default: 3)

Migration Required: Yes
Estimated Migration Time: < 30 seconds
Auto-migration Available: Yes

Configuration

Update Policy

{
  "updatePolicy": {
    "major": "manual",
    "minor": "automatic",
    "patch": "automatic",
    "security": "automatic"
  },
  "schedule": {
    "checkInterval": "daily",
    "checkTime": "02:00 AM",
    "timezone": "UTC"
  },
  "notifications": {
    "telegram": true,
    "adminOnly": false,
    "includeChangelog": true
  },
  "backupBefore": true,
  "autoRollbackOnFailure": true,
  "rollbackTimeout": 300
}

Safety & Best Practices

Always Test Updates - Use dry-run mode first, especially for major versions
Monitor After Updates - Check bot functionality immediately after updating
Keep Backups - Maintain version history for critical skills
Review Breaking Changes - Major updates may require configuration changes
Schedule Wisely - Update during low-traffic periods
Document Decisions - Log why you accepted or rejected updates
Gradual Rollout - Consider manual updates for important skills

Related Skills

changelog-generator - Review what changed in each skill version
code-reviewer - Audit skill updates for code quality
debugger - Troubleshoot issues after updates
continue-learning - Extract learnings from update patterns

Troubleshooting

Update Installation Failed

Check for skill conflicts, API key validation, and storage permissions.
Run in dry-run mode to identify the blocking issue.

Rollback Not Available

Version history may be cleared. Check the version tracking logs.
Reinstall from ClawdHub if manual installation is needed.

Notifications Not Working

Verify Telegram token is set in configuration.
Check that the admin user ID is correctly configured.
Ensure bot has permission to send direct messages.