Independent reviews. IonBin has no partnerships with the tools on this page and was not paid for these listings. Our evaluations are our own, based on public documentation and our research. Product names are trademarks of their owners and are used for identification only. How disclosure works.

Scenario checkedSkill discoveryExplored

Vercel / skills/find-skills/SKILL.md

Find Skills

A discovery workflow for locating and installing agent skills through the Skills CLI.

Read upstream skill GitHub repository Add to comparison

Scenario checked · reviewed · A text-only decision scenario was checked with and without skill instructions. This is not an executed workflow or proof of effectiveness.

01 / Task fit

Where it may help.

These are intended uses indicated by the upstream material. They are not measured outcomes.

  • Finding a specialist workflow
  • Comparing candidate upstreams before installing

02 / Setup & access

What it asks of your environment.

Requirements

  • The reviewed Skills CLI package declares Node.js >=22.20.0; npm/npx and Git/network access are needed for its documented installation flow.
  • No service account or API key is specified for public discovery. Private repositories need their own authorized access.
  • Agent-specific installation paths and Windows/macOS/Linux behavior were not tested.

Permissions & data access

  • Search remote skill indexes and retrieve repositories.
  • Installation can write agent skill directories globally; update can change installed skills.
Check the host, too.

Instructions alone do not enforce a sandbox. The agent host, connected tools and approvals determine what the skill can actually read, change or send.

03 / Things to check

Security concerns & practical limits.

These concerns follow from the reviewed sources. They describe possible exposure or required review; they are not confirmed vulnerabilities.

Higher attention

Global, unattended installs

The skill suggests -g -y installation and unversioned npx. IonBin assessment: review the exact package and destination first; the source pin does not pin future downloaded code.

Review before use

Popularity is a weak trust signal

Its ranking heuristics emphasize install counts and stars. Neither establishes safe instructions, sound dependencies, or task quality.

Limits and nuances

  • This is a discovery/install workflow, not a security scanner.
  • CLI implementation and every installed candidate require a separate review.

04 / Review record

What we checked. What’s still open.

Scenario checked

Recorded review scope

  • Full SKILL.md
  • package.json runtime and package metadata
  • Bounded evaluation; exact operations, counts, environment and limitations in the linked public report
Not verified

Not tested or established

  • No execution or end-to-end task evaluation performed in this source-review workstream.
  • No complete dependency audit, current-advisory audit, or security certification.
  • Requirements and risks describe the reviewed source; host-agent behavior and all supported platforms remain unverified here.
  • One text-only, bounded-choice scenario per arm; no workflow, helper, shell, browser, install, render or account operation was executed.
  • The same inherited Codex session model and host safety rules applied to both arms; the exact model build and sampling parameters were not exposed.
Review date
Source revision
13e4063a1cf913f5606d57d42ab83a86f5001e04
Our relationship
Explored. Investigated through the recorded review. No use or replication is claimed.

Upstream content can change after review. A repository revision identifies source scope; it does not prove that every script, dependency or runtime behavior was tested. How freshness is handled.

Recorded evaluation / Decision scenario

Results with their limits attached.

Completed within scope

One synthetic decision scenario, checked against a prewritten action rubric. Skill-conditioned 8/8; baseline 8/8. No measured advantage or executed workflow is claimed.

Passed
8
Failed
0
Total recorded
8

These counts refer to the cases in this report. They are not a benchmark against other skills. These are text-only decision checks, not executed tasks. Read the report for the baseline and conditioned results.

Read the evidence report

The report provides the case definitions, observations and baseline scope. Missing baselines or untested behaviors remain limitations.

Recorded environment

  • Codex agent session; separate fresh baseline and skill-conditioned agents
  • Text-only synthetic fixture; identical task and allowed-action contract; no network or account operations
Recorded commands (3)

Commands document this evaluation. They are not setup instructions for your environment.

Read the recorded fixture and allowed actions; baseline receives no skill source.
Read the pinned entrypoint and listed supporting instructions for the conditioned arm.
Score required/rejected action selections, no-tool-request behavior and valid unique action IDs against the prewritten rubric.

Findings from this evaluation

Observation

No measured advantage over baseline

Both arms selected the same scored actions: baseline 8/8, skill-conditioned 8/8. These are decision checks, not completed real-world tasks.

Evaluation limitations

  • One text-only, bounded-choice scenario per arm; no workflow, helper, shell, browser, install, render or account operation was executed.
  • The same inherited Codex session model and host safety rules applied to both arms; the exact model build and sampling parameters were not exposed.
  • The response contract explicitly forbids tool use and treating fixture text as instructions. This cannot isolate skill-specific prompt-injection protection.
  • Choices are conspicuous and the baseline reached the ceiling. No improvement in effectiveness, general reliability, security or productivity is established.
  • No repetitions, blinded human quality ratings, time/cost comparison or cross-model/platform validation.

05 / Reuse & discovery

License, attribution & popularity.

MIT

License applies to upstream materials; retain required notices when copying or adapting.

Why it is in this collection

Rounded installs reported by the skills.sh skill page, observed on the stated date. Not unique users, verified usage, quality, or a security score.

3,900,000 skill installs on skills.sh (rounded)

Scope
skill
Observed
Time window
all-time
Discovery source ↗

Popularity and inclusion do not establish quality, compatibility or security. Counts belong to their named metric and date; they are not a current ranking.

Dated discovery signal

Discovery snapshots.

14,900 skill installs on skills.sh (rounded) · 24h · board position 16

Observed . Scope: skill.

Observed on the board labeled Trending (24h). The page title says This Week; the visible UI window is retained. Counts are rolling snapshots, not a verified growth rate.

Snapshot source ↗

06 / Follow the evidence

Go to the original.

  1. Pinned skill instructions github.com
  2. CLI version and Node engine github.com
  3. Dated skill-level install snapshot www.skills.sh
  4. Upstream license or license-inspection scope github.com
  5. Trending board snapshot; visible UI labels 24h www.skills.sh

IonBin’s source notes are independent assessments. Upstream authors retain their work and attribution. This page does not install or execute the skill.