Star200+

Pre-install eval

dstack-prototyping 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
70
Eval report
72
Trust
80
Audit
40
Agent safety

do not auto install

Agent safety gate: This skill should not be selected by an agent without explicit human security review.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate dstack-prototyping before installing it in an agent workflow
  • research
  • Local desktop workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add dstackai/dstack --skill dstack-prototyping

Install command safety

92

pass

standard package or runtime install path

  • npx skills add dstackai/dstack --skill dstack-prototyping

Trust score

72

warn

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

  • Strong shortlist
  • 2.2K GitHub stars
  • MPL-2.0

Audit score

80

warn

Needs review

  • Dependency or permission surface needs review

Agent safety gate

40

fail

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.
  • Metadata combines secrets access with shell or command execution

License clarity

86

pass

MPL-2.0

  • MPL-2.0

Permission surface

22

fail

secrets or environment access, shell or command execution

  • 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
  • The skill does not explicitly advise on checking for malicious or untrusted images/modules when prototyping, though it points to official sources which mitigates risk.
  • High-risk permission hints: Shell or command execution, Secrets or environment access
  • Dependency or permission surface needs review
  • Permission surface may require sandboxing

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

100

1d since push

Alternatives available

pass

82

Alternative skills are available for comparison.