Evaluasi sebelum pemasangan

Piano Rs 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
60
Laporan evaluasi
70
Kepercayaan
65
Audit
37
Keamanan Agent

do not auto install

Permission surface: shell or command execution, filesystem or document access

Gerbang wajib

Pemeriksaan yang harus dilalui Agent sebelum memasang

Buka JSON

Kecocokan tugas

94

Lulus

Task wording matches this skill metadata.

  • Evaluate Piano Rs before installing it in an agent workflow
  • Otomasi produktivitas
  • RAG and knowledge workflows; Claude Code teams; builders willing to evaluate younger projects

Jalur pemasangan

92

Lulus

Install handoff is available.

  • npx skills add ritiek/piano-rs

Keamanan perintah pemasangan

92

Lulus

Jalur pemasangan paket atau runtime standar

  • npx skills add ritiek/piano-rs

Skor kepercayaan

70

Peringatan

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

  • Tinjauan manual
  • 234 star GitHub
  • MIT

Skor audit

65

Peringatan

Perlu ditinjau

  • Permission surface may require sandboxing

Gerbang keamanan Agent

37

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: eksekusi shell atau perintah

Kejelasan lisensi

86

Lulus

MIT

  • MIT

Cakupan izin

48

Gagal

shell or command execution, filesystem or document access

  • Shell or command execution: high
  • Network access: medium
  • Filesystem 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
  • Petunjuk izin berisiko tinggi: eksekusi shell atau perintah
  • Permission surface may require sandboxing
  • Repository appears stale

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

2 tahun sejak push

Alternatif tersedia

Lulus

82

Alternative skills are available for comparison.