update

Synchronize the local Fritz AI repository with upstream updates and run migrations.

2|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/intelligenttools-ai/fritz-ai-local --skill update-intelligenttools-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update
Source: https://github.com/intelligenttools-ai/fritz-ai-local/tree/main/skills/update
Command: npx skills add https://github.com/intelligenttools-ai/fritz-ai-local --skill update-intelligenttools-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual complexity of maintaining a distributed AI knowledge base by automating version synchronization, dependency management, and system migrations across multiple agent platforms.

Core Features & Use Cases

  • Automated Synchronization: Pulls the latest repository updates and ensures all agent-specific hooks and skill symlinks are correctly mapped.
  • System Integrity: Runs pending migrations to update the local brain schema and verifies MCP token wiring to maintain secure, uninterrupted agent connectivity.
  • Use Case: When a new version of the Fritz Local framework is released, this skill ensures your Claude, Codex, and Hermes agents are immediately updated with the latest capabilities without requiring manual file system intervention.

Quick Start

Run the update skill to synchronize your local brain installation and apply all pending system migrations.

Frequently Asked Questions about update

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

FAQPage Schema
How do I synchronize my local AI repository with the latest upstream version?

To synchronize your local AI repository, you run an automated update process that pulls the latest upstream changes and applies idempotent database migrations to keep your local brain schema current.

How does agent synchronization work across multiple runtimes like Claude and Codex?

Agent synchronization across runtimes like Claude and Codex works by automatically symlinking agent-specific hooks and verifying secure MCP token wiring to ensure consistent capabilities across all platforms.

Can I use this to fix configuration drift between my local brain and the upstream framework?

Yes, you can fix configuration drift by validating the integrity of your local brain contract, which detects inconsistencies and provides a comprehensive status report on your system's health.

Do I need to manually manage file system symlinks when migrating my local brain schema?

No, you do not need to manually manage file system symlinks. The migration process automatically maps all agent-specific hooks and skill symlinks during the synchronization sequence.

What is the best way to update agent hooks and run database migrations automatically?

The best way to update agent hooks and run database migrations automatically is to trigger an idempotent synchronization command that verifies token wiring and executes all pending schema updates.

Why does my local brain contract validation fail after a framework update?

Local brain contract validation may fail after an update if agent-specific hooks are incorrectly mapped or MCP token wiring is insecure, which the system integrity check identifies in its status report.