Pre-install eval

dbs-chatroom-austrian 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
76
Eval report
76
Trust
81
Audit
69
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

84

pass

Task wording matches this skill metadata.

  • Evaluate dbs-chatroom-austrian before installing it in an agent workflow
  • automation
  • Browser automation 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-chatroom-austrian

Install command safety

92

pass

standard package or runtime install path

  • npx skills add Pluviobyte/rnskill --skill dbs-chatroom-austrian

Trust score

76

warn

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

  • Strong shortlist
  • 1.4K GitHub stars
  • NOASSERTION

Audit score

81

warn

Needs review

  • Repository has no license detected (GitHub reports NOASSERTION), leaving reuse rights ambiguous.

Agent safety gate

69

warn

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

  • Require human approval before installing into a real workspace.
  • Repository has no license detected (GitHub reports NOASSERTION), leaving reuse rights ambiguous.

License clarity

86

pass

NOASSERTION

  • NOASSERTION

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 has no license detected (GitHub reports NOASSERTION), leaving reuse rights ambiguous.
  • SKILL.md references a separate `/dbs` skill for navigation, which may cause confusion if that skill is not installed.
  • Quality score needs review
  • Production credentials, payments, or irreversible account changes without explicit human 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.