Build Teaql App
teaql/teaql-agent-kit
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries.
9 パッケージ × 5 レジストリの version bump と関連ファイル更新 (Cargo.lock / package-lock.json / Swift checksum / CHANGELOG 昇格) を 1 コマンドで適用案にする read-mostly skill。release-prep (確認用) の続きに呼び、 実 bump 差分の markdown 提案 + 順序付き…
$ npx skills add ayutaz/piper-plus --skill prepare-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ayutaz/piper-plus prepare-release --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ayutaz/piper-plus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/prepare-release .claude/skills/prepare-release && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "prepare-release" agent skill from https://github.com/ayutaz/piper-plus/tree/dev/.claude/skills/prepare-release into .claude/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-release", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ayutaz/piper-plus/tree/dev/.claude/skills/prepare-releaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ayutaz/piper-plus --skill prepare-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ayutaz/piper-plus prepare-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ayutaz/piper-plus.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/prepare-release .agents/skills/prepare-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "prepare-release" agent skill from https://github.com/ayutaz/piper-plus/tree/dev/.claude/skills/prepare-release into .agents/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-release", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ayutaz/piper-plus --skill prepare-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ayutaz/piper-plus prepare-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ayutaz/piper-plus.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/prepare-release .cursor/skills/prepare-release && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "prepare-release" agent skill from https://github.com/ayutaz/piper-plus/tree/dev/.claude/skills/prepare-release into .cursor/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-release", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ayutaz/piper-plus.git --path .claude/skills/prepare-release--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ayutaz/piper-plus --skill prepare-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ayutaz/piper-plus prepare-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ayutaz/piper-plus.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/prepare-release .gemini/skills/prepare-release && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "prepare-release" agent skill from https://github.com/ayutaz/piper-plus/tree/dev/.claude/skills/prepare-release into .gemini/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-release", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ayutaz/piper-plus prepare-releaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ayutaz/piper-plus --skill prepare-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ayutaz/piper-plus.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/prepare-release .github/skills/prepare-release && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "prepare-release" agent skill from https://github.com/ayutaz/piper-plus/tree/dev/.claude/skills/prepare-release into .github/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-release", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ayutaz/piper-plus --skill prepare-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ayutaz/piper-plus prepare-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ayutaz/piper-plus.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/prepare-release .opencode/skills/prepare-release && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "prepare-release" agent skill from https://github.com/ayutaz/piper-plus/tree/dev/.claude/skills/prepare-release into .opencode/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-release", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
prepare-release9 パッケージ × 5 レジストリの version bump と関連ファイル更新 (Cargo.lock / package-lock.json / Swift checksum / CHANGELOG 昇格) を 1 コマンドで適用案にする read-mostly skill。release-prep (確認用) の続きに呼び、 実 bump 差分の markdown 提案 + 順序付き…
Prepare Release is an agent skill from ayutaz/piper-plus. 9 パッケージ × 5 レジストリの version bump と関連ファイル更新 (Cargo.lock / package-lock.json / Swift checksum / CHANGELOG 昇格) を 1 コマンドで適用案にする read-mostly skill。release-prep (確認用) の続きに呼び、 実 bump 差分の markdown 提案 + 順序付き publish ガイドを生成する。
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering iOS development, Changelog and release notes and Markdown. It works with npm, Rust, C# and Python. The repository describes itself as: Multilingual neural TTS (6 languages: JA/EN/ZH/ES/FR/PT, code supports SV) — C++, C, Rust, Go, Python, npm (WASM). VITS + Prosody, streaming, CUDA/CoreML/DirectML. pip install…. The licence is MIT.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 9c6946e. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
Bash(cat *)Bash(grep *)Bash(jq *)Bash(rg *)Bash(awk *)Bash(curl -s *)Bash(npm view *)Bash(git diff *)Bash(git log *)Bash(git status *)…and 4 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
uvnpmghcurljqswiftgitcargoFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
pypi.orgcrates.ioapi.nuget.orgsearch.maven.orgFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Prepare Release loads about 2k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 575 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from ayutaz/piper-plus at commit 9c6946e, republished under its MIT licence (© ayutaz). 575 words, ~1,966 tokens.
.claude/skills/prepare-release/SKILL.md (or your agent's skills folder).release-prep (read-mostly な確認) の続きとして、 実際の version bump 差分 を全 manifest にわたり生成する skill。
ユーザは memory feedback_conservative_changes.md / feedback_merge_caution.md に従い、 適用は明示確認を取ってから (デフォルト dry-run、 markdown diff 提示のみ)。
| 段階 | 対応 |
|---|---|
| Version 散在検出 | 9 manifest を一括 bump 案として markdown 出力 |
| Lockfile 再生成 | uv.lock / Cargo.lock / package-lock.json の更新コマンド提示 |
| Swift checksum | xcframework artifact 取得後の swift package compute-checksum 手順 |
| CHANGELOG 昇格 | [Unreleased] → [X.Y.Z] - YYYY-MM-DD の markdown diff |
| Tag 順序ガイド | npm tag (g2p 先行) / shared-lib tag / 内部 chain tag の順序 |
| 公開後検証 | 各 registry で publish 完了確認の手順 |
$ARGUMENTS 1 つ目: all / python / rust / csharp / npm / swift / kotlin--target-version X.Y.Z: 次回リリース version (必須)--dry-run (default): markdown 出力のみ、 ファイル変更しない--apply: dry-run の確認後にユーザが追加で渡す flag。 これがある時のみ Edit を実行git rev-parse --abbrev-ref HEADgit tag --sort=-v:refname | head -3並列で Read し、 各 manifest の現 version を抽出:
| Runtime | Manifest | 抽出キー |
|---|---|---|
| Python | VERSION | ファイル全体 |
| Python (g2p) | src/python/g2p/pyproject.toml | [project].version |
| Rust | src/rust/Cargo.toml | [workspace.package].version |
| C# Core | src/csharp/PiperPlus.Core/PiperPlus.Core.csproj | <Version> |
| C# Cli | src/csharp/PiperPlus.Cli/PiperPlus.Cli.csproj | <Version> |
| npm synth | src/wasm/openjtalk-web/package.json | .version |
| npm g2p | src/wasm/g2p/package.json | .version |
| Swift | Package.swift | let version = 行 + let g2pVersion = 行 |
| Kotlin | android/gradle.properties | VERSION_NAME= |
uv run python scripts/check_voice_catalog_parity.py 2>&1 | tail -3
uv run python scripts/check_ort_versions.py 2>&1 | tail -3
uv run python scripts/check_openjtalk_version_sync.py 2>&1 | tail -3
uv run python scripts/check_ruff_version_sync.py 2>&1 | tail -3
uv run python scripts/check_migration_changelog_parity.py 2>&1 | tail -3drift があれば bump 前に修復するよう警告。
--target-version を基準に、 該当 runtime の manifest 全てに対する diff を markdown 出力:
出力例 (markdown):
VERSION): 1.12.0 → 2.0.0src/rust/Cargo.toml [workspace.package].version): 0.4.0 → 0.5.0src/wasm/openjtalk-web/package.json): 0.6.0 → 0.7.0all の場合は 9 manifest 全てを順次出力する。
# Python
uv lock --upgrade-package piper-plus
# Rust
(cd src/rust && cargo update -p piper-plus)
# npm synth
(cd src/wasm/openjtalk-web && npm install --package-lock-only)
# npm g2p
(cd src/wasm/g2p && npm install --package-lock-only)--apply 時は順次実行、 そうでなければコマンドのみ表示。
Package.swift の checksum / g2pChecksum は tag commit に存在していなければならない (SwiftPM は tag の git ref の manifest を解決し、checksum 不一致なら artifact has changed checksum で fail。release-shared-lib.yml の release job も tag push 時に placeholder / 不一致を hard-fail させる)。よって tag push 前 に実施する (gh release download は release がまだ無いので使えない):
# 1. release-shared-lib.yml を tag 無しで workflow_dispatch 実行し artifact を生成
gh workflow run release-shared-lib.yml --ref dev
# 完了後、run の workflow artifact を取得 (release ではない)
gh run download <run-id> --name libpiper_plus-ios-xcframework
# g2pChecksum は g2pVersion が今回 tag と一致する時のみ取得・更新
gh run download <run-id> --name libpiper_plus_g2p-apple-xcframework
# 2. swift package compute-checksum (workflow artifact のファイル名は version 無し)
swift package compute-checksum libpiper_plus-ios.xcframework.zip
swift package compute-checksum libpiper_plus_g2p-apple.xcframework.zip # g2pVersion == TARGET のみ
# 3. Package.swift の `let checksum` (synthesis) を更新。
# `let g2pChecksum` は g2pVersion が今回 tag と一致する時のみ更新
# (異なる場合 release-shared-lib.yml が g2p checksum 検証を自動 skip する)。
# 4. dev に commit し、その commit に v<TARGET_VERSION> tag を push (フェーズ 7 の順序)workflow_dispatch build と tag build は deterministic なので checksum は一致する。この手順は tag push の直前 (フェーズ 7)。 dry-run でも手順を出力する。
awk '/^## \[Unreleased\]/{flag=1; next} /^## /{flag=0} flag' CHANGELOG.mdを抽出し、 以下を提案:
## [<TARGET_VERSION>] - <YYYY-MM-DD>
(Unreleased から移動した内容)
## [Unreleased]
(空 or next-version 着手項目)--apply で直接 Edit、 そうでなければ diff のみ出力。
CONTRIBUTING.md の規約に従い、 tag push 順序を明示:
wasm-g2p-v<X.Y.Z> (npm @piper-plus/g2p) — g2p に変更が無く既公開なら skipnpm-v<X.Y.Z> (npm piper-plus、 g2p に依存)dev-create-release.yml を workflow_dispatch (version 入力) で実行
→ PyPI / crates.io / NuGet を sleep 30 入りで連鎖 publish。 tag 駆動ではない (Actions UI から手動実行)kotlin-g2p-v<X.Y.Z> (Maven Central、 独立) — 既公開なら skipchecksum を pre-tag 更新 (フェーズ 5 の workflow_dispatch artifact から compute-checksum → dev に commit)v<X.Y.Z> tag を push → release-shared-lib.yml (libpiper_plus + iOS/Android xcframework)重要 (フェーズ 5 参照): Swift checksum 更新は
v<X.Y.Z>tag の 前 (ステップ 5)。 placeholder のまま tag を push すると release-shared-lib.yml の release job が hard-fail し、 post-tag の後追い PR では SwiftPM 解決を救済できない (tag の git ref が解決対象のため)。順序逆転による npm install 失敗 (g2p が無いと
piper-plusinstall fail) も防ぐ。v<X.Y.Z>tag は release-shared-lib.yml と docker-build.yml を同時発火させ、 Docker image (<X.Y.Z>/latest) も自動 publish される点に留意。
# 各 registry で publish 完了を確認
curl -s https://pypi.org/pypi/piper-plus/json | jq -r '.info.version'
curl -s https://crates.io/api/v1/crates/piper-plus | jq -r '.crate.max_version'
npm view piper-plus version
npm view @piper-plus/g2p version
curl -s "https://api.nuget.org/v3-flatcontainer/piperplus.core/index.json" | jq -r '.versions[-1]'
curl -s "https://search.maven.org/solrsearch/select?q=g:io.github.ayutaz+AND+a:piper-plus-g2p-android&rows=1&wt=json" | jq -r '.response.docs[0].latestVersion'target version と一致するまで sleep 30 で polling、 30 分以内に揃わなければエラー報告。
release-prep は「現状の version 散在確認」、 本 skill は「次回 version へ bump する適用案生成」。 先に release-prep で drift を解消してから本 skill を使う流れが推奨。--dry-run がデフォルト で、 --apply は明示指定が必要。# 全 runtime の v2.0.0 リリース bump 案を生成 (dry-run)
/prepare-release all --target-version 2.0.0
# Python だけ確定、 適用
/prepare-release python --target-version 2.0.0 --apply
# Rust 0.5.0 リリース、 lockfile 再生成手順のみ表示
/prepare-release rust --target-version 0.5.0[Unreleased] 昇格 の規定化 (現状: 手動 markdown 編集)© ayutaz, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/prepare-release of ayutaz/piper-plus.
Open the folder on GitHubat commit 9c6946e
Prepare Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Prepare Release this skillayutaz/piper-plus | 220 | — | ~2k | Automated safety check: Pass | MIT | |
| Build Teaql Appteaql/teaql-agent-kit | 2.8k | — | ~4.6k | Automated safety check: Pass | MIT | |
| Fory Performance Optimizationapache/fory | 4.6k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| MCP SDK Tier Auditmodelcontextprotocol/conformance | 129 | — | ~4.4k | Automated safety check: Pass | Custom licence | |
| Dbgtheodo-group/debug-that | 158 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Code Revieweralirezarezvani/claude-skills | 28k | 1 repos | ~1.6k | Automated safety check: Pass | MIT |
teaql/teaql-agent-kit
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries.
apache/fory
Run profile-driven bottleneck optimization across Apache Fory implementations (Java, C++, Python/Cython, Go, Rust, Swift, C, JavaScript/TypeScript, Dart, Kotlin, Scala).
modelcontextprotocol/conformance
Comprehensive tier assessment for an MCP SDK repository against SEP-1730.
theodo-group/debug-that
Debug applications using the dbg CLI debugger. An agent skill from theodo-group/debug-that.
alirezarezvani/claude-skills
Code review automation for TypeScript, JavaScript, Python, Go, Swift, Kotlin, C, .NET, Java, C, C++, Rust, Ruby, PHP, and Dart/Flutter.
nexmoe/eve
Universal release workflow. An agent skill from nexmoe/eve.
ayutaz/piper-plus
.claude/skills//SKILL.md の frontmatter / referenced script 実在 / trigger 衝突 / .claude/hooks/.sh の executable+shebang を検査する meta-skill。
ayutaz/piper-plus
ORT / openjtalk / ruff のような cross-runtime に canonical sync が必要な依存関係を 1 コマンドで bump する read-mostly skill。
ayutaz/piper-plus
Python canonical (src/pythonrun/piperplus/, src/python/pipertrain/, src/python/g2p/piperplusg2p/) を変更した PR で、 ONNX I/O 以外の追随漏れ (phonemizer / config schema / CLI flag / data 形式 / API 変更) を 7 ランタイム +…
ayutaz/piper-plus
ZH-EN code-switching loanword の同期と forward-compat を 1 コマンドで検査。zhenloanword.json を編集したり 5 ランタイムのいずれかに新規エントリを追加する前後に呼ぶ。Python source を canonical とし、Rust×2 / Go / C / WASM / C++ の 6 mirror + Python…
ayutaz/piper-plus
新規データアセット (JSON/TOML) を追加した PR で「7 箇所の package metadata 更新が全て揃っているか」を 1 コマンドで確認。MANIFEST.in / pyproject package-data / Cargo features / npm files / C Content / Android assets / SPM resources の更新漏れを…
ayutaz/piper-plus
PR 作成前の最終チェックリスト (lint/test/docs/CHANGELOG/未コミット確認)。/precheck の拡張版で、ドキュメント整合性も検証します。
Works with
Categories
9 パッケージ × 5 レジストリの version bump と関連ファイル更新 (Cargo.lock / package-lock.json / Swift checksum / CHANGELOG 昇格) を 1 コマンドで適用案にする read-mostly skill。release-prep (確認用) の続きに呼び、 実 bump 差分の markdown 提案 + 順序付き…. Prepare Release is an agent skill from ayutaz/piper-plus.
Prepare Release fits situations like: tasks that involve iOS development; tasks that involve Changelog and release notes; tasks that involve Markdown.
Run `npx skills add ayutaz/piper-plus --skill prepare-release -a claude-code`. Or copy the skill folder (.claude/skills/prepare-release in ayutaz/piper-plus) into .claude/skills/prepare-release in your project. Claude Code loads it when a task matches its description.
Run `npx skills add ayutaz/piper-plus --skill prepare-release -a codex`. Or copy the skill folder (.claude/skills/prepare-release in ayutaz/piper-plus) into .agents/skills/prepare-release in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ayutaz/piper-plus --skill prepare-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prepare-release, .gemini/skills/prepare-release, .github/skills/prepare-release and .opencode/skills/prepare-release in your project.
Going by SKILL.md and its folder, Prepare Release needs the command-line tools its instructions call (uv, npm, gh, curl, jq and swift). Our summary lists: Python 3; Node.js; Docker. Its frontmatter pre-approves these tools: Bash(cat *), Bash(grep *), Bash(jq *), Bash(rg *), Bash(awk *), Bash(curl -s *), Bash(npm view *), Bash(git diff *), Bash(git log *), Bash(git status *), Bash(swift package compute-checksum *), Read, Edit, Grep.
SKILL.md names 4 domains. In commands or code: pypi.org, crates.io, api.nuget.org and search.maven.org; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Prepare Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Prepare Release: Build Teaql App (teaql/teaql-agent-kit, 2.8k stars), Fory Performance Optimization (apache/fory, 4.6k stars), MCP SDK Tier Audit (modelcontextprotocol/conformance, 129 stars) and Dbg (theodo-group/debug-that, 158 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
ayutaz (a GitHub user) maintains it in ayutaz/piper-plus, which has 220 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 8, 2026.
Source: ayutaz/piper-plus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.