Pre-install eval
Emil Design Engineering 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.
do not auto install
Install path: No install command or repository handoff is available.
Required gates
Checks an agent must pass before install
Task fit
84
Task wording matches this skill metadata.
- Evaluate Emil Design Engineering before installing it in an agent workflow
- design-creative
- Design and creative workflows; Claude Code teams; teams that value GitHub adoption signals
Install path
20
No install command or repository handoff is available.
Install command safety
92
standard package or runtime install path
Trust score
91
Strong OpenAgentSkill Trust Score across adoption, recent maintenance, license clarity, documentation, dependency/runtime risk, install safety, permission surface, and install availability.
- Production candidate
- 13K GitHub stars
- MIT
Audit score
93
Safe to try
- No major audit warning from metadata.
Agent safety gate
61
Usable candidate, but the agent should surface permission and audit notes before installation.
- Skill source structure is not confirmed in the registry. Inspect the source and identify valid skill instructions before proposing an installation. A repository URL or GitHub stars do not prove installability.
License clarity
86
MIT
- MIT
Permission surface
76
shell or command execution
- Shell or command execution: high
- Browser automation: medium
- Network access: medium
Validation plan
What the agent should do next
- 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
- 2Install in an isolated workspace or sandbox with no production secrets available.
- 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
- 4Compare the selected skill against at least one alternative when the eval status is review or failed.
- 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
- Skill source structure is not confirmed in the registry. Inspect the source and identify valid skill instructions before proposing an installation. A repository URL or GitHub stars do not prove installability.
- No major trust warnings detected from available metadata
Supporting checks
Trust signals behind the decision
README/SKILL.md completeness
pass90
Metadata includes enough usage and workflow context
Recent maintenance
pass88
3mo since push
Alternatives available
pass82
Alternative skills are available for comparison.