automated-e2e-testing Eval
==========================

Status: failed
Score: 60/100
Risk: high
Decision: do_not_auto_install
Policy: block
Reason: Permission surface: secrets or environment access, network or browser access

Install:
npx skills add fishzjp/qa-skills --skill automated-e2e-testing

Required checks:
- PASS Task fit: Task wording matches this skill metadata.
- 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
- WARN Agent safety gate: Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
- PASS License clarity: MIT
- FAIL Permission surface: secrets or environment access, network or browser access

Warnings:
- Trust score: Potentially useful, but at least one trust signal needs human inspection.
- Audit score: Needs review
- Agent safety gate: Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
- README/SKILL.md completeness: Public metadata needs stronger README/SKILL.md context
- High-risk permission hints: Secrets or environment access
- Permission surface may require sandboxing
- SKILL.md references external dependencies under `../core/` (clarify-pattern.md, triage.md, pipeline-integration.md, report-template.md) that are not included in the skill directory; portability breaks outside the original repository layout.
- The workflow uses ecosystem-specific terminology (markmap, Schema, type_scope, automation_plan) without inline definitions; an agent outside the qa-skills context may need extra clarification.
- Bug evidence collection may capture sensitive data through screenshots, API logs, or console logs; no redaction or data-handling guidance is provided.
- Low GitHub adoption signal
- Quality score needs review
- Permission surface needs review: secrets or environment access, network or browser access

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
- Low GitHub adoption signal
- SKILL.md references external dependencies under `../core/` (clarify-pattern.md, triage.md, pipeline-integration.md, report-template.md) that are not included in the skill directory; portability breaks outside the original repository layout.
- No OpenAgentSkill engagement data yet
- High-risk permission hints: Secrets or environment access
- Permission surface may require sandboxing
- The workflow uses ecosystem-specific terminology (markmap, Schema, type_scope, automation_plan) without inline definitions; an agent outside the qa-skills context may need extra clarification.

URLs:
- Skill: https://www.openagentskill.com/skills/fishzjp-automated-e2e-testing
- Audit: https://www.openagentskill.com/skills/fishzjp-automated-e2e-testing/audit
- JSON: https://www.openagentskill.com/api/agent/evals?slug=fishzjp-automated-e2e-testing