Skip to content
TrustedSkillsbeta
Back to all skills

Openspec Continue Change

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

This skill continues a spec change operation if it fails midway, ensuring consistency and preventing disruptions in your workflow.

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-continue-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-continue-change/SKILL.md
Scanned
2 files, 252 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-continue-change skill allows an AI agent to continue a process described in an Open Specification (OpenSpec) and then modify that process. It can take existing OpenSpecs, execute them step-by-step, and introduce changes or additions as instructed. This enables iterative refinement of complex procedures directly within the AI agent's workflow.

When to use it

  • Refining automated workflows: You have an existing OpenSpec for a task (e.g., data processing) but need to adjust certain steps based on new requirements or feedback.
  • Debugging and improving processes: An OpenSpec is producing unexpected results, and you want the agent to execute it while making targeted modifications to identify and fix issues.
  • Experimenting with process variations: You want to explore different approaches within an existing OpenSpec without completely rewriting it from scratch.
  • Teaching AI agents new skills incrementally: Build upon existing knowledge by having the agent continue a known process and then add a new, related capability.

Key capabilities

  • Open Specification execution
  • Process continuation
  • Modification of Open Specifications
  • Step-by-step procedural refinement

Example prompts

  • "Continue this OpenSpec for generating marketing copy, but change the tone to be more formal."
  • "Execute this OpenSpec for data cleaning and add a step to remove duplicate entries."
  • “Run this OpenSpec for creating a presentation. After slide 3, insert a new slide with a summary of key findings.”

Tips & gotchas

The skill requires familiarity with Open Specification syntax and structure. Providing clear and specific instructions on the desired changes is crucial for successful modification.