sharing-skills

Define a structured upstream contribution workflow with branching and PR creation.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/Khoiwall/be_vidify --skill sharing-skills-khoiwall
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sharing-skills
Source: https://github.com/Khoiwall/be_vidify/tree/main/.opencode/skill/sharing-skills
Command: npx skills add https://github.com/Khoiwall/be_vidify --skill sharing-skills-khoiwall

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow helps developers share broadly useful skills upstream by guiding how to branch, edit the skill, commit, push, and open a pull request to the upstream repository.

Core Features & Use Cases

  • Guided branching and PR workflow: Streamlines creating feature branches, updating SKILL.md, and submitting PRs to upstream.
  • Standardized contribution process: Ensures consistent skill naming, metadata, and testing before sharing.
  • Broad applicability: Suitable for personal projects and organizational skill-sharing initiatives.

Quick Start

Create or update your skill under skills/your-skill-name/SKILL.md, commit the changes, push to a feature branch, 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 useful skills to an upstream repository via a pull request?

To contribute skills upstream, create a feature branch, add your skill under skills/your-skill-name/SKILL.md, commit changes, push the branch, and open a pull request to the upstream repository.

What metadata is required in a SKILL.md file to open an upstream contribution PR?

A valid SKILL.md requires frontmatter with name and description fields, plus explicit metadata including category, keywords, dependencies, and components to pass upstream contribution checks.

What is the standard git workflow for sharing broadly useful skills across projects?

The standard git workflow for sharing skills involves branching from the main repository, editing the SKILL.md file, committing the updates, pushing to a remote feature branch, and submitting a pull request upstream.

Does my skill need a Quick Start section before I push the branch and create a PR?

Yes, your skill needs a documented Quick Start section in the SKILL.md file before pushing your branch and creating a PR to ensure it meets upstream sharing standards.

Can I use this structured contribution process for organizational skill-sharing initiatives?

Yes, you can use this structured contribution process for organizational skill-sharing initiatives because it standardizes skill naming, enforces metadata consistency, and streamlines the pull request workflow across multiple projects.