Skip to content
TrustedSkillsbeta
Back to all skills

Openspec Ff Change

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

This skill modifies OpenSpec FF files to alter network configurations, streamlining changes and ensuring accurate device settings.

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-ff-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-ff-change/SKILL.md
Scanned
2 files, 192 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, openspec-ff-change, allows AI agents to modify existing Open Specification (OpenSpec) files. Specifically, it can change values within these files and apply those changes. It's designed to facilitate experimentation and iterative development of specifications by enabling easy adjustments to parameters and configurations.

When to use it

  • Experimenting with OpenSpec Parameters: Quickly test different parameter settings in an existing OpenSpec configuration to observe their impact on a system.
  • Iterative Specification Development: Modify and refine OpenSpec files during the development process, allowing for rapid prototyping and adjustments.
  • Debugging and Troubleshooting: Adjust values within an OpenSpec file to isolate and resolve issues related to specific configurations or parameters.
  • Automated Configuration Updates: Potentially integrate with automated workflows to update OpenSpec files based on predefined rules or data inputs.

Key capabilities

  • Modifies existing Open Specification (OpenSpec) files.
  • Changes values within OpenSpec files.
  • Applies the changes made to the file.

Example prompts

  • "Change the 'temperature' value in openspec.yaml to 0.7."
  • "Update the 'max_tokens' parameter in my_openspec.json to 512."
  • "Set the 'learning_rate' field in openspec-config.yml to 0.001 and apply the changes."

Tips & gotchas

  • Ensure you have a valid OpenSpec file as input for the skill to operate on. The format (YAML, JSON) must be correctly identified.