Pre-install eval
customer-onboarding-call 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
Permission surface: shell or command execution, network or browser access
Required gates
Checks an agent must pass before install
Task fit
94
Task wording matches this skill metadata.
- Evaluate customer-onboarding-call before installing it in an agent workflow
- business
- Customer support workflows; Claude Code teams; builders willing to evaluate younger projects
Install path
92
Install handoff is available.
- npx skills add CALLE-AI/awesome-phone-call-agents --skill customer-onboarding-call
Install command safety
92
standard package or runtime install path
- npx skills add CALLE-AI/awesome-phone-call-agents --skill customer-onboarding-call
Trust score
68
Potentially useful, but at least one trust signal needs human inspection.
- Manual review
- 63 GitHub stars
- MIT
Audit score
75
Needs review
- Permission surface may require sandboxing
Agent safety gate
47
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: Shell or command execution
License clarity
86
MIT
- MIT
Permission surface
50
shell or command execution, network or browser access
- Shell or command execution: high
- Network access: medium
- Database 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
- The skill does not explicitly address how to handle failures when writing to the CRM or when the provider does not return structured results as expected.
- High-risk permission hints: Shell or command execution
- Permission surface may require sandboxing
- Financial research output is not financial advice; require human review before any live investment decision
Supporting checks
Trust signals behind the decision
README/SKILL.md completeness
pass86
Metadata includes enough usage and workflow context
Recent maintenance
pass100
1d since push
Alternatives available
pass82
Alternative skills are available for comparison.