SaaS Metrics
Show HN: Sx – an open-source package manager for AI skills, MCPs, and commands
No tagline provided.
View Origin LinkProduct Positioning & Context
Related Ecosystem & Alternatives
Discover adjacent products, open-source repositories, and developer tools sharing similar technical architecture.
Deep-Dive FAQs
What is Sx – an open-source package manager for AI skills, MCPs, and commands?
Sx – an open-source package manager for AI skills, MCPs, and commands is a digital product or tool described as:
Where did Sx – an open-source package manager for AI skills, MCPs, and commands originate?
Data for Sx – an open-source package manager for AI skills, MCPs, and commands was aggregated directly from the Hacker News community ecosystem, representing raw developer and early-adopter sentiment.
When was Sx – an open-source package manager for AI skills, MCPs, and commands publicly launched?
The initial public indexing or launch date for Sx – an open-source package manager for AI skills, MCPs, and commands within our tracked developer communities was recorded on May 16, 2026.
How popular is Sx – an open-source package manager for AI skills, MCPs, and commands?
Sx – an open-source package manager for AI skills, MCPs, and commands has achieved measurable traction, logging over 39 traction score and facilitating 23 recorded discussions or engagements.
What are some commercial alternatives to Sx – an open-source package manager for AI skills, MCPs, and commands?
Our semantic intelligence engine identifies potential commercial alternatives in the SaaS space, such as WX , which offers overlapping value propositions.
Community Voice & Feedback
One more package manager will fix it. One more!I don't disagree there's probably a need and niche, but why not extend and adapt an existing package manager?
[dead]
I've been working on something very similar: https://github.com/shrug-labs/aipack/tree/main/I therefore love the idea. Thanks for sharing
How does one pronounce this tool
[flagged]
[dead]
why this do not belong to git, and does not go with release cycle.With bigger autonomy, I'd like my skill be tight to my release in prod/commit sha for dev, to figure out what version caused harm/bug. What is the motivation to decouple and make it a separate thing?
[flagged]
[dead]
Hi HN — I'm one of the maintainers.The short version: sx treats skills, MCP server configs, slash commands, agents, hooks, and rule files as versioned packages. You define them once, push them to a vault (a local folder, a git repo, or our hosted backend), and install them where they belong. There's a lockfile so installs are reproducible, scope levels for org / team / repo / individual, and the CLI translates the same asset into the format each AI client expects.Supported clients today: Claude Code, Cursor, GitHub Copilot, Cline, Codex, Gemini (CLI / VS Code / JetBrains / Android Studio), Kiro, claude.ai, chatgpt.com. The last two are what let non-engineering teams (marketing, legal, ops) use the same primitive instead of being locked out of the AI-assets ecosystem.The thing I'd most like feedback on is whether the scope model is the right shape. Org → team → repo → path → individual is what's emerged from talking to ~60 teams over the last six months, but I expect bigger orgs will surface scopes we haven't modeled (sub-team, environment, etc.).Why this and not just plugins / vendor marketplaces? Claude Code plugins are real and a good step up over raw git-checked-in CLAUDE.md files. The limitations show up at scale: each plugin is scoped to its publishing repo, so teams duplicate skills across plugins, and you're still locked to a single vendor's client. Full writeup with the technical details: https://www.sleuth.io/post/there-s-an-npm-shaped-hole-in-the...
Discovery Source
Hacker News Aggregated via automated community intelligence tracking.
Tech Stack Dependencies
No direct open-source NPM package mentions detected in the product documentation.
Media Tractions & Mentions
No mainstream media stories specifically mentioning this product name have been intercepted yet.
Deep Research & Science
No direct peer-reviewed scientific literature matched with this product's architecture.