Develop Ai Functions Example
Repository: ai
Author: vercel · Source status: Clear source
Score 80Clear source
Manual reviewDevelop examples for AI SDK functions.
Score basis：Clear source · Low risk signals · Claude
Author verified
Claude
21.6K
Compare skills
Pick 2–4 skills and compare what really matters: fit, risk, install effort, and community signal.
This comparison came from collection: Clear provenance
Useful for excluding unclear provenance early.
Selected skills (2/4)
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
create-an-asset
Execution risk：High
Threat tags：data exfiltration, memory context poisoning, human approval gap
Control gaps：missing license, broad permissions, network without allowlist
example-skill
Execution risk：High
Threat tags：data exfiltration, human approval gap
Control gaps：missing license, network without allowlist, no human approval
| Dimension | create-an-asset | example-skill |
|---|---|---|
| SAS-v2.1 pre-install audit | ||
Audit grade | C · Review first | C · Review first |
Execution risk | High | High |
Threat tags | data exfiltration, memory context poisoning, human approval gap | data exfiltration, human approval gap |
Control gaps | missing license, broad permissions, network without allowlist | missing license, network without allowlist, no human approval |
Permission summary | Network, Command | Network, Command |
Evidence confidence | 67% | 63% |
| Source & provenance | ||
Provenance | anthropics/knowledge-work-plugins/tree/main/sales/skills/create-an-asset | anthropics/claude-plugins-official/tree/main/plugins/example-plugin/skills/example-skill |
Category | Knowledge & RAG | Dev & Engineering |
Freshness | 2026-02-04 | |
| Risk & trust | ||
Trust score | 80 | 80 |
Audit signals | No explicit signals | |
| Install & compatibility | ||
Supported tools | Claude, Codex, Cursor, Universal | Claude, Codex, Cursor, Universal |
Install method | registry-install | registry-install |
Install friction | ||
| Community | ||
Stars | 6.6K | 7K |
Repository: openai/skills
Author: openai · Source status: Clear source
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval.
Score basis：Clear source · Low risk signals · Claude
Repository: openai/skills
Author: openai · Source status: Clear source
Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization.
Score basis：Clear source · Risk needs review · Claude
Permission hints | registry access, remote metadata pull, runtime dependencies may be required | registry access, remote metadata pull, runtime dependencies may be required |
|---|
50 |