autoskills vs n-skills
One command installs your project's AI skill stack: scans package.json/Gradle/configs, detects the tech stack, and pulls matching skills from an audited, hash-verified registry. — versus — 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.
Two curation-first answers to skill installation: autoskills detects your stack and decides for you from a hash-pinned registry; n-skills hands you a small human-curated marketplace on the universal SKILL.md format and lets you pick.
| autoskills | n-skills | |
|---|---|---|
| Stars | 6.5k | 1.0k |
| Forks | 597 | 105 |
| Language | Ruby | TypeScript |
| License | NOASSERTION | Apache-2.0 |
| Last activity | 11 days ago | today |
| Topics | skills | skills |
| Curated connections | 3 | 4 |
autoskills — the curator's take
The zero-config on-ramp for agent skills: `npx autoskills` detects your stack and installs only the matching skills — and the security model is the standout, a maintainer-synced registry scanned for prompt injection with SHA-256 manifests and a lockfile, instead of live-downloading from random repos. NOT for hand-picking: you get the registry's opinion of what a Next.js or Go project needs, and the registry's coverage is web/mobile-stack-shaped — niche stacks fall through. No standard license file at the time of review; check before corporate adoption.
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.