[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75JMDBFDCMZDBV6QRB584FQ":3,"skill-same:01M75JMDBFDCMZDBV6QRB584FQ":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":13,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M75JMDBFDCMZDBV6QRB584FQ","enforce-slsa",null,"Add an SLSA Verification (SlsaVerification) step to an existing Harness pipeline to verify SLSA provenance attestations and optionally enforce OPA policy sets on provenance data. Supports CI and CD (Deployment) including CI-only pipelines — append a Deploy stage via Phase 3b when verifying before deploy. Supports Docker, ECR, GCR, GAR, ACR, HAR, and Local artifacts. Only works with existing pipelines. Use when asked to verify SLSA, enforce SLSA policies, add SLSA verification step, validate SLSA attestation, or gate deploy on SLSA provenance. Trigger phrases: enforce SLSA, SLSA verification, verify SLSA, SLSA policy enforcement, SlsaVerification, verify SLSA attestation, add SLSA verify step.","AdmiralGallade\u002Fharness-repository","AdmiralGallade","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F59243621?v=4","01M759AG0891RDPWNGJBX1Y2TG","01M759AG10MS924J53ZWJ60AEC",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fenforce-slsa\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: enforce-slsa\ndescription: >-\n  Add an SLSA Verification (SlsaVerification) step to an existing Harness pipeline to verify SLSA\n  provenance attestations and optionally enforce OPA policy sets on provenance data. Supports CI and\n  CD (Deployment) including CI-only pipelines — append a Deploy stage via Phase 3b when verifying\n  before deploy. Supports Docker, ECR, GCR, GAR, ACR, HAR, and Local artifacts. Only works with\n  existing pipelines. Use when asked to verify SLSA, enforce SLSA policies, add SLSA verification\n  step, validate SLSA attestation, or gate deploy on SLSA provenance.\n  Trigger phrases: enforce SLSA, SLSA verification, verify SLSA, SLSA policy enforcement,\n  SlsaVerification, verify SLSA attestation, add SLSA verify step.\nmetadata:\n  author: Harness\n  version: 1.0.0\n  mcp-server: harness-mcp-v2\nlicense: Apache-2.0\ncompatibility: Requires Harness MCP v2 server (harness-mcp-v2)\n---\n\n# Enforce SLSA\n\nAdd an **SLSA Verification** (`SlsaVerification`) step to an existing Harness pipeline. The step\nverifies SLSA provenance attestations (when enabled) and optionally evaluates OPA policy sets against\nprovenance data.\n\nThis skill only works with **existing pipelines** — do not create standalone verification-only pipelines.\n\n**Prerequisites:** SLSA provenance must already exist for the artifact (typically from a `provenance`\nstep via `\u002Fgenerate-slsa` — UI label SLSA Generation). Optional **policy sets** for provenance\nenforcement (`\u002Fcreate-policy`, `harness_list` `policy_set`).\n\n**Supported stages:** CI, CD (`Deployment`), and Security. CD requires a **containerized step group**.\nUnlike SBOM enforcement, CI and CD both use **`SlsaVerification`** (no separate CD step type).\n\nGuide the user through a **step-by-step interactive wizard** (same UX as `\u002Fgenerate-slsa`):\n\n- Wizard: `references\u002Finteractive-wizard-flow.md`\n- UI ↔ YAML: `references\u002Fslsa-verification-step.md`\n- CD containerized step groups: `skills\u002Fgenerate-slsa\u002Freferences\u002Fcd-containerized-step-group.md`\n\n---\n\n## Interaction model (mandatory)\n\n1. **One question per turn** — use `AskQuestion` when available; otherwise numbered options with `(Recommended)`.\n2. **Opening message** — add SLSA Verification; mention generation + optional policy prerequisites.\n3. **Progress breadcrumb** — after pipeline fetch:\n   `Pipeline · Placement · Source · Details · Verify · Policy · Submit`\n4. **Record answers** — running summary; do not re-ask unless the user changes direction.\n5. **Fetch before configure** — `harness_get` before placement\u002Fsource questions.\n6. **Show pipeline structure** — highlight `provenance` (SLSA Generation) and connectors.\n7. **Infer source from generation** — when one `provenance` step exists (or `identifier: slsageneration`), reuse its source (map `repo` → `image_path`, lowercase → PascalCase types).\n8. **Never guess image tags** — default from generation step; ask if ambiguous.\n9. **Confirm before write** — summary + `harness_update` only after user confirms.\n10. **Stop after update** — after successful `harness_update`, provide a configuration summary and\n    point the user to `\u002Frun-pipeline` to execute. Do **not** call `harness_execute`, poll\n    executions, or run `harness_diagnose` in this skill (same pattern as `\u002Fconfigure-repo-scan`).\n11. **CD on CI-only pipeline** — do not reject CD verify; run Phase 3b to add Deploy stage + containerized group.\n12. **Verify method must match generation** — keyless ↔ keyless, keybased ↔ public key from same key pair.\n\nFull phase prompts: `references\u002Finteractive-wizard-flow.md`.\n\n---\n\n## Instructions\n\n### Wizard phases\n\n| Phase | Breadcrumb | Action |\n|-------|------------|--------|\n| 0 | Pipeline | AskQuestion: pipeline URL ready? |\n| 1 | Pipeline | Collect URL → `harness_get` |\n| 2 | Pipeline | Display structure; note missing `provenance` (SLSA Generation) step |\n| 3 | Placement | AskQuestion: after generation, CD before deploy, etc. |\n| 3b | Placement (CD) | Service, env, infra, step group if new Deploy stage |\n| 4 | Source | Infer from generation or pick registry tile |\n| 5 | Source | Registry provider (Third-Party only) |\n| 6 | Details | Connector (skip if obvious) |\n| 7 | Details | Image \u002F image_path (default from generation) |\n| 8 | Verify | AskQuestion: verify attestation method |\n| 9 | Policy | AskQuestion: policy set(s) or skip |\n| 10 | Submit | AskQuestion: confirm pipeline update |\n\nAfter Phase 10 `confirm` → insert step, `harness_update`, then provide summary (do not run the pipeline).\n\n### Supported stage types\n\n| Stage type | Step `type` | Placement notes |\n|------------|-------------|-----------------|\n| `CI` | `SlsaVerification` | **After** `provenance` \u002F `slsageneration` in the same stage |\n| `Deployment` | `SlsaVerification` | Containerized step group; **before** deploy |\n| `Security` | `SlsaVerification` | After generation when artifact is in registry |\n\n### CD edge case\n\nIf no `Deployment` stage and user chose CD verify:\n\n> No CD Deploy stage yet. We can add a **Deployment** stage with a **containerized step group** and\n> place **SLSA Verification** before deploy.\n\nRun Phase 3b (service, environment, infrastructure, `stepGroupInfra`) — mirror `\u002Fgenerate-slsa` Phase 3b.\nUse `skills\u002Fgenerate-slsa\u002Freferences\u002Fcd-containerized-step-group.md` with `SlsaVerification`.\n\n### After the wizard — backend steps\n\n#### Check prerequisites\n\n1. **SLSA generation** — pipeline contains `type: provenance` (SLSA Generation) or user confirms provenance exists.\n2. **Policy sets** (optional) — `harness_list(resource_type=\"policy_set\")`. If user wants policy\n   enforcement and none exist, direct to `\u002Fcreate-policy` before continuing.\n\n#### Extract context from pipeline YAML\n\nFrom `provenance` step (if present — also match `identifier: slsageneration`), copy and transform:\n\n| Generation | Verification |\n|------------|--------------|\n| `source.type: docker` | `source.type: Docker` |\n| `source.spec.repo` | `source.spec.image_path` |\n| `source.spec.connector` | `source.spec.connector` |\n| `spec.attestation` | matching `verify_attestation` (private → public key for keybased) |\n\n#### Generate SLSA verification step YAML\n\n**CI \u002F Security — Docker Registry, keyless verify:**\n\n```yaml\n- step:\n    identifier: slsaverification\n    name: SLSA Verification\n    type: SlsaVerification\n    spec:\n      source:\n        type: Docker\n        spec:\n          connector: lavakush07\n          image_path: lavakush07\u002Feasy-buggy-app:blog\n      verify_attestation:\n        type: keyless\n        spec:\n          oidcProvider: harness\n    timeout: 15m\n```\n\n**Key-based verify** (generation used `keybased` + private key):\n\n```yaml\n      verify_attestation:\n        type: keybased\n        spec:\n          publicKey: account.cosign_public_key\n```\n\nIf API validation rejects flat `keyless` \u002F `keybased`, retry with nested `cosign` wrapper — see\n`references\u002Fslsa-verification-step.md`.\n\n**Policy enforcement** (Advanced tab — step-level `enforce`):\n\n```yaml\n    enforce:\n      policySets:\n        - slsa_provenance_rules\n```\n\n**No attestation verify** (policy-only): omit `verify_attestation`.\n\n**CD Deploy** — same step type inside containerized `stepGroup`; use `\u003C+artifact.image>` for\n`image_path` when verifying service artifacts.\n\nFull provider mapping: `references\u002Fslsa-verification-step.md`.\n\n#### Insert step into pipeline YAML\n\n- Insert at Phase 3 placement — **after** `slsageneration` when possible.\n- Do not modify unrelated steps.\n- Step identifier: `slsaverification` (use `slsaverification_cd` in CD when CI already has one).\n- **CD:** inside containerized step group only.\n\n#### Update pipeline via MCP\n\n```\nharness_update\n  resource_type: pipeline\n  resource_id: \u003Cpipeline_identifier>\n  org_id: \u003Corganization>\n  project_id: \u003Cproject>\n  body: { yamlPipeline: \"\u003Cupdated pipeline YAML>\" }\n```\n\nOn validation errors, check PascalCase `source.type`, `image_path` vs `repo`, and `verify_attestation`\nshape (prefer flat `keyless`; fallback nested `cosign`).\n\n#### Provide summary\n\nReport the results to the user (same pattern as `\u002Fconfigure-repo-scan` — do **not** execute the pipeline):\n\n```\n## SLSA Verification Configured\n\n**Pipeline:** \u003Cpipeline_name>\n**Step:** SLSA Verification (SlsaVerification)\n**Location:** Stage \"\u003Cstage_name>\", \u003Cposition>\n**Source:** Docker — \u003Cconnector> — \u003Cimage_path>\n**Verify attestation:** Keyless (Harness OIDC) — or as configured\n**Policy sets:** \u003Clist or none>\n\n**Pipeline URL:** https:\u002F\u002Fapp.harness.io\u002Fng\u002Faccount\u002F\u003Caccount_id>\u002Fmodule\u002Fci\u002Forgs\u002F\u003Corg_id>\u002Fprojects\u002F\u003Cproject_id>\u002Fpipelines\u002F\u003Cpipeline_id>\u002Fpipeline-studio\u002F\n\n**Note:** Review the SLSA Verification step in Pipeline Studio to adjust Advanced settings.\n\n### Next Steps\n1. Run the pipeline via `\u002Frun-pipeline` to verify SLSA verification executes successfully\n2. If the run fails, diagnose with `\u002Fdebug-pipeline`\n3. View verification outcome on the execution **Supply Chain** tab\n4. If **Failed** due to policy deny, tune policies via `\u002Fcreate-policy`\n5. Add generation with `\u002Fgenerate-slsa` if provenance was missing\n6. Automate with `\u002Fcreate-trigger`\n```\n\n**CD pipelines:** note in the summary if runtime inputs (service artifact, environment, infrastructure)\nwill be required at run time — the user provides those via `\u002Frun-pipeline` or Harness UI Run.\n\n---\n\n## Examples\n\n### Verify after SLSA Generation\n\n```\n\u002Fenforce-slsa\nAdd SLSA verification after slsa-generation — keyless verify, policy set slsa_prod_rules\n```\n\n### CD before deploy\n\n```\n\u002Fenforce-slsa\nVerify SLSA in deploy stage before K8s rolling deploy for easy-buggy-app:blog\n```\n\n### Key-based verify (matches keybased generation)\n\n```\n\u002Fenforce-slsa\nVerify SLSA with public key account.cosign_public_key — same image as generation step\n```\n\n---\n\n## Performance Notes\n\n- Only **existing pipelines** (may append Deploy stage).\n- **Wizard UX mandatory** — one question per turn.\n- **Reuse generation source** — scan for `type: provenance` or `identifier: slsageneration`; map `repo` → `image_path`, lowercase → PascalCase types.\n- **Verification `source.type` is PascalCase** (`Docker`) — generation uses lowercase (`docker`).\n- **`verify_attestation`** is snake_case (not `verifyAttestation`). Prefer flat `type: keyless` + `oidcProvider` (same shape as generation `attestation`).\n- Policy sets on step **`enforce.policySets`** — not `spec.policy` like SBOM enforcement.\n- List `policy_set` via MCP — do not invent identifiers.\n- **CD:** containerized step group only; see `skills\u002Fgenerate-slsa\u002Freferences\u002Fcd-containerized-step-group.md`.\n- **Do not execute pipelines** in this skill — use `\u002Frun-pipeline` after configuration (same as `\u002Fconfigure-repo-scan`).\n- Pair with `\u002Fgenerate-slsa` (generate) and `\u002Fcreate-policy` (OPA rules).\n\n---\n\n## Troubleshooting\n\n### No SLSA Generation Step\n- Add `\u002Fgenerate-slsa` first with attestation enabled (`type: provenance` in YAML).\n- Verification needs `.att` in registry or provenance in SCS Artifacts.\n- Scan for `provenance` steps — not `SlsaGeneration` (API uses `provenance`).\n\n### Attestation Verification Failed\n- Verify method must match generation (`keyless` vs `keybased`).\n- Keybased: use **public** key secret (generation uses **private** key).\n- Keyless non-harness: configure Connector for Keyless Signing.\n\n### Wrong Image \u002F No Provenance\n- Use same `image_path` as generation `repo` field.\n- Symptom: verify passes wrong artifact — image mismatch.\n\n### Policy Evaluation Failed\n- Review policy set Rego rules; check Supply Chain tab for violations.\n- Confirm policy set identifier (not display name) in `enforce.policySets`.\n\n### YAML Validation Errors\n- `source.type` must be PascalCase for verification (`Docker`, not `docker`).\n- Docker source uses `image_path`, not `repo`.\n- `verify_attestation`: use flat `type: keyless` + `spec.oidcProvider: harness` — not nested `cosign` unless API rejects flat shape.\n- `DUPLICATE_IDENTIFIER` — rename `slsaverification`.\n\n### CD Step Errors\n- Place inside `stepGroup` with `stepGroupInfra` — not top-level `execution.steps`.\n- See `skills\u002Fgenerate-slsa\u002Freferences\u002Fcd-containerized-step-group.md`.\n\n### User Chose CD on CI-Only Pipeline\n- Expected — run Phase 3b; do not force CI-only unless user changes direction.\n\n### Pipeline Run Failed\n- Use `\u002Frun-pipeline` to execute and `\u002Fdebug-pipeline` to diagnose failures\n- Confirm verify method matches generation attestation; check public key for keybased\n- Missing runtime inputs: provide branch\u002Ftag or deploy inputs via `\u002Frun-pipeline` or Harness UI Run\n\n### MCP Errors\n- `CONNECTOR_NOT_FOUND` — verify connector in Project Settings.\n- `ACCESS_DENIED` — PAT needs pipeline edit and policy read permissions.\n","# Enforce SLSA\n\nAdd an **SLSA Verification** (`SlsaVerification`) step to an existing Harness pipeline. The step\nverifies SLSA provenance attestations (when enabled) and optionally evaluates OPA policy sets against\nprovenance data.\n\nThis skill only works with **existing pipelines** — do not create standalone verification-only pipelines.\n\n**Prerequisites:** SLSA provenance must already exist for the artifact (typically from a `provenance`\nstep via `\u002Fgenerate-slsa` — UI label SLSA Generation). Optional **policy sets** for provenance\nenforcement (`\u002Fcreate-policy`, `harness_list` `policy_set`).\n\n**Supported stages:** CI, CD (`Deployment`), and Security. CD requires a **containerized step group**.\nUnlike SBOM enforcement, CI and CD both use **`SlsaVerification`** (no separate CD step type).\n\nGuide the user through a **step-by-step interactive wizard** (same UX as `\u002Fgenerate-slsa`):\n\n- Wizard: `references\u002Finteractive-wizard-flow.md`\n- UI ↔ YAML: `references\u002Fslsa-verification-step.md`\n- CD containerized step groups: `skills\u002Fgenerate-slsa\u002Freferences\u002Fcd-containerized-step-group.md`\n\n---\n\n## Interaction model (mandatory)\n\n1. **One question per turn** — use `AskQuestion` when available; otherwise numbered options with `(Recommended)`.\n2. **Opening message** — add SLSA Verification; mention generation + optional policy prerequisites.\n3. **Progress breadcrumb** — after pipeline fetch:\n   `Pipeline · Placement · Source · Details · Verify · Policy · Submit`\n4. **Record answers** — running summary; do not re-ask unless the user changes direction.\n5. **Fetch before configure** — `harness_get` before placement\u002Fsource questions.\n6. **Show pipeline structure** — highlight `provenance` (SLSA Generation) and connectors.\n7. **Infer source from generation** — when one `provenance` step exists (or `identifier: slsageneration`), reuse its source (map `repo` → `image_path`, lowercase → PascalCase types).\n8. **Never guess image tags** — default from generation step; ask if ambiguous.\n9. **Confirm before write** — summary + `harness_update` only after user confirms.\n10. **Stop after update** — after successful `harness_update`, provide a configuration summary and\n    point the user to `\u002Frun-pipeline` to execute. Do **not** call `harness_execute`, poll\n    executions, or run `harness_diagnose` in this skill (same pattern as `\u002Fconfigure-repo-scan`).\n11. **CD on CI-only pipeline** — do not reject CD verify; run Phase 3b to add Deploy stage + containerized group.\n12. **Verify method must match generation** — keyless ↔ keyless, keybased ↔ public key from same key pair.\n\nFull phase prompts: `references\u002Finteractive-wizard-flow.md`.\n\n---\n\n## Instructions\n\n### Wizard phases\n\n| Phase | Breadcrumb | Action |\n|-------|------------|--------|\n| 0 | Pipeline | AskQuestion: pipeline URL ready? |\n| 1 | Pipeline | Collect URL → `harness_get` |\n| 2 | Pipeline | Display structure; note missing `provenance` (SLSA Generation) step |\n| 3 | Placement | AskQuestion: after generation, CD before deploy, etc. |\n| 3b | Placement (CD) | Service, env, infra, step group if new Deploy stage |\n| 4 | Source | Infer from generation or pick registry tile |\n| 5 | Source | Registry provider (Third-Party only) |\n| 6 | Details | Connector (skip if obvious) |\n| 7 | Details | Image \u002F image_path (default from generation) |\n| 8 | Verify | AskQuestion: verify attestation method |\n| 9 | Policy | AskQuestion: policy set(s) or skip |\n| 10 | Submit | AskQuestion: confirm pipeline update |\n\nAfter Phase 10 `confirm` → insert step, `harness_update`, then provide summary (do not run the pipeline).\n\n### Supported stage types\n\n| Stage type | Step `type` | Placement notes |\n|------------|-------------|-----------------|\n| `CI` | `SlsaVerification` | **After** `provenance` \u002F `slsageneration` in the same stage |\n| `Deployment` | `SlsaVerification` | Containerized step group; **before** deploy |\n| `Security` | `SlsaVerification` | After generation when artifact is in registry |\n\n### CD edge case\n\nIf no `Deployment` stage and user chose CD verify:\n\n> No CD Deploy stage yet. We can add a **Deployment** stage with a **containerized step group** and\n> place **SLSA Verification** before deploy.\n\nRun Phase 3b (service, environment, infrastructure, `stepGroupInfra`) — mirror `\u002Fgenerate-slsa` Phase 3b.\nUse `skills\u002Fgenerate-slsa\u002Freferences\u002Fcd-containerized-step-group.md` with `SlsaVerification`.\n\n### After the wizard — backend steps\n\n#### Check prerequisites\n\n1. **SLSA generation** — pipeline contains `type: provenance` (SLSA Generation) or user confirms provenance exists.\n2. **Policy sets** (optional) — `harness_list(resource_type=\"policy_set\")`. If user wants policy\n   enforcement and none exist, direct to `\u002Fcreate-policy` before continuing.\n\n#### Extract context from pipeline YAML\n\nFrom `provenance` step (if present — also match `identifier: slsageneration`), copy and transform:\n\n| Generation | Verification |\n|------------|--------------|\n| `source.type: docker` | `source.type: Docker` |\n| `source.spec.repo` | `source.spec.image_path` |\n| `source.spec.connector` | `source.spec.connector` |\n| `spec.attestation` | matching `verify_attestation` (private → public key for keybased) |\n\n#### Generate SLSA verification step YAML\n\n**CI \u002F Security — Docker Registry, keyless verify:**\n\n```yaml\n- step:\n    identifier: slsaverification\n    name: SLSA Verification\n    type: SlsaVerification\n    spec:\n      source:\n        type: Docker\n        spec:\n          connector: lavakush07\n          image_path: lavakush07\u002Feasy-buggy-app:blog\n      verify_attestation:\n        type: keyless\n        spec:\n          oidcProvider: harness\n    timeout: 15m\n```\n\n**Key-based verify** (generation used `keybased` + private key):\n\n```yaml\n      verify_attestation:\n        type: keybased\n        spec:\n          publicKey: account.cosign_public_key\n```\n\nIf API validation rejects flat `keyless` \u002F `keybased`, retry with nested `cosign` wrapper — see\n`references\u002Fslsa-verification-step.md`.\n\n**Policy enforcement** (Advanced tab — step-level `enforce`):\n\n```yaml\n    enforce:\n      policySets:\n        - slsa_provenance_rules\n```\n\n**No attestation verify** (policy-only): omit `verify_attestation`.\n\n**CD Deploy** — same step type inside containerized `stepGroup`; use `\u003C+artifact.image>` for\n`image_path` when verifying service artifacts.\n\nFull provider mapping: `references\u002Fslsa-verification-step.md`.\n\n#### Insert step into pipeline YAML\n\n- Insert at Phase 3 placement — **after** `slsageneration` when possible.\n- Do not modify unrelated steps.\n- Step identifier: `slsaverification` (use `slsaverification_cd` in CD when CI already has one).\n- **CD:** inside containerized step group only.\n\n#### Update pipeline via MCP\n\n```\nharness_update\n  resource_type: pipeline\n  resource_id: \u003Cpipeline_identifier>\n  org_id: \u003Corganization>\n  project_id: \u003Cproject>\n  body: { yamlPipeline: \"\u003Cupdated pipeline YAML>\" }\n```\n\nOn validation errors, check PascalCase `source.type`, `image_path` vs `repo`, and `verify_attestation`\nshape (prefer flat `keyless`; fallback nested `cosign`).\n\n#### Provide summary\n\nReport the results to the user (same pattern as `\u002Fconfigure-repo-scan` — do **not** execute the pipeline):\n\n```\n## SLSA Verification Configured\n\n**Pipeline:** \u003Cpipeline_name>\n**Step:** SLSA Verification (SlsaVerification)\n**Location:** Stage \"\u003Cstage_name>\", \u003Cposition>\n**Source:** Docker — \u003Cconnector> — \u003Cimage_path>\n**Verify attestation:** Keyless (Harness OIDC) — or as configured\n**Policy sets:** \u003Clist or none>\n\n**Pipeline URL:** https:\u002F\u002Fapp.harness.io\u002Fng\u002Faccount\u002F\u003Caccount_id>\u002Fmodule\u002Fci\u002Forgs\u002F\u003Corg_id>\u002Fprojects\u002F\u003Cproject_id>\u002Fpipelines\u002F\u003Cpipeline_id>\u002Fpipeline-studio\u002F\n\n**Note:** Review the SLSA Verification step in Pipeline Studio to adjust Advanced settings.\n\n### Next Steps\n1. Run the pipeline via `\u002Frun-pipeline` to verify SLSA verification executes successfully\n2. If the run fails, diagnose with `\u002Fdebug-pipeline`\n3. View verification outcome on the execution **Supply Chain** tab\n4. If **Failed** due to policy deny, tune policies via `\u002Fcreate-policy`\n5. Add generation with `\u002Fgenerate-slsa` if provenance was missing\n6. Automate with `\u002Fcreate-trigger`\n```\n\n**CD pipelines:** note in the summary if runtime inputs (service artifact, environment, infrastructure)\nwill be required at run time — the user provides those via `\u002Frun-pipeline` or Harness UI Run.\n\n---\n\n## Examples\n\n### Verify after SLSA Generation\n\n```\n\u002Fenforce-slsa\nAdd SLSA verification after slsa-generation — keyless verify, policy set slsa_prod_rules\n```\n\n### CD before deploy\n\n```\n\u002Fenforce-slsa\nVerify SLSA in deploy stage before K8s rolling deploy for easy-buggy-app:blog\n```\n\n### Key-based verify (matches keybased generation)\n\n```\n\u002Fenforce-slsa\nVerify SLSA with public key account.cosign_public_key — same image as generation step\n```\n\n---\n\n## Performance Notes\n\n- Only **existing pipelines** (may append Deploy stage).\n- **Wizard UX mandatory** — one question per turn.\n- **Reuse generation source** — scan for `type: provenance` or `identifier: slsageneration`; map `repo` → `image_path`, lowercase → PascalCase types.\n- **Verification `source.type` is PascalCase** (`Docker`) — generation uses lowercase (`docker`).\n- **`verify_attestation`** is snake_case (not `verifyAttestation`). Prefer flat `type: keyless` + `oidcProvider` (same shape as generation `attestation`).\n- Policy sets on step **`enforce.policySets`** — not `spec.policy` like SBOM enforcement.\n- List `policy_set` via MCP — do not invent identifiers.\n- **CD:** containerized step group only; see `skills\u002Fgenerate-slsa\u002Freferences\u002Fcd-containerized-step-group.md`.\n- **Do not execute pipelines** in this skill — use `\u002Frun-pipeline` after configuration (same as `\u002Fconfigure-repo-scan`).\n- Pair with `\u002Fgenerate-slsa` (generate) and `\u002Fcreate-policy` (OPA rules).\n\n---\n\n## Troubleshooting\n\n### No SLSA Generation Step\n- Add `\u002Fgenerate-slsa` first with attestation enabled (`type: provenance` in YAML).\n- Verification needs `.att` in registry or provenance in SCS Artifacts.\n- Scan for `provenance` steps — not `SlsaGeneration` (API uses `provenance`).\n\n### Attestation Verification Failed\n- Verify method must match generation (`keyless` vs `keybased`).\n- Keybased: use **public** key secret (generation uses **private** key).\n- Keyless non-harness: configure Connector for Keyless Signing.\n\n### Wrong Image \u002F No Provenance\n- Use same `image_path` as generation `repo` field.\n- Symptom: verify passes wrong artifact — image mismatch.\n\n### Policy Evaluation Failed\n- Review policy set Rego rules; check Supply Chain tab for violations.\n- Confirm policy set identifier (not display name) in `enforce.policySets`.\n\n### YAML Validation Errors\n- `source.type` must be PascalCase for verification (`Docker`, not `docker`).\n- Docker source uses `image_path`, not `repo`.\n- `verify_attestation`: use flat `type: keyless` + `spec.oidcProvider: harness` — not nested `cosign` unless API rejects flat shape.\n- `DUPLICATE_IDENTIFIER` — rename `slsaverification`.\n\n### CD Step Errors\n- Place inside `stepGroup` with `stepGroupInfra` — not top-level `execution.steps`.\n- See `skills\u002Fgenerate-slsa\u002Freferences\u002Fcd-containerized-step-group.md`.\n\n### User Chose CD on CI-Only Pipeline\n- Expected — run Phase 3b; do not force CI-only unless user changes direction.\n\n### Pipeline Run Failed\n- Use `\u002Frun-pipeline` to execute and `\u002Fdebug-pipeline` to diagnose failures\n- Confirm verify method matches generation attestation; check public key for keybased\n- Missing runtime inputs: provide branch\u002Ftag or deploy inputs via `\u002Frun-pipeline` or Harness UI Run\n\n### MCP Errors\n- `CONNECTOR_NOT_FOUND` — verify connector in Project Settings.\n- `ACCESS_DENIED` — PAT needs pipeline edit and policy read permissions.\n",{"name":5,"license":14,"metadata":23,"description":7,"compatibility":27},{"author":24,"version":25,"mcp-server":26},"Harness","1.0.0","harness-mcp-v2","Requires Harness MCP v2 server (harness-mcp-v2)","main","f3af6b6781621109871cca9e2989364afc509f3d","harnesses\u002Fharness-skills\u002Fskills\u002Fenforce-slsa","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository","https:\u002F\u002Fgithub.com\u002FAdmiralGallade","Eager to learn!\r\nI'll do anything for more knowledge anywhere.","2026-06-06 07:34:31",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add AdmiralGallade\u002Fharness-repository --skill enforce-slsa",{"tool":41,"command":42},"bunx","bunx skills add AdmiralGallade\u002Fharness-repository --skill enforce-slsa",{"tool":44,"command":45},"pnpm","pnpm dlx skills add AdmiralGallade\u002Fharness-repository --skill enforce-slsa","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fenforce-slsa\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Finteractive-wizard-flow.md","REFERENCE","参考文档",4691,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fenforce-slsa\u002Freferences\u002Finteractive-wizard-flow.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fslsa-verification-step.md",5908,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fenforce-slsa\u002Freferences\u002Fslsa-verification-step.md",[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M75JSM6WGJ71BTHM6VC8CJ1X","verify-sign","Add an Artifact Verification (SscaArtifactVerification) step to an existing Harness pipeline to verify Cosign signatures on container or local-stage artifacts. Supports CI, Security, and CD Deploy (containerized step group). Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Only works with existing pipelines. Use when asked to verify signed artifacts, verify artifact signature, verify-sign, validate Cosign signature, or configure SscaArtifactVerification. Trigger phrases: verify sign, verify artifact, artifact verification, verify signature, verify-sign, SscaArtifactVerification, verify signed image, verify Cosign, HAR verification.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fverify-sign\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M75JSDSTP77TFM3JFGBB8QKP","template-usage","Track Harness template dependencies, usage, and adoption via MCP v2 tools. Find which pipelines or other templates reference a given template, analyze update impact, identify unused templates, and compare version adoption. Use when asked about template usage, template references, template dependencies, impact analysis before updating a template, finding unused templates, or tracking template adoption across projects. Trigger phrases: template usage, who uses template, template references, template dependencies, template impact, unused templates, template adoption. Do NOT use for creating or updating templates (use create-template instead).","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Ftemplate-usage\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M75JS76Q2KC8PD598H2DZZRA","sign-artifact","Add an Artifact Signing (SscaArtifactSigning) step to an existing Harness pipeline to Cosign-sign container or local-stage artifacts with keyless, key-based, or Vault signing. Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Place after image build\u002Fpush; optionally upload .sig to the registry. Only works with existing pipelines. Use when asked to sign artifacts, add artifact signing, Cosign sign image, attach signature to registry, or configure SscaArtifactSigning. Trigger phrases: sign artifact, artifact signing, sign image, Cosign sign, add signing step, SscaArtifactSigning, attach signature, sign container image, HAR signing.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fsign-artifact\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M75JS16EEFFHA44EBNE8KWNT","sei-analytics","Advanced engineering analytics via Harness Software Engineering Insights (SEI) MCP. Configure sprint velocity and estimation accuracy tracking, engineering investment allocation breakdowns, sprint planning with capacity forecasts, and release readiness assessments. Use when asked about sprint analytics, investment allocation, sprint planning, capacity forecasting, or release readiness. Do NOT use for DORA metrics (use dora-metrics instead). Trigger phrases: sprint velocity, sprint analytics, investment allocation, capacity planning, sprint forecast, release readiness, engineering productivity, estimation accuracy, sprint planning, scope creep, code quality trends.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fsei-analytics\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M75JRWE3X3E7V9JFQ4ENZYZM","security-report","Generate security compliance reports using Harness SCS and STO via MCP. Analyze vulnerabilities, SBOMs, and manage exemptions. Use when user says \"security report\", \"vulnerabilities\", \"SBOM\", \"security scan\", \"compliance check\", or asks about application security.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fsecurity-report\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M75JRSFJSNZFZRFKX8MSPCS2","scorecard-review","Review service maturity scorecards and compliance using Harness IDP via MCP. Check production readiness, security, and documentation scores. Use when user says \"scorecard\", \"service maturity\", \"production readiness\", \"compliance score\", or asks about service health scores.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fscorecard-review\u002FSKILL.md",[],[]]