OpenAgentSkill
GitHub200+

Pre-install eval

daily-papers-notes 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
71
Eval report
73
Trust
79
Audit
51
Agent safety

manual review

Test manually in an isolated workspace and compare against safer alternatives.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate daily-papers-notes 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 huangkiki/dailypaper-skills --skill daily-papers-notes

Install command safety

92

pass

standard package or runtime install path

  • npx skills add huangkiki/dailypaper-skills --skill daily-papers-notes

Trust score

73

warn

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

  • Strong shortlist
  • 1.2K GitHub stars
  • Apache-2.0

Audit score

79

warn

Needs review

  • The skill assumes the presence of shared configuration files and the paper-reader skill; if the repository is not fully cloned or the pipeline is run in isolation, these dependencies may be missing.

Agent safety gate

51

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

86

pass

Apache-2.0

  • Apache-2.0

Permission surface

76

warn

shell or command execution

  • Shell or command execution: high
  • 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
  • The skill assumes the presence of shared configuration files and the paper-reader skill; if the repository is not fully cloned or the pipeline is run in isolation, these dependencies may be missing.
  • High-risk permission hints: Shell or command execution
  • The skill does not explicitly handle the case where the shared config file is absent or malformed, which could cause the agent to fail silently.
  • 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

3mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.