Skip to content
TrustedSkillsbeta
Back to all skills

Openspec Bulk Archive Change

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

This skill efficiently modifies multiple OpenSpec archives simultaneously, saving significant time and effort compared to individual updates.

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-bulk-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-bulk-archive-change/SKILL.md
Scanned
2 files, 454 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 you to make bulk changes to archived Open Specification documents. It can modify metadata, update document status, and perform other administrative tasks on a collection of archived specifications. This is useful for maintaining consistency and accuracy within a large archive of open standards documents.

When to use it

  • You need to update the status (e.g., "draft," "approved") of multiple archived Open Specification documents at once.
  • You want to change metadata like author or publication date across several specifications in your archive.
  • You are correcting errors or inconsistencies in a batch of previously archived documents.
  • You need to apply a standardized naming convention to a set of archived files.

Key capabilities

  • Bulk modification of Open Specification document metadata
  • Updating the status of archived documents
  • Administrative changes to archived specifications

Example prompts

  • "Change the status of all archived documents with 'draft' status to 'review'."
  • "Update the author field for all specifications authored by 'John Doe' to 'J. Doe'."
  • “Archive these 10 Open Specification files and set their publication date to today’s date.”

Tips & gotchas

This skill requires access to an archive of Open Specification documents and appropriate permissions to modify them. Incorrect usage could lead to unintended changes within the archive, so carefully review any proposed modifications before execution.