Sharing Skills

Automate skill contributions to a community repository via GitHub CLI pull requests.

3|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/trae-community/trae-templates --skill sharing-skills-trae-community
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Sharing Skills
Source: https://github.com/trae-community/trae-templates/tree/main/templates/tools-devops/superpowers-trae-init/.trae/skills/sharing-skills
Command: npx skills add https://github.com/trae-community/trae-templates --skill sharing-skills-trae-community

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of contributing valuable skills upstream by automating branch management, commits, and pull request creation.

Core Features & Use Cases

  • Automated Workflow: Guides users through cloning, branch creation, and pushing skills for contribution.
  • Pull Request Generation: Creates detailed PRs with structured content describing the skill and testing instructions.
  • Use Case: A developer has created a new skill and wants to submit it for review; this Skill automates the entire contribution process from local updates to upstream PR.

Quick Start

Create a new skill, commit your changes, push the branch, and run the command to generate a pull request automatically.

Frequently Asked Questions about Sharing Skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a GitHub pull request for a new skill contribution?

Automating a GitHub pull request for a new skill contribution involves using CLI commands to manage branches and generate structured PRs. This Skill streamlines the workflow from local commits to upstream submission with detailed descriptions.

What is the best way to manage branches when contributing upstream via GitHub CLI?

Managing branches when contributing via GitHub CLI requires creating dedicated branches for single-skill updates. This automation facilitates quick branch creation, pushing changes, and ensuring contributors follow best practices for isolated PRs.

Can I submit multiple skill updates in a single pull request?

Submitting multiple skill updates in a single pull request is discouraged. This workflow enforces best practices for single-skill PRs to maintain efficient collaboration and ensure structured, comprehensive descriptions for each contribution.

How does automated pull request generation work for community repositories?

Automated pull request generation for community repositories works by cloning, branching, and pushing changes through CLI commands. It then creates detailed PRs with structured content describing the skill and providing necessary testing instructions.

Do I need to manually write PR descriptions when contributing skills through CLI?

Manually writing PR descriptions when contributing skills through CLI is unnecessary. The automation generates comprehensive, structured pull request content automatically, describing the skill and including testing instructions for reviewers.