sharing-skills

Guide branch creation, editing, testing, and pull requests for upstream skill contributions.

Updated Dec 9, 2025

Search Tags:#git #workflow #pull-request #upstream #share #skill-contribution

Ready to run

npx skills add https://github.com/h4v1d/extension-collection-geminicli --skill sharing-skills-h4v1d

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sharing-skills
Source: https://github.com/h4v1d/extension-collection-geminicli/tree/main/sharing-skills
Command: npx skills add https://github.com/h4v1d/extension-collection-geminicli --skill sharing-skills-h4v1d

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides developers on contributing broadly useful skills upstream, ensuring a repeatable, well-documented process for branching, editing, testing, pushing, and creating PRs.

Core Features & Use Cases

Structured workflow: Branch, edit/create a skill, commit, push, and open a PR to contribute the skill back to the upstream repository.
Quality and collaboration: Encourages testing, documentation, and clear PR context to facilitate upstream acceptance.
Use Case: When you have a universally useful skill to share across teams, this Skill provides a proven, auditable workflow to upstream it.

Quick Start

Use the described workflow to prepare a new skill for upstream contribution by creating a branch, editing skills/your-skill/SKILL.md, and opening a PR.

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 broadly useful skill upstream via a pull request?▼

To contribute a skill upstream, create a branch, edit skills/your-skill/SKILL.md, commit changes, push to the repository, and open a pull request. This workflow ensures contributions are repeatable, well-documented, and auditable for upstream acceptance.

What is the correct repository structure and frontmatter required for sharing a skill?▼

The correct repository structure for sharing a skill requires a dedicated skills directory containing a SKILL.md file with specified frontmatter. You can also include optional resources like scripts, references, and assets to fully document and organize the skill contribution.

When should I upstream a skill instead of keeping it project-specific?▼

You should upstream a skill when it is broadly useful and not project-specific. If the skill provides universal value that should be shared across teams, it qualifies for the upstream contribution workflow to make it available to other developers.

What's the best way to prepare a new skill for an upstream pull request?▼

The best way to prepare a skill for an upstream pull request is to follow a structured workflow: create a branch, edit or create the skill file, test it locally, commit with clear messages, push the branch, and open a PR with clear context to facilitate acceptance.

Does contributing a skill upstream require testing and documentation before pushing?▼

Yes, contributing a skill upstream requires testing and documentation before pushing. Quality and collaboration are encouraged through local testing, clear frontmatter documentation, and providing full PR context to ensure the upstream repository maintainers can easily review and accept the contribution.