agentic-skill-mill 1.0.8 → 1.0.10

package/compiled/claude/agentic-skill-mill/SKILL.md

@@ -45,6 +45,8 @@ Skills (what to do)          CLI Companion (tools to do it with)
 - `src/errors/types.ts` — Typed error hierarchy (AppError, NotFoundError, etc.)
 - `src/cache/cache-manager.ts` — Two-tier cache (memory + disk) with TTL
 
+**Local installers:** Every project ships `install.sh` (bash) and `install.ps1` (PowerShell). Both support the same flags and produce identical installed state.
+
 **The local installer** (`install-local.sh`) builds the CLI, compiles skills, and copies compiled outputs to IDE-specific directories (~/.claude/skills, ~/.cursor/rules, etc.) with marker-based stale file cleanup. The bootstrap installer is hosted at `https://agenticskillmill.com/install.sh` (source: `site/install.sh`) and is also bundled in the npm package as `install.sh`. It installs the npm utility first, then delegates to `install-local.sh --skills-only`. Local installer functions use `set -e` for fail-fast behavior. Any function that uses an early-exit guard (`[[ -d ... ]] || return`, `[[ -z ... ]] && return`) **must** use `return 0`, never bare `return`. Bare `return` inherits the exit code of the last command, which for a failed conditional test is 1 -- and `set -e` treats that as a script-terminating failure with no error message.
 
 ### Key files to modify when augmenting a project
@@ -54,7 +56,7 @@ Skills (what to do)          CLI Companion (tools to do it with)
 | Add a CLI command | `src/core/<name>.ts`, `src/cli/commands/<name>.ts`, `src/cli/index.ts`, `src/index.ts` |
 | Add a fragment | `skill/fragments/<category>/<name>.md`, `skill/build/manifest.json`, skill source |
 | Add a skill | `skill/skills/<name>/<name>.md`, `skill/build/manifest.json`, `install-local.sh` SKILLS array |
-| Change installer behavior | `install.sh` (repo root) then copy to `site/install.sh` |
+| Change installer behavior | `install.sh` and `install.ps1` (repo root), then copy bootstraps to `site/` |
 | Update the landing page | `site/index.html`, `site/style.css` |
 | Change CI secrets or workflow | `.github/workflows/release.yml` or `deploy-pages.yml`, repo settings |
 | Rename the project | See the rename workflow |
@@ -65,11 +67,16 @@ Skills (what to do)          CLI Companion (tools to do it with)
 
 ### Distribution model
 
-The project is published to npmjs as a public package and hosted at `https://agenticskillmill.com`. There are three ways users consume it:
+The project is published to npmjs as a public package and hosted at `https://agenticskillmill.com`.
+
+**Remote install (no clone):** Every project hosts `site/install.sh` and `site/install.ps1` bootstrap scripts served via GitHub Pages. Non-npm projects use a clone-to-temp pattern instead of `npm install -g`.
+
+There are multiple ways users consume it:
 
 | Method | Command | Who uses it |
 |--------|---------|-------------|
-| Remote install (no clone) | `bash <(curl -fsSL https://agenticskillmill.com/install.sh) --all` | End users who want skills installed into their IDE tools |
+| Remote install (bash) | `bash <(curl -fsSL https://<domain>/install.sh)` | End users on Linux/macOS |
+| Remote install (PowerShell) | `irm https://<domain>/install.ps1 \| iex` | End users on Windows |
 | npx (no install) | `npx --yes agentic-skill-mill@latest <command>` | Users running CLI commands without global install |
 | Local development | `git clone` then `bash install-local.sh --all` | Contributors working on the project itself |
 
@@ -128,8 +135,9 @@ Static site served via GitHub Pages at `https://agenticskillmill.com`:
 | `site/index.html` | Landing page with architecture, CLI commands, and install instructions |
 | `site/style.css` | Site styles |
 | `site/install.sh` | Bootstrap installer served at `https://agenticskillmill.com/install.sh` |
+| `site/install.ps1` | PowerShell bootstrap installer served at `https://agenticskillmill.com/install.ps1` |
 
-When updating the bootstrap installer logic, edit `install.sh` at the repo root and copy it to `site/install.sh` to keep both in sync. The release workflow publishes the repo-root copy to npm; the Pages workflow serves the site copy to the domain.
+When updating the bootstrap installer logic, edit `install.sh` and `install.ps1` at the repo root and copy them to `site/install.sh` and `site/install.ps1` to keep both in sync. The release workflow publishes the repo-root copies to npm; the Pages workflow serves the site copies to the domain.
 
 ### Modifying distribution touchpoints
 
@@ -137,7 +145,7 @@ When updating the bootstrap installer logic, edit `install.sh` at the repo root
 |--------|----------------|
 | Add a new skill | `install-local.sh` SKILLS array, `skill/build/manifest.json` |
 | Change package name | `package.json` name + bin, `install.sh` default, `site/install.sh` default, `install-local.sh` PROJECT_NAME + CLI_BIN_NAME + MANAGED_MARKER, `site/index.html`, README |
-| Change bootstrap behavior | `install.sh` (repo root), then copy to `site/install.sh` |
+| Change bootstrap behavior | `install.sh` and `install.ps1` (repo root), then copy to `site/install.sh` and `site/install.ps1` |
 | Add a GitHub Actions secret | Repo settings, document in README |
 | Update domain | `site/CNAME`, README, skill source, architecture fragment |
 
@@ -504,6 +512,35 @@ Use conventional commit format with a detailed body:
 
 The commit body should list every file category changed (core modules, CLI wrappers, fragments, manifest, etc.) and what was done in each.
 
+### Cross-Artifact Skill Signature
+
+When updating or creating a skill, embed a deterministic signature in each externally searchable artifact so operators can query everything produced by that specific skill across systems.
+
+Derive the signature per skill name:
+
+- Compute `sha256("<skill-name>")`
+- Use the first 8 lowercase hex characters
+- Format as `skill-sig: <sig8>`
+
+For a given skill name, the value is permanently static across all versions.
+
+Example:
+
+- `sha256("3pp-skill")` -> `ad61853a...`
+- signature value: `skill-sig: ad61853a`
+
+### Artifact Embedding Rules
+
+- **Commit message body**: append a git trailer after a blank line: `Skill-Sig: <sig8>`
+- **PR markdown doc**: append `<sub>skill-sig: <sig8></sub>` after the `## Notes` section
+- **GUS HTML details**: append `<p style="font-size:0.8em;color:#888">skill-sig: <sig8></p>` before closing `</body></html>`
+
+### Searchability Targets
+
+- Git: `git log --grep="skill-sig: <sig8>"`
+- GitHub: search for `"skill-sig: <sig8>"`
+- GUS SOQL: `WHERE Details__c LIKE '%skill-sig: <sig8>%'`
+
 ---
 
 ## Anti-Patterns

package/compiled/codex/agentic-skill-mill/SKILL.md

@@ -45,6 +45,8 @@ Skills (what to do)          CLI Companion (tools to do it with)
 - `src/errors/types.ts` — Typed error hierarchy (AppError, NotFoundError, etc.)
 - `src/cache/cache-manager.ts` — Two-tier cache (memory + disk) with TTL
 
+**Local installers:** Every project ships `install.sh` (bash) and `install.ps1` (PowerShell). Both support the same flags and produce identical installed state.
+
 **The local installer** (`install-local.sh`) builds the CLI, compiles skills, and copies compiled outputs to IDE-specific directories (~/.claude/skills, ~/.cursor/rules, etc.) with marker-based stale file cleanup. The bootstrap installer is hosted at `https://agenticskillmill.com/install.sh` (source: `site/install.sh`) and is also bundled in the npm package as `install.sh`. It installs the npm utility first, then delegates to `install-local.sh --skills-only`. Local installer functions use `set -e` for fail-fast behavior. Any function that uses an early-exit guard (`[[ -d ... ]] || return`, `[[ -z ... ]] && return`) **must** use `return 0`, never bare `return`. Bare `return` inherits the exit code of the last command, which for a failed conditional test is 1 -- and `set -e` treats that as a script-terminating failure with no error message.
 
 ### Key files to modify when augmenting a project
@@ -54,7 +56,7 @@ Skills (what to do)          CLI Companion (tools to do it with)
 | Add a CLI command | `src/core/<name>.ts`, `src/cli/commands/<name>.ts`, `src/cli/index.ts`, `src/index.ts` |
 | Add a fragment | `skill/fragments/<category>/<name>.md`, `skill/build/manifest.json`, skill source |
 | Add a skill | `skill/skills/<name>/<name>.md`, `skill/build/manifest.json`, `install-local.sh` SKILLS array |
-| Change installer behavior | `install.sh` (repo root) then copy to `site/install.sh` |
+| Change installer behavior | `install.sh` and `install.ps1` (repo root), then copy bootstraps to `site/` |
 | Update the landing page | `site/index.html`, `site/style.css` |
 | Change CI secrets or workflow | `.github/workflows/release.yml` or `deploy-pages.yml`, repo settings |
 | Rename the project | See the rename workflow |
@@ -65,11 +67,16 @@ Skills (what to do)          CLI Companion (tools to do it with)
 
 ### Distribution model
 
-The project is published to npmjs as a public package and hosted at `https://agenticskillmill.com`. There are three ways users consume it:
+The project is published to npmjs as a public package and hosted at `https://agenticskillmill.com`.
+
+**Remote install (no clone):** Every project hosts `site/install.sh` and `site/install.ps1` bootstrap scripts served via GitHub Pages. Non-npm projects use a clone-to-temp pattern instead of `npm install -g`.
+
+There are multiple ways users consume it:
 
 | Method | Command | Who uses it |
 |--------|---------|-------------|
-| Remote install (no clone) | `bash <(curl -fsSL https://agenticskillmill.com/install.sh) --all` | End users who want skills installed into their IDE tools |
+| Remote install (bash) | `bash <(curl -fsSL https://<domain>/install.sh)` | End users on Linux/macOS |
+| Remote install (PowerShell) | `irm https://<domain>/install.ps1 \| iex` | End users on Windows |
 | npx (no install) | `npx --yes agentic-skill-mill@latest <command>` | Users running CLI commands without global install |
 | Local development | `git clone` then `bash install-local.sh --all` | Contributors working on the project itself |
 
@@ -128,8 +135,9 @@ Static site served via GitHub Pages at `https://agenticskillmill.com`:
 | `site/index.html` | Landing page with architecture, CLI commands, and install instructions |
 | `site/style.css` | Site styles |
 | `site/install.sh` | Bootstrap installer served at `https://agenticskillmill.com/install.sh` |
+| `site/install.ps1` | PowerShell bootstrap installer served at `https://agenticskillmill.com/install.ps1` |
 
-When updating the bootstrap installer logic, edit `install.sh` at the repo root and copy it to `site/install.sh` to keep both in sync. The release workflow publishes the repo-root copy to npm; the Pages workflow serves the site copy to the domain.
+When updating the bootstrap installer logic, edit `install.sh` and `install.ps1` at the repo root and copy them to `site/install.sh` and `site/install.ps1` to keep both in sync. The release workflow publishes the repo-root copies to npm; the Pages workflow serves the site copies to the domain.
 
 ### Modifying distribution touchpoints
 
@@ -137,7 +145,7 @@ When updating the bootstrap installer logic, edit `install.sh` at the repo root
 |--------|----------------|
 | Add a new skill | `install-local.sh` SKILLS array, `skill/build/manifest.json` |
 | Change package name | `package.json` name + bin, `install.sh` default, `site/install.sh` default, `install-local.sh` PROJECT_NAME + CLI_BIN_NAME + MANAGED_MARKER, `site/index.html`, README |
-| Change bootstrap behavior | `install.sh` (repo root), then copy to `site/install.sh` |
+| Change bootstrap behavior | `install.sh` and `install.ps1` (repo root), then copy to `site/install.sh` and `site/install.ps1` |
 | Add a GitHub Actions secret | Repo settings, document in README |
 | Update domain | `site/CNAME`, README, skill source, architecture fragment |
 
@@ -504,6 +512,35 @@ Use conventional commit format with a detailed body:
 
 The commit body should list every file category changed (core modules, CLI wrappers, fragments, manifest, etc.) and what was done in each.
 
+### Cross-Artifact Skill Signature
+
+When updating or creating a skill, embed a deterministic signature in each externally searchable artifact so operators can query everything produced by that specific skill across systems.
+
+Derive the signature per skill name:
+
+- Compute `sha256("<skill-name>")`
+- Use the first 8 lowercase hex characters
+- Format as `skill-sig: <sig8>`
+
+For a given skill name, the value is permanently static across all versions.
+
+Example:
+
+- `sha256("3pp-skill")` -> `ad61853a...`
+- signature value: `skill-sig: ad61853a`
+
+### Artifact Embedding Rules
+
+- **Commit message body**: append a git trailer after a blank line: `Skill-Sig: <sig8>`
+- **PR markdown doc**: append `<sub>skill-sig: <sig8></sub>` after the `## Notes` section
+- **GUS HTML details**: append `<p style="font-size:0.8em;color:#888">skill-sig: <sig8></p>` before closing `</body></html>`
+
+### Searchability Targets
+
+- Git: `git log --grep="skill-sig: <sig8>"`
+- GitHub: search for `"skill-sig: <sig8>"`
+- GUS SOQL: `WHERE Details__c LIKE '%skill-sig: <sig8>%'`
+
 ---
 
 ## Anti-Patterns

package/compiled/cursor/rules/agentic-skill-mill.mdc

@@ -45,6 +45,8 @@ Skills (what to do)          CLI Companion (tools to do it with)
 - `src/errors/types.ts` — Typed error hierarchy (AppError, NotFoundError, etc.)
 - `src/cache/cache-manager.ts` — Two-tier cache (memory + disk) with TTL
 
+**Local installers:** Every project ships `install.sh` (bash) and `install.ps1` (PowerShell). Both support the same flags and produce identical installed state.
+
 **The local installer** (`install-local.sh`) builds the CLI, compiles skills, and copies compiled outputs to IDE-specific directories (~/.claude/skills, ~/.cursor/rules, etc.) with marker-based stale file cleanup. The bootstrap installer is hosted at `https://agenticskillmill.com/install.sh` (source: `site/install.sh`) and is also bundled in the npm package as `install.sh`. It installs the npm utility first, then delegates to `install-local.sh --skills-only`. Local installer functions use `set -e` for fail-fast behavior. Any function that uses an early-exit guard (`[[ -d ... ]] || return`, `[[ -z ... ]] && return`) **must** use `return 0`, never bare `return`. Bare `return` inherits the exit code of the last command, which for a failed conditional test is 1 -- and `set -e` treats that as a script-terminating failure with no error message.
 
 ### Key files to modify when augmenting a project
@@ -54,7 +56,7 @@ Skills (what to do)          CLI Companion (tools to do it with)
 | Add a CLI command | `src/core/<name>.ts`, `src/cli/commands/<name>.ts`, `src/cli/index.ts`, `src/index.ts` |
 | Add a fragment | `skill/fragments/<category>/<name>.md`, `skill/build/manifest.json`, skill source |
 | Add a skill | `skill/skills/<name>/<name>.md`, `skill/build/manifest.json`, `install-local.sh` SKILLS array |
-| Change installer behavior | `install.sh` (repo root) then copy to `site/install.sh` |
+| Change installer behavior | `install.sh` and `install.ps1` (repo root), then copy bootstraps to `site/` |
 | Update the landing page | `site/index.html`, `site/style.css` |
 | Change CI secrets or workflow | `.github/workflows/release.yml` or `deploy-pages.yml`, repo settings |
 | Rename the project | See the rename workflow |
@@ -65,11 +67,16 @@ Skills (what to do)          CLI Companion (tools to do it with)
 
 ### Distribution model
 
-The project is published to npmjs as a public package and hosted at `https://agenticskillmill.com`. There are three ways users consume it:
+The project is published to npmjs as a public package and hosted at `https://agenticskillmill.com`.
+
+**Remote install (no clone):** Every project hosts `site/install.sh` and `site/install.ps1` bootstrap scripts served via GitHub Pages. Non-npm projects use a clone-to-temp pattern instead of `npm install -g`.
+
+There are multiple ways users consume it:
 
 | Method | Command | Who uses it |
 |--------|---------|-------------|
-| Remote install (no clone) | `bash <(curl -fsSL https://agenticskillmill.com/install.sh) --all` | End users who want skills installed into their IDE tools |
+| Remote install (bash) | `bash <(curl -fsSL https://<domain>/install.sh)` | End users on Linux/macOS |
+| Remote install (PowerShell) | `irm https://<domain>/install.ps1 \| iex` | End users on Windows |
 | npx (no install) | `npx --yes agentic-skill-mill@latest <command>` | Users running CLI commands without global install |
 | Local development | `git clone` then `bash install-local.sh --all` | Contributors working on the project itself |
 
@@ -128,8 +135,9 @@ Static site served via GitHub Pages at `https://agenticskillmill.com`:
 | `site/index.html` | Landing page with architecture, CLI commands, and install instructions |
 | `site/style.css` | Site styles |
 | `site/install.sh` | Bootstrap installer served at `https://agenticskillmill.com/install.sh` |
+| `site/install.ps1` | PowerShell bootstrap installer served at `https://agenticskillmill.com/install.ps1` |
 
-When updating the bootstrap installer logic, edit `install.sh` at the repo root and copy it to `site/install.sh` to keep both in sync. The release workflow publishes the repo-root copy to npm; the Pages workflow serves the site copy to the domain.
+When updating the bootstrap installer logic, edit `install.sh` and `install.ps1` at the repo root and copy them to `site/install.sh` and `site/install.ps1` to keep both in sync. The release workflow publishes the repo-root copies to npm; the Pages workflow serves the site copies to the domain.
 
 ### Modifying distribution touchpoints
 
@@ -137,7 +145,7 @@ When updating the bootstrap installer logic, edit `install.sh` at the repo root
 |--------|----------------|
 | Add a new skill | `install-local.sh` SKILLS array, `skill/build/manifest.json` |
 | Change package name | `package.json` name + bin, `install.sh` default, `site/install.sh` default, `install-local.sh` PROJECT_NAME + CLI_BIN_NAME + MANAGED_MARKER, `site/index.html`, README |
-| Change bootstrap behavior | `install.sh` (repo root), then copy to `site/install.sh` |
+| Change bootstrap behavior | `install.sh` and `install.ps1` (repo root), then copy to `site/install.sh` and `site/install.ps1` |
 | Add a GitHub Actions secret | Repo settings, document in README |
 | Update domain | `site/CNAME`, README, skill source, architecture fragment |
 
@@ -504,6 +512,35 @@ Use conventional commit format with a detailed body:
 
 The commit body should list every file category changed (core modules, CLI wrappers, fragments, manifest, etc.) and what was done in each.
 
+### Cross-Artifact Skill Signature
+
+When updating or creating a skill, embed a deterministic signature in each externally searchable artifact so operators can query everything produced by that specific skill across systems.
+
+Derive the signature per skill name:
+
+- Compute `sha256("<skill-name>")`
+- Use the first 8 lowercase hex characters
+- Format as `skill-sig: <sig8>`
+
+For a given skill name, the value is permanently static across all versions.
+
+Example:
+
+- `sha256("3pp-skill")` -> `ad61853a...`
+- signature value: `skill-sig: ad61853a`
+
+### Artifact Embedding Rules
+
+- **Commit message body**: append a git trailer after a blank line: `Skill-Sig: <sig8>`
+- **PR markdown doc**: append `<sub>skill-sig: <sig8></sub>` after the `## Notes` section
+- **GUS HTML details**: append `<p style="font-size:0.8em;color:#888">skill-sig: <sig8></p>` before closing `</body></html>`
+
+### Searchability Targets
+
+- Git: `git log --grep="skill-sig: <sig8>"`
+- GitHub: search for `"skill-sig: <sig8>"`
+- GUS SOQL: `WHERE Details__c LIKE '%skill-sig: <sig8>%'`
+
 ---
 
 ## Anti-Patterns

package/compiled/cursor/skills/agentic-skill-mill/SKILL.md

@@ -45,6 +45,8 @@ Skills (what to do)          CLI Companion (tools to do it with)
 - `src/errors/types.ts` — Typed error hierarchy (AppError, NotFoundError, etc.)
 - `src/cache/cache-manager.ts` — Two-tier cache (memory + disk) with TTL
 
+**Local installers:** Every project ships `install.sh` (bash) and `install.ps1` (PowerShell). Both support the same flags and produce identical installed state.
+
 **The local installer** (`install-local.sh`) builds the CLI, compiles skills, and copies compiled outputs to IDE-specific directories (~/.claude/skills, ~/.cursor/rules, etc.) with marker-based stale file cleanup. The bootstrap installer is hosted at `https://agenticskillmill.com/install.sh` (source: `site/install.sh`) and is also bundled in the npm package as `install.sh`. It installs the npm utility first, then delegates to `install-local.sh --skills-only`. Local installer functions use `set -e` for fail-fast behavior. Any function that uses an early-exit guard (`[[ -d ... ]] || return`, `[[ -z ... ]] && return`) **must** use `return 0`, never bare `return`. Bare `return` inherits the exit code of the last command, which for a failed conditional test is 1 -- and `set -e` treats that as a script-terminating failure with no error message.
 
 ### Key files to modify when augmenting a project
@@ -54,7 +56,7 @@ Skills (what to do)          CLI Companion (tools to do it with)
 | Add a CLI command | `src/core/<name>.ts`, `src/cli/commands/<name>.ts`, `src/cli/index.ts`, `src/index.ts` |
 | Add a fragment | `skill/fragments/<category>/<name>.md`, `skill/build/manifest.json`, skill source |
 | Add a skill | `skill/skills/<name>/<name>.md`, `skill/build/manifest.json`, `install-local.sh` SKILLS array |
-| Change installer behavior | `install.sh` (repo root) then copy to `site/install.sh` |
+| Change installer behavior | `install.sh` and `install.ps1` (repo root), then copy bootstraps to `site/` |
 | Update the landing page | `site/index.html`, `site/style.css` |
 | Change CI secrets or workflow | `.github/workflows/release.yml` or `deploy-pages.yml`, repo settings |
 | Rename the project | See the rename workflow |
@@ -65,11 +67,16 @@ Skills (what to do)          CLI Companion (tools to do it with)
 
 ### Distribution model
 
-The project is published to npmjs as a public package and hosted at `https://agenticskillmill.com`. There are three ways users consume it:
+The project is published to npmjs as a public package and hosted at `https://agenticskillmill.com`.
+
+**Remote install (no clone):** Every project hosts `site/install.sh` and `site/install.ps1` bootstrap scripts served via GitHub Pages. Non-npm projects use a clone-to-temp pattern instead of `npm install -g`.
+
+There are multiple ways users consume it:
 
 | Method | Command | Who uses it |
 |--------|---------|-------------|
-| Remote install (no clone) | `bash <(curl -fsSL https://agenticskillmill.com/install.sh) --all` | End users who want skills installed into their IDE tools |
+| Remote install (bash) | `bash <(curl -fsSL https://<domain>/install.sh)` | End users on Linux/macOS |
+| Remote install (PowerShell) | `irm https://<domain>/install.ps1 \| iex` | End users on Windows |
 | npx (no install) | `npx --yes agentic-skill-mill@latest <command>` | Users running CLI commands without global install |
 | Local development | `git clone` then `bash install-local.sh --all` | Contributors working on the project itself |
 
@@ -128,8 +135,9 @@ Static site served via GitHub Pages at `https://agenticskillmill.com`:
 | `site/index.html` | Landing page with architecture, CLI commands, and install instructions |
 | `site/style.css` | Site styles |
 | `site/install.sh` | Bootstrap installer served at `https://agenticskillmill.com/install.sh` |
+| `site/install.ps1` | PowerShell bootstrap installer served at `https://agenticskillmill.com/install.ps1` |
 
-When updating the bootstrap installer logic, edit `install.sh` at the repo root and copy it to `site/install.sh` to keep both in sync. The release workflow publishes the repo-root copy to npm; the Pages workflow serves the site copy to the domain.
+When updating the bootstrap installer logic, edit `install.sh` and `install.ps1` at the repo root and copy them to `site/install.sh` and `site/install.ps1` to keep both in sync. The release workflow publishes the repo-root copies to npm; the Pages workflow serves the site copies to the domain.
 
 ### Modifying distribution touchpoints
 
@@ -137,7 +145,7 @@ When updating the bootstrap installer logic, edit `install.sh` at the repo root
 |--------|----------------|
 | Add a new skill | `install-local.sh` SKILLS array, `skill/build/manifest.json` |
 | Change package name | `package.json` name + bin, `install.sh` default, `site/install.sh` default, `install-local.sh` PROJECT_NAME + CLI_BIN_NAME + MANAGED_MARKER, `site/index.html`, README |
-| Change bootstrap behavior | `install.sh` (repo root), then copy to `site/install.sh` |
+| Change bootstrap behavior | `install.sh` and `install.ps1` (repo root), then copy to `site/install.sh` and `site/install.ps1` |
 | Add a GitHub Actions secret | Repo settings, document in README |
 | Update domain | `site/CNAME`, README, skill source, architecture fragment |
 
@@ -504,6 +512,35 @@ Use conventional commit format with a detailed body:
 
 The commit body should list every file category changed (core modules, CLI wrappers, fragments, manifest, etc.) and what was done in each.
 
+### Cross-Artifact Skill Signature
+
+When updating or creating a skill, embed a deterministic signature in each externally searchable artifact so operators can query everything produced by that specific skill across systems.
+
+Derive the signature per skill name:
+
+- Compute `sha256("<skill-name>")`
+- Use the first 8 lowercase hex characters
+- Format as `skill-sig: <sig8>`
+
+For a given skill name, the value is permanently static across all versions.
+
+Example:
+
+- `sha256("3pp-skill")` -> `ad61853a...`
+- signature value: `skill-sig: ad61853a`
+
+### Artifact Embedding Rules
+
+- **Commit message body**: append a git trailer after a blank line: `Skill-Sig: <sig8>`
+- **PR markdown doc**: append `<sub>skill-sig: <sig8></sub>` after the `## Notes` section
+- **GUS HTML details**: append `<p style="font-size:0.8em;color:#888">skill-sig: <sig8></p>` before closing `</body></html>`
+
+### Searchability Targets
+
+- Git: `git log --grep="skill-sig: <sig8>"`
+- GitHub: search for `"skill-sig: <sig8>"`
+- GUS SOQL: `WHERE Details__c LIKE '%skill-sig: <sig8>%'`
+
 ---
 
 ## Anti-Patterns

package/compiled/opencode/agentic-skill-mill.md

@@ -49,6 +49,8 @@ Skills (what to do)          CLI Companion (tools to do it with)
 - `src/errors/types.ts` — Typed error hierarchy (AppError, NotFoundError, etc.)
 - `src/cache/cache-manager.ts` — Two-tier cache (memory + disk) with TTL
 
+**Local installers:** Every project ships `install.sh` (bash) and `install.ps1` (PowerShell). Both support the same flags and produce identical installed state.
+
 **The local installer** (`install-local.sh`) builds the CLI, compiles skills, and copies compiled outputs to IDE-specific directories (~/.claude/skills, ~/.cursor/rules, etc.) with marker-based stale file cleanup. The bootstrap installer is hosted at `https://agenticskillmill.com/install.sh` (source: `site/install.sh`) and is also bundled in the npm package as `install.sh`. It installs the npm utility first, then delegates to `install-local.sh --skills-only`. Local installer functions use `set -e` for fail-fast behavior. Any function that uses an early-exit guard (`[[ -d ... ]] || return`, `[[ -z ... ]] && return`) **must** use `return 0`, never bare `return`. Bare `return` inherits the exit code of the last command, which for a failed conditional test is 1 -- and `set -e` treats that as a script-terminating failure with no error message.
 
 ### Key files to modify when augmenting a project
@@ -58,7 +60,7 @@ Skills (what to do)          CLI Companion (tools to do it with)
 | Add a CLI command | `src/core/<name>.ts`, `src/cli/commands/<name>.ts`, `src/cli/index.ts`, `src/index.ts` |
 | Add a fragment | `skill/fragments/<category>/<name>.md`, `skill/build/manifest.json`, skill source |
 | Add a skill | `skill/skills/<name>/<name>.md`, `skill/build/manifest.json`, `install-local.sh` SKILLS array |
-| Change installer behavior | `install.sh` (repo root) then copy to `site/install.sh` |
+| Change installer behavior | `install.sh` and `install.ps1` (repo root), then copy bootstraps to `site/` |
 | Update the landing page | `site/index.html`, `site/style.css` |
 | Change CI secrets or workflow | `.github/workflows/release.yml` or `deploy-pages.yml`, repo settings |
 | Rename the project | See the rename workflow |
@@ -69,11 +71,16 @@ Skills (what to do)          CLI Companion (tools to do it with)
 
 ### Distribution model
 
-The project is published to npmjs as a public package and hosted at `https://agenticskillmill.com`. There are three ways users consume it:
+The project is published to npmjs as a public package and hosted at `https://agenticskillmill.com`.
+
+**Remote install (no clone):** Every project hosts `site/install.sh` and `site/install.ps1` bootstrap scripts served via GitHub Pages. Non-npm projects use a clone-to-temp pattern instead of `npm install -g`.
+
+There are multiple ways users consume it:
 
 | Method | Command | Who uses it |
 |--------|---------|-------------|
-| Remote install (no clone) | `bash <(curl -fsSL https://agenticskillmill.com/install.sh) --all` | End users who want skills installed into their IDE tools |
+| Remote install (bash) | `bash <(curl -fsSL https://<domain>/install.sh)` | End users on Linux/macOS |
+| Remote install (PowerShell) | `irm https://<domain>/install.ps1 \| iex` | End users on Windows |
 | npx (no install) | `npx --yes agentic-skill-mill@latest <command>` | Users running CLI commands without global install |
 | Local development | `git clone` then `bash install-local.sh --all` | Contributors working on the project itself |
 
@@ -132,8 +139,9 @@ Static site served via GitHub Pages at `https://agenticskillmill.com`:
 | `site/index.html` | Landing page with architecture, CLI commands, and install instructions |
 | `site/style.css` | Site styles |
 | `site/install.sh` | Bootstrap installer served at `https://agenticskillmill.com/install.sh` |
+| `site/install.ps1` | PowerShell bootstrap installer served at `https://agenticskillmill.com/install.ps1` |
 
-When updating the bootstrap installer logic, edit `install.sh` at the repo root and copy it to `site/install.sh` to keep both in sync. The release workflow publishes the repo-root copy to npm; the Pages workflow serves the site copy to the domain.
+When updating the bootstrap installer logic, edit `install.sh` and `install.ps1` at the repo root and copy them to `site/install.sh` and `site/install.ps1` to keep both in sync. The release workflow publishes the repo-root copies to npm; the Pages workflow serves the site copies to the domain.
 
 ### Modifying distribution touchpoints
 
@@ -141,7 +149,7 @@ When updating the bootstrap installer logic, edit `install.sh` at the repo root
 |--------|----------------|
 | Add a new skill | `install-local.sh` SKILLS array, `skill/build/manifest.json` |
 | Change package name | `package.json` name + bin, `install.sh` default, `site/install.sh` default, `install-local.sh` PROJECT_NAME + CLI_BIN_NAME + MANAGED_MARKER, `site/index.html`, README |
-| Change bootstrap behavior | `install.sh` (repo root), then copy to `site/install.sh` |
+| Change bootstrap behavior | `install.sh` and `install.ps1` (repo root), then copy to `site/install.sh` and `site/install.ps1` |
 | Add a GitHub Actions secret | Repo settings, document in README |
 | Update domain | `site/CNAME`, README, skill source, architecture fragment |
 
@@ -508,6 +516,35 @@ Use conventional commit format with a detailed body:
 
 The commit body should list every file category changed (core modules, CLI wrappers, fragments, manifest, etc.) and what was done in each.
 
+### Cross-Artifact Skill Signature
+
+When updating or creating a skill, embed a deterministic signature in each externally searchable artifact so operators can query everything produced by that specific skill across systems.
+
+Derive the signature per skill name:
+
+- Compute `sha256("<skill-name>")`
+- Use the first 8 lowercase hex characters
+- Format as `skill-sig: <sig8>`
+
+For a given skill name, the value is permanently static across all versions.
+
+Example:
+
+- `sha256("3pp-skill")` -> `ad61853a...`
+- signature value: `skill-sig: ad61853a`
+
+### Artifact Embedding Rules
+
+- **Commit message body**: append a git trailer after a blank line: `Skill-Sig: <sig8>`
+- **PR markdown doc**: append `<sub>skill-sig: <sig8></sub>` after the `## Notes` section
+- **GUS HTML details**: append `<p style="font-size:0.8em;color:#888">skill-sig: <sig8></p>` before closing `</body></html>`
+
+### Searchability Targets
+
+- Git: `git log --grep="skill-sig: <sig8>"`
+- GitHub: search for `"skill-sig: <sig8>"`
+- GUS SOQL: `WHERE Details__c LIKE '%skill-sig: <sig8>%'`
+
 ---
 
 ## Anti-Patterns

package/compiled/windsurf/rules/agentic-skill-mill.md

@@ -45,6 +45,8 @@ Skills (what to do)          CLI Companion (tools to do it with)
 - `src/errors/types.ts` — Typed error hierarchy (AppError, NotFoundError, etc.)
 - `src/cache/cache-manager.ts` — Two-tier cache (memory + disk) with TTL
 
+**Local installers:** Every project ships `install.sh` (bash) and `install.ps1` (PowerShell). Both support the same flags and produce identical installed state.
+
 **The local installer** (`install-local.sh`) builds the CLI, compiles skills, and copies compiled outputs to IDE-specific directories (~/.claude/skills, ~/.cursor/rules, etc.) with marker-based stale file cleanup. The bootstrap installer is hosted at `https://agenticskillmill.com/install.sh` (source: `site/install.sh`) and is also bundled in the npm package as `install.sh`. It installs the npm utility first, then delegates to `install-local.sh --skills-only`. Local installer functions use `set -e` for fail-fast behavior. Any function that uses an early-exit guard (`[[ -d ... ]] || return`, `[[ -z ... ]] && return`) **must** use `return 0`, never bare `return`. Bare `return` inherits the exit code of the last command, which for a failed conditional test is 1 -- and `set -e` treats that as a script-terminating failure with no error message.
 
 ### Key files to modify when augmenting a project
@@ -54,7 +56,7 @@ Skills (what to do)          CLI Companion (tools to do it with)
 | Add a CLI command | `src/core/<name>.ts`, `src/cli/commands/<name>.ts`, `src/cli/index.ts`, `src/index.ts` |
 | Add a fragment | `skill/fragments/<category>/<name>.md`, `skill/build/manifest.json`, skill source |
 | Add a skill | `skill/skills/<name>/<name>.md`, `skill/build/manifest.json`, `install-local.sh` SKILLS array |
-| Change installer behavior | `install.sh` (repo root) then copy to `site/install.sh` |
+| Change installer behavior | `install.sh` and `install.ps1` (repo root), then copy bootstraps to `site/` |
 | Update the landing page | `site/index.html`, `site/style.css` |
 | Change CI secrets or workflow | `.github/workflows/release.yml` or `deploy-pages.yml`, repo settings |
 | Rename the project | See the rename workflow |
@@ -65,11 +67,16 @@ Skills (what to do)          CLI Companion (tools to do it with)
 
 ### Distribution model
 
-The project is published to npmjs as a public package and hosted at `https://agenticskillmill.com`. There are three ways users consume it:
+The project is published to npmjs as a public package and hosted at `https://agenticskillmill.com`.
+
+**Remote install (no clone):** Every project hosts `site/install.sh` and `site/install.ps1` bootstrap scripts served via GitHub Pages. Non-npm projects use a clone-to-temp pattern instead of `npm install -g`.
+
+There are multiple ways users consume it:
 
 | Method | Command | Who uses it |
 |--------|---------|-------------|
-| Remote install (no clone) | `bash <(curl -fsSL https://agenticskillmill.com/install.sh) --all` | End users who want skills installed into their IDE tools |
+| Remote install (bash) | `bash <(curl -fsSL https://<domain>/install.sh)` | End users on Linux/macOS |
+| Remote install (PowerShell) | `irm https://<domain>/install.ps1 \| iex` | End users on Windows |
 | npx (no install) | `npx --yes agentic-skill-mill@latest <command>` | Users running CLI commands without global install |
 | Local development | `git clone` then `bash install-local.sh --all` | Contributors working on the project itself |
 
@@ -128,8 +135,9 @@ Static site served via GitHub Pages at `https://agenticskillmill.com`:
 | `site/index.html` | Landing page with architecture, CLI commands, and install instructions |
 | `site/style.css` | Site styles |
 | `site/install.sh` | Bootstrap installer served at `https://agenticskillmill.com/install.sh` |
+| `site/install.ps1` | PowerShell bootstrap installer served at `https://agenticskillmill.com/install.ps1` |
 
-When updating the bootstrap installer logic, edit `install.sh` at the repo root and copy it to `site/install.sh` to keep both in sync. The release workflow publishes the repo-root copy to npm; the Pages workflow serves the site copy to the domain.
+When updating the bootstrap installer logic, edit `install.sh` and `install.ps1` at the repo root and copy them to `site/install.sh` and `site/install.ps1` to keep both in sync. The release workflow publishes the repo-root copies to npm; the Pages workflow serves the site copies to the domain.
 
 ### Modifying distribution touchpoints
 
@@ -137,7 +145,7 @@ When updating the bootstrap installer logic, edit `install.sh` at the repo root
 |--------|----------------|
 | Add a new skill | `install-local.sh` SKILLS array, `skill/build/manifest.json` |
 | Change package name | `package.json` name + bin, `install.sh` default, `site/install.sh` default, `install-local.sh` PROJECT_NAME + CLI_BIN_NAME + MANAGED_MARKER, `site/index.html`, README |
-| Change bootstrap behavior | `install.sh` (repo root), then copy to `site/install.sh` |
+| Change bootstrap behavior | `install.sh` and `install.ps1` (repo root), then copy to `site/install.sh` and `site/install.ps1` |
 | Add a GitHub Actions secret | Repo settings, document in README |
 | Update domain | `site/CNAME`, README, skill source, architecture fragment |
 
@@ -504,6 +512,35 @@ Use conventional commit format with a detailed body:
 
 The commit body should list every file category changed (core modules, CLI wrappers, fragments, manifest, etc.) and what was done in each.
 
+### Cross-Artifact Skill Signature
+
+When updating or creating a skill, embed a deterministic signature in each externally searchable artifact so operators can query everything produced by that specific skill across systems.
+
+Derive the signature per skill name:
+
+- Compute `sha256("<skill-name>")`
+- Use the first 8 lowercase hex characters
+- Format as `skill-sig: <sig8>`
+
+For a given skill name, the value is permanently static across all versions.
+
+Example:
+
+- `sha256("3pp-skill")` -> `ad61853a...`
+- signature value: `skill-sig: ad61853a`
+
+### Artifact Embedding Rules
+
+- **Commit message body**: append a git trailer after a blank line: `Skill-Sig: <sig8>`
+- **PR markdown doc**: append `<sub>skill-sig: <sig8></sub>` after the `## Notes` section
+- **GUS HTML details**: append `<p style="font-size:0.8em;color:#888">skill-sig: <sig8></p>` before closing `</body></html>`
+
+### Searchability Targets
+
+- Git: `git log --grep="skill-sig: <sig8>"`
+- GitHub: search for `"skill-sig: <sig8>"`
+- GUS SOQL: `WHERE Details__c LIKE '%skill-sig: <sig8>%'`
+
 ---
 
 ## Anti-Patterns

package/compiled/windsurf/skills/agentic-skill-mill/SKILL.md

@@ -45,6 +45,8 @@ Skills (what to do)          CLI Companion (tools to do it with)
 - `src/errors/types.ts` — Typed error hierarchy (AppError, NotFoundError, etc.)
 - `src/cache/cache-manager.ts` — Two-tier cache (memory + disk) with TTL
 
+**Local installers:** Every project ships `install.sh` (bash) and `install.ps1` (PowerShell). Both support the same flags and produce identical installed state.
+
 **The local installer** (`install-local.sh`) builds the CLI, compiles skills, and copies compiled outputs to IDE-specific directories (~/.claude/skills, ~/.cursor/rules, etc.) with marker-based stale file cleanup. The bootstrap installer is hosted at `https://agenticskillmill.com/install.sh` (source: `site/install.sh`) and is also bundled in the npm package as `install.sh`. It installs the npm utility first, then delegates to `install-local.sh --skills-only`. Local installer functions use `set -e` for fail-fast behavior. Any function that uses an early-exit guard (`[[ -d ... ]] || return`, `[[ -z ... ]] && return`) **must** use `return 0`, never bare `return`. Bare `return` inherits the exit code of the last command, which for a failed conditional test is 1 -- and `set -e` treats that as a script-terminating failure with no error message.
 
 ### Key files to modify when augmenting a project
@@ -54,7 +56,7 @@ Skills (what to do)          CLI Companion (tools to do it with)
 | Add a CLI command | `src/core/<name>.ts`, `src/cli/commands/<name>.ts`, `src/cli/index.ts`, `src/index.ts` |
 | Add a fragment | `skill/fragments/<category>/<name>.md`, `skill/build/manifest.json`, skill source |
 | Add a skill | `skill/skills/<name>/<name>.md`, `skill/build/manifest.json`, `install-local.sh` SKILLS array |
-| Change installer behavior | `install.sh` (repo root) then copy to `site/install.sh` |
+| Change installer behavior | `install.sh` and `install.ps1` (repo root), then copy bootstraps to `site/` |
 | Update the landing page | `site/index.html`, `site/style.css` |
 | Change CI secrets or workflow | `.github/workflows/release.yml` or `deploy-pages.yml`, repo settings |
 | Rename the project | See the rename workflow |
@@ -65,11 +67,16 @@ Skills (what to do)          CLI Companion (tools to do it with)
 
 ### Distribution model
 
-The project is published to npmjs as a public package and hosted at `https://agenticskillmill.com`. There are three ways users consume it:
+The project is published to npmjs as a public package and hosted at `https://agenticskillmill.com`.
+
+**Remote install (no clone):** Every project hosts `site/install.sh` and `site/install.ps1` bootstrap scripts served via GitHub Pages. Non-npm projects use a clone-to-temp pattern instead of `npm install -g`.
+
+There are multiple ways users consume it:
 
 | Method | Command | Who uses it |
 |--------|---------|-------------|
-| Remote install (no clone) | `bash <(curl -fsSL https://agenticskillmill.com/install.sh) --all` | End users who want skills installed into their IDE tools |
+| Remote install (bash) | `bash <(curl -fsSL https://<domain>/install.sh)` | End users on Linux/macOS |
+| Remote install (PowerShell) | `irm https://<domain>/install.ps1 \| iex` | End users on Windows |
 | npx (no install) | `npx --yes agentic-skill-mill@latest <command>` | Users running CLI commands without global install |
 | Local development | `git clone` then `bash install-local.sh --all` | Contributors working on the project itself |
 
@@ -128,8 +135,9 @@ Static site served via GitHub Pages at `https://agenticskillmill.com`:
 | `site/index.html` | Landing page with architecture, CLI commands, and install instructions |
 | `site/style.css` | Site styles |
 | `site/install.sh` | Bootstrap installer served at `https://agenticskillmill.com/install.sh` |
+| `site/install.ps1` | PowerShell bootstrap installer served at `https://agenticskillmill.com/install.ps1` |
 
-When updating the bootstrap installer logic, edit `install.sh` at the repo root and copy it to `site/install.sh` to keep both in sync. The release workflow publishes the repo-root copy to npm; the Pages workflow serves the site copy to the domain.
+When updating the bootstrap installer logic, edit `install.sh` and `install.ps1` at the repo root and copy them to `site/install.sh` and `site/install.ps1` to keep both in sync. The release workflow publishes the repo-root copies to npm; the Pages workflow serves the site copies to the domain.
 
 ### Modifying distribution touchpoints
 
@@ -137,7 +145,7 @@ When updating the bootstrap installer logic, edit `install.sh` at the repo root
 |--------|----------------|
 | Add a new skill | `install-local.sh` SKILLS array, `skill/build/manifest.json` |
 | Change package name | `package.json` name + bin, `install.sh` default, `site/install.sh` default, `install-local.sh` PROJECT_NAME + CLI_BIN_NAME + MANAGED_MARKER, `site/index.html`, README |
-| Change bootstrap behavior | `install.sh` (repo root), then copy to `site/install.sh` |
+| Change bootstrap behavior | `install.sh` and `install.ps1` (repo root), then copy to `site/install.sh` and `site/install.ps1` |
 | Add a GitHub Actions secret | Repo settings, document in README |
 | Update domain | `site/CNAME`, README, skill source, architecture fragment |
 
@@ -504,6 +512,35 @@ Use conventional commit format with a detailed body:
 
 The commit body should list every file category changed (core modules, CLI wrappers, fragments, manifest, etc.) and what was done in each.
 
+### Cross-Artifact Skill Signature
+
+When updating or creating a skill, embed a deterministic signature in each externally searchable artifact so operators can query everything produced by that specific skill across systems.
+
+Derive the signature per skill name:
+
+- Compute `sha256("<skill-name>")`
+- Use the first 8 lowercase hex characters
+- Format as `skill-sig: <sig8>`
+
+For a given skill name, the value is permanently static across all versions.
+
+Example:
+
+- `sha256("3pp-skill")` -> `ad61853a...`
+- signature value: `skill-sig: ad61853a`
+
+### Artifact Embedding Rules
+
+- **Commit message body**: append a git trailer after a blank line: `Skill-Sig: <sig8>`
+- **PR markdown doc**: append `<sub>skill-sig: <sig8></sub>` after the `## Notes` section
+- **GUS HTML details**: append `<p style="font-size:0.8em;color:#888">skill-sig: <sig8></p>` before closing `</body></html>`
+
+### Searchability Targets
+
+- Git: `git log --grep="skill-sig: <sig8>"`
+- GitHub: search for `"skill-sig: <sig8>"`
+- GUS SOQL: `WHERE Details__c LIKE '%skill-sig: <sig8>%'`
+
 ---
 
 ## Anti-Patterns

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agentic-skill-mill",
-  "version": "1.0.8",
+  "version": "1.0.10",
   "description": "Forge and refine agent skill projects -- fragment-composed skills compiled to 7 IDE targets with a companion CLI",
   "type": "module",
   "bin": {

package/skill/build/manifest.json

@@ -18,7 +18,8 @@
         "meta/core-module-pattern.md",
         "meta/cli-command-pattern.md",
         "meta/fragment-composition.md",
-        "meta/rename-workflow.md"
+        "meta/rename-workflow.md",
+        "meta/skill-signature.md"
       ]
     }
   },

package/skill/fragments/meta/architecture-overview.md

@@ -31,6 +31,8 @@ Skills (what to do)          CLI Companion (tools to do it with)
 - `src/errors/types.ts` — Typed error hierarchy (AppError, NotFoundError, etc.)
 - `src/cache/cache-manager.ts` — Two-tier cache (memory + disk) with TTL
 
+**Local installers:** Every project ships `install.sh` (bash) and `install.ps1` (PowerShell). Both support the same flags and produce identical installed state.
+
 **The local installer** (`install-local.sh`) builds the CLI, compiles skills, and copies compiled outputs to IDE-specific directories (~/.claude/skills, ~/.cursor/rules, etc.) with marker-based stale file cleanup. The bootstrap installer is hosted at `https://agenticskillmill.com/install.sh` (source: `site/install.sh`) and is also bundled in the npm package as `install.sh`. It installs the npm utility first, then delegates to `install-local.sh --skills-only`. Local installer functions use `set -e` for fail-fast behavior. Any function that uses an early-exit guard (`[[ -d ... ]] || return`, `[[ -z ... ]] && return`) **must** use `return 0`, never bare `return`. Bare `return` inherits the exit code of the last command, which for a failed conditional test is 1 -- and `set -e` treats that as a script-terminating failure with no error message.
 
 ### Key files to modify when augmenting a project
@@ -40,7 +42,7 @@ Skills (what to do)          CLI Companion (tools to do it with)
 | Add a CLI command | `src/core/<name>.ts`, `src/cli/commands/<name>.ts`, `src/cli/index.ts`, `src/index.ts` |
 | Add a fragment | `skill/fragments/<category>/<name>.md`, `skill/build/manifest.json`, skill source |
 | Add a skill | `skill/skills/<name>/<name>.md`, `skill/build/manifest.json`, `install-local.sh` SKILLS array |
-| Change installer behavior | `install.sh` (repo root) then copy to `site/install.sh` |
+| Change installer behavior | `install.sh` and `install.ps1` (repo root), then copy bootstraps to `site/` |
 | Update the landing page | `site/index.html`, `site/style.css` |
 | Change CI secrets or workflow | `.github/workflows/release.yml` or `deploy-pages.yml`, repo settings |
 | Rename the project | See the rename workflow |

package/skill/fragments/meta/distribution-and-ci.md

@@ -1,10 +1,15 @@
 ### Distribution model
 
-The project is published to npmjs as a public package and hosted at `https://agenticskillmill.com`. There are three ways users consume it:
+The project is published to npmjs as a public package and hosted at `https://agenticskillmill.com`.
+
+**Remote install (no clone):** Every project hosts `site/install.sh` and `site/install.ps1` bootstrap scripts served via GitHub Pages. Non-npm projects use a clone-to-temp pattern instead of `npm install -g`.
+
+There are multiple ways users consume it:
 
 | Method | Command | Who uses it |
 |--------|---------|-------------|
-| Remote install (no clone) | `bash <(curl -fsSL https://agenticskillmill.com/install.sh) --all` | End users who want skills installed into their IDE tools |
+| Remote install (bash) | `bash <(curl -fsSL https://<domain>/install.sh)` | End users on Linux/macOS |
+| Remote install (PowerShell) | `irm https://<domain>/install.ps1 \| iex` | End users on Windows |
 | npx (no install) | `npx --yes agentic-skill-mill@latest <command>` | Users running CLI commands without global install |
 | Local development | `git clone` then `bash install-local.sh --all` | Contributors working on the project itself |
 
@@ -63,8 +68,9 @@ Static site served via GitHub Pages at `https://agenticskillmill.com`:
 | `site/index.html` | Landing page with architecture, CLI commands, and install instructions |
 | `site/style.css` | Site styles |
 | `site/install.sh` | Bootstrap installer served at `https://agenticskillmill.com/install.sh` |
+| `site/install.ps1` | PowerShell bootstrap installer served at `https://agenticskillmill.com/install.ps1` |
 
-When updating the bootstrap installer logic, edit `install.sh` at the repo root and copy it to `site/install.sh` to keep both in sync. The release workflow publishes the repo-root copy to npm; the Pages workflow serves the site copy to the domain.
+When updating the bootstrap installer logic, edit `install.sh` and `install.ps1` at the repo root and copy them to `site/install.sh` and `site/install.ps1` to keep both in sync. The release workflow publishes the repo-root copies to npm; the Pages workflow serves the site copies to the domain.
 
 ### Modifying distribution touchpoints
 
@@ -72,6 +78,6 @@ When updating the bootstrap installer logic, edit `install.sh` at the repo root
 |--------|----------------|
 | Add a new skill | `install-local.sh` SKILLS array, `skill/build/manifest.json` |
 | Change package name | `package.json` name + bin, `install.sh` default, `site/install.sh` default, `install-local.sh` PROJECT_NAME + CLI_BIN_NAME + MANAGED_MARKER, `site/index.html`, README |
-| Change bootstrap behavior | `install.sh` (repo root), then copy to `site/install.sh` |
+| Change bootstrap behavior | `install.sh` and `install.ps1` (repo root), then copy to `site/install.sh` and `site/install.ps1` |
 | Add a GitHub Actions secret | Repo settings, document in README |
 | Update domain | `site/CNAME`, README, skill source, architecture fragment |

package/skill/fragments/meta/skill-signature.md

@@ -0,0 +1,28 @@
+### Cross-Artifact Skill Signature
+
+When updating or creating a skill, embed a deterministic signature in each externally searchable artifact so operators can query everything produced by that specific skill across systems.
+
+Derive the signature per skill name:
+
+- Compute `sha256("<skill-name>")`
+- Use the first 8 lowercase hex characters
+- Format as `skill-sig: <sig8>`
+
+For a given skill name, the value is permanently static across all versions.
+
+Example:
+
+- `sha256("3pp-skill")` -> `ad61853a...`
+- signature value: `skill-sig: ad61853a`
+
+### Artifact Embedding Rules
+
+- **Commit message body**: append a git trailer after a blank line: `Skill-Sig: <sig8>`
+- **PR markdown doc**: append `<sub>skill-sig: <sig8></sub>` after the `## Notes` section
+- **GUS HTML details**: append `<p style="font-size:0.8em;color:#888">skill-sig: <sig8></p>` before closing `</body></html>`
+
+### Searchability Targets
+
+- Git: `git log --grep="skill-sig: <sig8>"`
+- GitHub: search for `"skill-sig: <sig8>"`
+- GUS SOQL: `WHERE Details__c LIKE '%skill-sig: <sig8>%'`

package/skill/skills/agentic-skill-mill/agentic-skill-mill.md

@@ -125,6 +125,8 @@ Use conventional commit format with a detailed body:
 
 The commit body should list every file category changed (core modules, CLI wrappers, fragments, manifest, etc.) and what was done in each.
 
+{{include:meta/skill-signature.md}}
+
 ---
 
 ## Anti-Patterns