[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78EEJAAK2GZ2FXR8PT6SPSY":3,"skill-same:01M78EEJAAK2GZ2FXR8PT6SPSY":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M78EEJAAK2GZ2FXR8PT6SPSY","npm-release",null,"Releases one @mobrienv\u002Fpi-tidy-* workspace through GitHub and npm Trusted Publishing. Use when asked to prepare changelog entries, cut, publish, or monitor a patch, minor, major, or explicit-version release.","mikeyobrien\u002Fpi-tidy-tools","mikeyobrien","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11792047?v=4","01M78EA4XJ7CY5SB8V7EPB1581","Mikey O'Brien","01M78EA4YD4ECB9199H176CNQY",63,"MIT","https:\u002F\u002Fgithub.com\u002Fmikeyobrien\u002Fpi-tidy-tools\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fnpm-release\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: npm-release\ndescription: Releases one @mobrienv\u002Fpi-tidy-* workspace through GitHub and npm Trusted Publishing. Use when asked to prepare changelog entries, cut, publish, or monitor a patch, minor, major, or explicit-version release.\ncompatibility: Requires Node.js 22.19+, npm, git, GitHub CLI authentication, and push access to mikeyobrien\u002Fpi-tidy-tools.\n---\n\n# npm Release\n\nRelease one workspace through `.github\u002Fworkflows\u002Fpublish.yml`. Every package owns its manifest, version, changelog, and package-qualified tag. Pushing the package-qualified tag triggers tokenless npm Trusted Publishing with provenance; the GitHub Release is the human-readable record.\n\n## Inputs\n\nResolve:\n\n1. Package: `pi-tidy-\u003Cname>` or `@mobrienv\u002Fpi-tidy-\u003Cname>`\n2. Version: `patch`, `minor`, `major`, or an explicit SemVer\n\nIf the package is omitted, infer it only when the repository has exactly one publishable workspace; otherwise ask. Normalize the package to:\n\n```text\nSLUG=pi-tidy-\u003Cname>\nPACKAGE=@mobrienv\u002F$SLUG\nDIR=packages\u002F$SLUG\n```\n\nNormalize `v0.2.0` to `0.2.0`. The release tag is `$SLUG-v\u003CTARGET>`.\n\n## Safety\n\n- Run from the repository root with a clean `main` synchronized to `origin\u002Fmain`.\n- Publish functional releases only through a pushed release tag and `.github\u002Fworkflows\u002Fpublish.yml`. The sole exception is the explicitly approved `0.0.0` first-package bootstrap below; never publish functional package code locally.\n- Use GitHub OIDC. Keep npm tokens absent from prompts, files, output, and workflow configuration.\n- Preserve independent package versions. Update only the selected manifest, its changelog, and the root lockfile.\n- Stop on ambiguous input, failed validation, an existing npm version\u002Ftag\u002Fchangelog heading, or a package with no user-visible changes.\n- Preserve history: annotated tags are immutable; commits are not amended or force-pushed.\n- Changelog entries describe observable behavior, with implementation-only work omitted.\n\n## Changelog contract\n\nThe selected package owns `$DIR\u002FCHANGELOG.md`, using Keep a Changelog 1.1.0 and SemVer:\n\n```markdown\n# Changelog\n\nAll notable changes to this project will be documented in this file.\n\nThe format is based on [Keep a Changelog](https:\u002F\u002Fkeepachangelog.com\u002Fen\u002F1.1.0\u002F),\nand this project adheres to [Semantic Versioning](https:\u002F\u002Fsemver.org\u002Fspec\u002Fv2.0.0.html).\n\n## [Unreleased]\n\n## [X.Y.Z] - YYYY-MM-DD\n\n### Added\n\n- User-visible addition.\n\n[Unreleased]: https:\u002F\u002Fgithub.com\u002Fmikeyobrien\u002Fpi-tidy-tools\u002Fcompare\u002FSLUG-vX.Y.Z...HEAD\n[X.Y.Z]: https:\u002F\u002Fgithub.com\u002Fmikeyobrien\u002Fpi-tidy-tools\u002Fcompare\u002FPREVIOUS_TAG...SLUG-vX.Y.Z\n```\n\nUse sections in this order and omit empty sections: `Added`, `Changed`, `Deprecated`, `Removed`, `Fixed`, `Security`.\n\nEach bullet carries one user-visible change. Put breaking changes first and label them **BREAKING**. Name migration paths for deprecations. Keep internal helpers, tests, refactors, file paths, CI mechanics, and reverted work out of the changelog unless users must act on them. Inspect code changes as the primary source and commits as intent.\n\n## Procedure\n\n### 1. Resolve and preflight\n\nList publishable workspaces and resolve the input before changing files:\n\n```bash\nnpm pkg get name version private --workspaces\ngit status --short\ngit branch --show-current\ngit fetch origin main --tags\ngit rev-list --left-right --count origin\u002Fmain...main\ngh auth status\nnpm view \"$PACKAGE\" version --json\n```\n\nRequire `$DIR\u002Fpackage.json`, package name exactly `$PACKAGE`, an empty working tree, branch `main`, no ahead\u002Fbehind count, and valid GitHub authentication. Treat npm `E404` for the unversioned package lookup as a first-publication signal, not proof that OIDC is ready: npm cannot attach a trusted publisher until the package record exists.\n\nConfirm `.github\u002Fworkflows\u002Fpublish.yml` has `id-token: write`, uses environment `npm`, triggers only on `pi-tidy-*-v*` tag pushes with no alternate functional trigger such as `workflow_dispatch`, pins third-party actions to full commit hashes, disables persisted checkout credentials and `setup-node` package-manager caching, installs the lockfile with `npm ci --ignore-scripts`, resolves release tags to an allowlisted public workspace path, publishes with `--workspace`, and contains no `NODE_AUTH_TOKEN` or `NPM_TOKEN` reference.\n\n### 1a. Bootstrap a new npm package record when required\n\nRun this step only when `npm view \"$PACKAGE\" version --json` returns a genuine registry `E404`. Do not create the target release commit, tag, or GitHub Release first: the OIDC workflow cannot publish a package that does not yet exist.\n\nThis is an irreversible external action and requires the owner's explicit approval. In an isolated temporary directory, prepare a public `0.0.0` placeholder containing only:\n\n- `package.json` with the exact package name, version `0.0.0`, public access, license, description, and repository metadata;\n- a README stating that the artifact is a non-functional Trusted Publishing bootstrap and that functional releases begin at the approved `TARGET`;\n- no package runtime, scripts, dependencies, credentials, or repository checkout files.\n\nInspect `npm pack --dry-run` and the actual tarball before the owner publishes that temporary directory once with interactive npm authentication, 2FA, `--access public`, and `--tag oidc-bootstrap`. The dedicated dist-tag prevents the non-functional placeholder from becoming `latest` while trust is configured. Never substitute the real workspace package or a pre-release functional build for the placeholder.\n\nAfter `npm view \"$PACKAGE@0.0.0\" version --json` succeeds and `npm view \"$PACKAGE\" dist-tags --json` reports `oidc-bootstrap: 0.0.0` with no `latest`, configure the package's npm Trusted Publisher exactly as follows:\n\n```text\nprovider: GitHub Actions\norganization\u002Fuser: mikeyobrien\nrepository: pi-tidy-tools\nworkflow: publish.yml\nenvironment: npm\nallowed action: npm publish\n```\n\nThen require two-factor authentication and disallow ordinary tokens for publishing. Verify the saved publisher fields and package access in npm's settings before continuing. The placeholder gets no repository tag, GitHub Release, or changelog section; it exists only to break npm's first-publish\u002FOIDC dependency cycle. All functional versions still follow the tokenless GitHub process below.\n\n### 2. Determine and guard the target\n\nRead the current version from `$DIR\u002Fpackage.json`. Calculate the requested bump without editing files. An explicit version must be greater than the current version.\n\nFind the latest package-qualified release tag:\n\n```bash\ngit tag --list \"$SLUG-v*\" --sort=-version:refname | head -1\n```\n\nFor `pi-tidy-tools` only, if no package-qualified tag exists, use the latest historical `vX.Y.Z` tag as `PREVIOUS_TAG`. Other packages with no tag are first releases.\n\nSet `TAG=\"$SLUG-v$TARGET\"`, then guard it:\n\n```bash\ngit rev-parse -q --verify \"refs\u002Ftags\u002F$TAG\"\nnpm view \"$PACKAGE@$TARGET\" version --json\n```\n\nBoth must report absence. npm `E404` is expected absence; any other registry error stops the release.\n\n### 3. Analyze package changes\n\nUse the selected package seam:\n\n```bash\ngit diff \"$PREVIOUS_TAG\"..HEAD --stat -- \"$DIR\"\ngit diff \"$PREVIOUS_TAG\"..HEAD -- \"$DIR\"\ngit log \"$PREVIOUS_TAG\"..HEAD --oneline --no-merges -- \"$DIR\"\n```\n\nFor a first release, inspect the package tree and relevant repository history instead of diffing a missing tag. Account for every user-visible change in `$DIR`; shared root changes belong in this changelog only when they alter this package's observable behavior.\n\nComplete this step when every observable change is represented once and implementation-only changes are excluded. Stop on an empty release.\n\n### 4. Prepare metadata\n\nCreate `$DIR\u002FCHANGELOG.md` with the contract if absent. Otherwise preserve released sections and move current Unreleased entries into `## [TARGET] - YYYY-MM-DD`, using the current UTC date. Add missing entries found during diff review without duplication.\n\nUpdate links:\n\n- `[Unreleased]` compares `$TAG...HEAD`.\n- `[TARGET]` compares `$PREVIOUS_TAG...$TAG`.\n- A first release links `[TARGET]` to the repository tree at `$TAG`.\n\nUpdate only the selected version:\n\n```bash\nnpm version \"$TARGET\" --workspace \"$PACKAGE\" --no-git-tag-version\n```\n\nConfirm `$DIR\u002Fpackage.json` and the workspace entry in `package-lock.json` both report `TARGET`.\n\nExtract the new changelog section, excluding `[Unreleased]` and reference links, to `\u002Ftmp\u002F$SLUG-release-v$TARGET.md`. Review it for accuracy and implementation leakage.\n\n### 5. Validate\n\n```bash\nnpm ci\nnpm test\nnpm run check\nnpm pack --workspace \"$PACKAGE\" --dry-run\nnpm pack --workspace \"$PACKAGE\" --dry-run --json\ngit diff --check\ngit status --short\n```\n\nInspect the selected tarball allowlist, package identity, Pi manifest resources, and repository metadata. Confirm one non-empty target changelog section, correct compare links, exact release notes, and no changed package metadata outside the selected workspace except `package-lock.json`.\n\n### 6. Commit and tag\n\nStage only selected release metadata:\n\n```bash\ngit add \"$DIR\u002Fpackage.json\" \"$DIR\u002FCHANGELOG.md\" package-lock.json\ngit commit -m \"chore($SLUG): release v$TARGET\"\ngit tag -a \"$TAG\" -m \"$PACKAGE v$TARGET\"\ngit push origin main --follow-tags\n```\n\nVerify the annotated tag points to the release commit. The tag push starts the publish workflow.\n\n### 7. Monitor the publish run and create the GitHub Release\n\n```bash\ngh release create \"$TAG\" \\\n  --verify-tag \\\n  --notes-file \"\u002Ftmp\u002F$SLUG-release-v$TARGET.md\" \\\n  --title \"$PACKAGE v$TARGET\"\nrm \"\u002Ftmp\u002F$SLUG-release-v$TARGET.md\"\n```\n\nLocate the tag-triggered workflow run whose `headBranch` is `$TAG`, then block until completion:\n\n```bash\ngh run list --workflow publish.yml --event push --limit 10 \\\n  --json databaseId,headBranch,status,conclusion,url\ngh run watch \u003CRUN_ID> --exit-status\n```\n\nOn failure, inspect `gh run view \u003CRUN_ID> --log-failed`. Diagnose before proposing any retry or corrective version.\n\n### 8. Verify publication\n\nAllow for registry propagation, then require all checks to agree:\n\n```bash\nnpm view \"$PACKAGE\" version dist.integrity --json\ngh run view \u003CRUN_ID> --json conclusion,url,headSha\ngh release view \"$TAG\" --json url,tagName\ngit status --short\n```\n\nSuccess means npm reports exactly `TARGET` with non-empty integrity, the workflow succeeded for `$TAG`, the GitHub Release exists, and the working tree is clean.\n\n## Final report\n\nReport the package\u002Fversion, changelog sections, release commit\u002Ftag, GitHub Release URL, workflow URL\u002Fconclusion, validation, npm integrity, and residual risks.\n","# npm Release\n\nRelease one workspace through `.github\u002Fworkflows\u002Fpublish.yml`. Every package owns its manifest, version, changelog, and package-qualified tag. Pushing the package-qualified tag triggers tokenless npm Trusted Publishing with provenance; the GitHub Release is the human-readable record.\n\n## Inputs\n\nResolve:\n\n1. Package: `pi-tidy-\u003Cname>` or `@mobrienv\u002Fpi-tidy-\u003Cname>`\n2. Version: `patch`, `minor`, `major`, or an explicit SemVer\n\nIf the package is omitted, infer it only when the repository has exactly one publishable workspace; otherwise ask. Normalize the package to:\n\n```text\nSLUG=pi-tidy-\u003Cname>\nPACKAGE=@mobrienv\u002F$SLUG\nDIR=packages\u002F$SLUG\n```\n\nNormalize `v0.2.0` to `0.2.0`. The release tag is `$SLUG-v\u003CTARGET>`.\n\n## Safety\n\n- Run from the repository root with a clean `main` synchronized to `origin\u002Fmain`.\n- Publish functional releases only through a pushed release tag and `.github\u002Fworkflows\u002Fpublish.yml`. The sole exception is the explicitly approved `0.0.0` first-package bootstrap below; never publish functional package code locally.\n- Use GitHub OIDC. Keep npm tokens absent from prompts, files, output, and workflow configuration.\n- Preserve independent package versions. Update only the selected manifest, its changelog, and the root lockfile.\n- Stop on ambiguous input, failed validation, an existing npm version\u002Ftag\u002Fchangelog heading, or a package with no user-visible changes.\n- Preserve history: annotated tags are immutable; commits are not amended or force-pushed.\n- Changelog entries describe observable behavior, with implementation-only work omitted.\n\n## Changelog contract\n\nThe selected package owns `$DIR\u002FCHANGELOG.md`, using Keep a Changelog 1.1.0 and SemVer:\n\n```markdown\n# Changelog\n\nAll notable changes to this project will be documented in this file.\n\nThe format is based on [Keep a Changelog](https:\u002F\u002Fkeepachangelog.com\u002Fen\u002F1.1.0\u002F),\nand this project adheres to [Semantic Versioning](https:\u002F\u002Fsemver.org\u002Fspec\u002Fv2.0.0.html).\n\n## [Unreleased]\n\n## [X.Y.Z] - YYYY-MM-DD\n\n### Added\n\n- User-visible addition.\n\n[Unreleased]: https:\u002F\u002Fgithub.com\u002Fmikeyobrien\u002Fpi-tidy-tools\u002Fcompare\u002FSLUG-vX.Y.Z...HEAD\n[X.Y.Z]: https:\u002F\u002Fgithub.com\u002Fmikeyobrien\u002Fpi-tidy-tools\u002Fcompare\u002FPREVIOUS_TAG...SLUG-vX.Y.Z\n```\n\nUse sections in this order and omit empty sections: `Added`, `Changed`, `Deprecated`, `Removed`, `Fixed`, `Security`.\n\nEach bullet carries one user-visible change. Put breaking changes first and label them **BREAKING**. Name migration paths for deprecations. Keep internal helpers, tests, refactors, file paths, CI mechanics, and reverted work out of the changelog unless users must act on them. Inspect code changes as the primary source and commits as intent.\n\n## Procedure\n\n### 1. Resolve and preflight\n\nList publishable workspaces and resolve the input before changing files:\n\n```bash\nnpm pkg get name version private --workspaces\ngit status --short\ngit branch --show-current\ngit fetch origin main --tags\ngit rev-list --left-right --count origin\u002Fmain...main\ngh auth status\nnpm view \"$PACKAGE\" version --json\n```\n\nRequire `$DIR\u002Fpackage.json`, package name exactly `$PACKAGE`, an empty working tree, branch `main`, no ahead\u002Fbehind count, and valid GitHub authentication. Treat npm `E404` for the unversioned package lookup as a first-publication signal, not proof that OIDC is ready: npm cannot attach a trusted publisher until the package record exists.\n\nConfirm `.github\u002Fworkflows\u002Fpublish.yml` has `id-token: write`, uses environment `npm`, triggers only on `pi-tidy-*-v*` tag pushes with no alternate functional trigger such as `workflow_dispatch`, pins third-party actions to full commit hashes, disables persisted checkout credentials and `setup-node` package-manager caching, installs the lockfile with `npm ci --ignore-scripts`, resolves release tags to an allowlisted public workspace path, publishes with `--workspace`, and contains no `NODE_AUTH_TOKEN` or `NPM_TOKEN` reference.\n\n### 1a. Bootstrap a new npm package record when required\n\nRun this step only when `npm view \"$PACKAGE\" version --json` returns a genuine registry `E404`. Do not create the target release commit, tag, or GitHub Release first: the OIDC workflow cannot publish a package that does not yet exist.\n\nThis is an irreversible external action and requires the owner's explicit approval. In an isolated temporary directory, prepare a public `0.0.0` placeholder containing only:\n\n- `package.json` with the exact package name, version `0.0.0`, public access, license, description, and repository metadata;\n- a README stating that the artifact is a non-functional Trusted Publishing bootstrap and that functional releases begin at the approved `TARGET`;\n- no package runtime, scripts, dependencies, credentials, or repository checkout files.\n\nInspect `npm pack --dry-run` and the actual tarball before the owner publishes that temporary directory once with interactive npm authentication, 2FA, `--access public`, and `--tag oidc-bootstrap`. The dedicated dist-tag prevents the non-functional placeholder from becoming `latest` while trust is configured. Never substitute the real workspace package or a pre-release functional build for the placeholder.\n\nAfter `npm view \"$PACKAGE@0.0.0\" version --json` succeeds and `npm view \"$PACKAGE\" dist-tags --json` reports `oidc-bootstrap: 0.0.0` with no `latest`, configure the package's npm Trusted Publisher exactly as follows:\n\n```text\nprovider: GitHub Actions\norganization\u002Fuser: mikeyobrien\nrepository: pi-tidy-tools\nworkflow: publish.yml\nenvironment: npm\nallowed action: npm publish\n```\n\nThen require two-factor authentication and disallow ordinary tokens for publishing. Verify the saved publisher fields and package access in npm's settings before continuing. The placeholder gets no repository tag, GitHub Release, or changelog section; it exists only to break npm's first-publish\u002FOIDC dependency cycle. All functional versions still follow the tokenless GitHub process below.\n\n### 2. Determine and guard the target\n\nRead the current version from `$DIR\u002Fpackage.json`. Calculate the requested bump without editing files. An explicit version must be greater than the current version.\n\nFind the latest package-qualified release tag:\n\n```bash\ngit tag --list \"$SLUG-v*\" --sort=-version:refname | head -1\n```\n\nFor `pi-tidy-tools` only, if no package-qualified tag exists, use the latest historical `vX.Y.Z` tag as `PREVIOUS_TAG`. Other packages with no tag are first releases.\n\nSet `TAG=\"$SLUG-v$TARGET\"`, then guard it:\n\n```bash\ngit rev-parse -q --verify \"refs\u002Ftags\u002F$TAG\"\nnpm view \"$PACKAGE@$TARGET\" version --json\n```\n\nBoth must report absence. npm `E404` is expected absence; any other registry error stops the release.\n\n### 3. Analyze package changes\n\nUse the selected package seam:\n\n```bash\ngit diff \"$PREVIOUS_TAG\"..HEAD --stat -- \"$DIR\"\ngit diff \"$PREVIOUS_TAG\"..HEAD -- \"$DIR\"\ngit log \"$PREVIOUS_TAG\"..HEAD --oneline --no-merges -- \"$DIR\"\n```\n\nFor a first release, inspect the package tree and relevant repository history instead of diffing a missing tag. Account for every user-visible change in `$DIR`; shared root changes belong in this changelog only when they alter this package's observable behavior.\n\nComplete this step when every observable change is represented once and implementation-only changes are excluded. Stop on an empty release.\n\n### 4. Prepare metadata\n\nCreate `$DIR\u002FCHANGELOG.md` with the contract if absent. Otherwise preserve released sections and move current Unreleased entries into `## [TARGET] - YYYY-MM-DD`, using the current UTC date. Add missing entries found during diff review without duplication.\n\nUpdate links:\n\n- `[Unreleased]` compares `$TAG...HEAD`.\n- `[TARGET]` compares `$PREVIOUS_TAG...$TAG`.\n- A first release links `[TARGET]` to the repository tree at `$TAG`.\n\nUpdate only the selected version:\n\n```bash\nnpm version \"$TARGET\" --workspace \"$PACKAGE\" --no-git-tag-version\n```\n\nConfirm `$DIR\u002Fpackage.json` and the workspace entry in `package-lock.json` both report `TARGET`.\n\nExtract the new changelog section, excluding `[Unreleased]` and reference links, to `\u002Ftmp\u002F$SLUG-release-v$TARGET.md`. Review it for accuracy and implementation leakage.\n\n### 5. Validate\n\n```bash\nnpm ci\nnpm test\nnpm run check\nnpm pack --workspace \"$PACKAGE\" --dry-run\nnpm pack --workspace \"$PACKAGE\" --dry-run --json\ngit diff --check\ngit status --short\n```\n\nInspect the selected tarball allowlist, package identity, Pi manifest resources, and repository metadata. Confirm one non-empty target changelog section, correct compare links, exact release notes, and no changed package metadata outside the selected workspace except `package-lock.json`.\n\n### 6. Commit and tag\n\nStage only selected release metadata:\n\n```bash\ngit add \"$DIR\u002Fpackage.json\" \"$DIR\u002FCHANGELOG.md\" package-lock.json\ngit commit -m \"chore($SLUG): release v$TARGET\"\ngit tag -a \"$TAG\" -m \"$PACKAGE v$TARGET\"\ngit push origin main --follow-tags\n```\n\nVerify the annotated tag points to the release commit. The tag push starts the publish workflow.\n\n### 7. Monitor the publish run and create the GitHub Release\n\n```bash\ngh release create \"$TAG\" \\\n  --verify-tag \\\n  --notes-file \"\u002Ftmp\u002F$SLUG-release-v$TARGET.md\" \\\n  --title \"$PACKAGE v$TARGET\"\nrm \"\u002Ftmp\u002F$SLUG-release-v$TARGET.md\"\n```\n\nLocate the tag-triggered workflow run whose `headBranch` is `$TAG`, then block until completion:\n\n```bash\ngh run list --workflow publish.yml --event push --limit 10 \\\n  --json databaseId,headBranch,status,conclusion,url\ngh run watch \u003CRUN_ID> --exit-status\n```\n\nOn failure, inspect `gh run view \u003CRUN_ID> --log-failed`. Diagnose before proposing any retry or corrective version.\n\n### 8. Verify publication\n\nAllow for registry propagation, then require all checks to agree:\n\n```bash\nnpm view \"$PACKAGE\" version dist.integrity --json\ngh run view \u003CRUN_ID> --json conclusion,url,headSha\ngh release view \"$TAG\" --json url,tagName\ngit status --short\n```\n\nSuccess means npm reports exactly `TARGET` with non-empty integrity, the workflow succeeded for `$TAG`, the GitHub Release exists, and the working tree is clean.\n\n## Final report\n\nReport the package\u002Fversion, changelog sections, release commit\u002Ftag, GitHub Release URL, workflow URL\u002Fconclusion, validation, npm integrity, and residual risks.\n",{"name":5,"description":7,"compatibility":24},"Requires Node.js 22.19+, npm, git, GitHub CLI authentication, and push access to mikeyobrien\u002Fpi-tidy-tools.","main","b253d1504091e48e3d60ebab19535bf0d1cec363",".pi\u002Fskills\u002Fnpm-release",3,"https:\u002F\u002Fgithub.com\u002Fmikeyobrien\u002Fpi-tidy-tools","https:\u002F\u002Fgithub.com\u002Fmikeyobrien","mobrienv.dev","Sr. SDE @ Amazon. Austin, TX. AI Enthusiast. \r\n","2026-10-13 08:29:57",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add mikeyobrien\u002Fpi-tidy-tools --skill npm-release",{"tool":40,"command":41},"bunx","bunx skills add mikeyobrien\u002Fpi-tidy-tools --skill npm-release",{"tool":43,"command":44},"pnpm","pnpm dlx skills add mikeyobrien\u002Fpi-tidy-tools --skill npm-release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmikeyobrien\u002Fpi-tidy-tools\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fnpm-release\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M78EEXKEADXTNBVN3096T211","pi-tidy-bots-cli","Drive the pi-tidy-bots fleet runtime from an agent — init, daemonized start, status, stop, hot bot onboarding, and the HTTP+WS machine API (messages, transcripts, compaction, question cards) — all non-interactive with checked exit codes and --json shapes.","https:\u002F\u002Fgithub.com\u002Fmikeyobrien\u002Fpi-tidy-tools\u002Fblob\u002Fmain\u002Fskills\u002Fpi-tidy-bots-cli\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M78EES9YE4WYNC6NJZNZD628","qa-loop","Run a human-gated QA and repair loop for pi-tidy-tools.","https:\u002F\u002Fgithub.com\u002Fmikeyobrien\u002Fpi-tidy-tools\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fqa-loop\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M78EEP74RPPZYAZYEJRJ2DXK","pi-tidy-tools-ethos","Narrative guardrails for @mobrienv\u002Fpi-tidy-tools. Use when designing, implementing, reviewing, or documenting non-release changes to that package.","https:\u002F\u002Fgithub.com\u002Fmikeyobrien\u002Fpi-tidy-tools\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fpi-tidy-tools-ethos\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M78EEEWYRACQEPDPC039DEK0","build-loop","Build and independently verify one ready implementation ticket through a human-gated repair loop.","https:\u002F\u002Fgithub.com\u002Fmikeyobrien\u002Fpi-tidy-tools\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fbuild-loop\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M78EEA9XNRCCR1SKEFSPXPTC","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Fmikeyobrien\u002Fpi-tidy-tools\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M78EE7FYS5EH3K5ETM10BBVZ","unslop","Cut AI tells from any writing. Must always apply.","https:\u002F\u002Fgithub.com\u002Fmikeyobrien\u002Fpi-tidy-tools\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funslop\u002FSKILL.md",[],[]]