Evaluasi sebelum pemasangan

api-graphql 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
63
Kepercayaan
72
Audit
44
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 api-graphql before installing it in an agent workflow
  • other
  • Database and SQL workflows; Claude Code teams; builders willing to evaluate younger projects

Jalur pemasangan

92

Lulus

Install handoff is available.

  • npx skills add NoorQureshi/SploitAgent --skill api-graphql

Keamanan perintah pemasangan

92

Lulus

Jalur pemasangan paket atau runtime standar

  • npx skills add NoorQureshi/SploitAgent --skill api-graphql

Skor kepercayaan

63

Peringatan

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

  • Tinjauan manual
  • 20 star GitHub
  • MIT

Skor audit

72

Gagal

Berisiko

  • Permission surface may require sandboxing

Gerbang keamanan Agent

44

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

MIT

  • MIT

Cakupan izin

48

Gagal

secrets or environment access, network or browser access

  • Network access: medium
  • Secrets or environment access: high
  • 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

  • Tim yang membutuhkan SLA dengan dukungan vendor
  • production agents without a repository review
  • Low GitHub adoption signal
  • SKILL.md does not include an explicit authorization and scope statement; it assumes pentest/bugbounty context but should clearly state that testing is only permitted on systems the user owns or is explicitly authorized to assess.
  • Audit risk risky exceeds max_risk=medium
  • Petunjuk izin berisiko tinggi: Secrets or environment access

Pemeriksaan pendukung

Sinyal kepercayaan di balik keputusan

Kelengkapan README/SKILL.md

Peringatan

76

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

Pemeliharaan terbaru

Lulus

100

10 hari sejak push

Alternatif tersedia

Lulus

82

Alternative skills are available for comparison.