OpenAgentSkill
GitHub200+

Pre-install eval

cpp-pro 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
79
Eval report
78
Trust
84
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 cpp-pro before installing it in an agent workflow
  • design-creative
  • Design and creative workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add Jeffallan/claude-skills --skill cpp-pro

Install command safety

92

pass

standard package or runtime install path

  • npx skills add Jeffallan/claude-skills --skill cpp-pro

Trust score

78

warn

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

  • Strong shortlist
  • 11K GitHub stars
  • MIT

Audit score

84

warn

Needs review

  • SKILL.md does not include an explicit 'Limitations' or 'When Not to Use' section, so safe operating boundaries are only implied by the constraints.

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.
  • SKILL.md does not include an explicit 'Limitations' or 'When Not to Use' section, so safe operating boundaries are only implied by the constraints.

License clarity

86

pass

MIT

  • MIT

Permission surface

86

pass

filesystem or document access

  • 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
  • SKILL.md does not include an explicit 'Limitations' or 'When Not to Use' section, so safe operating boundaries are only implied by the constraints.
  • Some reference file excerpts appear truncated or incomplete, which could reduce usefulness if the actual files are not fully populated.
  • No explicit guidance on how to handle unsafe or malicious user C++ code requests beyond general good-practice constraints.
  • 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

3mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.