Star200+

Pre-install eval

Jfrog Skills Eval report.

A machine-readable install decision for agents: task fit, Trust Score, Audit Score, install safety, permission surface, and a concrete validation plan before this skill touches a workspace.

FailedHigh riskBLOCK Policy
69
Eval report
72
Trust
78
Audit
46
Agent safety

do not auto install

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

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate Jfrog Skills before installing it in an agent workflow
  • security
  • GitHub automation workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add jfrog/jfrog-skills

Install command safety

92

pass

standard package or runtime install path

  • npx skills add jfrog/jfrog-skills

Trust score

72

warn

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

  • Strong shortlist
  • 18 GitHub stars
  • Apache-2.0

Audit score

78

warn

Needs review

  • Dependency or permission surface needs review

Agent safety gate

46

warn

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

  • Test manually in an isolated workspace and compare against safer alternatives.
  • High-risk permission hints: Shell or command execution

License clarity

86

pass

Apache-2.0

  • Apache-2.0

Permission surface

48

fail

shell or command execution, filesystem or document access

  • Shell or command execution: high
  • Network access: medium
  • Filesystem access: medium

Validation plan

What the agent should do next

  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.

Do not use when

Conditions that require another skill

  • teams that need a vendor-supported SLA
  • production agents without a repository review
  • Low GitHub adoption signal
  • High-risk permission hints: Shell or command execution
  • Dependency or permission surface needs review
  • Permission surface may require sandboxing

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

100

Metadata includes enough usage and workflow context

Recent maintenance

pass

100

12d since push

Alternatives available

pass

82

Alternative skills are available for comparison.