Star0

Pre-install eval

Docker Ipsec Vpn Server 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.

Needs reviewMEDIUM RISKREVIEW POLICY
86
Eval
86
Trust
90
Audit
62
Safety

manual review

Require human approval before installing into a real workspace.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate Docker Ipsec Vpn Server before installing it in an agent workflow
  • legal-compliance
  • GitHub automation workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add hwdsl2/docker-ipsec-vpn-server

Install command safety

92

pass

standard package or runtime install path

  • npx skills add hwdsl2/docker-ipsec-vpn-server

Trust score

86

pass

Strong OpenAgentSkill Trust Score across adoption, recent maintenance, license clarity, documentation, dependency/runtime risk, install safety, permission surface, and install availability.

  • Production candidate
  • 7.1K GitHub stars
  • Unknown

Audit score

90

pass

Safe to try

  • License is unclear

Agent safety gate

62

warn

Usable candidate, but the agent should surface permission and audit notes before installation.

  • Require human approval before installing into a real workspace.
  • High-risk permission hints: Shell or command execution

License clarity

42

warn

Unknown

  • Unknown

Permission surface

62

warn

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
  • high-compliance environments without internal security review
  • No major risk signals from current metadata
  • High-risk permission hints: Shell or command execution
  • License is unclear
  • License clarity: Unknown

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

90

Metadata includes enough usage and workflow context

Recent maintenance

pass

100

6d since push

Alternatives available

pass

82

Alternative skills are available for comparison.