sharing-skills

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

1|Updated Sep 26, 2025
One-click install
npx skills add https://github.com/pascallammers/mylo-travel-concierge-v2 --skill sharing-skills-pascallammers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sharing-skills
Source: https://github.com/pascallammers/mylo-travel-concierge-v2/tree/main/.factory/skills/sharing-skills
Command: npx skills add https://github.com/pascallammers/mylo-travel-concierge-v2 --skill sharing-skills-pascallammers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a clear, step-by-step process for contributing newly developed skills back to the upstream repository, ensuring consistency and facilitating community growth.

Core Features & Use Cases

  • Streamlined Contribution: Guides users through branching, committing, pushing, and creating pull requests for new skills.
  • Best Practices: Emphasizes when to share a skill and when to keep it personal, along with prerequisites like testing and CLI setup.
  • Use Case: After developing a new, broadly applicable skill for managing API keys, you can use this guide to ensure it's properly formatted, tested, and submitted for inclusion in the main project.

Quick Start

Follow the workflow to create a feature branch for your new skill named 'api-key-management'.

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

To contribute a skill via pull request, create a feature branch, commit your changes, push to the repository, and use the GitHub CLI to open a PR for upstream review.

When should I share a developed skill upstream instead of keeping it personal?

You should share a skill upstream when it is broadly applicable and thoroughly tested, ensuring it provides value to the community while adhering to formatting best practices.

Do I need the GitHub CLI installed to submit a skill pull request?

Yes, the GitHub CLI is required to execute the workflow for pushing branches and creating pull requests when contributing your developed skills to the upstream repository.

What is the correct workflow for managing multi-skill contributions in git?

Managing multi-skill contributions involves creating separate feature branches for each skill, editing, committing, pushing, and submitting distinct pull requests to maintain organized upstream review.

What are the prerequisites for submitting a new skill contribution to GitHub?

Prerequisites for a skill contribution include completing local testing, verifying proper formatting, and setting up the GitHub CLI to facilitate the branch and pull request workflow.