sharing-skills

Coordinates branching, committing, pushing fork-based feature branches to upstream PRs for skill contributions.

3|Updated Dec 30, 2025

Search Tags:#documentation #branching #open-source #git-workflow #pull-request #community-contribution #share-skills

Ready to run

npx skills add https://github.com/martin-janci/claude-marketplace --skill sharing-skills-martin-janci

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sharing-skills
Source: https://github.com/martin-janci/claude-marketplace/tree/main/plugins/story-agents/skills/sharing-skills
Command: npx skills add https://github.com/martin-janci/claude-marketplace --skill sharing-skills-martin-janci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enable teams to share broadly useful skills by guiding the process of branching, committing, pushing, and creating PRs to upstream repositories.

Core Features & Use Cases

Provides a standardized workflow for creating skill branches, updating skill documentation, committing with clear messages, pushing to a fork, and submitting PRs to upstream projects.
Documents best practices for testing and documenting skills before sharing, and for coordinating with maintainers.
Use case: when you develop a reusable skill and want it adopted upstream by the community, not just in a single project.

Quick Start

Create a new feature branch named add-<your-skill>-skill, implement the skill in skills/<your-skill>/SKILL.md, commit with a clear message, push to your fork, and open a PR to 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 reusable skill to an open-source upstream repository?▼

To contribute a reusable skill, create a feature branch named add-<skill>-skill, implement it in skills/<your-skill>/SKILL.md, push to your fork, and open a pull request to the upstream repository.

What is the correct git workflow for sharing community contributions broadly?▼

The correct git workflow for sharing community contributions involves a structured process: branching from main, committing with clear messages, pushing to a fork, and submitting a pull request to the upstream project.

When should I submit a pull request to upstream instead of keeping a skill local?▼

You should submit a pull request to upstream when you develop a general-purpose skill useful across multiple projects, rather than a skill tied to a single codebase.

How do I prepare skill documentation before creating a pull request?▼

To prepare skill documentation before a pull request, document best practices within skills/<your-skill>/SKILL.md, test the skill thoroughly, and coordinate with project maintainers.

Does this workflow support branching directly from the main branch for pull requests?▼

Yes, this workflow enforces a structured pattern starting from the main branch to create named feature branches, ensuring clear commit messages before pushing to your fork and opening a PR.

What are the limitations of using a standardized branching workflow for open-source contributions?▼

This standardized branching workflow requires strict adherence to naming conventions like add-<skill>-skill and clear commit messages, meaning informal or unstructured local branches cannot be directly submitted upstream.