Star200+

Pre-install eval

event-sales-script 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.

Needs reviewMedium riskREVIEW Policy
74
Eval report
74
Trust
80
Audit
68
Agent safety

manual review

Require human approval before installing into a real workspace.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate event-sales-script before installing it in an agent workflow
  • business
  • Sales and CRM workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add bam-bam-2/solo-skills --skill event-sales-script

Install command safety

92

pass

standard package or runtime install path

  • npx skills add bam-bam-2/solo-skills --skill event-sales-script

Trust score

74

warn

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

  • Strong shortlist
  • 128 GitHub stars
  • MIT

Audit score

80

warn

Needs review

  • The skill does not explicitly state that it only generates text and does not send messages or interact with external services, but this is inferred from the documentation.

Agent safety gate

68

warn

Usable candidate, but the agent should surface permission and audit notes before installation.

  • Require human approval before installing into a real workspace.
  • The skill does not explicitly state that it only generates text and does not send messages or interact with external services, but this is inferred from the documentation.

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
  • production agents without a repository review
  • The skill does not explicitly state that it only generates text and does not send messages or interact with external services, but this is inferred from the documentation.
  • The reference framework.md is included, but attribution to the original source (다오랩, 다오콘 2026) is informal and may need more explicit citation if required.
  • Quality score needs review
  • Stars/forks activity: 128 stars, 22 forks; issue activity unavailable in current metadata

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

Pushed today

Alternatives available

pass

82

Alternative skills are available for comparison.