[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79BA7XC7DB5WZMBJ9N4KT2Z":3,"skill-same:01M79BA7XC7DB5WZMBJ9N4KT2Z":52},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M79BA7XC7DB5WZMBJ9N4KT2Z","ship-ipa-package",null,"Prepare and verify npm releases of ipa-tools or ipa-prompt-api-fallback in inference-provider-api. Use for shipping a named package, preparing a version bump, or checking publication and its demo update. Questions about whether a release is needed call for advice, not publication.","SamSamskies\u002Finference-provider-api","SamSamskies","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3655410?v=4","01M79BA31BJFFFNX0KV8NS0CAC","Sam Samskies","01M79BA32CE4FQF4P08Z9CG7S3",8,"MIT","https:\u002F\u002Fgithub.com\u002FSamSamskies\u002Finference-provider-api\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fship-ipa-package\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ship-ipa-package\ndescription: >-\n  Prepare and verify npm releases of ipa-tools or ipa-prompt-api-fallback in\n  inference-provider-api. Use for shipping a named package, preparing a version\n  bump, or checking publication and its demo update. Questions about whether a\n  release is needed call for advice, not publication.\n---\n\n# Ship an IPA package\n\nRelease only the package selected by the user. If the target is ambiguous, ask\nwhich package; never default to releasing both. Keep their versions independent.\nUse the current repository files and registry metadata rather than remembered\nversions or a previous release's commands.\n\n| Package | Workspace | Versioned documentation and demo imports |\n| --- | --- | --- |\n| `ipa-tools` | `packages\u002Fipa-tools` | Its README and matching `ipa-tools@` imports in `examples\u002F**` |\n| `ipa-prompt-api-fallback` | `packages\u002Fipa-prompt-api-fallback` | Its README and the `ipa-prompt-api-fallback@` import in `examples\u002Fprompt-api-fallback\u002Findex.html` |\n\n## Prepare and verify\n\n1. Work on an authorized feature or release branch based on current `main`,\n   preserving unrelated user changes. Read the selected package's manifest,\n   changelog, scripts, and changes since its published version. A request to\n   prepare or bump a version does not itself authorize publishing it.\n2. Check `npm view PACKAGE versions --json` and its dist-tags. Keep the current\n   manifest version for a first publish if it is appropriate and unpublished;\n   otherwise choose a SemVer bump from the published version. Use patch for\n   compatible fixes, minor for compatible additions, and major for breaking\n   changes. The spec's draft status does not reset package versioning. A failed\n   registry lookup is not proof that a version is unpublished.\n3. Update the selected manifest and root lockfile together. For example,\n   `npm version VERSION --workspace PACKAGE --no-git-tag-version --ignore-scripts`.\n   Move applicable notes from `[Unreleased]` into a version section dated with\n   today's UTC date, retaining an empty `[Unreleased]` section for future work.\n   A prepared changelog entry is separate from confirmed npm publication.\n4. Review the documentation and demo pins listed above. Update pins intended to\n   demonstrate this release; leave historical migration notes and unrelated\n   package pins intact. Keep the other package's version unchanged. Change a\n   fallback peer requirement only when compatibility actually requires it.\n5. Use the root manifest's supported Node version and run `npm test` from the\n   repository root. It builds both workspaces before running tests and TypeScript\n   checks, avoiding stale local peer output. Resolve failures before publishing.\n6. Pack the selected workspace into a temporary directory with\n   `npm pack --workspace PACKAGE --pack-destination TEMP_DIR`. Inspect the packed\n   version, exports, and files, then exercise the changed behavior using the\n   packed artifact. For the fallback, verify it with a published `ipa-tools`\n   version satisfying its peer range, rather than relying only on the local\n   workspace. Do not silently raise the peer requirement to make the check pass.\n7. Run `git diff --check` and review the release diff. Follow the task's Git\n   authorization for commits, pushes, and PRs. Keep a release PR in draft while\n   its demo imports point to an unpublished or unavailable version. Create or\n   push a release tag only when the user asks.\n\nReplace `PACKAGE`, `VERSION`, and `TEMP_DIR` with concrete values. Give the user\npaste-ready commands for the selected workspace, not unresolved placeholders.\n\n## Publish with the selected package's rules\n\n- **`ipa-tools`:** Preserve its existing user-publishes policy. The agent must not\n  run `npm login` or `npm publish` for this package. After preparation and checks,\n  give the user commands to enter `packages\u002Fipa-tools`, run `npm login`, and run\n  `npm publish`; wait for their response. Explain this skill requirement when\n  handing off the publish step. If they request a publish dry-run, they run it.\n- **`ipa-prompt-api-fallback`:** When publishing is part of the user's request,\n  the agent may attempt one publish of the verified release. If npm requires\n  interactive authentication (`EOTP`, `ENEEDAUTH`, or an authentication error),\n  stop retrying and give the user the workspace-specific `npm publish` command;\n  include `npm login` only if sign-in is needed. Do not automate login or bypass\n  two-factor authentication. Preparation-only requests stop before publication.\n\nNever read or print `~\u002F.npmrc` or auth tokens, or use `npm whoami` as a release\ngate. Report name, ownership, or version conflicts without renaming a package or\nchanging access automatically. Do not run a publish dry-run unless requested.\n\n## Confirm publication and finish the demo update\n\n1. After a successful publish or the user says they published, query the exact\n   version with\n   `npm view PACKAGE@VERSION version dist.tarball dist.shasum --json --prefer-online`\n   and check the intended dist-tag. Do not rely on `latest` alone.\n2. npm may report that an upload is processing before the version becomes\n   readable. Keep any release PR in draft and retry read-only checks at 30-60 second\n   intervals for up to five minutes. If still unavailable, report publication\n   as pending and leave any release PR draft. Do not republish, bump again, or treat\n   processing as an authentication failure.\n3. Verify the registry artifact matches the tested release. For changed CDN\n   pins, fetch the exact entry URL and its resolved JavaScript and peer imports;\n   a working wrapper alone does not prove the demo module is available.\n4. Once the version and all changed CDN imports resolve, update any release PR\n   to describe the released version and validation, remove obsolete pending-auth\n   notes, and mark it ready. Leave merging to the user's authorized Git\n   workflow. After the user reports a merge, check deployment status and the\n   import actually served by the live demo.\n5. Report the package and published version, install command, registry link,\n   PR\u002Fdemo status, and any remaining user action. Distinguish pending publication\n   from a release confirmed available on npm.\n","# Ship an IPA package\n\nRelease only the package selected by the user. If the target is ambiguous, ask\nwhich package; never default to releasing both. Keep their versions independent.\nUse the current repository files and registry metadata rather than remembered\nversions or a previous release's commands.\n\n| Package | Workspace | Versioned documentation and demo imports |\n| --- | --- | --- |\n| `ipa-tools` | `packages\u002Fipa-tools` | Its README and matching `ipa-tools@` imports in `examples\u002F**` |\n| `ipa-prompt-api-fallback` | `packages\u002Fipa-prompt-api-fallback` | Its README and the `ipa-prompt-api-fallback@` import in `examples\u002Fprompt-api-fallback\u002Findex.html` |\n\n## Prepare and verify\n\n1. Work on an authorized feature or release branch based on current `main`,\n   preserving unrelated user changes. Read the selected package's manifest,\n   changelog, scripts, and changes since its published version. A request to\n   prepare or bump a version does not itself authorize publishing it.\n2. Check `npm view PACKAGE versions --json` and its dist-tags. Keep the current\n   manifest version for a first publish if it is appropriate and unpublished;\n   otherwise choose a SemVer bump from the published version. Use patch for\n   compatible fixes, minor for compatible additions, and major for breaking\n   changes. The spec's draft status does not reset package versioning. A failed\n   registry lookup is not proof that a version is unpublished.\n3. Update the selected manifest and root lockfile together. For example,\n   `npm version VERSION --workspace PACKAGE --no-git-tag-version --ignore-scripts`.\n   Move applicable notes from `[Unreleased]` into a version section dated with\n   today's UTC date, retaining an empty `[Unreleased]` section for future work.\n   A prepared changelog entry is separate from confirmed npm publication.\n4. Review the documentation and demo pins listed above. Update pins intended to\n   demonstrate this release; leave historical migration notes and unrelated\n   package pins intact. Keep the other package's version unchanged. Change a\n   fallback peer requirement only when compatibility actually requires it.\n5. Use the root manifest's supported Node version and run `npm test` from the\n   repository root. It builds both workspaces before running tests and TypeScript\n   checks, avoiding stale local peer output. Resolve failures before publishing.\n6. Pack the selected workspace into a temporary directory with\n   `npm pack --workspace PACKAGE --pack-destination TEMP_DIR`. Inspect the packed\n   version, exports, and files, then exercise the changed behavior using the\n   packed artifact. For the fallback, verify it with a published `ipa-tools`\n   version satisfying its peer range, rather than relying only on the local\n   workspace. Do not silently raise the peer requirement to make the check pass.\n7. Run `git diff --check` and review the release diff. Follow the task's Git\n   authorization for commits, pushes, and PRs. Keep a release PR in draft while\n   its demo imports point to an unpublished or unavailable version. Create or\n   push a release tag only when the user asks.\n\nReplace `PACKAGE`, `VERSION`, and `TEMP_DIR` with concrete values. Give the user\npaste-ready commands for the selected workspace, not unresolved placeholders.\n\n## Publish with the selected package's rules\n\n- **`ipa-tools`:** Preserve its existing user-publishes policy. The agent must not\n  run `npm login` or `npm publish` for this package. After preparation and checks,\n  give the user commands to enter `packages\u002Fipa-tools`, run `npm login`, and run\n  `npm publish`; wait for their response. Explain this skill requirement when\n  handing off the publish step. If they request a publish dry-run, they run it.\n- **`ipa-prompt-api-fallback`:** When publishing is part of the user's request,\n  the agent may attempt one publish of the verified release. If npm requires\n  interactive authentication (`EOTP`, `ENEEDAUTH`, or an authentication error),\n  stop retrying and give the user the workspace-specific `npm publish` command;\n  include `npm login` only if sign-in is needed. Do not automate login or bypass\n  two-factor authentication. Preparation-only requests stop before publication.\n\nNever read or print `~\u002F.npmrc` or auth tokens, or use `npm whoami` as a release\ngate. Report name, ownership, or version conflicts without renaming a package or\nchanging access automatically. Do not run a publish dry-run unless requested.\n\n## Confirm publication and finish the demo update\n\n1. After a successful publish or the user says they published, query the exact\n   version with\n   `npm view PACKAGE@VERSION version dist.tarball dist.shasum --json --prefer-online`\n   and check the intended dist-tag. Do not rely on `latest` alone.\n2. npm may report that an upload is processing before the version becomes\n   readable. Keep any release PR in draft and retry read-only checks at 30-60 second\n   intervals for up to five minutes. If still unavailable, report publication\n   as pending and leave any release PR draft. Do not republish, bump again, or treat\n   processing as an authentication failure.\n3. Verify the registry artifact matches the tested release. For changed CDN\n   pins, fetch the exact entry URL and its resolved JavaScript and peer imports;\n   a working wrapper alone does not prove the demo module is available.\n4. Once the version and all changed CDN imports resolve, update any release PR\n   to describe the released version and validation, remove obsolete pending-auth\n   notes, and mark it ready. Leave merging to the user's authorized Git\n   workflow. After the user reports a merge, check deployment status and the\n   import actually served by the live demo.\n5. Report the package and published version, install command, registry link,\n   PR\u002Fdemo status, and any remaining user action. Distinguish pending publication\n   from a release confirmed available on npm.\n",{"name":5,"description":7},"main","66008805fb0fd5e62a437d45ce98e8b7d0f164ec",".agents\u002Fskills\u002Fship-ipa-package",1,"https:\u002F\u002Fgithub.com\u002FSamSamskies\u002Finference-provider-api","https:\u002F\u002Fgithub.com\u002FSamSamskies","Hey. Hey. Hey! This is library 😂","2026-11-12 11:32:34",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add SamSamskies\u002Finference-provider-api --skill ship-ipa-package",{"tool":38,"command":39},"bunx","bunx skills add SamSamskies\u002Finference-provider-api --skill ship-ipa-package",{"tool":41,"command":42},"pnpm","pnpm dlx skills add SamSamskies\u002Finference-provider-api --skill ship-ipa-package","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSamSamskies\u002Finference-provider-api\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fship-ipa-package\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",250,"https:\u002F\u002Fgithub.com\u002FSamSamskies\u002Finference-provider-api\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fship-ipa-package\u002Fagents\u002Fopenai.yaml",[53,60,66],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M79BAFCSMSRG6AT7GGGAYB2H","build-with-ipa","Build or adapt browser apps to use the Inference Provider API (IPA, window.inference) for user-approved AI inference. Use for IPA chat, tools, hosted search, images, or bounded speech in an app. Not for implementing a browser extension or other IPA provider.","https:\u002F\u002Fgithub.com\u002FSamSamskies\u002Finference-provider-api\u002Fblob\u002Fmain\u002Fskills\u002Fbuild-with-ipa\u002FSKILL.md",[],[],{"skillNo":61,"name":5,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79BAC37XW9C6NSJ1RBC07TG","Prepare and verify npm releases of ipa-tools or ipa-prompt-api-fallback in this repository.","https:\u002F\u002Fgithub.com\u002FSamSamskies\u002Finference-provider-api\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fship-ipa-package\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79BA4NRRXAT6TRE55AMQQ43","create-demo-og","Create or update matching Open Graph preview cards and social metadata for demo apps in the inference-provider-api repository. Use when adding an OG image or share preview to a demo under examples\u002F, or refreshing one of these demo cards.","https:\u002F\u002Fgithub.com\u002FSamSamskies\u002Finference-provider-api\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcreate-demo-og\u002FSKILL.md",[],[]]