OpenAgentSkill
GitHub200+

Pre-install eval

designing-data-intensive-applications 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
74
Trust
81
Audit
65
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 designing-data-intensive-applications 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 ciembor/agent-rules-books --skill designing-data-intensive-applications

Install command safety

92

pass

standard package or runtime install path

  • npx skills add ciembor/agent-rules-books --skill designing-data-intensive-applications

Trust score

74

warn

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

  • Strong shortlist
  • 2.8K GitHub stars
  • MIT

Audit score

81

warn

Needs review

  • No critical security risks found; the skill contains static reference material and does not instruct code execution, downloads, secret access, or destructive actions.

Agent safety gate

65

warn

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

  • Require human approval before installing into a real workspace.
  • No critical security risks found; the skill contains static reference material and does not instruct code execution, downloads, secret access, or destructive actions.

License clarity

86

pass

MIT

  • MIT

Permission surface

88

pass

database access

  • 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
  • production agents without a repository review
  • No critical security risks found; the skill contains static reference material and does not instruct code execution, downloads, secret access, or destructive actions.
  • SKILL.md is quite thin and mostly points to supporting files; the core workflow, expected output format, and limitations are not fully stated in SKILL.md itself.
  • The relationship between the .mini.md, .md, and .nano.md files could be clearer, especially regarding when to escalate from one to another.
  • The imperative 'OBEY' framing is unusual and could be mistaken for an injection-style instruction, though the content itself is benign.

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.