oma-explanation Eval
====================

Status: failed
Score: 69/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 first-fluke/oh-my-agent --skill oma-explanation

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
- 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:
- Trust score: Potentially useful, but at least one trust signal needs human inspection.
- Audit score: Needs review
- 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 require HTML-escaping all diff-derived content and PR text before embedding it in the generated explainer; this should be codified in the html-contract to prevent script/HTML injection inside the self-contained file.
- The `open <path>` step should be specified to use an argument-list subprocess call rather than shell interpolation, so a malicious or unexpected slug/path cannot inject shell commands.
- The excerpt does not include a dedicated setup/installation section; listing required tools (`git`, optional `gh`, optional Serena MCP) and their installation state would make the skill more self-contained.
- Quality score needs review
- Permission surface needs review: secrets or environment access, shell or command execution
- Dependency/runtime risk: command execution surface, credential or environment access
- Permission surface: 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 require HTML-escaping all diff-derived content and PR text before embedding it in the generated explainer; this should be codified in the html-contract to prevent script/HTML injection inside the self-contained file.
- No OpenAgentSkill engagement data yet
- High-risk permission hints: Shell or command execution, Secrets or environment access
- Dependency or permission surface needs review
- Permission surface may require sandboxing
- The `open <path>` step should be specified to use an argument-list subprocess call rather than shell interpolation, so a malicious or unexpected slug/path cannot inject shell commands.

URLs:
- Skill: https://www.openagentskill.com/skills/first-fluke-oma-explanation
- Audit: https://www.openagentskill.com/skills/first-fluke-oma-explanation/audit
- JSON: https://www.openagentskill.com/api/agent/evals?slug=first-fluke-oma-explanation