Pre-install eval

task-triage 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
69
Eval report
70
Trust
74
Audit
62
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

94

pass

Task wording matches this skill metadata.

  • Evaluate task-triage before installing it in an agent workflow
  • automation
  • Workflow automation workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add suyuan2022/suyuan-skill --skill task-triage

Install command safety

92

pass

standard package or runtime install path

  • npx skills add suyuan2022/suyuan-skill --skill task-triage

Trust score

70

warn

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

  • Manual review
  • 27 GitHub stars
  • MIT

Audit score

74

warn

Needs review

  • No executable code or external dependencies; the skill is purely a decision framework, so security risk is inherently low.

Agent safety gate

62

warn

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

  • Require human approval before installing into a real workspace.
  • No executable code or external dependencies; the skill is purely a decision framework, so security risk is inherently low.

License clarity

86

pass

MIT

  • MIT

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
  • Low GitHub adoption signal
  • No executable code or external dependencies; the skill is purely a decision framework, so security risk is inherently low.
  • The SKILL.md is complete and self-contained; minor formatting quirk in the YAML frontmatter (description uses '|-' but actual text is clear).
  • Quality score needs review

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.