OMNI — All-In-One Master Skill
Repository: openclaw/skills
Author: eternal0404 · Source status: Clear source
The all-in-one master skill — unified interface for every capability domain.
Score basis:Clear source · High risk signals · Claude
Repository: openclaw/skills
Author: e2e5g · Source status: Clear source
智能AI成本优化系统,集成Token预算管理、边际收益检测、多维度成本统计。当用户要求优化AI调用成本、控制Token使用、监控预算消耗、生成成本报告、降低API费用时使用。
Score basis:Clear source · Risk needs review · Claude
Trust level
80 · Review first
Usable, but inspect source, install method, and risk hints before adoption.
Risk decision
High attention
needs credentials, writes files
Install readiness
instruction-only · source-link only
SkillTrust only shows install guidance and copy actions; it never executes installs.
Before you install
Review source, permissions, and execution risk first, then alternatives. Scores prioritize review; they do not replace manual judgment.
Review weakest dimensions and next actions before copying commands.
Evidence or risk signals are incomplete; compare alternatives first.
Audit grade
C · Review first
Execution risk
High
Evidence confidence
69%
SAS-v2.1 radar
SAS-v2.1
Audit grade
C · Review first
Execution risk
High
Top threats
unexpected code execution, identity privilege abuse
Control gaps
missing license, broad permissions
Evidence confidence
69%
Repository
openclaw/skills
Author
e2e5g
Community signal
0 stars · 0 forks
Last updated
2026-04-02
Primary source
openclaw/skills
Source status
Clear source
Install method
instruction-only
Command & code execution
34Focus: Whether it runs commands or scripts
Next action: Manually confirm command-running skills in an isolated directory.
High-risk action confirmation
38Focus: Whether destructive or external actions require confirmation
Next action: Avoid directly installing high-risk skills without confirmation controls.
Secrets, identity & credentials
42Focus: Whether it handles tokens, private keys, or agent identity
Next action: Do not provide long-lived tokens or private keys to source-pending skills.
Supported tools can change install steps; Universal entries need source review.
Explicitly supported
Candidate support (inferred)
Candidate tools are inferred signals, not official compatibility certifications.
No explicit install command yet. Review source and install docs before deciding.Copy is disabled because no explicit command is available yet.
needs credentials, writes files
Review source and permissions before copying install commands.
Evidence or risk signals are incomplete; compare alternatives first.
Focus: Who published it and whether it is traceable
Next action: Review repository, author, and README first; do not install directly when source is pending.
Focus: Whether install steps can be reviewed
Next action: Prefer candidates with install docs and repository evidence.
Focus: Whether tool descriptions may hide instructions
Next action: Read README, rules, and tool descriptions before install.
Focus: What it can access
Next action: Grant only task-required permissions and prefer Ask/manual confirmation.
Focus: Whether it runs commands or scripts
Next action: Manually confirm command-running skills in an isolated directory.
Focus: Whether file reads/writes can escape scope
Next action: Check working directory and file access scope before running.
Focus: Whether it may send data out
Next action: If unsure, restrict network access or allow only known domains.
Focus: Whether it handles tokens, private keys, or agent identity
Next action: Do not provide long-lived tokens or private keys to source-pending skills.
Focus: Whether external content can steer behavior
Next action: For browser/RAG/rules skills, review permissions and confirmation controls first.
Focus: Whether memory or retrieved context can be poisoned
Next action: Try RAG/memory skills in a low-privilege environment first.
Focus: Whether external tools and MCP access are clearly bounded
Next action: Confirm which external tools it will connect to before install, and start with the smallest possible set.
Focus: Whether destructive or external actions require confirmation
Next action: Avoid directly installing high-risk skills without confirmation controls.
Focus: How far impact can spread when something goes wrong
Next action: If unsure, test in an isolated project first.
Focus: Whether actions can be traced
Next action: Prefer candidates with logs or previews.
Focus: Whether it is maintained and reusable
Next action: Check license and maintenance before organizational use.
Usable, but inspect source, install method, and risk hints before adoption.
Phase 1 only shows installation-aware, source-backed signals. SkillTrust does not execute install scripts for users.
Risk factors
needs credentials, writes files
Permission hints
verify source provenance before install
Why related: Same task category, Also supports Claude...
Why related: Same task category, Also supports Claude, Keyword overlap
Repository: openclaw/skills
Author: dexploarer · Source status: Clear source
Crypto market rankings and leaderboards.
Score basis:Clear source · High risk signals · Universal
Why related: Same task category, Keyword overlap...
Why related: Same task category, Keyword overlap, Same repository ecosystem
Repository: openclaw/skills
Author: kongbai233 · Source status: Clear source
Data visualization tool producing SVG charts.
Score basis:Clear source · High risk signals · Universal
Why related: Same task category, Keyword overlap...
Why related: Same task category, Keyword overlap, Same repository ecosystem
Repository: openclaw/skills
Author: jpengcheng523-netizen · Source status: Clear source
Analyze resource usage patterns and predict future scaling needs using trend analysis and forecasting methods for capacity planning and auto-scaling decisions.
Score basis:Clear source · High risk signals · Universal
Why related: Same task category, Keyword overlap...
Why related: Same task category, Keyword overlap, Same repository ecosystem
Repository: openclaw/skills
Author: zaferliu · Source status: Clear source
信息调研报告自动化工作流。一键完成:多源搜索 → 深度挖掘 → 政府风格 DOCX 报告生成 → 邮件发送。
Score basis:Clear source · High risk signals · OpenClaw
Why related: Same task category, Keyword overlap...
Why related: Same task category, Keyword overlap, Same repository ecosystem