Introduction
Most teams that use AI coding clients end up with skill files scattered everywhere. Someone in legal writes a good contract-review prompt, someone in sales has a call-summary skill, and they live in personal folders or Slack threads. Developers can put these in a git repo. Most other staff won't.
Sx 2.0 (Sx) is an open source package manager for AI assets from Sleuth. It handles skills, MCP configs, rules and commands. Version 2.0, announced on 10 July 2026 by Dylan Etkin, adds a native desktop app for Mac, Windows and Linux. Its main idea is simple. You point the app at a shared Dropbox, Google Drive, OneDrive or iCloud folder, and that folder becomes your team's skill library. Per the announcement, you need no git, no terminal, no server and no accounts.
scored.tools has not run Sx. This review relies on the maker's announcement post and the everydev.ai directory listing, and it says so wherever that matters. Sx gets an overall rating of 6.6/10. It scores well on price and ease of use, and lower where independent evidence is missing.
Key Features
Desktop app for people who avoid the terminal
The 2.0 release targets non-developers. Sleuth says it built the app after about sixty discovery interviews this year, and it names marketing, legal, sales and ops as the audience. These people write skills but stay away from the command line. Per the post, you open the app, point it at a cloud folder and drag skills in. Downloads are in the GitHub release assets for all three desktop platforms.
Shared-folder library
Your file sync service does the replication. When a teammate publishes a skill to the shared folder, everyone else connected to that folder sees it. Sleuth's pitch is that a team already pays for Dropbox or Google Workspace, so it needs no new infrastructure. The vault format (v2) stores the latest version of each asset as plain markdown in assets/<name>/, with history in .sx/versions/. So you can grep the vault, open it in Obsidian or link it to .claude/skills.
One library, many clients
Sx installs skills into Claude Code, Cursor, Copilot, Codex, Gemini, Cline and Kiro. When you click Sync, the app runs sx install in the background. Per the post, it translates each asset into the format each client expects (Claude Code skills, Cursor rules, Copilot instructions) and writes it to the right local path. If your team is split between Claude Code and Cursor, this is the main reason to look at Sx.
Git vaults for developers
The developer workflow from earlier versions still works. Skills can be versioned in git vaults with a lock file and deterministic installs. The CLI is a Go binary (brew install sx), and the app and CLI read the same vaults. Engineers can keep strict versioning while the rest of the company uses the folder.
Collections and extensions
Collections group related skills that install as a unit. Membership is resolved at read time, so a skill added to a shared collection reaches teammates without anyone re-running anything. Extensions are a folder with a manifest and one ES module, with no build step. The bundled marketplace ships 15 of them, per the post. Examples include Collection Doctor, which scores collections from 0 to 100 and flags issues, and Collection Export, which compiles a collection to a Claude Code, Codex or Gemini plugin or a zip. Extensions are permission-gated. They get no filesystem, Node or network access beyond hosts they declare, and org admins can allowlist or disable third-party extensions.
Pricing Breakdown
| Plan | Price | What you get |
|---|---|---|
| Open source | Free | Package manager for AI assets, git vaults, desktop app for Mac, Windows and Linux |
Sx is free and licensed under Apache 2.0, with source at github.com/sleuth-io/sx. The announcement doesn't mention pricing. The everydev.ai listing does show a paid Sleuth plan, but that belongs to a separate Sleuth product. Sx itself has no required paid dependency. Your real cost is the cloud storage you already pay for. The flip side is that you get no paid support tier or SLA, and you get none of the team-admin features a commercial product would sell you.
Scores
| Criterion | Score | Basis |
|---|---|---|
| Output quality | 5/10 | Only vendor descriptions of format translation and markdown storage. No independent results. |
| Ease of use | 8/10 | Open app, point at a folder, drag skills in. A docs page could not be found. |
| Pricing value | 9/10 | Free, Apache 2.0, no required paid dependency. |
| API and integration | 6/10 | Seven supported clients, a lock file and a CLI. No documented API or SDK found. |
| Problem fit | 5/10 | The vendor describes the workflow. The directory lists no user ratings to confirm it delivers. |
| Overall | 6.6/10 |
Pros & Cons
Pros
- It reuses a sync service your team already pays for, so you run no server and manage no accounts, per the post.
- It is built for non-developers who write skills but avoid git.
- One library installs into seven AI clients, from Claude Code to Kiro.
- It is open source under Apache 2.0, with a lock file for repeatable installs.
- The vault is plain markdown, so you can leave Sx and keep your files.
- Extensions are permission-gated, and admins can allowlist or block them.
Cons
- A synced folder gives you less access control and audit history than a git workflow. Anyone with write access to the Dropbox folder can change what the whole team installs.
- Sleuth itself says it is least sure the shared-folder setup holds up under real Dropbox latency, and it asks users to report where it breaks.
- How portable a skill is depends on each client's own skill and MCP support. Translation can't add features a client lacks.
- The evidence is thin. The announcement is the main source, no docs page turned up, and the directory listing has no user ratings.
- 2.0 is new, so it has little public track record yet.
Who Is It For
The best fit is a mixed team where a few developers already manage skills in git and everyone else keeps prompts in Google Docs. Sx lets the ops lead or the legal counsel publish a skill by dropping a markdown file into a folder they already use, while engineers keep the git vault and lock file. It also suits small companies that use more than one AI client and want one source of truth instead of copying rules between .cursor and .claude directories.
It fits less well in regulated teams that need approval flows, per-user permissions and a full audit trail on who changed which skill. Version history in .sx/versions/ helps. Folder-level sync permissions are still a blunt tool, though. If you want to pack code context for an LLM rather than manage reusable skills, Repomix solves a different problem.
Verdict
Sx 2.0 takes a sensible route to team skill sharing. It reuses the shared folder most offices already have and leaves the replication work to Dropbox or Drive. It costs nothing, the files stay as plain markdown, and the multi-client install covers the AI tools most teams use. Those are the reasons behind the 9 for pricing value and the 8 for ease of use.
The 6.6 overall reflects the gaps. Almost everything known about Sx comes from Sleuth's own blog post, and the maker itself flags sync latency as an open question. Our recommendation: if your non-developer staff are writing skills and have no good way to share them, install Sx 2.0 and pilot it with one small team on a test folder before rolling it out. Developers who want strict versioning should stick with the git vaults, which Sx still supports. Wait for user reports before trusting the folder model with anything sensitive.
