Star200+

Evaluasi sebelum pemasangan

Rebrowser Patches Laporan evaluasi.

Keputusan pemasangan yang dapat dibaca mesin untuk Agent: kecocokan tugas, Trust Score, Audit Score, keamanan pemasangan, cakupan izin, dan rencana validasi konkret sebelum skill menyentuh workspace.

Perlu ditinjauRisiko sedangTinjau Kebijakan
70
Laporan evaluasi
79
Kepercayaan
72
Audit
56
Keamanan Agent

Tinjauan manual

Test manually in an isolated workspace and compare against safer alternatives.

Gerbang wajib

Pemeriksaan yang harus dilalui Agent sebelum memasang

Buka JSON

Kecocokan tugas

84

Lulus

Task wording matches this skill metadata.

  • Evaluate Rebrowser Patches before installing it in an agent workflow
  • browser-automation
  • Browser automation workflows; Claude Code teams; teams that value GitHub adoption signals

Jalur pemasangan

92

Lulus

Install handoff is available.

  • npx skills add rebrowser/rebrowser-patches

Keamanan perintah pemasangan

92

Lulus

Jalur pemasangan paket atau runtime standar

  • npx skills add rebrowser/rebrowser-patches

Skor kepercayaan

79

Peringatan

Good trust signals with a few areas worth checking before rollout.

  • Shortlist kuat
  • 1.4K star GitHub
  • Tidak diketahui

Skor audit

72

Peringatan

Perlu ditinjau

  • Lisensi tidak jelas

Gerbang keamanan Agent

56

Peringatan

Sparse or mixed signals. Useful for discovery, but not for autonomous installation.

  • Test manually in an isolated workspace and compare against safer alternatives.
  • Lisensi tidak jelas

Kejelasan lisensi

42

Peringatan

Tidak diketahui

  • Tidak diketahui

Cakupan izin

86

Lulus

network or browser access

  • Browser automation: medium
  • Network access: medium

Rencana validasi

Langkah Agent berikutnya

  1. 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
  2. 2Install in an isolated workspace or sandbox with no production secrets available.
  3. 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
  4. 4Compare the selected skill against at least one alternative when the eval status is review or failed.
  5. 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Jangan gunakan ketika

Kondisi yang membutuhkan skill lain

  • teams that require actively maintained dependencies
  • production agents without a repository review
  • Repository looks stale
  • Lisensi tidak jelas
  • Repository appears stale
  • Quality score needs review

Pemeriksaan pendukung

Sinyal kepercayaan di balik keputusan

Kelengkapan README/SKILL.md

Lulus

90

Metadata memuat konteks penggunaan dan alur kerja yang cukup

Pemeliharaan terbaru

Gagal

38

1 tahun sejak push

Alternatif tersedia

Lulus

82

Alternative skills are available for comparison.