Most AI skills, the prompts and workflows that make AI useful, stay stuck with the engineers: buried in repos and Slack, out of reach for non-technical teammates. Install one MCP server and your whole org (sales, marketing, ops, not just devs) gets a shared catalog of AI skills they use by name inside Claude, Cursor, ChatGPT, or Gemini. No code required. Anyone can create and share skills; admins govern with review and versioning; and skills can be Git-backed, with edits syncing as PRs.
Hey Product Hunt 👋
I'm Hamza. Everyone's figuring out great ways to use AI: prompt workflows, coding patterns, analysis playbooks, review checklists. But the good ones stay trapped with the technical folks, in GitHub or Slack threads or someone's head. The non-technical teammates who'd benefit most never get them.
Skillburst is our fix. Install one MCP server and your whole org gets a shared catalog of AI skills. A marketer can open claude.ai, ask for the "investor update" skill by name, and just use it. No code, no setup, no new app to learn. Anyone can create and share skills, an admin reviews the org-wide ones, and everyone stays on the latest version automatically. Engineers who live in GitHub can sync skills straight from their repos, with edits flowing back as pull requests.
The hard part was making "share this with my whole company" feel as safe and versioned as merging code, while staying dead simple for someone who's never touched a terminal.
We're in early access and it's free for 15 days with everything unlocked. I'd genuinely love your feedback (bugs go to info@skillburst.ai, straight to me).
Looking forward to your feedback!
Report
Finally something that gets AI skills out of engineering-only territory. The Git-backed sync as PRs is a nice touch, keeps everything auditable without forcing non-technical folks to learn git. Curious how version conflicts play out across a large team.
@enolgneypnpqwr Its versioned semantically and is linked to git branches :)
Report
Finally, a way to stop pestering our devs for the prompts they swear work in Cursor. Setting it up was genuinely painless and the PR-backed edits make me feel like marketing can't accidentally nuke the sales team's skills.
GitTrends
Finally something that gets AI skills out of engineering-only territory. The Git-backed sync as PRs is a nice touch, keeps everything auditable without forcing non-technical folks to learn git. Curious how version conflicts play out across a large team.
GitTrends
@enolgneypnpqwr Its versioned semantically and is linked to git branches :)
Finally, a way to stop pestering our devs for the prompts they swear work in Cursor. Setting it up was genuinely painless and the PR-backed edits make me feel like marketing can't accidentally nuke the sales team's skills.
GitTrends
@tlay1638040 :-)!