sharing-skills

Contribute skills to upstream repositories via branch, commit, push, and PR workflow.

Updated Nov 3, 2025

Search Tags:#git #workflow #contribution #pull request #open source #skills #sharing

Ready to run

npx skills add https://github.com/ayourtch/kimichat --skill sharing-skills-ayourtch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sharing-skills
Source: https://github.com/ayourtch/kimichat/tree/main/skills/sharing-skills
Command: npx skills add https://github.com/ayourtch/kimichat --skill sharing-skills-ayourtch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of contributing valuable skills back to a shared repository, ensuring your proven techniques benefit others and adhere to contribution standards.

Core Features & Use Cases

Standardized Workflow: Guides through Git operations (branching, committing, pushing) and Pull Request creation for skill contributions.
Contribution Best Practices: Ensures skills are well-tested, documented, and broadly applicable before sharing them upstream.
gh CLI Integration: Provides commands for creating pull requests using the GitHub CLI, simplifying the submission process.
Use Case: After developing a new async-patterns skill and thoroughly testing it, use this skill to create a feature branch, commit your changes, and submit a pull request to the upstream repository.

Quick Start

I'm using the sharing-skills skill to contribute my new error-handling-patterns skill to the main 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 open source repository using Git?▼

Contributing a skill involves creating a feature branch, editing or creating a SKILL.md file in the skills/category/skill-name/ directory, committing your changes, pushing to your fork, and opening a pull request via the gh CLI. Follow the conventional skill structure and ensure your skill is tested via the writing-skills TDD process before submission.

What's the standard workflow for submitting a pull request with a new skill?▼

The workflow is: branch from main, create or edit your SKILL.md file, commit with clear messages, push to your remote, then use gh CLI to create a pull request. Ensure proper branch hygiene, resolve any conflicts, and include testing and context metadata so maintainers can evaluate your contribution for upstream adoption.

Do I need to test my skill before sharing it to the main repository?▼

Yes, testing is required before contribution. Use the writing-skills TDD process to validate your skill thoroughly. Testing ensures your skill is reliable and broadly applicable, which is essential for upstream adoption and maintains repository quality standards.

What documentation structure does a shared skill require?▼

A shared skill must follow the conventional structure: skills/category/skill-name/SKILL.md. The SKILL.md file should document your skill clearly and include testing metadata and context information. This standardized format helps maintainers review and integrate your contribution consistently.

How do I handle merge conflicts when contributing a skill upstream?▼

When conflicts arise during a pull request, resolve them locally on your branch, commit the resolution, and push the updated commits. The gh CLI and Git workflow manage this; clear branch hygiene—keeping your branch updated and commits atomic—minimizes conflicts and simplifies the review process.

Can I use the gh CLI to automate my pull request creation for skill contributions?▼

Yes, the gh CLI is integrated into this workflow to simplify pull request creation. After pushing your branch with your skill changes, use gh to create and submit your PR directly from the command line, streamlining the contribution process for skill sharing.