repo-skill-maintenance

Synchronizes shared repo skills between CLAUDE and Codex trees.

19|2|Updated Mar 14, 2025
One-click install
npx skills add https://github.com/ThalesGroup/agilab --skill repo-skill-maintenance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-skill-maintenance
Source: https://github.com/ThalesGroup/agilab/tree/main/.claude/skills/repo-skill-maintenance
Command: npx skills add https://github.com/ThalesGroup/agilab --skill repo-skill-maintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keep shared agent skills synchronized across the CLAUDE and Codex trees, ensuring a single canonical source of truth and drift-free maintenance.

Core Features & Use Cases

  • Canonical contract and placement rules for repo-managed skills to prevent conflicting updates
  • Safe migration of user-managed or local skills into the public repository with drift reconciliation
  • Validation, index regeneration, and targeted synchronization between repo skill trees to maintain consistency
  • Guardrails and documentation for AGILAB workflows to avoid overwriting unrelated content

Quick Start

Identify a shared skill and follow the repo workflow to synchronize, validate, and regenerate the Codex index.

Frequently Asked Questions about repo-skill-maintenance

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

FAQPage Schema
How do I synchronize repo skills across CLAUDE and Codex trees to prevent drift?

To synchronize repo skills and prevent drift, you reconcile shared skills across CLAUDE and Codex trees by enforcing a canonical contract. This maintains a single source of truth through targeted sync and validation.

What is the best way to migrate a local skill into a shared repository without overwriting unrelated content?

Migrating a local skill into a shared repository requires following repo workflow guardrails to safely reconcile drift. These guardrails prevent overwriting unrelated content while enforcing canonical placement rules for the new skill.

How does Codex index regeneration work when updating shared agent skills?

Codex index regeneration updates the index after you add or update a shared skill in the repository. It is part of the validation and targeted synchronization workflow that maintains consistency between the repo skill trees.

Do I need a canonical contract to maintain shared skills across CLAUDE and Codex?

Yes, a canonical contract is required to maintain shared skills across CLAUDE and Codex without drift. It enforces placement rules that prevent conflicting updates and ensure consistent maintenance across both agent skill trees.

When should I use targeted synchronization instead of a full repo skill update?

Use targeted synchronization when reconciling specific Claude or Codex copies to avoid overwriting unrelated skills. It allows you to apply updates and validation only to the shared skills that require drift reconciliation.