Star200+

Evaluasi sebelum pemasangan

Objectbox Go 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
71
Laporan evaluasi
80
Kepercayaan
74
Audit
54
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 Objectbox Go before installing it in an agent workflow
  • robotics-iot
  • Database and SQL workflows; Claude Code teams; teams that value GitHub adoption signals

Jalur pemasangan

92

Lulus

Install handoff is available.

  • npx skills add objectbox/objectbox-go

Keamanan perintah pemasangan

92

Lulus

Jalur pemasangan paket atau runtime standar

  • npx skills add objectbox/objectbox-go

Skor kepercayaan

80

Peringatan

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

  • Shortlist kuat
  • 1.3K star GitHub
  • Apache-2.0

Skor audit

74

Peringatan

Perlu ditinjau

  • Repository appears stale

Gerbang keamanan Agent

54

Peringatan

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

  • Test manually in an isolated workspace and compare against safer alternatives.
  • Repository appears stale

Kejelasan lisensi

86

Lulus

Apache-2.0

  • Apache-2.0

Cakupan izin

74

Peringatan

filesystem or document access, database access

  • Network access: medium
  • Filesystem access: medium
  • Database 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
  • Repository appears stale
  • Financial research output is not financial advice; require human review before any live investment decision
  • Financial research output is not financial advice; require human review before any live investment decision.

Pemeriksaan pendukung

Sinyal kepercayaan di balik keputusan

Kelengkapan README/SKILL.md

Peringatan

74

Metadata publik memerlukan konteks README/SKILL.md yang lebih kuat

Pemeliharaan terbaru

Gagal

38

1 tahun sejak push

Alternatif tersedia

Lulus

82

Alternative skills are available for comparison.