Evaluasi sebelum pemasangan

Backend Ico Dashboard 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.

GagalRisiko tinggiBlokir Kebijakan
56
Laporan evaluasi
65
Kepercayaan
59
Audit
31
Keamanan Agent

do not auto install

One or more required eval gates failed.

Gerbang wajib

Pemeriksaan yang harus dilalui Agent sebelum memasang

Buka JSON

Kecocokan tugas

94

Lulus

Task wording matches this skill metadata.

  • Evaluate Backend Ico Dashboard before installing it in an agent workflow
  • web3-analytics
  • Coding agents workflows; Claude Code teams; builders willing to evaluate younger projects

Jalur pemasangan

92

Lulus

Install handoff is available.

  • npx skills add secret-tech/backend-ico-dashboard

Keamanan perintah pemasangan

68

Peringatan

credential-bearing install command, standard package or runtime install path

  • npx skills add secret-tech/backend-ico-dashboard

Skor kepercayaan

65

Peringatan

Potentially useful, but at least one trust signal needs human inspection.

  • Tinjauan manual
  • 126 star GitHub
  • MIT

Skor audit

59

Peringatan

Perlu ditinjau

  • Permission surface may require sandboxing

Gerbang keamanan Agent

31

Peringatan

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

  • Test manually in an isolated workspace and compare against safer alternatives.
  • Petunjuk izin berisiko tinggi: Secrets or environment access

Kejelasan lisensi

86

Lulus

MIT

  • MIT

Cakupan izin

60

Peringatan

secrets or environment access, filesystem or document access

  • Network access: medium
  • Filesystem access: medium
  • Secrets or environment access: high

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
  • Petunjuk izin berisiko tinggi: Secrets or environment access
  • Permission surface may require sandboxing
  • Repository appears stale

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

22

5 tahun sejak push

Alternatif tersedia

Lulus

82

Alternative skills are available for comparison.