Is release-libs safe to install?

SaferSkills independently audited release-libs (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

.claude/skills/release-libs/SKILL.md · 1 file

.claude/skills/release-libs/SKILL.md2.4 KB · Markdown

name: release-libs

description: Release a new version of the tapo (Rust) and tapo-py (Python) crates together, sharing the same version number

Release tapo & tapo-py

Release a new version of the tapo (Rust) and tapo-py (Python) crates. Both libraries are released simultaneously and share the same version number.

Steps

Determine the new version. Read the current version from tapo/Cargo.toml. Ask the user what the new version should be if not provided.

Bump the versions. Update the version field in both:

tapo/Cargo.toml
tapo-py/pyproject.toml

Update changelog. In CHANGELOG.md:

Replace the heading ## [Python Unreleased][Unreleased] with ## [Python vX.X.X][vX.X.X] - YYYY-MM-DD (use the current date).
Replace the heading ## [Rust Unreleased][Unreleased] with ## [Rust vX.X.X][vX.X.X] - YYYY-MM-DD (use the current date).
Insert new empty ## [Rust Unreleased][Unreleased] and ## [Python Unreleased][Unreleased] sections (in that order) immediately above the newly versioned Rust section.
If a ## [MCP Unreleased][Unreleased] section exists elsewhere in the file, move it (with its body intact) so it sits immediately after the new ## [Python Unreleased][Unreleased] section, keeping all three Unreleased sections grouped at the top in the order Rust → Python → MCP.
Add a link reference [vX.X.X]: https://github.com/mihai-dinculescu/tapo/tree/vX.X.X to the link definitions at the bottom of the file (right after the [Unreleased] link).

Commit. Run /commit with message chore(tapo): release vX.X.X.

Tag. Create an annotated git tag:

   git tag -a vX.X.X -m "vX.X.X"

Push. Ask the user for confirmation, then:

   git push && git push origin vX.X.X

Create GitHub release. Ask the user for confirmation. Use the content under the ## [Rust vX.X.X][vX.X.X] and ## [Python vX.X.X][vX.X.X] headings from CHANGELOG.md as the release body, followed by a full changelog comparison link. The previous version (vP.P.P) is the tag before this release:

   gh release create vX.X.X --title "Tapo vX.X.X" --notes "$(cat <<'EOF'
   ## Rust

   <rust changelog content here>

   ## Python

   <python changelog content here>

   **Full Changelog**: https://github.com/mihai-dinculescu/tapo/compare/vP.P.P...vX.X.X
   EOF
   )"

release-libs— agent skill

Is release-libs safe to install?

Release tapo & tapo-py

Steps

Audit the pieces. Scan the whole. Decide.