oma-debug Eval report.

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
• SKILL.md references resources/execution-protocol.md and examples, but those files are not present in the submitted skill directory. Either include them or remove the references.
• High-risk permission hints: Shell or command execution
• The skill lacks a concrete end-to-end example showing the full debug workflow from symptom to root cause to regression test.
• The bundled resources are heavily frontend/React-focused. Since the skill claims general bug debugging, backend, API, database, and concurrency bug patterns should be added or clearly scoped.