Pre-install eval

academic-integrity-rewrite 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.

FailedHigh riskBLOCK Policy
65
Eval report
67
Trust
74
Audit
46
Agent safety

do not auto install

Install path: No install command or repository handoff is available.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate academic-integrity-rewrite before installing it in an agent workflow
  • research
  • Research agents workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

20

fail

No install command or repository handoff is available.

Install command safety

92

pass

standard package or runtime install path

Trust score

67

warn

Potentially useful, but at least one trust signal needs human inspection.

  • Manual review
  • 82 GitHub stars
  • MIT

Audit score

74

warn

Needs review

  • The audit script's measurement regex may miss some uncommon unit notations (e.g., scientific notation, complex compound units), but this is explicitly acknowledged in the skill and manual review is recommended.

Agent safety gate

46

warn

Sparse or mixed signals. Useful for discovery, but not for autonomous installation.

  • The tracked source changed or could not be synchronized. Review the current source before installing.

License clarity

86

pass

MIT

  • MIT

Permission surface

76

warn

shell or command execution

  • 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 audit script's measurement regex may miss some uncommon unit notations (e.g., scientific notation, complex compound units), but this is explicitly acknowledged in the skill and manual review is recommended.
  • High-risk permission hints: Shell or command execution
  • The tracked source changed or could not be synchronized. Review the current source before installing.
  • No explicit handling for non-UTF8 encodings in plain text files, though most modern editors default to UTF-8.

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

76

Public metadata needs stronger README/SKILL.md context

Recent maintenance

pass

88

2mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.