TrustSkills
Overview
TrustSkills is the compact first version of TrustSkills. It does not do deep technical verification yet. It answers one earlier and simpler question before install: "Can I trust where this skill came from?"
Use it to verify source provenance before installation by checking a short list of trusted distribution channels and clearly separating:
- - official vendor-owned sources
- official discovery indexes
- unsupported or unverified third-party sources
Primary Usage
The natural invocation pattern for this skill is:
Examples:
When invoked this way, treat the URL after /trustskills as the source under review and answer directly.
The primary job is to decide:
- - trust
- do not trust
- trust the directory, but not automatically the specific item
When To Use This Skill
Use this skill when the user asks questions like:
- - "/trustskills https://clawhub.ai/steipete/model-usage"
- "/trustskills https://github.com/likw99/agent-skills"
- "Is this skill source official?"
- "What is the official GitHub repo for Codex or Claude skills?"
- "Can I trust this marketplace or directory?"
- "Is
skills.sh official?" - "Which GitHub repos count as official skill distribution channels?"
This skill is especially useful when the source is:
- - a GitHub repository
- a marketplace or agent store
- a vendor docs page
- a directory site such as INLINECODE5
What This Skill Does
This skill:
- - identifies the platform
- checks whether the source matches a compact trusted root list
- makes a trust decision under the current compact policy
- cites the strongest trusted distribution channel available
- explains the safest known install path
- warns when a directory is official but the listed repo is not automatically official
This skill does not:
- - certify code safety
- perform malware analysis
- verify signatures or SBOMs
- prove that a popular listing is safe
- prove that installability means officiality
- explain what the skill does unless the user explicitly asks for that
Workflow
- 1. Parse the command input.
If the user provides
/trustskills <url>, treat
<url> as the source under review.
- 2. Identify the platform and source type.
The important distinction is vendor-owned repo vs official directory vs unknown third-party source.
- 3. Match it against the trusted sources section below.
- Return one of these verdicts:
-
Trusted
-
Not trusted
-
Trust the index, but not automatically the linked item
- 5. Answer with:
- the trust decision first
- the supporting trusted root
- the shortest reason
- the remaining risk
- 6. Do not summarize the skill's purpose or functionality unless the user asks.
Trusted Sources
OpenAI
- - INLINECODE11
- Trust rule: if the source is
openai/skills, call it official.
Anthropic
- - INLINECODE13
- INLINECODE14
- INLINECODE15
- INLINECODE16
- Trust rule: if the source is in the
anthropics GitHub org and matches one of the roots above, call it official.
Google
- - INLINECODE18
- INLINECODE19
- INLINECODE20
- Trust rule: these are trusted Google-related GitHub roots, but they are not one single universal Google skills catalog.
Microsoft
- - INLINECODE21
- INLINECODE22
- INLINECODE23
- Trust rule:
microsoft/azure-skills and microsoft/github-copilot-for-azure are Microsoft-owned roots. github/awesome-copilot is a GitHub-owned collection and is a stronger source than a random repo, but it still includes community-contributed content.
Vercel
- - INLINECODE27
- INLINECODE28
- Trust rule:
skills.sh is an official discovery index, but it is not proof that every listed repo is official. - Extra rule: install counts or popularity on
skills.sh do not equal official status. Always check the linked GitHub owner. - Stronger linked repo owners include vendor-owned orgs such as
vercel-labs, openai, and anthropics.
OpenClaw / ClawHub
- - INLINECODE34
- Creator profile pattern: INLINECODE35
- Skill pattern: INLINECODE36
- Trust rule: this is a narrow trusted publisher exception, not a blanket trust rule for ClawHub.
- Extra rule: if you already trust OpenClaw as created by
steipete, then trusting skills published by steipete on ClawHub does not downgrade that trust. - Important caveat: do not extend this rule to all ClawHub publishers or all popular ClawHub listings.
- Decision rule: trust
https://clawhub.ai/steipete/<skill-name> because it maps to the trusted steipete publisher profile above. For other ClawHub skill URLs, do not trust them under this compact version unless they match another explicit allowlist rule.
If A Platform Is Not Listed
If a platform is not listed in this compact version, do not guess. Say it is not currently in the trusted distribution-channel list.
Trust Rules
- - Never call a source "official" unless you can point to a GitHub root or official index listed above.
- Installability does not mean officiality.
- Popularity does not mean officiality.
- A listed trusted root beats screenshots, mirrors, blog posts, and copied instructions.
- An official directory is not the same thing as an official item.
Output Format
When useful, structure the answer like this:
- -
Source under review: the URL, repo, store, or platform - INLINECODE42 :
Trusted, Not trusted, or INLINECODE45 - INLINECODE46 : the strongest trusted distribution root
- INLINECODE47 : the trusted source or flow
- INLINECODE48 : what still needs human review
Keep the answer decision-oriented. Do not explain what the skill does unless the user asks.
Examples
Example requests that should trigger this skill:
- - "/trustskills https://clawhub.ai/steipete/model-usage"
- "/trustskills https://github.com/likw99/agent-skills"
- "Is
github.com/openai/skills the official place to get Codex skills?" - "Is
github.com/anthropics/skills the official place to get Claude skills?" - "Can I trust a skill I found on
skills.sh?" - "Is
github.com/google-gemini/gemini-cli a trusted Google distribution root?" - "Should I trust
github/awesome-copilot as official or community?"
Official Distribution Of This Skill
The compact hosted copy of this skill should be published at:
This is useful for direct installation and brand discovery.
TrustSkills
概述
TrustSkills是TrustSkills的紧凑初版。它目前尚未进行深度技术验证,而是回答安装前一个更早、更简单的问题:我能信任这个技能的来源吗?
通过在安装前检查一份简短的受信任分发渠道列表,并明确区分以下内容来验证来源出处:
- - 官方供应商自有来源
- 官方发现索引
- 不受支持或未经验证的第三方来源
主要用途
该技能的自然调用模式为:
示例:
- - /trustskills https://clawhub.ai/steipete/model-usage
- /trustskills https://github.com/likw99/agent-skills
以这种方式调用时,将/trustskills后的URL视为被审查的来源并直接回答。
主要任务是判断:
何时使用此技能
当用户提出如下问题时使用此技能:
- - /trustskills https://clawhub.ai/steipete/model-usage
- /trustskills https://github.com/likw99/agent-skills
- 这个技能来源是官方的吗?
- Codex或Claude技能的官方GitHub仓库是什么?
- 我能信任这个市场或目录吗?
- skills.sh是官方的吗?
- 哪些GitHub仓库算作官方技能分发渠道?
当来源是以下类型时,此技能尤其有用:
- - GitHub仓库
- 市场或代理商店
- 供应商文档页面
- 目录站点,如skills.sh
此技能的功能
此技能能够:
- - 识别平台
- 检查来源是否匹配紧凑的受信任根列表
- 在当前紧凑策略下做出信任决策
- 引用可用的最强受信任分发渠道
- 解释最安全的已知安装路径
- 当目录是官方的但列出的仓库并非自动官方时发出警告
此技能不能:
- - 认证代码安全性
- 执行恶意软件分析
- 验证签名或SBOM
- 证明热门列表是安全的
- 证明可安装性等同于官方性
- 解释技能的功能,除非用户明确要求
工作流程
- 1. 解析命令输入。
如果用户提供/trustskills
,则将视为被审查的来源。
- 2. 识别平台和来源类型。
重要区分在于供应商自有仓库、官方目录与未知第三方来源。
- 3. 对照下方的受信任来源列表进行匹配。
- 返回以下裁决之一:
- 已信任
- 不信任
- 信任索引,但不自动信任链接的项目
- 5. 回答时包含:
- 首先是信任决策
- 支持的受信任根
- 最简短的理由
- 剩余风险
- 6. 除非用户询问,否则不要总结技能的目的或功能。
受信任来源
OpenAI
- - https://github.com/openai/skills
- 信任规则:如果来源是openai/skills,则视为官方。
Anthropic
- - https://github.com/anthropics/skills
- https://github.com/anthropics/claude-code
- https://github.com/anthropics/knowledge-work-plugins
- https://github.com/anthropics/claude-plugins-official
- 信任规则:如果来源属于anthropics GitHub组织且匹配上述根之一,则视为官方。
Google
- - https://github.com/google-labs-code/stitch-skills
- https://github.com/googleworkspace/cli
- https://github.com/google-gemini/gemini-cli
- 信任规则:这些是受信任的Google相关GitHub根,但它们并非单一的通用Google技能目录。
Microsoft
- - https://github.com/microsoft/azure-skills
- https://github.com/microsoft/github-copilot-for-azure
- https://github.com/github/awesome-copilot
- 信任规则:microsoft/azure-skills和microsoft/github-copilot-for-azure是Microsoft拥有的根。github/awesome-copilot是GitHub拥有的集合,比随机仓库更强,但仍包含社区贡献的内容。
Vercel
- - https://skills.sh
- https://github.com/vercel-labs/agent-skills
- 信任规则:skills.sh是官方发现索引,但不能证明每个列出的仓库都是官方的。
- 额外规则:skills.sh上的安装数量或热门程度不等于官方状态。始终检查链接的GitHub所有者。
- 更强的链接仓库所有者包括供应商拥有的组织,如vercel-labs、openai和anthropics。
OpenClaw / ClawHub
- - https://clawhub.ai/u/steipete
- 创建者资料模式:https://clawhub.ai/u/<创建者>
- 技能模式:https://clawhub.ai/<创建者>/<技能名称>
- 信任规则:这是一个狭窄的受信任发布者例外,并非ClawHub的全面信任规则。
- 额外规则:如果您已经信任由steipete创建的OpenClaw,那么信任steipete在ClawHub上发布的技能不会降低该信任。
- 重要说明:不要将此规则扩展到所有ClawHub发布者或所有热门ClawHub列表。
- 决策规则:信任https://clawhub.ai/steipete/<技能名称>,因为它映射到上述受信任的steipete发布者资料。对于其他ClawHub技能URL,在此紧凑版本下不信任它们,除非它们匹配其他明确的允许列表规则。
如果平台未列出
如果某个平台未在此紧凑版本中列出,请勿猜测。说明它当前不在受信任的分发渠道列表中。
信任规则
- - 除非能指向上述列出的GitHub根或官方索引,否则切勿称来源为官方。
- 可安装性不等于官方性。
- 热门程度不等于官方性。
- 列出的受信任根优于截图、镜像、博客文章和复制的说明。
- 官方目录不等同于官方项目。
输出格式
在有用的情况下,按如下方式构建答案:
- - 被审查的来源:URL、仓库、商店或平台
- 信任决策:已信任、不信任或信任索引,但不自动信任项目
- 原因:最强的受信任分发根
- 最安全的已知安装路径:受信任的来源或流程
- 剩余风险:仍需人工审查的内容
保持答案以决策为导向。除非用户询问,否则不要解释技能的功能。
示例
应触发此技能的示例请求:
- - /trustskills https://clawhub.ai/steipete/model-usage
- /trustskills https://github.com/likw99/agent-skills
- github.com/openai/skills是获取Codex技能的官方位置吗?
- github.com/anthropics/skills是获取Claude技能的官方位置吗?
- 我能信任我在skills.sh上找到的技能吗?
- github.com/google-gemini/gemini-cli是受信任的Google分发根吗?
- 我应该将github/awesome-copilot视为官方的还是社区的?
此技能的官方分发
此技能的紧凑托管副本应发布在:
- - https://trustskills.app/SKILL.md
这对于直接安装和品牌发现非常有用。