Pre-install eval

clinical-reports 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
73
Eval report
74
Trust
80
Audit
52
Agent safety

manual review

Test manually in an isolated workspace and compare against safer alternatives.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate clinical-reports before installing it in an agent workflow
  • security
  • Security and compliance workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add foryourhealth111-pixel/Vibe-Skills --skill clinical-reports

Install command safety

92

pass

standard package or runtime install path

  • npx skills add foryourhealth111-pixel/Vibe-Skills --skill clinical-reports

Trust score

74

warn

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

  • Strong shortlist
  • 3.1K GitHub stars
  • MIT License

Audit score

80

warn

Needs review

  • The skill allows Bash execution, which could be a security risk if the skill is used to run arbitrary commands. However, the skill content does not appear to exploit this, and it is used for legitimate script execution (e.g., generating schematics).

Agent safety gate

52

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: Shell or command execution

License clarity

86

pass

MIT License

  • MIT License

Permission surface

62

warn

shell or command execution, filesystem or document access

  • Shell or command execution: high
  • 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 allows Bash execution, which could be a security risk if the skill is used to run arbitrary commands. However, the skill content does not appear to exploit this, and it is used for legitimate script execution (e.g., generating schematics).
  • High-risk permission hints: Shell or command execution
  • The skill mandates the use of the scientific-schematics skill for every report, which may create a hard dependency on another skill that might not be available in all environments.
  • Quality score needs review

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

88

2mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.