n-skills vs skillkit
Curated skill marketplace for AI coding agents on the universal SKILL.md/AGENTS.md format — write a skill once, install it into Claude Code, Codex, Copilot, Cursor and friends. — versus — Package manager for AI agent skills — install from 400K+ skills across 31 sources, auto-translate between 46 agents' incompatible formats, security-scan on install, sync to every agent at once.
Same job — getting skills into any agent's format. skillkit is the breadth play (400K+ skills, 31 sources, security scans); n-skills is the depth play: one small marketplace where a human curated every entry.
| n-skills | skillkit | |
|---|---|---|
| Stars | 1.0k | 1.4k |
| Forks | 105 | 127 |
| Language | TypeScript | TypeScript |
| License | Apache-2.0 | Apache-2.0 |
| Last activity | yesterday | 1 months ago |
| Topics | skills | coding, skills |
| Curated connections | 4 | 11 |
n-skills — the curator's take
The 'write once, run everywhere' bet applied to agent skills: one curated marketplace on the SKILL.md + AGENTS.md conventions, installed via openskills into whichever agent you drive. Smaller and more opinionated than the mega-registries — curation IS the pitch, every skill is hand-picked. NOT a discovery engine: if you want breadth across hundreds of sources, a package manager with security scanning covers more ground; and it's one person's taste with ~1k stars — check the skills you'd rely on exist before adopting the workflow.
skillkit — the curator's take
Use it the moment skills must live on more than one agent — you write Claude SKILL.md, a teammate runs Cursor: author once, `skillkit sync` translates and deploys everywhere; the install-time security scan is a real feature now that skill marketplaces are a prompt-injection vector. NOT needed if you're all-in on a single agent — Claude Code's first-party plugin/marketplace flow is simpler and better supported. Format translation is lossy at the edges (agent-specific frontmatter, hooks, tool references), so verify ported skills actually trigger; and treat the optional mesh/messaging/REST extras as experiments, not infrastructure.