agentsclimarketplace

Opsx spec validate

Skill vladcheck/skills/opsx-spec-validate

Skills that are authored by me.

Install
npx -y skills add vladcheck/skills --skill opsx-spec-validate

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when you need to validate if your openspec artifacts violate any specs defined by openspec.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.7 KB, as published. Nobody here has run it

Files to check

  • proposal.md - initial artifact
  • design.md - builds on proposal.md
  • specs/* - builds on proposal.md
  • tasks.md - builds on every spec above

Rules for proposal.md

  • Has sections: Why, What Changes, Capabilities (New + Modified), Impact
  • Capabilities use kebab-case names
  • Each new capability listed in New Capabilities has a corresponding spec file in specs/
  • Each modified capability listed in Modified Capabilities has a corresponding delta spec file in specs/
  • Breaking changes marked with BREAKING
  • Concise (1-2 pages)

Rules for design.md

  • Has sections: Context, Goals/Non-Goals, Decisions, Risks/Trade-offs, Migration Plan, Open Questions
  • Each Decision explains rationale (why X over Y?)
  • Risks have mitigation
  • Migration Plan has concrete steps
  • No empty sections

Rules for spec files (all)

  • Scenario headers: exactly 4 hashtags (#### Scenario: ...)
  • Requirement headers: exactly 3 hashtags (### Requirement: ...)
  • Every requirement has at least one scenario
  • SHALL/MUST for normative statements
  • Delta section headers valid: only ## ADDED, ## MODIFIED, ## REMOVED, ## RENAMED
  • No empty delta sections

Cross-artifact consistency

  • Every new capability in proposal.md → has spec file in specs/
  • Every modified capability in proposal.md → has delta spec file in specs/
  • No extra spec files without corresponding proposal entries
  • No extra proposal entries without corresponding spec files

Algorithm

  1. Ask a subagent to verify if your specs violate openspec conventions
  2. Fix violations

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.