sharing-skills

Contribute local skills to an upstream repository via pull requests.

17|Updated Oct 13, 2025
One-click install
npx skills add https://github.com/cipherstash/cipherpowers --skill sharing-skills-cipherstash
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sharing-skills
Source: https://github.com/cipherstash/cipherpowers/tree/main/plugin/skills/sharing-skills
Command: npx skills add https://github.com/cipherstash/cipherpowers --skill sharing-skills-cipherstash

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

This Skill eliminates the confusion and friction around contributing your locally developed skills back to the main repository, ensuring proper version control and collaboration workflows.

Core Features & Use Cases

  • Structured Contribution Process: Guides you through branching, committing, pushing, and creating pull requests for skill contributions.
  • Quality Assurance: Ensures skills are well-tested and documented before sharing with the community.
  • Use Case: Imagine you've created a powerful debugging skill that others would benefit from. Use this Skill to properly contribute it upstream following best practices for version control and collaboration.

Quick Start

Use the sharing-skills skill to contribute your new async-patterns skill to the upstream repository.

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 skill to an upstream repository using Git?

Contributing a skill involves branching from the main repository, creating or editing your skill, committing changes, pushing to your fork, and opening a pull request. The sharing-skills Skill guides you through this branching, committing, pushing, and PR workflow to ensure your contribution follows version control best practices.

What should I include in a pull request when sharing a new skill?

Pull requests for skill contributions require well-tested, well-documented code suitable for general use. The sharing-skills Skill specifies PR content requirements to ensure consistent upstream contributions and community-ready quality.

Do I need the GitHub CLI to share skills upstream?

Yes, the sharing-skills Skill requires the gh CLI as a dependency. You'll also need a local clone of the repository at ~/.config/cipherpowers/skills/ to begin the contribution workflow.

What's the proper workflow for sharing locally developed skills with others?

The structured contribution process follows Branch → Edit/Create skill → Commit → Push → PR workflow. This ensures skills are version-controlled, tested, and documented before reaching the main repository for community use.

Can I share a skill that I've only tested locally?

Skills must be well-tested and well-documented before sharing upstream. The sharing-skills Skill enforces quality assurance requirements, so local-only testing isn't sufficient for community contribution.