[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75C9994C8SPDP1PNBA49WTR":3,"skill-same:01M75C9994C8SPDP1PNBA49WTR":96},{"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":41,"commitSha":42,"skillDirectory":43,"forksCount":13,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M75C9994C8SPDP1PNBA49WTR","process-mapper",null,"Use when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean \u002F Six Sigma \u002F Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.","AdmiralGallade\u002Fharness-repository","AdmiralGallade","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F59243621?v=4","01M759AG0891RDPWNGJBX1Y2TG","01M759AG10MS924J53ZWJ60AEC",0,"MIT","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fbusiness-operations\u002Fskills\u002Fprocess-mapper\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: process-mapper\ndescription: Use when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean \u002F Six Sigma \u002F Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.\nversion: 2.8.0\nauthor: claude-code-skills\nlicense: MIT\ntags: [bizops, process, bpmn, bottleneck, cycle-time, lean, six-sigma, value-stream]\ncompatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]\n---\n\n# process-mapper\n\nBPMN-style business process documentation, bottleneck detection, and cycle-time analysis for internal-operations leaders.\n\n## Purpose\n\nInternal-operations work suffers from three recurring failure modes:\n\n1. **Implicit process** — the steps exist only in tribal knowledge, so handoffs drop and onboarding takes weeks.\n2. **Invisible waiting** — most of the elapsed time on any business process is queue \u002F wait \u002F approval time, not actual work; teams optimize the wrong stage.\n3. **Local optimization** — Goldratt's Theory of Constraints is ignored; resources are added to non-constraint stages, gaining nothing.\n\nThis skill produces a documented process map, identifies where work waits, and points the constraint out by name with deterministic logic — not LLM intuition.\n\n## When to use\n\n- Documenting a new business process (procurement intake, vendor onboarding, employee onboarding, incident handoff, expense reimbursement, customer onboarding, claims adjudication).\n- An existing process is \"too slow\" but nobody can name the bottleneck.\n- Cycle time is being measured but value-add ratio is not — so the team can't tell whether the process is healthy or waste-heavy.\n- Cross-functional handoffs are dropping work and root cause is unclear.\n\n## Workflow\n\nFive-step deterministic flow:\n\n1. **Intake.** Capture the process as a JSON file with one entry per stage: `name`, `owner`, `type` (`value-add` | `wait` | `rework`), `duration_minutes_p50`, `duration_minutes_p90`. Use `assets\u002Fprocess_template.md` and its JSON skeleton.\n2. **Map stages.** Run `process_documenter.py` to produce an ASCII swim-lane diagram + a normalized JSON artifact. The swim-lane separates lanes by owner so cross-functional handoffs become visible.\n3. **Measure cycle time.** Run `cycle_time_analyzer.py` to compute total P50, total P90, value-add ratio (VA%), and a Little's-Law throughput estimate. Verdict: VA% > 25% = HEALTHY, 10–25% = TYPICAL, \u003C 10% = WASTE-HEAVY.\n4. **Detect bottlenecks.** Run `bottleneck_detector.py` with the appropriate `--profile` (saas \u002F services \u002F manufacturing \u002F healthcare). Output is a ranked list with severity (CRITICAL \u002F HIGH \u002F MEDIUM), root-cause hypothesis, and one recommended action per finding.\n5. **Recommend.** Pair the bottleneck list with the cycle-time verdict; recommend a single constraint-focused intervention per Goldratt's \"subordinate everything to the constraint\" rule. Don't recommend optimization of a non-constraint stage.\n\n## Scripts\n\n**`scripts\u002Fprocess_documenter.py`** — Reads a process JSON, validates it, and emits a text-based BPMN-style swim-lane diagram in Markdown (lanes by owner, stages annotated with type + duration). Also outputs a normalized JSON artifact for downstream tools. Stdlib only. `--sample` prints a 6-stage procurement-intake example.\n\n**`scripts\u002Fbottleneck_detector.py`** — Applies three deterministic detection rules: (a) stage P50 > 2× mean of value-add stages, (b) wait-state % > 40% of total cycle, (c) rework % > 15%. Thresholds adjust by `--profile` because SaaS, services, manufacturing, and healthcare have different \"normal\" wait ratios. Output is a ranked list with severity, hypothesis, action.\n\n**`scripts\u002Fcycle_time_analyzer.py`** — Computes total P50 and P90 cycle time, value-add ratio (VA%), wait %, rework %, and a Little's-Law throughput estimate (WIP \u002F cycle time). Per Lean canon: VA% > 25% = HEALTHY, 10–25% = TYPICAL (most non-manufacturing processes land here), \u003C 10% = WASTE-HEAVY.\n\n## References\n\n- `references\u002Flean_six_sigma_canon.md` — TIMWOOD wastes, value-stream mapping, Theory of Constraints, Kanban WIP, Little's Law. Cites Womack & Jones, Rother & Shook, Goldratt, Ohno, Liker, Pyzdek, Anderson.\n- `references\u002Fbpmn_essentials.md` — Pools, lanes, gateways, events, message flows, common notation mistakes. Cites the OMG BPMN 2.0 spec, Silver, Allweyer, Freund\u002FRücker, OASIS, ISO\u002FIEC 19510:2013.\n- `references\u002Fbottleneck_anti_patterns.md` — Seven specific anti-patterns drawn from Goldratt, Kim et al., Spear, DORA, Deming, and process-mining research.\n\n## Assumptions\n\n1. The user can provide stage-level cycle-time data (even rough P50 \u002F P90 estimates). If they cannot, the first step is to instrument the process — not to map it.\n2. \"Process\" here means a repeatable business workflow with discrete stages, not a one-off project.\n3. The user has authority to act on bottlenecks (or can route findings to someone who does). Without that, the output is academic.\n4. Stage `type` is honest: a \"value-add\" stage labeled as such by the user really does change the work product from the customer's perspective. Mis-labelling waiting as value-add is the most common data-quality failure.\n\n## Anti-patterns\n\n- **Mapping every process at once.** Pick one. Goldratt: the constraint is a single point.\n- **Optimizing the non-constraint.** If stage 4 is the bottleneck, speeding up stage 2 just builds inventory in front of stage 4. Subordinate everything to the constraint.\n- **Mistaking total cycle time for processing time.** They are almost never the same; VA% reveals the gap.\n- **Adding people to a wait-bound process.** Wait time is not solved by more headcount; it's solved by removing the handoff or batch.\n- **Treating rework as a separate problem.** Rework loops belong in the process map. Hiding them understates true cycle time.\n\n## Distinct from\n\n- **business-growth skills** — external sales motion, lead-funnel conversion, customer-success retention. Process-mapper is *internal* operations.\n- **engineering\u002Fslo-architect** — system-reliability SLOs \u002F error budgets \u002F burn-rate alerts. Process-mapper is *business-process* cycle time, not system uptime.\n- **c-level-advisor (COO \u002F CEO)** — strategic prioritization of which processes to fix. Process-mapper is the tactical instrument used after that prioritization decision.\n- **project-management skills** — Jira \u002F Confluence ticket workflow tooling. Process-mapper is process *design*, not ticket *tracking*.\n\n## Forcing-question library (Matt Pocock grill discipline)\n\nBefore invoking the tools, the orchestrator (or `\u002Fcs:grill-bizops`) walks the user through these questions **one at a time, with a recommended answer + canon citation**. Never bundled.\n\n1. **\"Do you have measured cycle times for the top-3 longest stages, or only estimates?\"**\n   Recommended: insist on measured data.\n   Canon: Goldratt 1984 (*The Goal*) — optimizing estimated bottlenecks reliably attacks the wrong constraint.\n\n2. **\"Are you mapping the *current* process (as-is) or the *intended* process (to-be)?\"**\n   Recommended: map as-is first. To-be after bottleneck is identified.\n   Canon: Rother & Shook 1999 (*Learning to See*) — value-stream mapping starts with the current state, always.\n\n3. **\"Where do handoffs occur between teams, and how long does each handoff wait?\"**\n   Recommended: log every handoff with median wait time.\n   Canon: Reinertsen 2009 (*Principles of Product Development Flow*) — wait time at handoffs is the largest invisible cost.\n\n4. **\"What's your batch size at each stage?\"**\n   Recommended: drive batch size toward 1 wherever possible.\n   Canon: Anderson 2010 (*Kanban*) — batch size correlates 1:1 with cycle time variance.\n\n5. **\"What's the rework rate per stage?\"**\n   Recommended: surface it explicitly; rework loops belong in the map.\n   Canon: Pyzdek (*Six Sigma Handbook*) — hidden rework drives 30-50% of total cycle time in service processes.\n\nWalk depth-first. Don't open question 4 before 1-3 are answered. After all 5 are locked, invoke `process_documenter.py` → `bottleneck_detector.py` → `cycle_time_analyzer.py` in sequence.\n","# process-mapper\n\nBPMN-style business process documentation, bottleneck detection, and cycle-time analysis for internal-operations leaders.\n\n## Purpose\n\nInternal-operations work suffers from three recurring failure modes:\n\n1. **Implicit process** — the steps exist only in tribal knowledge, so handoffs drop and onboarding takes weeks.\n2. **Invisible waiting** — most of the elapsed time on any business process is queue \u002F wait \u002F approval time, not actual work; teams optimize the wrong stage.\n3. **Local optimization** — Goldratt's Theory of Constraints is ignored; resources are added to non-constraint stages, gaining nothing.\n\nThis skill produces a documented process map, identifies where work waits, and points the constraint out by name with deterministic logic — not LLM intuition.\n\n## When to use\n\n- Documenting a new business process (procurement intake, vendor onboarding, employee onboarding, incident handoff, expense reimbursement, customer onboarding, claims adjudication).\n- An existing process is \"too slow\" but nobody can name the bottleneck.\n- Cycle time is being measured but value-add ratio is not — so the team can't tell whether the process is healthy or waste-heavy.\n- Cross-functional handoffs are dropping work and root cause is unclear.\n\n## Workflow\n\nFive-step deterministic flow:\n\n1. **Intake.** Capture the process as a JSON file with one entry per stage: `name`, `owner`, `type` (`value-add` | `wait` | `rework`), `duration_minutes_p50`, `duration_minutes_p90`. Use `assets\u002Fprocess_template.md` and its JSON skeleton.\n2. **Map stages.** Run `process_documenter.py` to produce an ASCII swim-lane diagram + a normalized JSON artifact. The swim-lane separates lanes by owner so cross-functional handoffs become visible.\n3. **Measure cycle time.** Run `cycle_time_analyzer.py` to compute total P50, total P90, value-add ratio (VA%), and a Little's-Law throughput estimate. Verdict: VA% > 25% = HEALTHY, 10–25% = TYPICAL, \u003C 10% = WASTE-HEAVY.\n4. **Detect bottlenecks.** Run `bottleneck_detector.py` with the appropriate `--profile` (saas \u002F services \u002F manufacturing \u002F healthcare). Output is a ranked list with severity (CRITICAL \u002F HIGH \u002F MEDIUM), root-cause hypothesis, and one recommended action per finding.\n5. **Recommend.** Pair the bottleneck list with the cycle-time verdict; recommend a single constraint-focused intervention per Goldratt's \"subordinate everything to the constraint\" rule. Don't recommend optimization of a non-constraint stage.\n\n## Scripts\n\n**`scripts\u002Fprocess_documenter.py`** — Reads a process JSON, validates it, and emits a text-based BPMN-style swim-lane diagram in Markdown (lanes by owner, stages annotated with type + duration). Also outputs a normalized JSON artifact for downstream tools. Stdlib only. `--sample` prints a 6-stage procurement-intake example.\n\n**`scripts\u002Fbottleneck_detector.py`** — Applies three deterministic detection rules: (a) stage P50 > 2× mean of value-add stages, (b) wait-state % > 40% of total cycle, (c) rework % > 15%. Thresholds adjust by `--profile` because SaaS, services, manufacturing, and healthcare have different \"normal\" wait ratios. Output is a ranked list with severity, hypothesis, action.\n\n**`scripts\u002Fcycle_time_analyzer.py`** — Computes total P50 and P90 cycle time, value-add ratio (VA%), wait %, rework %, and a Little's-Law throughput estimate (WIP \u002F cycle time). Per Lean canon: VA% > 25% = HEALTHY, 10–25% = TYPICAL (most non-manufacturing processes land here), \u003C 10% = WASTE-HEAVY.\n\n## References\n\n- `references\u002Flean_six_sigma_canon.md` — TIMWOOD wastes, value-stream mapping, Theory of Constraints, Kanban WIP, Little's Law. Cites Womack & Jones, Rother & Shook, Goldratt, Ohno, Liker, Pyzdek, Anderson.\n- `references\u002Fbpmn_essentials.md` — Pools, lanes, gateways, events, message flows, common notation mistakes. Cites the OMG BPMN 2.0 spec, Silver, Allweyer, Freund\u002FRücker, OASIS, ISO\u002FIEC 19510:2013.\n- `references\u002Fbottleneck_anti_patterns.md` — Seven specific anti-patterns drawn from Goldratt, Kim et al., Spear, DORA, Deming, and process-mining research.\n\n## Assumptions\n\n1. The user can provide stage-level cycle-time data (even rough P50 \u002F P90 estimates). If they cannot, the first step is to instrument the process — not to map it.\n2. \"Process\" here means a repeatable business workflow with discrete stages, not a one-off project.\n3. The user has authority to act on bottlenecks (or can route findings to someone who does). Without that, the output is academic.\n4. Stage `type` is honest: a \"value-add\" stage labeled as such by the user really does change the work product from the customer's perspective. Mis-labelling waiting as value-add is the most common data-quality failure.\n\n## Anti-patterns\n\n- **Mapping every process at once.** Pick one. Goldratt: the constraint is a single point.\n- **Optimizing the non-constraint.** If stage 4 is the bottleneck, speeding up stage 2 just builds inventory in front of stage 4. Subordinate everything to the constraint.\n- **Mistaking total cycle time for processing time.** They are almost never the same; VA% reveals the gap.\n- **Adding people to a wait-bound process.** Wait time is not solved by more headcount; it's solved by removing the handoff or batch.\n- **Treating rework as a separate problem.** Rework loops belong in the process map. Hiding them understates true cycle time.\n\n## Distinct from\n\n- **business-growth skills** — external sales motion, lead-funnel conversion, customer-success retention. Process-mapper is *internal* operations.\n- **engineering\u002Fslo-architect** — system-reliability SLOs \u002F error budgets \u002F burn-rate alerts. Process-mapper is *business-process* cycle time, not system uptime.\n- **c-level-advisor (COO \u002F CEO)** — strategic prioritization of which processes to fix. Process-mapper is the tactical instrument used after that prioritization decision.\n- **project-management skills** — Jira \u002F Confluence ticket workflow tooling. Process-mapper is process *design*, not ticket *tracking*.\n\n## Forcing-question library (Matt Pocock grill discipline)\n\nBefore invoking the tools, the orchestrator (or `\u002Fcs:grill-bizops`) walks the user through these questions **one at a time, with a recommended answer + canon citation**. Never bundled.\n\n1. **\"Do you have measured cycle times for the top-3 longest stages, or only estimates?\"**\n   Recommended: insist on measured data.\n   Canon: Goldratt 1984 (*The Goal*) — optimizing estimated bottlenecks reliably attacks the wrong constraint.\n\n2. **\"Are you mapping the *current* process (as-is) or the *intended* process (to-be)?\"**\n   Recommended: map as-is first. To-be after bottleneck is identified.\n   Canon: Rother & Shook 1999 (*Learning to See*) — value-stream mapping starts with the current state, always.\n\n3. **\"Where do handoffs occur between teams, and how long does each handoff wait?\"**\n   Recommended: log every handoff with median wait time.\n   Canon: Reinertsen 2009 (*Principles of Product Development Flow*) — wait time at handoffs is the largest invisible cost.\n\n4. **\"What's your batch size at each stage?\"**\n   Recommended: drive batch size toward 1 wherever possible.\n   Canon: Anderson 2010 (*Kanban*) — batch size correlates 1:1 with cycle time variance.\n\n5. **\"What's the rework rate per stage?\"**\n   Recommended: surface it explicitly; rework loops belong in the map.\n   Canon: Pyzdek (*Six Sigma Handbook*) — hidden rework drives 30-50% of total cycle time in service processes.\n\nWalk depth-first. Don't open question 4 before 1-3 are answered. After all 5 are locked, invoke `process_documenter.py` → `bottleneck_detector.py` → `cycle_time_analyzer.py` in sequence.\n",{"name":5,"tags":23,"author":32,"license":14,"version":33,"description":7,"compatible_tools":34},[24,25,26,27,28,29,30,31],"bizops","process","bpmn","bottleneck","cycle-time","lean","six-sigma","value-stream","claude-code-skills","2.8.0",[35,36,37,38,39,40],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","f3af6b6781621109871cca9e2989364afc509f3d","harnesses\u002Fclaude-skills\u002Fbusiness-operations\u002Fskills\u002Fprocess-mapper","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":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add AdmiralGallade\u002Fharness-repository --skill process-mapper",{"tool":54,"command":55},"bunx","bunx skills add AdmiralGallade\u002Fharness-repository --skill process-mapper",{"tool":57,"command":58},"pnpm","pnpm dlx skills add AdmiralGallade\u002Fharness-repository --skill process-mapper","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fbusiness-operations\u002Fskills\u002Fprocess-mapper\u002FSKILL.md",true,[62,68,74,78,82,88,92],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"assets\u002Fprocess_template.md","ASSET","资产文件",4333,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fbusiness-operations\u002Fskills\u002Fprocess-mapper\u002Fassets\u002Fprocess_template.md",{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fbottleneck_anti_patterns.md","REFERENCE","参考文档",7800,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fbusiness-operations\u002Fskills\u002Fprocess-mapper\u002Freferences\u002Fbottleneck_anti_patterns.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fbpmn_essentials.md",6491,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fbusiness-operations\u002Fskills\u002Fprocess-mapper\u002Freferences\u002Fbpmn_essentials.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Flean_six_sigma_canon.md",6569,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fbusiness-operations\u002Fskills\u002Fprocess-mapper\u002Freferences\u002Flean_six_sigma_canon.md",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Fbottleneck_detector.py","SCRIPT","脚本",11051,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fbusiness-operations\u002Fskills\u002Fprocess-mapper\u002Fscripts\u002Fbottleneck_detector.py",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Fcycle_time_analyzer.py",8559,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fbusiness-operations\u002Fskills\u002Fprocess-mapper\u002Fscripts\u002Fcycle_time_analyzer.py",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"scripts\u002Fprocess_documenter.py",9145,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fbusiness-operations\u002Fskills\u002Fprocess-mapper\u002Fscripts\u002Fprocess_documenter.py",[97,105,112,119,126,133],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fverify-sign\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"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":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"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":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"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":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"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",[],[]]