diegosouzapw/awesome-omni-skill/sharing-skills
Claude Code and agent skill by diegosouzapw/awesome-omni-skill
- community
Checking that the SKILL.md file is still in the repository.
Contribute skills back to upstream via branch and PR
Install
npx vskill@latest install diegosouzapw/awesome-omni-skill/sharing-skillsSKILL.md
The same SKILL.md was published earlier as diegosouzapw/awesome-omni-skill/sharing-skills.
Sharing Skills
Overview
Contribute skills from your local branch back to the upstream repository.
Workflow: Branch → Edit/Create skill → Commit → Push → PR
When to Share
Share when:
- Skill applies broadly (not project-specific)
- Pattern/technique others would benefit from
- Well-tested and documented
- Follows skills/meta/writing-skills guidelines
Keep personal when:
- Project-specific or organization-specific
- Experimental or unstable
- Contains sensitive information
- Too narrow/niche for general use
Prerequisites
ghCLI installed and authenticated- Working directory is
~/.config/superpowers/skills/(your local clone) - Skill has been tested (see skills/meta/writing-skills for TDD process)
Sharing Workflow
1. Ensure You're on Main and Synced
2. Create Feature Branch
3. Create or Edit Skill
4. Commit Changes
5. Push to Your Fork
6. Create Pull Request
Complete Example
Here's a complete example of sharing a skill called "async-patterns":
After PR is Merged
Once your PR is merged:
- Sync your local main branch:
- Delete the feature branch:
Troubleshooting
"gh: command not found"
- Install GitHub CLI: https://cli.github.com/
- Authenticate:
gh auth login
"Permission denied (publickey)"
- Check SSH keys:
gh auth status - Set up SSH: https://docs.github.com/en/authentication
"Skill already exists"
- You're creating a modified version
- Consider different skill name or coordinate with the skill's maintainer
PR merge conflicts
- Rebase on latest upstream:
git fetch upstream && git rebase upstream/main - Resolve conflicts
- Force push:
git push -f origin your-branch
Multi-Skill Contributions
Do NOT batch multiple skills in one PR.
Each skill should:
- Have its own feature branch
- Have its own PR
- Be independently reviewable
Why? Individual skills can be reviewed, iterated, and merged independently.
Related Skills
- skills/meta/writing-skills - How to create well-tested skills
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/testing-security/sharing-skills/SKILL.md
Popularity
- Repository stars
- 39
- Repository forks
- 13
- 7-day trend score
- 18
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 4 May 2026, 6 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/diegosouzapw/awesome-omni-skill/sharing-skills)