agentsclimarketplace
Sign in

Openspec explore

Skill TheSmuks/openspec-hermes/skills/openspec/openspec-explore

Use when working with OpenSpec in Hermes: investigate unclear requirements or architecture before creating a change.From its SKILL.md

Install
npx -y skills add TheSmuks/openspec-hermes --skill openspec-explore

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

  • 0 stars0 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 file declares

Copied from the file, not written here

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

2.0 KB, 356 tokens by cl100k_base, as published. Nobody here has run it

openspec-explore

Use this for OpenSpec's /opsx:explore workflow.

Hermes operating rules for OpenSpec

  • Work from the user's project root. If unknown, inspect the current directory first.
  • Ensure the OpenSpec CLI exists before using it: openspec --version. If missing, install with npm install -g @fission-ai/openspec@latest.
  • Initialize projects with openspec init --tools none unless the user also wants other AI-tool integrations. Hermes uses these skills, not OpenSpec-generated slash commands.
  • Prefer agent-compatible OpenSpec CLI calls with --json where available: openspec list --json, openspec status --change <id> --json, openspec instructions <artifact> --change <id> --json, openspec validate --all --json.
  • Read generated artifacts before editing or implementing. Do not invent OpenSpec state.
  • Run validation after changing OpenSpec artifacts: openspec validate <change> or openspec validate --all.
  • Keep changes focused. If user scope diverges, update the existing change only when intent is the same; otherwise create a new change.

Procedure

  1. Ask for the exploration topic only if it is not in the user request.
  2. Inspect the codebase and existing OpenSpec state: openspec list --json, openspec list --specs --json, and project files relevant to the topic.
  3. Research options, constraints, tradeoffs, and existing patterns.
  4. Do not create OpenSpec artifacts during exploration unless the user explicitly asks to proceed.
  5. End with findings, options considered, recommendation, and a suggested change name if ready.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,834. 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.