Star200+

Pre-install eval

multi-tenant-data-partitioner 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
67
Eval report
68
Trust
74
Audit
58
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 multi-tenant-data-partitioner before installing it in an agent workflow
  • data-analysis
  • Database and SQL workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add codebygarv/Ai-skills --skill multi-tenant-data-partitioner

Install command safety

92

pass

standard package or runtime install path

  • npx skills add codebygarv/Ai-skills --skill multi-tenant-data-partitioner

Trust score

68

warn

Potentially useful, but at least one trust signal needs human inspection.

  • Manual review
  • 21 GitHub stars
  • MIT

Audit score

74

warn

Needs review

  • Example middleware code uses string interpolation for tenantId in SQL, which could be vulnerable to SQL injection if tenantId is not properly sanitized.

Agent safety gate

58

warn

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

  • Require human approval before installing into a real workspace.
  • Example middleware code uses string interpolation for tenantId in SQL, which could be vulnerable to SQL injection if tenantId is not properly sanitized.

License clarity

86

pass

MIT

  • MIT

Permission surface

74

warn

network or browser access, 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
  • Low GitHub adoption signal
  • Example middleware code uses string interpolation for tenantId in SQL, which could be vulnerable to SQL injection if tenantId is not properly sanitized.
  • Quality score needs review
  • GitHub adoption: 21 GitHub stars

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

2d since push

Alternatives available

pass

82

Alternative skills are available for comparison.