Skip to content
TrustedSkillsbeta
Back to all skills

Openspec Verify Change

Checked
pbh-btn·vlatest·testing·GPL-3.0

This skill automates verification of changes against OpenSPEC requirements, ensuring compliance and reducing manual effort for quality assurance.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add pbh-btn/peerbanhelper --skill openspec-verify-change -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

pbh-btn

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned pbh-btn/peerbanhelper at 471956a9a0.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
471956a9a0
Manifest
.claude/skills/openspec-verify-change/SKILL.md
Scanned
2 files, 330 lines
Copies in repo
2 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The openspec-verify-change skill allows AI agents to verify changes against an Open Specification (OpenSpec) document. It can determine if a proposed change is valid according to the specification's rules and constraints, providing feedback on potential inconsistencies or errors. This helps ensure modifications adhere to established standards and maintain integrity.

When to use it

  • Software Development: Validate code changes against an OpenSpec that defines API behavior.
  • Configuration Management: Verify infrastructure configuration updates align with a defined OpenSpec.
  • Policy Enforcement: Ensure policy modifications comply with documented requirements outlined in an OpenSpec.
  • Data Transformation: Confirm data transformation scripts adhere to the rules and constraints specified in an OpenSpec.

Key capabilities

  • Open Specification parsing
  • Change validation against specification rules
  • Error reporting & feedback generation

Example prompts

  • "Verify this change to the API endpoint /users against the OpenSpec document located at https://example.com/api-spec.openspec."
  • "Is this proposed configuration update valid according to the OpenSpec?"
  • “Check if these policy changes are compliant with the documented OpenSpec.”

Tips & gotchas

  • The skill requires access to a valid Open Specification document, typically provided as a URL.
  • Ensure the OpenSpec document is well-defined and accurately reflects the intended rules and constraints for verification.