Pre-install eval

dbs-xhs-title 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
73
Eval report
74
Trust
80
Audit
64
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

70

warn

Task fit is weak; compare alternatives before selecting.

  • Evaluate dbs-xhs-title 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 Pluviobyte/rnskill --skill dbs-xhs-title

Install command safety

92

pass

standard package or runtime install path

  • npx skills add Pluviobyte/rnskill --skill dbs-xhs-title

Trust score

74

warn

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

  • Strong shortlist
  • 1.4K GitHub stars
  • NOASSERTION

Audit score

80

warn

Needs review

  • Repository license is detected as NOASSERTION, so reuse/redistribution terms are not clearly defined.

Agent safety gate

64

warn

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

  • Require human approval before installing into a real workspace.
  • Repository license is detected as NOASSERTION, so reuse/redistribution terms are not clearly defined.

License clarity

86

pass

NOASSERTION

  • NOASSERTION

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
  • Repository license is detected as NOASSERTION, so reuse/redistribution terms are not clearly defined.
  • The SKILL.md embeds 75 formulas attributed to YAO's external PDF, but there is no explicit permission statement for redistributing that formula list and the original example titles.
  • The provided excerpt ends partway through formula #9; confirm that the committed SKILL.md actually contains the complete 75-formula library inline.
  • 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.