OpenAgentSkill
GitHub200+

Pre-install eval

edit-scene 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
67
Eval report
68
Trust
72
Audit
56
Agent safety

do not auto install

Install path: No install command or repository handoff is available.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate edit-scene before installing it in an agent workflow
  • automation
  • Workflow automation workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

20

fail

No install command or repository handoff is available.

Install command safety

92

pass

standard package or runtime install path

Trust score

68

warn

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

  • Manual review
  • 19 GitHub stars
  • Unlicense

Audit score

72

warn

Needs review

  • SKILL.md does not state the minimal environment prerequisites up front; required tools such as `unity_play_control`, `get_unity_compilation_result`, and `run_method_in_unity` are mentioned as if already available, and setup details are only in a referenced troubleshooting resource.

Agent safety gate

56

warn

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

  • The tracked source changed or could not be synchronized. Review the current source before installing.

License clarity

86

pass

Unlicense

  • Unlicense

Permission surface

86

pass

filesystem or document access

  • 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
  • SKILL.md does not state the minimal environment prerequisites up front; required tools such as `unity_play_control`, `get_unity_compilation_result`, and `run_method_in_unity` are mentioned as if already available, and setup details are only in a referenced troubleshooting resource.
  • The tracked source changed or could not be synchronized. Review the current source before installing.
  • The submitted SKILL.md excerpt appears to end prematurely at the Play Mode rule in the file listing; if the actual file is truncated, the later Gotchas and resource sections are missing and should be restored.

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

88

1mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.