push-skills

Push exported skills to a GitHub repository as .claude/commands slash-command files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/edri2or/project-life-132 --skill push-skills-edri2or
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: push-skills
Source: https://github.com/edri2or/project-life-132/tree/main/exported-skills/push-skills
Command: npx skills add https://github.com/edri2or/project-life-132 --skill push-skills-edri2or

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pushes portable skills from exported-skills/ to a target GitHub repository as .claude/commands/<name>.md slash-command files. Works for any repo regardless of existing structure — GitHub API creates the directory automatically. Use when you want to install, transfer, or deploy global skills to another repo.

Core Features & Use Cases

  • Automates deployment of global skills to target repositories by creating or updating .claude/commands/ entries and syncing exported-skills SKILL.md.
  • Handles branch creation, per-skill pushes, and PR creation to integrate changes safely across multiple repos.
  • Use Case: Deploy a new global skill to a fresh repository and propagate updates to existing deployments with minimal manual steps.

Quick Start

Execute the push-skills workflow to push all exported-skills/*/SKILL.md into the target repository and create a pull request for review.

Frequently Asked Questions about push-skills

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

FAQPage Schema
How do I deploy global skills to a GitHub repository as slash commands?▼

To deploy global skills to a GitHub repository, push portable skills from exported-skills/ directories into the target repo by creating .claude/commands/<name>.md slash-command files using the GitHub API. This workflow automates the transfer of skills as accessible commands.

Can I push skills to a repository that does not have an existing .claude directory?▼

Yes, you can push skills to any repository regardless of its existing structure. The deployment workflow leverages the GitHub API to automatically create missing directories and files, ensuring the .claude/commands/ path exists in the target repo.

What is the best way to automate skill deployment across multiple repositories?▼

The best way to automate skill deployment across multiple repositories is using a controlled workflow that pushes exported-skills manifests and per-skill commands. It handles branch creation and PR generation to safely integrate slash-command updates across repos.

Does pushing global skills to a repo require manual pull request creation?▼

No, manual pull request creation is not required. The push-skills workflow uses an optional branch creation and PR flow to automatically generate a pull request for review after pushing the .claude/commands/ files and exported-skills manifests to the target repository.

How do I propagate updates to existing slash command deployments in GitHub?▼

To propagate updates to existing slash command deployments, execute the push workflow to push all exported-skills/*/SKILL.md files into the target repository. This updates the existing .claude/commands/ entries and syncs the exported-skills manifests with minimal manual steps.