env-manager Eval
================

Status: failed
Score: 61/100
Risk: high
Decision: do_not_auto_install
Policy: block
Reason: Agent safety gate: This skill should not be selected by an agent without explicit human security review.

Install:
npx skills add laolaoshiren/claude-code-skills-zh --skill env-manager

Required checks:
- WARN Task fit: Task fit is weak; compare alternatives before selecting.
- PASS Install path: Install handoff is available.
- PASS Install command safety: standard package or runtime install path
- WARN Trust score: Potentially useful, but at least one trust signal needs human inspection.
- WARN Audit score: Needs review
- FAIL Agent safety gate: This skill should not be selected by an agent without explicit human security review.
- PASS License clarity: MIT
- FAIL Permission surface: secrets or environment access, shell or command execution

Warnings:
- Task fit: Task fit is weak; compare alternatives before selecting.
- Trust score: Potentially useful, but at least one trust signal needs human inspection.
- Audit score: Needs review
- README/SKILL.md completeness: Public metadata needs stronger README/SKILL.md context
- High-risk permission hints: Shell or command execution, Secrets or environment access
- Dependency or permission surface needs review
- Permission surface may require sandboxing
- SKILL.md does not explicitly instruct the agent to treat scanned .env files and source code as untrusted data, leaving room for prompt injection if a repository contains malicious instructions.
- The workflow lists desired outcomes for validation, generation, and synchronization, but lacks concrete command or tool examples, which may lead to inconsistent agent behavior.
- The limitations of static scanning are mentioned only briefly in the checklist and boundaries; they should be a dedicated section to prevent false confidence in 'unused' or 'safe' findings.
- Quality score needs review
- Permission surface needs review: secrets or environment access, shell or command execution

Validation plan:
1. Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. Install in an isolated workspace or sandbox with no production secrets available.
3. Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. Compare the selected skill against at least one alternative when the eval status is review or failed.
5. Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Do not use when:
- teams that need a vendor-supported SLA
- production agents without a repository review
- SKILL.md does not explicitly instruct the agent to treat scanned .env files and source code as untrusted data, leaving room for prompt injection if a repository contains malicious instructions.
- High-risk permission hints: Shell or command execution, Secrets or environment access
- Dependency or permission surface needs review
- Permission surface may require sandboxing
- The workflow lists desired outcomes for validation, generation, and synchronization, but lacks concrete command or tool examples, which may lead to inconsistent agent behavior.
- The limitations of static scanning are mentioned only briefly in the checklist and boundaries; they should be a dedicated section to prevent false confidence in 'unused' or 'safe' findings.

URLs:
- Skill: https://www.openagentskill.com/skills/laolaoshiren-env-manager
- Audit: https://www.openagentskill.com/skills/laolaoshiren-env-manager/audit
- JSON: https://www.openagentskill.com/api/agent/evals?slug=laolaoshiren-env-manager