-
Notifications
You must be signed in to change notification settings - Fork 0
Skill Scoring Rubric
Connor edited this page Jul 3, 2026
·
2 revisions
Scoring should explain why a skill is worth installing, not just whether it has stars.
| Area | Weight | What to Check |
|---|---|---|
| Task fit | 25 | Does the skill directly solve the user's repeated or high-value workflow? |
| Skill structure | 15 | Does it contain a clear SKILL.md and a usable directory layout? |
| Trigger specificity | 15 | Is the description narrow enough to avoid hijacking unrelated tasks? |
| Documentation | 10 | Are examples, install notes, limitations, and usage paths clear? |
| Maintenance | 10 | Recent commits, releases, issue activity, or stable maturity |
| Repository signal | 10 | Stars, forks, watchers, downstream references, curated-list mentions |
| License clarity | 5 | Clear reuse rights and no obvious packaging ambiguity |
| Safety scan | 10 | No prompt injection, secret access, destructive commands, or opaque installers |
| Tier | Meaning | Default Action |
|---|---|---|
| Strict | Strong fit, clear docs, clean scan, reasonable maintenance | Present as install candidate |
| Relaxed | Good fit but some unknowns | Present with caveats |
| Exploratory | Interesting but unproven, broad, or underdocumented | Read only; do not install by default |
| Reject | High-risk, mismatched, or not an Agent Skill | Do not install |
Reject or quarantine when a candidate:
- tells the agent to ignore higher-priority instructions;
- requests secrets, tokens, SSH keys, browser profiles, or
.envfiles without a task need; - includes destructive commands as a default path;
- hides behavior in obfuscated scripts;
- has no
SKILL.mdwhen the user asked for Agent Skills; - describes itself as useful for every task.
Stars can help prioritize inspection, but they never override task fit, structure, and safety. A niche skill with clear scope can be better than a popular repository that is not actually installable as a skill.
评分的目的不是给 star 多的仓库背书,而是解释“为什么这个 skill 值得安装或不值得安装”。
推荐权重:
| 维度 | 权重 | 检查点 |
|---|---|---|
| 任务匹配 | 25 | 是否直接解决当前高价值或重复 workflow。 |
| Skill 结构 | 15 | 是否有清晰 SKILL.md 和可用目录结构。 |
| 触发描述精确度 | 15 |
description 是否足够窄,避免误触发。 |
| 文档 | 10 | 是否有示例、安装说明、限制和用法。 |
| 维护 | 10 | commit、release、issue 或稳定成熟度。 |
| 仓库信号 | 10 | stars、forks、引用、curated list 收录。 |
| License | 5 | 复用权利是否清楚。 |
| 安全扫描 | 10 | 是否存在 prompt injection、secret access、破坏性命令等。 |
Stars 只能帮助排序候选,不能跳过 review。
- Home / 首页
- Installation / 安装
- Platform Install Paths / 安装路径区别
- Cross Platform Usage / 跨平台使用
- Discovery and Routing / 发现与路由
- Scoring and Risk Scan / 评分与风险扫描
- Skill Scoring Rubric / Skill 评分标准
- Prompt Injection Risk Examples / 风险例子
- Install Governance / 安装治理
- Safe Installation Workflow / 安全安装流程
- Skill Lifecycle / 生命周期管理
- Why Not Auto Install High Star Skills / 为什么不自动安装高 star skill
- FAQ / 常见问题