refresh-project-agent-routing

Name: refresh-project-agent-routing
Availability: InStock
Author: Guhan

Refresh project agent routing contracts with delta-only file changes.

Updated May 11, 2026

Search Tags:#routing #configuration management #agile development #refresh #project agent

Ready to run

npx skills add https://github.com/guhans6/agent-workbench --skill refresh-project-agent-routing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: refresh-project-agent-routing
Source: https://github.com/guhans6/agent-workbench/tree/main/shared/skills/refresh-project-agent-routing
Command: npx skills add https://github.com/guhans6/agent-workbench --skill refresh-project-agent-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, tomllib, subprocess, shutil, tempfile, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the refresh of existing routing contracts for project agents, ensuring that changes in models, capabilities, tools, or repository evidence are reflected in the routing configuration.

Core Features & Use Cases

Automated Routing Refresh: Refreshes existing routing contracts with minimal changes, preserving all unaffected routes and assignments.
Delta-Only Proposal: Proposes changes only for the affected files, reducing the risk of unintended consequences.
First-Time Routing: Uses project-agent-architect for initial routing.
Use Case: Ideal for environments where routing contracts need to be updated frequently, such as in agile development or when integrating new tools or models.

Quick Start

Run the refresh-routing script with the appropriate parameters to refresh the routing for a specific repository.

Frequently Asked Questions about refresh-project-agent-routing

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

FAQPage Schema

How do I refresh routing contracts for project agents after updating models or tools?▼

Routing contract refresh updates existing agent configurations to reflect changes in models, capabilities, or repository evidence. It proposes delta-only changes for affected files, preserving all unaffected routes and assignments to minimize unintended consequences.

How do I update only the affected files when refreshing agent routing configurations?▼

Run the refresh-routing.py script with the appropriate repository parameters to execute the routing refresh. This script leverages Python3, tomllib, and subprocess to analyze repository evidence and propose delta-only changes for affected files.

Do I need Python3 and tomllib to automate routing refresh for project agents?▼

Yes, automating routing refresh requires Python3, tomllib, subprocess, shutil, and tempfile. These dependencies power the refresh-routing.py script to parse configurations and execute delta-only routing contract updates.

Can I use the refresh script for first-time routing configuration of a new project agent?▼

No, the refresh script handles existing routing contracts only. For first-time routing, use the project-agent-architect to establish initial routes. The refresh script then maintains these contracts by proposing delta-only changes when models or tools update.

When should I avoid using automated routing refresh in agile development environments?▼

Routing refresh is ideal for agile environments with frequent model, tool, or capability updates. It automates routing contract updates with delta-only proposals, reducing manual configuration overhead and ensuring routing accuracy during rapid development iterations.