Evaluasi sebelum pemasangan

Quanttrader 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
63
Laporan evaluasi
73
Kepercayaan
65
Audit
49
Keamanan Agent

do not auto install

Audit score: Risky

Gerbang wajib

Pemeriksaan yang harus dilalui Agent sebelum memasang

Buka JSON

Kecocokan tugas

84

Lulus

Task wording matches this skill metadata.

  • Evaluate Quanttrader before installing it in an agent workflow
  • finance
  • Finance and quant workflows; Claude Code teams; teams that value GitHub adoption signals

Jalur pemasangan

92

Lulus

Install handoff is available.

  • npx skills add letianzj/quanttrader

Keamanan perintah pemasangan

92

Lulus

Jalur pemasangan paket atau runtime standar

  • npx skills add letianzj/quanttrader

Skor kepercayaan

73

Peringatan

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

  • Shortlist kuat
  • 738 star GitHub
  • Apache-2.0

Skor audit

65

Gagal

Berisiko

  • Repository appears stale

Gerbang keamanan Agent

49

Gagal

This skill should not be selected by an agent without explicit human security review.

  • Do not auto-install. Inspect the source, dependencies, and permission surface first.
  • Audit risk exceeds the requested agent policy

Kejelasan lisensi

86

Lulus

Apache-2.0

  • Apache-2.0

Cakupan izin

86

Lulus

Akses sistem file atau dokumen

  • 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
  • Audit risk risky exceeds max_risk=medium
  • Repository appears stale
  • 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

22

2 tahun sejak push

Alternatif tersedia

Lulus

82

Alternative skills are available for comparison.