Vercel
Repository: openclaw/skills
Author: byungkyu · Source status: Clear source
Vercel API integration with managed OAuth.
Score basis:Clear source · High risk signals · Cursor
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
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
microsoft-code-reference
Execution risk:High
Threat tags:data exfiltration, human approval gap
Control gaps:missing license, broad permissions, network without allowlist
Binance Onchain Pay
Execution risk:High
Threat tags:unexpected code execution, identity privilege abuse, data exfiltration
Control gaps:missing license, broad permissions, shell without guardrails
skill-seekers
Execution risk:High
Threat tags:unexpected code execution, identity privilege abuse, data exfiltration
Control gaps:missing license, broad permissions, shell without guardrails
| Dimension | microsoft-code-reference | Binance Onchain Pay | skill-seekers |
|---|---|---|---|
| SAS-v2.1 pre-install audit | |||
Audit grade | C · Review first | C · Review first | D · Limited evidence |
Execution risk | High | High | High |
Threat tags | data exfiltration, human approval gap | unexpected code execution, identity privilege abuse, data exfiltration | unexpected code execution, identity privilege abuse, data exfiltration |
Control gaps | missing license, broad permissions, network without allowlist | missing license, broad permissions, shell without guardrails | missing license, broad permissions, shell without guardrails |
Permission summary | Permission review, Network, Command | Permission review, Network, Secrets, Command | Permission review, Network, Secrets, Command |
Evidence confidence | 63% | 67% | 71% |
| Source & provenance | |||
Provenance | github/awesome-copilot/tree/main/skills/microsoft-code-reference | openclaw/skills | openclaw/skills |
Category | Dev & Engineering | Dev & Engineering | Dev & Engineering |
Freshness | |||
| Risk & trust | |||
Trust score | 80 | 85 | 88 |
Audit signals | network access | needs credentials, network access, runs shell, writes files | needs credentials, network access, runs shell, writes files |
| Install & compatibility | |||
Supported tools | Claude, Codex, Cursor, Universal | Claude | Claude, Cursor, Windsurf |
Install method | registry-install | script-backed | script-backed |
Install friction | |||
| Community | |||
Stars | 20.6K | 0 | 0 |
Repository: openclaw/skills
Author: leaofelipe · Source status: Clear source
Runs Organizze personal finance API operations via Node.js CLI scripts: accounts, categories, transactions (filters, tag grouping), credit cards (invoices, payments), and transfers.
Score basis:Clear source · High risk signals · Universal
Repository: openclaw/skills
Author: kongbai233 · Source status: Clear source
This skill should be used when the user needs to analyze Git repositories, compare developer commit patterns, work habits, development efficiency, code style, code quality, and slacking behaviors.
Score basis:Clear source · High risk signals · Universal
Repository: openclaw/skills
Author: diagnostikon · Source status: Clear source
Trades CPI range bin markets on Kalshi using the constraint that mutually exclusive bins must sum to ~100%.
Score basis:Clear source · High risk signals · Universal
2026-02-04 |
2026-04-01 |
2026-04-04 |
Permission hints |
|---|
registry access, remote metadata pull, runtime dependencies may be required |
verify source provenance before install |
verify source provenance before install |
50 |
65 |
65 |