skills-update

Audit and synchronize the ray-ai-skills repository from local canonical sources.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits and keeps the ray-ai-skills repository aligned with canonical sources under ~/.claude/skills/, ensuring changes are reviewed before syncing to the public mirror and managing the shared-skills lifecycle.

Core Features & Use Cases

  • Audit: compare local mirrors to canonical sources and surface diffs.
  • Sync: update the public mirror after verification without auto-committing.
  • Lifecycle: add/remove skills from the shared list and update README entries accordingly.

Quick Start

Run an audit followed by a sync to apply changes to the skills mirror.

Frequently Asked Questions about skills-update

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

FAQPage Schema
How do I audit and sync a local skills repository from canonical sources?

To audit and sync a skills repository, the tool compares local mirrors against canonical sources under ~/.claude/skills/ and reports differences. Syncing updates the public mirror after verification without auto-committing changes.

Can I add or remove skills from a shared repository using natural language commands?

Yes, you can add or remove skills from the shared repository using natural-language prompts. Commands like 'remove ray-foo' update the shared-skills lifecycle and modify README entries accordingly without manual file editing.

Why audit a skills repository before syncing changes to a public mirror?

Auditing before syncing prevents unreviewed changes from reaching the public mirror. The workflow enforces a comparison between canonical sources and local mirrors, surfacing diffs so you can verify changes before applying them.

Does syncing skills with this workflow auto-commit changes to the public repository?

No, syncing skills does not auto-commit changes to the public repository. The tool mirrors canonical sources while preserving them, reporting all changes so you can review and commit manually after verification.

What is the best way to manage the lifecycle of shared Claude skills across local and mirrored repositories?

Managing shared Claude skills lifecycle involves auditing canonical sources under ~/.claude/skills/, syncing verified changes to the public mirror, and updating the .shared-skills list and README entries through natural-language add or remove requests.

How do I compare local skill mirrors against canonical sources to find differences?

Run an audit to compare local mirrors to canonical sources under ~/.claude/skills/. The audit surfaces diffs between the two locations, ensuring you can review all discrepancies before initiating any synchronization.