Pre-install eval

vcard 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
75
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 vcard before installing it in an agent workflow
  • productivity
  • Workflow automation workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add metadist/synaplan-desktop --skill vcard

Install command safety

92

pass

standard package or runtime install path

  • npx skills add metadist/synaplan-desktop --skill vcard

Trust score

74

warn

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

  • Strong shortlist
  • 257 GitHub stars
  • Apache-2.0

Audit score

80

warn

Needs review

  • The script does not enforce that the output path is inside the out-box as stated in SKILL.md; it will write to any path provided.

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 script does not enforce that the output path is inside the out-box as stated in SKILL.md; it will write to any path provided.

License clarity

86

pass

Apache-2.0

  • Apache-2.0

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 script does not enforce that the output path is inside the out-box as stated in SKILL.md; it will write to any path provided.
  • No OpenAgentSkill engagement data yet
  • No validation for empty full_name; if an empty string is passed, the script will crash with an IndexError.
  • Quality score needs review

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

8d since push

Alternatives available

info

55

No close alternatives were found in the current shortlist.