team

manage-skills-hub

Manage and use Ray Skills Hub, a GitHub-based skills catalog (compatible with Claude Code and Codex). Use when the user asks to browse available team skills, install a skill from this hub, add or update a skill, prepare a release, maintain CATALOG.yaml/README.md, migrate a local skill into the hub, or record third-party/upstream provenance.

v0.4.0 stable Ray MIT

Install source

复制 raw SKILL.md 链接，或者复制 repo/path 安装命令。

View SKILL.md 
https://raw.githubusercontent.com/Coco422/ray-skills-hub/main/skills/team/manage-skills-hub/SKILL.md

Manage Skills Hub v0.3.0

Overview

Use this skill to operate the Ray Skills Hub with the smallest reliable workflow. The hub is a GitHub repository where each skill remains a normal skill folder, and CATALOG.yaml plus README.md provide the human and machine index.

Repository Shape

Expected layout:

README.md
CATALOG.yaml
skills/
  team/<skill-name>/
    SKILL.md
    references/
    assets/
  personal/<skill-name>/
    SKILL.md
third_party/

Only SKILL.md is required for a skill. Keep optional folders only when they are used.

Common Tasks

Browse Skills

Read CATALOG.yaml first, then README.md if the user needs a human-facing summary. Report skill id, path, version, maturity, owner, and whether it is recommended.

Install a Skill

Claude Code

Copy the skill folder to ~/.claude/skills/<skill-name>/ (global) or <project>/.claude/skills/<skill-name>/ (project-scoped):

# Clone the hub repo
gh repo clone Coco422/ray-skills-hub /tmp/ray-skills-hub

# Copy a team or personal skill
cp -r /tmp/ray-skills-hub/skills/team/<skill-name> ~/.claude/skills/

Or use the install script (if available):

python3 scripts/install-skill-from-github.py \
  --repo <owner>/<repo> \
  --path skills/team/<skill-name>

After installation, restart the Claude Code session (or /skills to reload).

Codex

Copy the skill folder to ~/.codex/skills/<skill-name>/ and restart Codex.

Add or Update a Team Skill

  1. Put team skills under skills/team/<skill-name>/; put Ray personal skills under skills/personal/<skill-name>/.
  2. Ensure folder name equals SKILL.md frontmatter name.
  3. Keep SKILL.md concise; move long material to references/.
  4. Update CATALOG.yaml and the skills table in README.md.
  5. Validate YAML, paths, and name consistency before finishing.

Collaborator PR Flow

For external collaborators, use this exact flow:

  1. Fork Coco422/ray-skills-hub.
  2. Create a branch in the fork, such as feat/add-<skill-name> or fix/update-<skill-name>.
  3. Add or update files only under the relevant skill directory plus CATALOG.yaml and README.md. Team skills go under skills/team/; Ray personal skills go under skills/personal/.
  4. Keep historical versions in Git history; the repository tree should contain only the latest accepted version of each skill.
  5. Push the branch to the fork and open a PR against Coco422/ray-skills-hub:main.
  6. Ask the PR author to include purpose, trigger examples, source/license, assets included, and validation run.

When Ray asks an agent to process a PR, review the diff, verify the catalog and skill frontmatter, check assets/provenance, then either request changes or merge.

Branch Rules

The remote repository should protect main with a GitHub ruleset:

Third-Party or Upstream Skills

Do not trust a moving upstream branch as production input. Record upstream repo, commit/ref, license, importer, and review status. Keep third-party material isolated until reviewed.

Release

For a release, update hub version, skill entry versions, and README install examples. Do not keep draft folders in the repository. If the user asks to push, confirm the Git repo has a remote and use normal git commit/tag/push flow.

Validation

Run targeted checks:

python3 scripts/validate_catalog.py