Autoskills CLI auto-detects your stack
A new open-source CLI called Autoskills can auto-detect common stacks—React, Next.js, Supabase, Stripe—and install AI-powered developer 'skills' with a single npx command. The tool is pitched as a way to speed repetitive setup and add opinionated AI workflows to projects, which could shorten early-stage wiring for portfolio builds. Because it’s open-source, teams can inspect what it installs and fit it into their own scaffold rather than relying on a closed black box. (x.com)
A coding assistant is only as useful as the setup notes you give it, and most projects start with none. Autoskills is a new command-line tool that tries to fix that by scanning a codebase and installing matching “skills” with one `npx autoskills` run. (github.com) A command-line tool is just a text command you run in a terminal, like telling a computer “set up the boring parts for me.” Autoskills says it reads files like `package.json`, framework config files, and even Gradle files to figure out whether a project uses things like React, Next.js, Supabase, or Stripe. (autoskills.sh, npmjs.com) The “skills” part is a newer pattern in coding tools. Cursor calls Agent Skills an open standard for reusable knowledge and scripts, and Microsoft says the same format can work across Visual Studio Code, GitHub Copilot command line, and GitHub Copilot coding agent. (cursor.com, code.visualstudio.com) Anthropic describes a skill as a folder that can include instructions, templates, and executable code, which Claude loads when relevant instead of stuffing every rule into every chat. That turns a general assistant into something closer to a specialist that already knows the local playbook. (platform.claude.com) Autoskills sits on top of that idea and automates the matching step. Instead of manually hunting for a React best-practices skill and then a Supabase database skill and then a Stripe billing skill, it maps the stack it detects to packages published through `skills.sh` and offers to install them. (autoskills.sh, github.com) The project’s own list is broad enough to show what it is aiming for. The current README names frontend tools like React, Next.js, Vue, Astro, and Tailwind Cascading Style Sheets, backend tools like Express and NestJS, data tools like Supabase, Neon, Prisma, and Drizzle Object Relational Mapper, plus billing with Stripe and cloud platforms like Vercel, Cloudflare, Amazon Web Services, and Azure. (github.com, npmjs.com) It also tries to work with multiple assistants instead of one house brand. The npm page says it installs curated skills for Cursor, Claude Code, and other coding assistants, and the GitHub README says that if Claude Code is the target, the tool writes a `CLAUDE.md` summary file in the project root after installation. (npmjs.com, github.com) There is a practical reason this could catch on with small teams and solo builders. Early project work is full of repetitive wiring like auth patterns, deployment conventions, test setup, and database habits, and Autoskills adds a `--dry-run` mode so developers can preview what would be installed before changing anything. (github.com, autoskills.sh) The open-source part matters because these tools are literally writing guidance into your development workflow. Autoskills is public on GitHub under a Creative Commons Attribution-NonCommercial 4.0 license, with 1.8 thousand stars, 159 forks, and a latest release tagged `v0.2.4` three days ago as of April 10, 2026, which means teams can inspect the mapping instead of trusting a sealed product. (github.com) The catch is that automatic setup is only as good as the opinions it installs. The autoskills site already shows gaps like “Express — no skills yet,” so the tool is less a magic programmer and more a fast dispatcher that connects a known stack to a growing catalog of reusable workflows. (autoskills.sh)
