openspec-plus-apply 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
• The skill depends on the external `openspec-plus-tdd` skill and a vanilla `/opsx-apply` environment, but the submission does not document how to verify or install those dependencies.
• Subagents are told to follow AGENTS.md/CLAUDE.md/GEMINI.md rules, but there is no explicit precedence statement that the skill's own safety and process constraints override repository instructions if they conflict. Malicious repository content could attempt to steer subagent behavior.
• Quality score needs review
• Stars/forks activity: 167 stars, 9 forks; issue activity unavailable in current metadata