Compare skills
Pick 2–4 skills and compare what really matters: fit, risk, install effort, and community signal.
This comparison came from collection: Notion workspace
Compare database access, page writes, and provenance transparency.
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
Notion
Execution risk：Low
Threat tags：identity privilege abuse, data exfiltration, supply chain
Control gaps：missing repo, missing license, unclear tool boundary
database
Execution risk：High
Threat tags：unexpected code execution, data exfiltration, human approval gap
Control gaps：missing license, broad permissions, shell without guardrails
Notion
Execution risk：High
Threat tags：unexpected code execution, identity privilege abuse, data exfiltration
Control gaps：missing repo, missing license, broad permissions
| Dimension | Notion | database | Notion |
|---|---|---|---|
| SAS-v2.1 pre-install audit | |||
Audit grade | D · Limited evidence | C · Review first | D · Limited evidence |
Execution risk | Low | High | High |
Threat tags | identity privilege abuse, data exfiltration, supply chain | unexpected code execution, data exfiltration, human approval gap | unexpected code execution, identity privilege abuse, data exfiltration |
Control gaps | missing repo, missing license, unclear tool boundary | missing license, broad permissions, shell without guardrails | missing repo, missing license, broad permissions |
Permission summary | Permission review, Network, Secrets | Permission review, Network, Command | Permission review, Network, Secrets, Command |
Evidence confidence | 63% | 65% | 67% |
| Source & provenance | |||
Provenance | Source needs review | haymon-ai/database | Source needs review |
Freshness | 2026-01-27 | 2026-04-08 | 2026-01-05 |
| Risk & trust | |||
Trust score | 65 | 76 | 70 |
Audit signals | network access | No explicit signals | needs credentials, network access, runs shell, writes files |
| Install & compatibility | |||
Supported tools | Codex, OpenClaw, Claude, Cursor, Universal | Universal | Codex, OpenClaw, Claude, Cursor, Universal |
Install method | instruction-only | script-backed | instruction-only |
Install friction | |||
| Community | |||
Stars | 12 | 6 | 225 |
Repository: Database
Author: WhyDRS · Source status: Clear source
The WhyDRS database is a collection of data on transfer agents for public companies.
Score basis：Clear source · Risk needs review · Universal
Permission hints |
|---|
review skill metadata before install, check required credentials in skill docs |
repository clone, local runtime dependencies |
review skill metadata before install, check required credentials in skill docs |
85 |
40 |
100 |
