specrate

Name: specrate
Author: rickygao

Checked

rickygao·v1.0.0·writing·Apache-2.0

Skill to manage specs and changes. Use this when working with specrate-managed documents.

Install on your platform

Showing OpenClaw.

1
Run this in your terminal
terminal
```
$ 
```

What we know about this skill

Publisher

rickygao

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 5 Oct 2026

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 rickygao/specrate at c3512338e1.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: c3512338e1
Manifest: SKILL.md
Scanned: 17 files, 480 lines

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 manages specifications (specs) and associated change requests within a system that utilizes SpecRate for document control. It allows users to create, track, and update specifications while ensuring proper versioning and audit trails of any modifications made. The skill facilitates collaboration around specs by providing tools for requesting changes and managing their approval process.

When to use it

Reviewing an existing specification document for accuracy and completeness before a product launch.
Submitting a change request to update a spec due to newly discovered requirements or design flaws.
Tracking the status of a pending change request, including approvals and comments.
Auditing changes made to a specification over time to understand its evolution.

Key capabilities

Creation of new specifications within SpecRate-managed documents.
Submission of change requests related to existing specifications.
Tracking the status (e.g., pending, approved, rejected) of change requests.
Management and versioning of specification documents.

Example prompts

"Create a new spec for the 'Widget X' component."
"Submit a change request to update section 3.2 of the 'System Architecture' specification."
"Show me the status of change request #12789."

Tips & gotchas

This skill is specifically designed for use with documents managed by SpecRate. It will not function correctly outside of that environment and requires access to a SpecRate instance.