Star200+

Pre-install eval

lark-attendance 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
78
Eval report
81
Trust
87
Audit
59
Agent safety

do not auto install

Permission surface: shell or command execution, network or browser access

Required gates

Checks an agent must pass before install

Open JSON

Task fit

70

warn

Task fit is weak; compare alternatives before selecting.

  • Evaluate lark-attendance 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 larksuite/cli --skill lark-attendance

Install command safety

92

pass

standard package or runtime install path

  • npx skills add larksuite/cli --skill lark-attendance

Trust score

81

warn

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

  • Strong shortlist
  • 17K GitHub stars
  • MIT

Audit score

87

warn

Needs review

  • Permission surface may require sandboxing

Agent safety gate

59

warn

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

  • Require human approval before installing into a real workspace.
  • High-risk permission hints: Shell or command execution

License clarity

86

pass

MIT

  • MIT

Permission surface

50

fail

shell or command execution, network or browser access

  • Shell or command execution: high
  • 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
  • high-compliance environments without internal security review
  • No major risk signals from current metadata
  • High-risk permission hints: Shell or command execution
  • Permission surface may require sandboxing
  • Quality score needs review

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

70

Public metadata needs stronger README/SKILL.md context

Recent maintenance

pass

100

Pushed today

Alternatives available

pass

82

Alternative skills are available for comparison.