Skip to content

Why Not Auto Install High Star Skills

Connor edited this page Jul 3, 2026 · 2 revisions

Why Not Auto Install High Star Skills

High-star repositories are useful discovery signals, but they are not install decisions.

Stars Do Not Prove Fit

A repository can be popular because it is:

  • a general tool, not an Agent Skill;
  • useful for a different agent surface;
  • old but historically famous;
  • broad enough to attract attention but too vague for skill routing;
  • impressive as a project but irrelevant to the user's current task.

Stars Do Not Prove Safety

High-star projects can still contain:

  • prompt injection instructions;
  • opaque install scripts;
  • broad filesystem access;
  • secret-reading behavior;
  • destructive cleanup commands;
  • stale dependencies.

Stars Do Not Prove Installability

The curator should check:

Check Why
SKILL.md exists Confirms it is an Agent Skill
Skill folder is isolated Avoids copying an entire unrelated repository
Description is narrow Prevents mis-invocation
License is clear Reduces reuse ambiguity
Install path is known Avoids partial installs
Safety scan is acceptable Reduces prompt and supply-chain risk

Better Policy

Use stars to rank candidates for review. Do not use stars to skip review.

The best install candidate is usually the smallest skill that clearly solves the current workflow, has understandable files, and has no serious safety findings.

中文说明

高 star 只能说明一个仓库受关注,不能说明它适合当前任务,也不能说明它安全、可安装、可维护。

不能自动安装 high-star skill 的原因:

原因 说明
不一定是 Agent Skill 可能只是普通库、CLI、模板或文章。
不一定匹配任务 热门项目也可能和当前 workflow 无关。
不一定安全 仍可能包含 prompt injection、secret access 或破坏性命令。
不一定可安装 可能没有 SKILL.md,或 skill folder 不独立。
不一定描述精确 触发描述过宽会污染 agent routing。

更好的策略:用 stars 帮助排序候选,但安装前仍然要检查 SKILL.md、目录结构、license、维护状态、触发描述和安全风险。

Clone this wiki locally