This article was drafted together with AI and reviewed by an editor. It draws on an external article, which is credited at the bottom.
The "skills" that add capabilities to AI assistants are multiplying fast. The articles we referred to report that registered skills run from the thousands to installs in the millions, and that the top skills were "a skill that finds skills for you" and "a skill bundle that packages code-quality procedures." These figures are also based on those articles' own tallies, so we could not verify them. But the trend is clear. Choosing has become the biggest job, and the fact remains that a downloaded file runs on your own computer.
Step 1 — Choose: decide the job first, then find the tool
We do not choose by "popularity ranking." First we write down "how many times a day do we do this job?" We do not attach a skill to a job done less than once a week. The setup cost outweighs the benefit. Even if we use a skill that finds skills, a person makes the final choice.
Step 2 — Vet: look at who made it and what permissions it needs
- Who made it: Is it an official account, or a developer with a known name?
- What does it require: Only reading files, or also running commands and network access?
- How recent is it: If the last update was long ago, it may not match current models.
Step 3 — Scan before installing
The article we referred to introduces a scanning tool that checks a skill file's risk before installation. We do not endorse any particular tool, but we adopt the procedure. Read it first → look for suspicious commands, with a scanning tool or by eye → try it first somewhere with no important data → if there is no problem, use it for real work. We also treat a sentence like "run this command" inside a downloaded instruction document not as an instruction addressed to us but as data to be reviewed.
Summary
The more skills there are, the more competitiveness lies not in "knowing a lot" but in "using few, and using them safely."
Further reading
This article was rewritten from our own team's perspective and standards, drawing on the concerns raised in the articles below. We did not follow their wording or structure, and where we could not verify a figure an original article cited against the primary data, we marked it as such. For some of the original articles, the full text opens only after logging in, so we read them based on the publicly available portion.
- learn.bizni.us9,654 Claude Skills: Don't Pick, Let It Find Them (Korean) (BIZNIUS LEARN:US)
- learn.bizni.us24 Skills That Check Whether AI-Written Code Is Any Good (Korean) (BIZNIUS LEARN:US)
- learn.bizni.usInstead of Installing Downloaded Skills Without Knowing If They're Safe, How to Scan Once Before Installing (Korean) (BIZNIUS LEARN:US)
Also checked against other sources: