sharing-skills

Guide contributors through a Git workflow to push skills upstream via PRs.

1|1|Updated Sep 22, 2025
One-click install
npx skills add https://github.com/SkogAI/skillsandknowledge --skill sharing-skills-skogai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sharing-skills
Source: https://github.com/SkogAI/skillsandknowledge/tree/main/skills/claude/skills/sharing-skills
Command: npx skills add https://github.com/SkogAI/skillsandknowledge --skill sharing-skills-skogai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers contribute broadly useful skills upstream by providing a clear, repeatable PR workflow that reduces friction and miscommunication when sharing skills with the wider project.

Core Features & Use Cases

  • Branch and feature-skill isolation to avoid conflicts across projects.
  • Comprehensive PR-based submission with clear guidelines and testing expectations.
  • Step-by-step process to create, test, and propose skill updates to upstream repositories.

Quick Start

  • Sync with upstream: cd ~/.config/superpowers/skills/
  • git checkout main
  • git pull upstream main
  • git push origin main
  • Create feature branch: git checkout -b "add-your-skill-name-skill"
  • Create or edit the skill: skills/your-skill-name/SKILL.md
  • Commit changes: git add skills/your-skill-name/; git commit -m "Add your-skill-name skill Brief description of what this skill does. Tested with: describe testing approach "
  • Push to fork: git push -u origin "add-your-skill-name-skill"
  • Create PR: gh pr create --repo upstream-org/upstream-repo --title "Add your-skill-name skill" --body "## Summary Brief description of the skill and what problem it solves.

Testing

Describe how you tested this skill (pressure scenarios, baseline tests, etc.).

Context

Any additional context about why this skill is needed and how it should be used. "

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 useful skill upstream via a pull request, sync your local repository, create a feature branch named after your skill, and commit your changes before pushing to your fork. You then use the GitHub CLI to open a PR against the upstream repository with a structured body.

What is the correct git workflow for sharing skills across projects?

The correct git workflow for sharing skills involves checking out from main, pulling upstream changes, and creating an isolated feature branch. This branch isolation strategy avoids conflicts across projects while you develop, test, and submit your skill update.

What should I include in a pull request for an upstream skill contribution?

A pull request for an upstream skill contribution should include a summary of the problem solved, a detailed testing section describing your testing approach, and additional context. The commit message must also document the skill's purpose and testing methodology.

Do I need a specific file structure to propose skill updates to an upstream repository?

Yes, proposing skill updates requires a root SKILL.md file containing YAML frontmatter with name and description fields, plus a Markdown body. This structure ensures the skill is loaded correctly during activation and satisfies the requirements for a valid Skill Unit.

Can I use the GitHub CLI to create a PR for a new skill?

Yes, you can use the GitHub CLI to create a PR for a new skill by running the gh pr create command. You must specify the upstream repository, title, and a formatted body containing the summary, testing details, and context.

When should I create a feature branch for skill sharing?

You should create a feature branch for skill sharing immediately after syncing your local main branch with the upstream repository. This isolation step prevents conflicts across projects and ensures your contribution is built on the latest codebase.