Pre-install eval
humanizer 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.
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
Task fit
94
Task wording matches this skill metadata.
- Evaluate humanizer before installing it in an agent workflow
- security
- Content automation workflows; Claude Code teams; builders willing to evaluate younger projects
Install path
92
Install handoff is available.
- npx skills add org-quicko/skills --skill humanizer
Install command safety
92
standard package or runtime install path
- npx skills add org-quicko/skills --skill humanizer
Trust score
56
Sparse or weak trust signals. Treat this as an experimental candidate.
- High review required
- 0 GitHub stars
- Unknown
Audit score
55
Needs review
- License is unclear
Agent safety gate
27
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: Secrets or environment access
License clarity
42
Unknown
- Unknown
Permission surface
46
secrets or environment access, filesystem or document access
- Network access: medium
- Filesystem access: medium
- Secrets or environment access: high
Validation plan
What the agent should do next
- 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
- 2Install in an isolated workspace or sandbox with no production secrets available.
- 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
- 4Compare the selected skill against at least one alternative when the eval status is review or failed.
- 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 a license or attribution notice.
- High-risk permission hints: Secrets or environment access
- License is unclear
Supporting checks
Trust signals behind the decision
README/SKILL.md completeness
pass86
Metadata includes enough usage and workflow context
Recent maintenance
warn62
7mo since push
Alternatives available
pass82
Alternative skills are available for comparison.