Pre-install eval

sun-yuchen-perspective 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
67
Eval report
67
Trust
73
Audit
57
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 sun-yuchen-perspective before installing it in an agent workflow
  • research
  • Research agents workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add alchaincyf/sun-yuchen-perspective --skill sun-yuchen-perspective

Install command safety

92

pass

standard package or runtime install path

  • npx skills add alchaincyf/sun-yuchen-perspective --skill sun-yuchen-perspective

Trust score

67

warn

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

  • Manual review
  • 180 GitHub stars
  • Unknown

Audit score

73

warn

Needs review

  • License is unclear

Agent safety gate

57

warn

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

  • Test manually in an isolated workspace and compare against safer alternatives.
  • License is unclear

License clarity

42

warn

Unknown

  • Unknown

Permission surface

100

pass

no high-risk permission surface in public metadata

  • Network access: medium
  • Database 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 detected as 'Unknown'; README shows MIT badge but actual LICENSE file absent or not recognized. License clarity needed.
  • License is unclear
  • Financial research output is not financial advice; require human review before any live investment decision
  • Skill role-plays a real, controversial persona; while disclaimers exist, potential misuse for deceptive or manipulative purposes should be explicitly mitigated in SKILL.md (e.g., forbidding use for actual financial fraud).

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.