Pre-install eval
emails 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.
manual review
Review the audit page, then allow agent install in a sandboxed workflow.
Required gates
Checks an agent must pass before install
Task fit
84
Task wording matches this skill metadata.
- Evaluate emails before installing it in an agent workflow
- productivity
- Workflow automation workflows; Claude Code teams; teams that value GitHub adoption signals
Install path
92
Install handoff is available.
- npx skills add coreyhaines31/marketingskills --skill emails
Install command safety
92
standard package or runtime install path
- npx skills add coreyhaines31/marketingskills --skill emails
Trust score
84
Good trust signals with a few areas worth checking before rollout.
- Strong shortlist
- 47K GitHub stars
- MIT
Audit score
87
Safe to try
- No explicit security boundaries or instructions about handling sensitive data, but the skill only generates text and reads local context files, so risk is low.
Agent safety gate
75
Good audit and safety signals with no high-risk permission hints in public metadata.
- Review the audit page, then allow agent install in a sandboxed workflow.
- Safe-to-try audit
License clarity
86
MIT
- MIT
Permission surface
100
no high-risk permission surface in public metadata
- 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
- production agents without a repository review
- No explicit security boundaries or instructions about handling sensitive data, but the skill only generates text and reads local context files, so risk is low.
- Production credentials, payments, or irreversible account changes without explicit human review
- Sensitive private data before reviewing repository code, license, and permission surface
- Automatic installation in a production workspace
Supporting checks
Trust signals behind the decision
README/SKILL.md completeness
pass86
Metadata includes enough usage and workflow context
Recent maintenance
pass88
2mo since push
Alternatives available
pass82
Alternative skills are available for comparison.