org-skill-pipeline

Name: org-skill-pipeline
Availability: InStock
Author: edri2or

Automate skill distribution across enrolled GitHub repositories via a three-workflow pipeline.

Updated Aug 23, 2026

Search Tags:#automation #deployment #github-actions #ci-cd #workflows #skill-sync #org-wide

Ready to run

npx skills add https://github.com/edri2or/project-life-132 --skill org-skill-pipeline

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: org-skill-pipeline
Source: https://github.com/edri2or/project-life-132/tree/main/exported-skills/org-skill-pipeline
Command: npx skills add https://github.com/edri2or/project-life-132 --skill org-skill-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Org Skill Pipeline automates organization-wide distribution of skills across GitHub repositories by syncing skills from a central repository to all enrolled org repos, reducing drift and manual setup.

Core Features & Use Cases

3-workflow pipeline that centralizes sync, per-repo fan-out, and distribution to enrolled repos via a reusable workflow.
Auto-deploys skill updates from any repository to a central hub and propagates changes to all targets.
Use Case: An organization wants to standardize skill plugins across dozens of repos with minimal manual maintenance.

Quick Start

Kick off the org-wide skill distribution by deploying the 3-workflow pipeline to automate syncing and distribution of skills across all enrolled repos.

Frequently Asked Questions about org-skill-pipeline

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

FAQPage Schema

How do I automate skill distribution across multiple GitHub repositories in my organization?▼

Automating skill distribution across GitHub repositories requires deploying a 3-workflow pipeline that syncs skills from any repository to a central hub and fans out updates to all enrolled org repos.

What is the best way to standardize skill plugins across dozens of GitHub repositories?▼

Standardizing skill plugins across GitHub repositories is best achieved by centralizing skill updates in a single repository and using a reusable workflow to propagate changes automatically to enrolled targets.

Do I need admin permissions to set up an org-wide GitHub Actions CI/CD pipeline for syncing skills?▼

Yes, setting up an org-wide GitHub Actions pipeline for skill syncing requires admin permissions to configure repository access and manage secrets across the central skills repository and enrolled org repos.

Can I use a centralized GitHub Actions workflow to sync skills from any repository to a central hub?▼

Yes, you can use a centralized GitHub Actions workflow to automatically deploy skill updates from any repository to a central hub, which then propagates those changes to all enrolled org repos.

What limitations exist when using a centralized skills repository for org-wide synchronization?▼

A centralized skills repository for org-wide synchronization requires all enrolled repositories to reside within the same GitHub organization and depends on properly configured access and secrets to avoid sync failures.

How does a 3-workflow pipeline handle per-repo fan-out for organization-wide skill updates?▼

A 3-workflow pipeline handles per-repo fan-out by first centralizing skill sync, then triggering a reusable workflow that distributes the updated skills to each enrolled repository within the organization.