Pre-install eval

archival-fragments 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
68
Eval report
68
Trust
73
Audit
61
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 archival-fragments before installing it in an agent workflow
  • automation
  • Browser automation 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

68

warn

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

  • Manual review
  • 212 GitHub stars
  • Unknown

Audit score

73

warn

Needs review

  • License is unclear

Agent safety gate

61

warn

Usable candidate, but the agent should surface permission and audit notes before installation.

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

License clarity

42

warn

Unknown

  • Unknown

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
  • Repository license is unknown/no LICENSE file detected, so reuse rights are not clearly granted.
  • License is unclear
  • The tracked source changed or could not be synchronized. Review the current source before installing.
  • The actual setup and credential commands are in references/00-setup.md, which was not included in the reviewed excerpt; those commands should be verified against official sources and secret-handling best practices.

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.