Skillbox keeps your AI skills in one library and syncs them to Claude Code, Cursor and Codex. Follow GitHub sources, review diffs, and scan each version for prompt injection. Trim shortens noisy command output so sessions last longer.
Hi Product Hunt, I'm Adenekan Wonderful, the maker of Skillbox.
I built this because my AI skills were everywhere. A few lived in GitHub repos, some sat inside project folders, and some were installed for Claude Code but missing from Cursor. A better version of one would turn up and I'd have no idea. Copying files was easy. Knowing what I had, where it came from, whether it had changed, and whether it was safe was the hard part.
So Skillbox does four things:
One library, and a smaller active set. Keep everything you've collected, and deliver only what each tool or project needs. Every skill your agent loads costs context, so we don't treat "saved" as "installed".
Sources stay attached. Skills added from GitHub or GitLab keep following their source. When one changes, you see the diff and decide whether to take it.
Trust, per version. Each version is scanned for prompt injection, data exfiltration, command injection, hardcoded secrets and obfuscated code, including by Cisco's Skill Scanner. Approval is tied to the exact content that was reviewed, so it doesn't carry over silently when a skill changes. A passing check is evidence, not a guarantee.
Trim. It shortens noisy test, git and build output before your agent reads it. The full output stays one command away, and your sessions last longer.
It syncs across Claude Code, Cursor and Codex. Trim currently covers more than that, but session insights are deepest on Claude Code.
There's a permanent free plan for the library, sync, updates and Trust. Trim and AI features are on Individual, with a 7-day trial.
I'd love to hear how your skills are scattered today, and what would make you trust a skill you didn't write. I'm here all day and will reply to everything.
I keep a few dozen skills across my coding agents, many pulled from GitHub repos, and keeping them in sync is exactly the mess you describe. The prompt-injection scan on each version is the part I care about most: a skill update is instructions that run with my permissions.
Does the scan run locally, and can I pin a source to a version I've reviewed, so new versions wait for my approval?
We have one skill that only makes sense in one repo, it's about our deploy scripts. Can I keep it active there and nowhere else?
We publish skills for coding agents, and besides the skill files, each agent wants the MCP server the skills use declared in its own way: Claude Code with "type": "http", Cursor with just the address, Codex with "streamable-http" in an mcp.json.
Does Skillbox carry a skill's server entry across tools, or only the skill files?
About Skillbox on Product Hunt
“One library for your AI skills, synced to every agent”
Skillbox launched on Product Hunt on November 11th, 2026 and earned 83 upvotes and 7 comments, placing #10 on the daily leaderboard. Skillbox keeps your AI skills in one library and syncs them to Claude Code, Cursor and Codex. Follow GitHub sources, review diffs, and scan each version for prompt injection. Trim shortens noisy command output so sessions last longer.
Skillbox was featured in Productivity (665.3k followers), Developer Tools (522.9k followers) and Artificial Intelligence (483.4k followers) on Product Hunt. Together, these topics include over 407.8k products, making this a competitive space to launch in.
Who hunted Skillbox?
Skillbox was hunted by Adenekan Wonderful. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Skillbox stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Adenekan Wonderful
Hi Product Hunt, I'm Adenekan Wonderful, the maker of Skillbox.
I built this because my AI skills were everywhere. A few lived in GitHub repos, some sat inside project folders, and some were installed for Claude Code but missing from Cursor. A better version of one would turn up and I'd have no idea. Copying files was easy. Knowing what I had, where it came from, whether it had changed, and whether it was safe was the hard part.
So Skillbox does four things:
One library, and a smaller active set. Keep everything you've collected, and deliver only what each tool or project needs. Every skill your agent loads costs context, so we don't treat "saved" as "installed".
Sources stay attached. Skills added from GitHub or GitLab keep following their source. When one changes, you see the diff and decide whether to take it.
Trust, per version. Each version is scanned for prompt injection, data exfiltration, command injection, hardcoded secrets and obfuscated code, including by Cisco's Skill Scanner. Approval is tied to the exact content that was reviewed, so it doesn't carry over silently when a skill changes. A passing check is evidence, not a guarantee.
Trim. It shortens noisy test, git and build output before your agent reads it. The full output stays one command away, and your sessions last longer.
It syncs across Claude Code, Cursor and Codex. Trim currently covers more than that, but session insights are deepest on Claude Code.
There's a permanent free plan for the library, sync, updates and Trust. Trim and AI features are on Individual, with a 7-day trial.
I'd love to hear how your skills are scattered today, and what would make you trust a skill you didn't write. I'm here all day and will reply to everything.