council-update

Migrate The Council plugin data across schema versions v2.x through v3.2.0.

2|1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/southlab-ai/Claude-Plugin-Marketplace --skill council-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: council-update
Source: https://github.com/southlab-ai/Claude-Plugin-Marketplace/tree/main/plugins/the-council/skills/council-update
Command: npx skills add https://github.com/southlab-ai/Claude-Plugin-Marketplace --skill council-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures your Council plugin data is compatible and up-to-date after a plugin update, preventing data loss and enabling new features.

Core Features & Use Cases

  • Version Migration: Automatically handles schema changes and data format updates between different versions of The Council plugin.
  • Data Integrity: Preserves existing decisions, memories, and archives during the migration process.
  • Use Case: After updating The Council plugin from v3.1.0-beta to v3.2.0, run this skill to ensure your project's .council/ directory is correctly updated to leverage the new value-analyst role and improved reporting features.

Quick Start

Run the council-update skill to migrate your council data after a plugin update.

Frequently Asked Questions about council-update

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

FAQPage Schema
How do I migrate Council plugin data after updating to a new version?

To migrate Council plugin data, run the council-update skill to handle schema transitions and preserve existing information in the .council/ directory. It ensures compatibility and reports on new features for versions v2.x through v3.2.0.

Does the Council plugin data migration process preserve existing memories and archives?

Yes, Council plugin data migration preserves existing decisions, memories, and archives during the process. It handles schema changes and data format updates automatically to prevent data loss and ensure compatibility across updates.

When do I need to run a data migration for The Council plugin?

You need to run Council plugin data migration after updating the plugin to a new version, such as from v3.1.0-beta to v3.2.0. This ensures your project's .council/ directory is correctly updated to leverage new features and improved reporting.

What directory access is required to update Council plugin data?

Updating Council plugin data requires access to the .council/ directory for data manipulation and version checking. This access allows the migration skill to handle schema transitions and ensure data integrity across plugin versions.

What's the best way to handle schema transitions between Council plugin versions?

The best way to handle Council plugin schema transitions is running the council-update skill, which automatically manages data format updates between versions v2.x through v3.2.0 while preserving existing information and enabling new features.

Why does my Council plugin data need migration after updating to v3.2.0?

Council plugin data needs migration after updating to v3.2.0 because the new version introduces schema changes and features like the value-analyst role. Migration ensures your .council/ directory is correctly updated to leverage these improvements.