agentic-skill-mill 1.0.8 → 1.0.9

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

@@ -504,6 +504,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

@@ -504,6 +504,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

@@ -504,6 +504,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

@@ -504,6 +504,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

@@ -508,6 +508,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

@@ -504,6 +504,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

@@ -504,6 +504,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.9",
   "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/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