Compare skills
Pick 2–4 skills and compare what really matters: fit, risk, install effort, and community signal.
Comparison matrix
Highlights show current best; tooltip explains diff/best rules.
SAS-v2.1 diff rules / risk tag notes
Start with the matrix. Open this section when you need to understand audit grades, top threats, control gaps, and best-value highlights.
Suggested baseline
Repository: openclaw/skills
Author: lookupmark · Source status: Clear source
Find and send local files to a chat channel (Telegram, Discord, WhatsApp, Signal, Slack).
Score basis：Clear source · High risk signals · OpenClaw
Search to add skills, or paste 2–4 comma-separated slugs.
How differences are detected
A row is marked different when selected skills have distinct values. Only-differences mode hides rows that are identical.
How best values are highlighted
Audit score, evidence confidence, trust score, and community signal prefer higher values; execution risk and install friction prefer lower values.
How to read risk tags
Risk tags come from SAS-v2.1 public-evidence signals and point to command, network, secret, context, or supply-chain items to review before install.
Selected audit signals
LookupMark Tailscale Manager
Execution risk：High
Threat tags：unexpected code execution, identity privilege abuse, data exfiltration
Control gaps：missing license, broad permissions, shell without guardrails
Memory Stack Core
Execution risk：High
Threat tags：unexpected code execution, identity privilege abuse, data exfiltration
Control gaps：missing license, broad permissions, shell without guardrails
赛博算命 Skill
Execution risk：Low
Threat tags：data exfiltration, supply chain, human approval gap
Control gaps：missing license, missing install docs, broad permissions
| Dimension | LookupMark Tailscale Manager | Memory Stack Core | 赛博算命 Skill |
|---|---|---|---|
| SAS-v2.1 pre-install audit | |||
Audit grade | C · Review first | C · Review first | C · Review first |
Execution risk | High | High | Low |
Threat tags | unexpected code execution, identity privilege abuse, data exfiltration | unexpected code execution, identity privilege abuse, data exfiltration | data exfiltration, supply chain, human approval gap |
Control gaps | missing license, broad permissions, shell without guardrails | missing license, broad permissions, shell without guardrails | missing license, missing install docs, broad permissions |
Permission summary | Permission review, Network, Secrets, Command | Permission review, Network, Secrets, Command | Network |
Evidence confidence | 67% | 71% | 60% |
| Source & provenance | |||
Provenance | openclaw/skills | openclaw/skills | jinchenma94/bazi-skill |
Category | Vertical & Solutions | Knowledge & RAG | Vertical & Solutions |
Freshness | |||
| Risk & trust | |||
Trust score | 85 | 85 | 92 |
Audit signals | needs credentials, network access, runs shell, writes files | needs credentials, writes files | No explicit signals |
| Install & compatibility | |||
Supported tools | Universal | Claude, OpenClaw | Claude Code, Claude |
Install method | script-backed | script-backed | source-link |
Install friction | |||
| Community | |||
Stars | 0 | 0 | 986 |
Repository: openclaw/skills
Author: fishhao123 · Source status: Clear source
Curate ultra-luxury travel experiences for discerning travelers seeking the finest accommodations, first-class flights, private jets, luxury cruises, and exclusive experiences.
Score basis：Clear source · High risk signals · Universal
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: grantmacnamara · Source status: Clear source
Run a Mopidy music system in party mode for shared or group chats, where everyone can contribute songs but only the host can control playback.
Score basis：Clear source · High risk signals · Universal
2026-04-05 |
2026-04-02 |
2026-04-18 |
Permission hints |
|---|
verify source provenance before install |
verify source provenance before install |
No explicit hints |
65 |
55 |
62 |
