Pre-install eval

game-art-direction 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
76
Eval report
81
Trust
83
Audit
71
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

70

warn

Task fit is weak; compare alternatives before selecting.

  • Evaluate game-art-direction before installing it in an agent workflow
  • video-creation
  • Multimodal media workflows; Claude Code teams; teams that value GitHub adoption signals

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

81

warn

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

  • Strong shortlist
  • 859 GitHub stars
  • MIT

Audit score

83

pass

Safe to try

  • AI review approval is missing

Agent safety gate

71

warn

Good audit and safety signals with no high-risk permission hints in public metadata.

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

License clarity

86

pass

MIT

  • MIT

Permission surface

100

pass

no high-risk permission surface in public metadata

  • Network 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
  • AI review approval is missing
  • The tracked source changed or could not be synchronized. Review the current source before installing.
  • Quality score needs review

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

76

Public metadata needs stronger README/SKILL.md context

Recent maintenance

pass

100

21d since push

Alternatives available

pass

82

Alternative skills are available for comparison.