OpenAgentSkill
GitHub200+

Pre-install eval

Briefing Deck 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
59
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 Briefing Deck 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 Player-YN/PawWork_ZhuaZhua --skill Briefing Deck

Install command safety

92

pass

standard package or runtime install path

  • npx skills add Player-YN/PawWork_ZhuaZhua --skill Briefing Deck

Trust score

73

warn

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

  • Strong shortlist
  • 1.3K GitHub stars
  • MIT

Audit score

79

warn

Needs review

  • The skill references internal tools and skills (e.g., `acquire fetch`, `inspect`, `deck`, `slides`, `visual-compile`) without describing their interfaces or security implications, which may be unclear to external reviewers.

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.
  • The skill references internal tools and skills (e.g., `acquire fetch`, `inspect`, `deck`, `slides`, `visual-compile`) without describing their interfaces or security implications, which may be unclear to external reviewers.

License clarity

86

pass

MIT

  • MIT

Permission surface

72

warn

filesystem or document access, network or browser access

  • Network access: medium
  • Filesystem 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
  • production agents without a repository review
  • The skill references internal tools and skills (e.g., `acquire fetch`, `inspect`, `deck`, `slides`, `visual-compile`) without describing their interfaces or security implications, which may be unclear to external reviewers.
  • The SKILL.md contains a mix of English and Chinese (e.g., 「这页」), which could reduce clarity for non-Chinese readers.
  • 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.