rb-setup-local-agent-skills

Audit local RB agent skill installations and symlink targets across Codex and Claude Code.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/richardmbailey/rb-skills --skill rb-setup-local-agent-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rb-setup-local-agent-skills
Source: https://github.com/richardmbailey/rb-skills/tree/main/rb-setup-local-agent-skills
Command: npx skills add https://github.com/richardmbailey/rb-skills --skill rb-setup-local-agent-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves configuration drift, missing dependencies, or discovery issues within your RB agent environment, ensuring your workflows are correctly installed and accessible.

Core Features & Use Cases

  • Environment Verification: Automatically checks for the presence of required global skills and project-specific resources.
  • Repair and Sync: Identifies stale installations and provides the necessary commands to re-synchronize your local skill repository.
  • Use Case: If you have recently updated your repository or moved your agent configuration and find that commands like rb-start-project are no longer recognized, this skill will diagnose the pathing and installation status to restore functionality.

Quick Start

Invoke the rb-setup-local-agent-skills command to perform a full diagnostic check of your current agent environment and receive repair recommendations.

Frequently Asked Questions about rb-setup-local-agent-skills

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

FAQPage Schema
How do I fix agent configuration drift when local skills are missing?

To fix agent configuration drift, you need to verify local directory paths, symlink targets, and global skill availability. Auditing your installation status identifies missing dependencies and provides synchronization commands to restore functionality.

Why does my project workflow fail to recognize agent commands after moving directories?

Project workflows fail to recognize commands because moving directories invalidates symlink targets and pathing configurations. Running a diagnostic check audits local project resources and re-synchronizes the repository to restore command discovery.

What is the best way to verify global skill availability across Codex and Claude Code?

The best way to verify global skill availability is to run a full diagnostic check that audits local filesystem paths and global configurations across Codex and Claude Code environments to ensure workflows are correctly installed.

Do I need filesystem access to troubleshoot agent skill synchronization issues?

Yes, filesystem access is required to troubleshoot agent skill synchronization. The diagnostic process validates local configuration files, checks symlink targets, and executes synchronization scripts to repair stale installations.

How do I repair stale local agent skill installations?

To repair stale local agent skill installations, execute a diagnostic audit of your local repository to identify pathing errors and missing dependencies, then apply the provided synchronization commands to re-sync your environment.