[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75JG99GD079G5PPM804HR61":3,"skill-same:01M75JG99GD079G5PPM804HR61":55},{"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},"01M75JG99GD079G5PPM804HR61","create-agent-template",null,"Generate Harness Agent Template files for AI-powered automation agents. Produces metadata.json, pipeline.yaml (v1 syntax), and wiki.MD files. Agents automate tasks like code review, security scanning, test generation, and documentation. This is a YAML generation skill. Use when asked to create an agent template, build an AI agent, create an automation agent, generate agent pipeline files, or set up a Harness agent. Trigger phrases: create agent template, agent template, AI agent, automation agent, build agent, code review agent, security scanner agent, Harness agent.","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\u002Fcreate-agent-template\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: create-agent-template\ndescription: >-\n  Generate Harness Agent Template files for AI-powered automation agents. Produces metadata.json,\n  pipeline.yaml (v1 syntax), and wiki.MD files. Agents automate tasks like code review, security\n  scanning, test generation, and documentation. This is a YAML generation skill. Use when asked to\n  create an agent template, build an AI agent, create an automation agent, generate agent pipeline\n  files, or set up a Harness agent. Trigger phrases: create agent template, agent template, AI agent,\n  automation agent, build agent, code review agent, security scanner agent, Harness agent.\nmetadata:\n  author: Harness\n  mcp-server: harness-mcp-v2\n  version: 1.0.0\nlicense: Apache-2.0\ncompatibility: No MCP server required. Generates YAML files locally.\n---\n\n# Create Agent Template Skill\n\nGenerate Harness Agent Template files for AI-powered automation agents.\n\n## Instructions\n\n1. **Identify the agent's purpose** - What task should the agent automate (code review, security scanning, test generation, documentation)?\n2. **Define inputs and configuration** - What parameters does the agent need (repo, branch, connector, secrets)?\n3. **Generate three files** - metadata.json (template metadata), pipeline.yaml (v1 syntax), and wiki.MD (user documentation)\n4. **Validate consistency** - Ensure input references in pipeline.yaml match definitions in metadata.json\n\n## Overview\n\nAgent templates are modular pipeline definitions that encapsulate AI-powered automation. Each template produces three files:\n\n| File | Required | Purpose |\n|------|----------|---------|\n| `metadata.json` | Yes | Template name, description, version |\n| `pipeline.yaml` | Yes | Pipeline definition (v1 syntax) |\n| `wiki.MD` | Recommended | User-facing documentation |\n\n## Directory Structure\n\n```\ntemplates\u002F\u003Cagent-name>\u002F\n  metadata.json\n  pipeline.yaml\n  wiki.MD\n```\n\n## metadata.json\n\n```json\n{\n  \"name\": \"Agent Name\",\n  \"description\": \"Brief description of what this agent does (1-2 sentences)\",\n  \"version\": \"1.0.0\"\n}\n```\n\n**Rules:**\n- `name`: Sentence Case (`Code Review`, not `code-review`)\n- `description`: Under 200 characters, clear value proposition\n- `version`: Semantic versioning `MAJOR.MINOR.PATCH`\n\n## pipeline.yaml\n\n### Core Structure\n\n```yaml\nversion: 1\npipeline:\n  clone:\n    depth: 1\n    ref:\n      name: \u003C+inputs.branch>\n      type: branch\n    repo: \u003C+inputs.repo>\n    connector: \"\u003C+inputs.gitConnector != null ? inputs.gitConnector.id : ''>\"\n\n  stages:\n    - name: \u003Cstage-name>\n      steps:\n        - name: \u003Cstep-name>\n          run:\n            container:\n              image: \u003Cregistry>\u002F\u003Cimage>:\u003Ctag>\n            with:\n              param: value\n            env:\n              SECRET_VAR: \u003C+inputs.secretInput>\n      platform:\n        os: linux\n        arch: arm64\n\n  inputs:\n    repo:\n      type: string\n      required: true\n    branch:\n      type: string\n      default: main\n    llmConnector:\n      type: connector\n    gitConnector:\n      type: connector\n```\n\n### Clone Configurations\n\n**Branch clone:**\n\n```yaml\nclone:\n  depth: 1\n  ref:\n    name: \u003C+inputs.branch>\n    type: branch\n  repo: \u003C+inputs.repo>\n  connector: \"\u003C+inputs.gitConnector != null ? inputs.gitConnector.id : ''>\"\n```\n\n**Pull request clone:**\n\n```yaml\nclone:\n  depth: 1000\n  ref:\n    type: pull-request\n    number: \u003C+inputs.pullReq>\n  repo: \u003C+inputs.repo>\n```\n\n### Input Types\n\n| Type | Usage | Example |\n|------|-------|---------|\n| `string` | Text values | repo name, branch, file paths |\n| `secret` | Sensitive values | API keys, tokens |\n| `connector` | Harness connectors | Git connector, LLM connector |\n\n```yaml\ninputs:\n  repo:\n    type: string\n    required: true\n  branch:\n    type: string\n    default: main\n    description: Branch to analyze\n  apiKey:\n    type: secret\n    default: account.my_secret\n  llmConnector:\n    type: connector\n    description: LLM provider connector\n  gitConnector:\n    type: connector\n    description: Git repository connector\n```\n\n### Step Types\n\n**Container plugin step:**\n\n```yaml\n- name: my-step\n  run:\n    container:\n      image: registry\u002Fimage:tag\n    with:\n      plugin_param: value\n    env:\n      API_KEY: \u003C+inputs.apiKey>\n```\n\n**Shell script step:**\n\n```yaml\n- name: shell-step\n  run:\n    shell: bash\n    script: |-\n      echo \"Running script\"\n      git add -A\n      git diff --cached\n    env:\n      MY_VAR: value\n```\n\n### Expression Syntax\n\n```yaml\n# Input references\n\u003C+inputs.variableName>\n\n# Connector token\n\u003C+inputs.connectorName.token>\n\n# Step outputs\n\u003C+pipeline.stages.STAGE.steps.STEP.output.outputVariables.VAR>\n\n# Environment variables\n\u003C+env.HARNESS_ACCOUNT_ID>\n\u003C+env.HARNESS_ORG_ID>\n\u003C+env.HARNESS_PROJECT_ID>\n\n# Alternative syntax for inputs in env blocks\n${{inputs.repo}}\n```\n\n## wiki.MD\n\n```markdown\n# Agent Name\n\n**Version:** 1.0.0\n**Name:** Agent Name\n\n## Overview\n\nWhat this agent does and why it is useful.\n\n---\n\n## Key Capabilities\n\n- **Capability 1**: Description\n- **Capability 2**: Description\n\n---\n\n## How It Works\n\n1. **Step 1**: Description\n2. **Step 2**: Description\n3. **Step 3**: Description\n\n## Required Inputs\n\n| Input | Type | Description | Default |\n|-------|------|-------------|---------|\n| `repo` | string | Repository identifier | -- |\n| `branch` | string | Branch to analyze | main |\n\n## Usage Example\n\n\\`\\`\\`yaml\ninputs:\n  repo: \"my-org\u002Fmy-repo\"\n  branch: \"main\"\n\\`\\`\\`\n\n## Troubleshooting\n\n### Common Issue 1\nSolution description.\n```\n\n## Complete Examples and Common Patterns\n\nFor complete agent examples (Code Review, Security Scanner, Documentation Generator) and reusable patterns (SCM detection, coding agent, PR creation), consult references\u002Fagent-examples.md.\n\n## Examples\n\n### Create a code review agent\n\n```\n\u002Fcreate-agent-template\nCreate an agent template for code review that analyzes pull requests,\nprovides feedback, and posts review comments\n```\n\n### Create a security scanner agent\n\n```\n\u002Fcreate-agent-template\nGenerate a security scanner agent that finds vulnerabilities and\ncreates a report\n```\n\n### Create a documentation generator\n\n```\n\u002Fcreate-agent-template\nCreate an agent that analyzes a codebase and generates documentation,\nthen opens a PR with the results\n```\n\n### Create a test generator\n\n```\n\u002Fcreate-agent-template\nBuild an agent template that generates unit tests to improve code coverage\n```\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Invalid metadata | Missing name, description, or version | Include all three required fields |\n| Invalid version | Not semver format | Use `MAJOR.MINOR.PATCH` (e.g., `1.0.0`) |\n| Pipeline validation error | Invalid v1 YAML syntax | Verify pipeline structure follows v1 schema |\n| Connector not found | Referenced connector does not exist | Create the connector before running the agent |\n| Undefined input reference | `\u003C+inputs.x>` used but `x` not defined in inputs | Add missing input definition |\n\n## Performance Notes\n\n- Validate all three generated files (metadata.json, pipeline.yaml, wiki.MD) are consistent with each other.\n- Ensure the pipeline YAML uses correct v1 syntax with lowercase types and ${{ }} expressions.\n- Test that all input references in the pipeline match the inputs defined in metadata.json.\n\n## Troubleshooting\n\n### Agent Not Executing\n\n1. Verify all `required: true` inputs have values\n2. Check connector inputs are valid and accessible\n3. Confirm container images exist and are accessible from the build infrastructure\n\n### SCM Provider Detection Failing\n\n1. Verify `DRONE_REPO_SCM` environment variable is available\n2. Check that connector tokens have correct permissions\n3. Test with a known SCM provider before adding multi-provider logic\n\n### PR Creation Failing\n\n1. Confirm git changes exist (`git diff --cached` is non-empty)\n2. Verify the token has write access to create branches and PRs\n3. Check that `PLUGIN_REPO` format matches the SCM provider expectations\n\n### Output Variables Not Available\n\n1. Write outputs using `echo \"KEY=value\" >> $DRONE_OUTPUT`\n2. Write secret outputs using `echo \"KEY=value\" >> $HARNESS_OUTPUT_SECRET_FILE`\n3. Reference with full path: `\u003C+pipeline.stages.STAGE.steps.STEP.output.outputVariables.KEY>`\n\n## Best Practices\n\n- Never hardcode secrets -- use `type: secret` inputs\n- Use `type: connector` for authentication rather than raw tokens\n- Include meaningful descriptions on all inputs\n- Keep stages focused on single responsibilities\n- Always include the SCM detection pattern for multi-provider support\n- Store secret outputs with `$HARNESS_OUTPUT_SECRET_FILE`, not `$DRONE_OUTPUT`\n- Set `depth: 1000` for PR clones to ensure full diff history\n- Set `depth: 1` for branch clones to minimize clone time\n","# Create Agent Template Skill\n\nGenerate Harness Agent Template files for AI-powered automation agents.\n\n## Instructions\n\n1. **Identify the agent's purpose** - What task should the agent automate (code review, security scanning, test generation, documentation)?\n2. **Define inputs and configuration** - What parameters does the agent need (repo, branch, connector, secrets)?\n3. **Generate three files** - metadata.json (template metadata), pipeline.yaml (v1 syntax), and wiki.MD (user documentation)\n4. **Validate consistency** - Ensure input references in pipeline.yaml match definitions in metadata.json\n\n## Overview\n\nAgent templates are modular pipeline definitions that encapsulate AI-powered automation. Each template produces three files:\n\n| File | Required | Purpose |\n|------|----------|---------|\n| `metadata.json` | Yes | Template name, description, version |\n| `pipeline.yaml` | Yes | Pipeline definition (v1 syntax) |\n| `wiki.MD` | Recommended | User-facing documentation |\n\n## Directory Structure\n\n```\ntemplates\u002F\u003Cagent-name>\u002F\n  metadata.json\n  pipeline.yaml\n  wiki.MD\n```\n\n## metadata.json\n\n```json\n{\n  \"name\": \"Agent Name\",\n  \"description\": \"Brief description of what this agent does (1-2 sentences)\",\n  \"version\": \"1.0.0\"\n}\n```\n\n**Rules:**\n- `name`: Sentence Case (`Code Review`, not `code-review`)\n- `description`: Under 200 characters, clear value proposition\n- `version`: Semantic versioning `MAJOR.MINOR.PATCH`\n\n## pipeline.yaml\n\n### Core Structure\n\n```yaml\nversion: 1\npipeline:\n  clone:\n    depth: 1\n    ref:\n      name: \u003C+inputs.branch>\n      type: branch\n    repo: \u003C+inputs.repo>\n    connector: \"\u003C+inputs.gitConnector != null ? inputs.gitConnector.id : ''>\"\n\n  stages:\n    - name: \u003Cstage-name>\n      steps:\n        - name: \u003Cstep-name>\n          run:\n            container:\n              image: \u003Cregistry>\u002F\u003Cimage>:\u003Ctag>\n            with:\n              param: value\n            env:\n              SECRET_VAR: \u003C+inputs.secretInput>\n      platform:\n        os: linux\n        arch: arm64\n\n  inputs:\n    repo:\n      type: string\n      required: true\n    branch:\n      type: string\n      default: main\n    llmConnector:\n      type: connector\n    gitConnector:\n      type: connector\n```\n\n### Clone Configurations\n\n**Branch clone:**\n\n```yaml\nclone:\n  depth: 1\n  ref:\n    name: \u003C+inputs.branch>\n    type: branch\n  repo: \u003C+inputs.repo>\n  connector: \"\u003C+inputs.gitConnector != null ? inputs.gitConnector.id : ''>\"\n```\n\n**Pull request clone:**\n\n```yaml\nclone:\n  depth: 1000\n  ref:\n    type: pull-request\n    number: \u003C+inputs.pullReq>\n  repo: \u003C+inputs.repo>\n```\n\n### Input Types\n\n| Type | Usage | Example |\n|------|-------|---------|\n| `string` | Text values | repo name, branch, file paths |\n| `secret` | Sensitive values | API keys, tokens |\n| `connector` | Harness connectors | Git connector, LLM connector |\n\n```yaml\ninputs:\n  repo:\n    type: string\n    required: true\n  branch:\n    type: string\n    default: main\n    description: Branch to analyze\n  apiKey:\n    type: secret\n    default: account.my_secret\n  llmConnector:\n    type: connector\n    description: LLM provider connector\n  gitConnector:\n    type: connector\n    description: Git repository connector\n```\n\n### Step Types\n\n**Container plugin step:**\n\n```yaml\n- name: my-step\n  run:\n    container:\n      image: registry\u002Fimage:tag\n    with:\n      plugin_param: value\n    env:\n      API_KEY: \u003C+inputs.apiKey>\n```\n\n**Shell script step:**\n\n```yaml\n- name: shell-step\n  run:\n    shell: bash\n    script: |-\n      echo \"Running script\"\n      git add -A\n      git diff --cached\n    env:\n      MY_VAR: value\n```\n\n### Expression Syntax\n\n```yaml\n# Input references\n\u003C+inputs.variableName>\n\n# Connector token\n\u003C+inputs.connectorName.token>\n\n# Step outputs\n\u003C+pipeline.stages.STAGE.steps.STEP.output.outputVariables.VAR>\n\n# Environment variables\n\u003C+env.HARNESS_ACCOUNT_ID>\n\u003C+env.HARNESS_ORG_ID>\n\u003C+env.HARNESS_PROJECT_ID>\n\n# Alternative syntax for inputs in env blocks\n${{inputs.repo}}\n```\n\n## wiki.MD\n\n```markdown\n# Agent Name\n\n**Version:** 1.0.0\n**Name:** Agent Name\n\n## Overview\n\nWhat this agent does and why it is useful.\n\n---\n\n## Key Capabilities\n\n- **Capability 1**: Description\n- **Capability 2**: Description\n\n---\n\n## How It Works\n\n1. **Step 1**: Description\n2. **Step 2**: Description\n3. **Step 3**: Description\n\n## Required Inputs\n\n| Input | Type | Description | Default |\n|-------|------|-------------|---------|\n| `repo` | string | Repository identifier | -- |\n| `branch` | string | Branch to analyze | main |\n\n## Usage Example\n\n\\`\\`\\`yaml\ninputs:\n  repo: \"my-org\u002Fmy-repo\"\n  branch: \"main\"\n\\`\\`\\`\n\n## Troubleshooting\n\n### Common Issue 1\nSolution description.\n```\n\n## Complete Examples and Common Patterns\n\nFor complete agent examples (Code Review, Security Scanner, Documentation Generator) and reusable patterns (SCM detection, coding agent, PR creation), consult references\u002Fagent-examples.md.\n\n## Examples\n\n### Create a code review agent\n\n```\n\u002Fcreate-agent-template\nCreate an agent template for code review that analyzes pull requests,\nprovides feedback, and posts review comments\n```\n\n### Create a security scanner agent\n\n```\n\u002Fcreate-agent-template\nGenerate a security scanner agent that finds vulnerabilities and\ncreates a report\n```\n\n### Create a documentation generator\n\n```\n\u002Fcreate-agent-template\nCreate an agent that analyzes a codebase and generates documentation,\nthen opens a PR with the results\n```\n\n### Create a test generator\n\n```\n\u002Fcreate-agent-template\nBuild an agent template that generates unit tests to improve code coverage\n```\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Invalid metadata | Missing name, description, or version | Include all three required fields |\n| Invalid version | Not semver format | Use `MAJOR.MINOR.PATCH` (e.g., `1.0.0`) |\n| Pipeline validation error | Invalid v1 YAML syntax | Verify pipeline structure follows v1 schema |\n| Connector not found | Referenced connector does not exist | Create the connector before running the agent |\n| Undefined input reference | `\u003C+inputs.x>` used but `x` not defined in inputs | Add missing input definition |\n\n## Performance Notes\n\n- Validate all three generated files (metadata.json, pipeline.yaml, wiki.MD) are consistent with each other.\n- Ensure the pipeline YAML uses correct v1 syntax with lowercase types and ${{ }} expressions.\n- Test that all input references in the pipeline match the inputs defined in metadata.json.\n\n## Troubleshooting\n\n### Agent Not Executing\n\n1. Verify all `required: true` inputs have values\n2. Check connector inputs are valid and accessible\n3. Confirm container images exist and are accessible from the build infrastructure\n\n### SCM Provider Detection Failing\n\n1. Verify `DRONE_REPO_SCM` environment variable is available\n2. Check that connector tokens have correct permissions\n3. Test with a known SCM provider before adding multi-provider logic\n\n### PR Creation Failing\n\n1. Confirm git changes exist (`git diff --cached` is non-empty)\n2. Verify the token has write access to create branches and PRs\n3. Check that `PLUGIN_REPO` format matches the SCM provider expectations\n\n### Output Variables Not Available\n\n1. Write outputs using `echo \"KEY=value\" >> $DRONE_OUTPUT`\n2. Write secret outputs using `echo \"KEY=value\" >> $HARNESS_OUTPUT_SECRET_FILE`\n3. Reference with full path: `\u003C+pipeline.stages.STAGE.steps.STEP.output.outputVariables.KEY>`\n\n## Best Practices\n\n- Never hardcode secrets -- use `type: secret` inputs\n- Use `type: connector` for authentication rather than raw tokens\n- Include meaningful descriptions on all inputs\n- Keep stages focused on single responsibilities\n- Always include the SCM detection pattern for multi-provider support\n- Store secret outputs with `$HARNESS_OUTPUT_SECRET_FILE`, not `$DRONE_OUTPUT`\n- Set `depth: 1000` for PR clones to ensure full diff history\n- Set `depth: 1` for branch clones to minimize clone time\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","No MCP server required. Generates YAML files locally.","main","f3af6b6781621109871cca9e2989364afc509f3d","harnesses\u002Fharness-skills\u002Fskills\u002Fcreate-agent-template","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 create-agent-template",{"tool":41,"command":42},"bunx","bunx skills add AdmiralGallade\u002Fharness-repository --skill create-agent-template",{"tool":44,"command":45},"pnpm","pnpm dlx skills add AdmiralGallade\u002Fharness-repository --skill create-agent-template","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fcreate-agent-template\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fagent-examples.md","REFERENCE","参考文档",10534,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fcreate-agent-template\u002Freferences\u002Fagent-examples.md",[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"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":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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",[],[]]