sharing-skills

Branch, commit, push, and open pull requests to share local skills upstream.

4|Updated Oct 3, 2025
One-click install
npx skills add https://github.com/apexbusiness-systems/APEX-OmniHub --skill sharing-skills-apexbusiness-systems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sharing-skills
Source: https://github.com/apexbusiness-systems/APEX-OmniHub/tree/main/.cursor/superpowers/skills/sharing-skills
Command: npx skills add https://github.com/apexbusiness-systems/APEX-OmniHub --skill sharing-skills-apexbusiness-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers share broadly useful skills back to upstream repositories, enabling collaboration and standardization across teams.

Core Features & Use Cases

  • Guided upstream contribution: Provides a repeatable workflow to branch, edit or create skills, commit changes, and open PRs against the upstream repository.
  • Quality-first sharing: Encourages testing, documentation, and alignment with upstream contribution guidelines.
  • Collaboration enablement: Facilitates knowledge transfer by making broadly useful skills discoverable and reusable.

Quick Start

  1. Sync with upstream and switch to main, then push to your fork
  2. Create a feature branch like add-skillname-skill
  3. Add or edit skills/skill-name/SKILL.md with a clear description and guidelines
  4. Commit with a descriptive message including testing notes
  5. Push the branch to your fork and open a PR against upstream

Frequently Asked Questions about sharing-skills

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

FAQPage Schema
How do I contribute a new skill to an upstream repository via a PR workflow?

To contribute a skill upstream, sync your fork with the main branch, create a feature branch like add-skillname-skill, add your SKILL.md file, commit with descriptive testing notes, push to your fork, and open a PR against the upstream repository.

What is the best way to manage git branching when sharing a local skill upstream?

The best way to manage git branching for upstream contribution is to sync with upstream main, push to your fork, and create a dedicated feature branch named add-skillname-skill to isolate your skill changes before opening a PR.

When do I need to use an upstream contribution workflow for skill sharing?

You need to use an upstream contribution workflow when you have created a broadly useful local skill and want to make it discoverable, reusable, and standardized across teams by contributing it back to the central repository.

Does the upstream PR workflow require specific documentation for the skill?

Yes, the upstream PR workflow requires proper PR documentation and alignment with upstream contribution guidelines. You must add or edit the skills/skill-name/SKILL.md file with a clear description and include testing notes in your commit message.

Can I automate creating a pull request for a local skill contribution?

Yes, this skill automates the process of sharing a local skill upstream by guiding the branching, committing, pushing, and PR creation steps to satisfy testable workflow requirements and proper branch management.

What are the limitations of sharing skills back to an upstream repository?

Limitations include the requirement to align with upstream contribution guidelines, the need for testable workflows, and the necessity of proper PR documentation, meaning untested or undocumented skills may be rejected during the upstream review.