Star200+

Pre-install eval

lofn-daily 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
59
Eval report
57
Trust
68
Audit
36
Agent safety

do not auto install

Trust score: Sparse or weak trust signals. Treat this as an experimental candidate.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate lofn-daily before installing it in an agent workflow
  • security
  • Research agents workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add LocalSymmetry/lofn --skill lofn-daily

Install command safety

92

pass

standard package or runtime install path

  • npx skills add LocalSymmetry/lofn --skill lofn-daily

Trust score

57

fail

Sparse or weak trust signals. Treat this as an experimental candidate.

  • High review required
  • 22 GitHub stars
  • Unknown

Audit score

68

warn

Needs review

  • License is unclear

Agent safety gate

36

warn

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

  • Test manually in an isolated workspace and compare against safer alternatives.
  • High-risk permission hints: Shell or command execution

License clarity

42

warn

Unknown

  • Unknown

Permission surface

48

fail

shell or command execution, filesystem or document access

  • Shell or command execution: high
  • Browser automation: medium
  • 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
  • Repository license is unknown; SKILL.md does not include license or attribution information.
  • No OpenAgentSkill engagement data yet
  • High-risk permission hints: Shell or command execution

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

76

Public metadata needs stronger README/SKILL.md context

Recent maintenance

pass

100

Pushed today

Alternatives available

pass

82

Alternative skills are available for comparison.