skills.rest
Crumbgrabber
CrumbgrabberCOMMUNITY
Explore all skills by this author →
Website𝕏@crumbgrabbersGitHub

sharing-skills

Guide users through contributing a new skill via GitHub CLI pull requests.

3|2|Updated Dec 28, 2025
Search Tags:#git#collaboration#contribution#pull request#skill sharing#github
One-click install
npx skills add https://github.com/Crumbgrabber/llm_system_template_agents_skills_patterns_tools_prompts --skill sharing-skills-crumbgrabber
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sharing-skills
Source: https://github.com/Crumbgrabber/llm_system_template_agents_skills_patterns_tools_prompts/tree/main/skills/sharing-skills
Command: npx skills add https://github.com/Crumbgrabber/llm_system_template_agents_skills_patterns_tools_prompts --skill sharing-skills-crumbgrabber

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of contributing newly developed, broadly applicable skills back to the main repository, ensuring consistency and facilitating community growth.

Core Features & Use Cases

  • Guided Contribution Workflow: Provides step-by-step instructions for branching, committing, pushing, and creating pull requests.
  • Best Practices Enforcement: Guides users on when to share a skill and when to keep it personal, promoting quality contributions.
  • Use Case: After developing a new, generally useful skill for managing API keys, you can follow this guide to properly format and submit it for inclusion in the central skill library.

Quick Start

Follow the steps in this skill to branch, commit, and push your new skill to the upstream 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 new skill to an upstream GitHub repository?▼

To contribute a skill upstream, you branch your changes, commit your work, push to your fork, and submit a pull request using the GitHub CLI. This workflow ensures your new skill is properly formatted for the central repository.

When should I share a skill upstream versus keeping it personal?▼

You should share a skill upstream when it is broadly useful, well-tested, and documented. If the skill is highly specific to your personal workflow, it is best kept as a private contribution rather than submitted to the central library.

What is the best way to create a pull request for a skill using the GitHub CLI?▼

The best way to create a pull request for a skill is to follow a guided contribution workflow using the GitHub CLI. This involves pushing your committed skill to a fork and executing the CLI command to open a pull request against the upstream repository.

Do I need to fork a repository before contributing a new skill?▼

Forking a repository is a required step for contributing a new skill. You must push your committed skill changes to your fork before you can open a pull request to merge those updates into the upstream repository.

Can I use git to submit a skill contribution without the GitHub CLI?▼

While you can use standard git commands for branching, committing, and pushing, the GitHub CLI streamlines the pull request creation step. Using the CLI ensures the skill contribution workflow is completed efficiently without leaving the terminal.

Related Skills

Explore More Software Engineering Skills→
mnthemnthe

project-init

Create a Python automation project scaffold with docs, src, and tests directories.

Community
Intermediate
spencerpaulyspencerpauly
672

babysitting-pr

Monitor open pull requests and resolve CI failures, review comments, and merge conflicts.

Community
Advanced
julianobarbosajulianobarbosa
7

Git

Automate Git commit, branch, merge, and PR workflows with GitHub CLI and security checks.

Community
Advanced
twjarviszyra-webtwjarviszyra-web
3

github-code-review

Review GitHub code changes for defects, security risks, and improvements.

Community
Advanced