Skip to content
TrustedSkillsbeta
Back to all skills

Openspec Archive Change

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

This skill retrieves and compares changes between different versions of OpenSpec documents, streamlining compliance verification and analysis.

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-archive-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-archive-change/SKILL.md
Scanned
2 files, 224 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

This skill allows an AI agent to modify entries within a specific Open Specification Archive. It can be used to update existing records, add new information, or correct inaccuracies found in the archive's data. The skill focuses on targeted changes rather than wholesale replacements of content.

When to use it

  • Correcting errors: If you find an error in an existing specification entry, this skill can fix it directly within the archive.
  • Adding supplemental information: You can add clarifying notes or links to relevant resources for a specific specification.
  • Updating version numbers: When specifications are updated, this skill ensures the archive reflects those changes accurately.
  • Standardizing formatting: Use this to ensure consistency in how entries are presented within the Open Specification Archive.

Key capabilities

  • Modify existing specification records
  • Add new information to specification records
  • Correct inaccuracies in specification data
  • Update version numbers of specifications

Example prompts

  • "Update the 'XYZ Protocol' entry to reflect the latest version 3.2."
  • "Add a link to the official documentation for the 'ABC Standard'."
  • "Correct the typo in the description of the '123 Framework'."

Tips & gotchas

  • Requires familiarity with the structure and content of the Open Specification Archive. Incorrect modifications can impact data integrity.