Star200+

Pre-install eval

email-marketing 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
79
Eval report
76
Trust
86
Audit
54
Agent safety

do not auto install

Permission surface: secrets or environment access, filesystem or document access

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate email-marketing before installing it in an agent workflow
  • research
  • Research agents workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add nexu-io/open-design --skill email-marketing

Install command safety

92

pass

standard package or runtime install path

  • npx skills add nexu-io/open-design --skill email-marketing

Trust score

76

warn

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

  • Strong shortlist
  • 91K GitHub stars
  • Apache-2.0

Audit score

86

warn

Needs review

  • Permission surface may require sandboxing

Agent safety gate

54

warn

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

  • Test manually in an isolated workspace and compare against safer alternatives.
  • High-risk permission hints: Secrets or environment access

License clarity

86

pass

Apache-2.0

  • Apache-2.0

Permission surface

46

fail

secrets or environment access, filesystem or document access

  • Browser automation: medium
  • 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.md mentions 'table fallback' in the description but the workflow does not describe how to implement table-based layout for email clients that require it.
  • High-risk permission hints: Secrets or environment access
  • Permission surface may require sandboxing
  • The excerpt is truncated; the full SKILL.md may contain additional details, but based on the provided content, the workflow is clear.

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

100

Pushed today

Alternatives available

pass

82

Alternative skills are available for comparison.