sharing-skills

Guide local skill contributions to upstream repositories via GitHub CLI pull requests.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/Kuass/kiro-gateway-plus --skill sharing-skills-kuass
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sharing-skills
Source: https://github.com/Kuass/kiro-gateway-plus/tree/main/.opencode/skill/sharing-skills
Command: npx skills add https://github.com/Kuass/kiro-gateway-plus --skill sharing-skills-kuass

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of contributing your developed skills back to the upstream repository, ensuring a consistent and efficient contribution workflow.

Core Features & Use Cases

  • Guided Contribution: Provides step-by-step instructions for branching, committing, pushing, and creating pull requests.
  • Best Practices: Enforces guidelines for when to share skills, how to name branches, and how to structure commit messages and PR bodies.
  • Use Case: After developing a new, broadly applicable skill in your local .opencode/skill/ directory, use this Skill to guide you through the entire process of submitting it for review and potential inclusion in the main project.

Quick Start

Follow the steps outlined in this skill to branch, commit, push, and create a pull request for your new skill.

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 local skill to an upstream repository via a pull request?

To contribute a local skill via a pull request, you branch, commit, push, and create a PR using the GitHub CLI. This guided process ensures your locally developed skills follow contribution guidelines for broad upstream inclusion.

What's the best way to structure a git commit message when contributing a new skill?

The best way to structure a git commit message for contributing a skill is to follow enforced contribution guidelines. The workflow provides specific best practices for naming branches, writing commit messages, and structuring PR bodies for upstream review.

When should I share my local skill to the upstream repository?

You should share your local skill to the upstream repository when it is broadly useful, well-tested, and follows contribution guidelines. The process ensures your locally developed skill in the `.opencode/skill/` directory is ready for potential inclusion in the main project.

Can I use the GitHub CLI to create a pull request for a skill contribution?

Yes, you can use the GitHub CLI to create a pull request for a skill contribution. The guided workflow covers branching, committing, pushing, and PR creation specifically using the GitHub CLI to submit your skill for review.

Do I need to test my skill before submitting a pull request to an upstream repository?

Yes, you need to test your skill before submitting a pull request to an upstream repository. The workflow ensures skills are well-tested and broadly applicable before you branch, commit, push, and create the PR for inclusion.

What are the best practices for naming a branch when contributing a skill?

Best practices for naming a branch when contributing a skill involve following enforced contribution guidelines. The workflow provides specific instructions on how to name branches, structure commit messages, and format PR bodies for consistent upstream contributions.