ワンクリックでManusで任意のスキルを実行

$pwd:

create-secret

Name: Create Secret
Author: thisrohangupta

// Generate Harness Secret definitions and manage secrets via MCP v2 tools. Supports SecretText, SecretFile, SSHKey, and WinRmCredentials types with configurable secret managers (Harness built-in, HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, GCP Secret Manager). Use when asked to create a secret, store credentials, manage API keys, set up SSH keys, configure WinRM credentials, rotate secrets, or reference secrets in pipelines. Trigger phrases: create secret, secret text, secret file, SSH key, API key, password, credentials, secret manager, store secret.

Manusで実行

$ git log --oneline --stat

stars:1

forks:0

updated:2026年4月16日 23:31

ファイルエクスプローラー

2 ファイル

SKILL.md

readonly

related-skills.json

同じリポジトリ

manage-freeze-windows.md

from "thisrohangupta/cursor-harness-plugin"

Manage Harness deployment freeze windows via MCP. Create, list, get, update, and delete project-level freeze windows; toggle them Enabled/Disabled; and get or enable/disable the project-level global freeze. Use when asked about freeze windows, deployment freezes, change freezes, release blackouts, maintenance windows, holiday freezes, or to pause deployments. Trigger phrases: freeze window, deployment freeze, change freeze, release blackout, maintenance window, holiday freeze, pause deployments, block pipeline execution, global freeze.

2026-04-161

manage-pull-requests.md

from "thisrohangupta/cursor-harness-plugin"

Manage Harness Code pull requests via MCP. List, create, update, and merge PRs; add reviewers and submit review decisions (approve / request changes); post, update, and delete comments; read the discussion timeline; and check CI status. Use when asked to open a PR, merge a PR, approve a PR, leave a code review comment, request changes, assign reviewers, or inspect PR checks and activity. Trigger phrases: pull request, PR review, merge PR, approve PR, request changes, add reviewer, PR comments, PR checks, PR activity, code review.

2026-04-161

audit-report.md

from "thisrohangupta/cursor-harness-plugin"

Generate audit reports and compliance trails using Harness audit trail data via MCP v2 tools. Track user actions, resource changes, authentication events, and access patterns across accounts, organizations, and projects. Use when asked to audit activity, generate compliance reports, investigate security incidents, review user actions, check change logs, or produce SOC2/GDPR/HIPAA audit evidence. Trigger phrases: audit report, audit trail, compliance audit, user activity log, change log, access audit, security investigation, who changed what, audit events.

2026-04-161

create-pipeline.md

from "thisrohangupta/cursor-harness-plugin"

Generate Harness v0 Pipeline YAML for CI/CD workflows and create them via MCP. Supports CI stages (build, test, Docker push), CD stages (Kubernetes, Helm, ECS, serverless), approval gates, parallel execution, matrix strategies, and failure rollback. Use when asked to create a pipeline, build pipeline, deployment pipeline, CI/CD workflow, or set up Harness pipelines. Do NOT use for v1 simplified pipelines (use create-pipeline-v1). Trigger phrases: create pipeline, build pipeline, deployment pipeline, CI/CD, Harness pipeline, Kubernetes deploy pipeline.

2026-04-161

create-pipeline-v1.md

from "thisrohangupta/cursor-harness-plugin"

Generate Harness v1 simplified Pipeline YAML using the new concise syntax with flat structure, ${{ }} expressions, script field, and action steps. Supports CI stages (run, run-test, background), CD stages (service/environment with action steps for K8s, Helm, ECS), approval (stage-level and inline), parallel execution, matrix/for/while strategies, caching, volumes, and templates. Use when asked for a v1 pipeline, simplified pipeline, new pipeline format, or when user specifically requests v1 syntax. Do NOT use for v0/standard pipelines (use create-pipeline). Trigger phrases: v1 pipeline, simplified pipeline, new pipeline format, create v1, modern pipeline syntax.

2026-04-161

manage-roles.md

from "thisrohangupta/cursor-harness-plugin"

Manage Harness RBAC roles, role assignments, permissions, and resource groups via MCP v2 tools. List, create, update, and delete custom roles. View role assignments and permissions for users, groups, and service accounts. Use when asked to manage access control, assign roles, check permissions, create custom roles, review RBAC configuration, onboard users, or audit access. Trigger phrases: manage roles, RBAC, role assignment, user permissions, access control, custom role, resource group, who has access, grant access, revoke access.

2026-04-161

package.json

"author": "thisrohangupta"

"repository": "thisrohangupta/cursor-harness-plugin"

GitHub リポジトリを開く Creator のリポジトリを見る

$ install --global

$ download --local

Manusで実行

$ useful --forSOC

情報セキュリティアナリストコンピュータ・数学職15-1212L4

name	create-secret
description	Generate Harness Secret definitions and manage secrets via MCP v2 tools. Supports SecretText, SecretFile, SSHKey, and WinRmCredentials types with configurable secret managers (Harness built-in, HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, GCP Secret Manager). Use when asked to create a secret, store credentials, manage API keys, set up SSH keys, configure WinRM credentials, rotate secrets, or reference secrets in pipelines. Trigger phrases: create secret, secret text, secret file, SSH key, API key, password, credentials, secret manager, store secret.
metadata	{"author":"Harness","version":"1.0.0","mcp-server":"harness-mcp-v2"}
license	Apache-2.0
compatibility	Requires Harness MCP v2 server (harness-mcp-v2)

Create Secret Skill

Generate Harness Secret definitions and manage secrets via MCP v2 tools.

MCP v2 Tools Used

Tool	Resource Type	Purpose
`harness_list`	`secret`	List existing secrets
`harness_get`	`secret`	Get secret metadata (not the value)
`harness_create`	`secret`	Create a new secret
`harness_update`	`secret`	Update secret metadata or value
`harness_delete`	`secret`	Delete a secret
`harness_describe`	`secret`	List supported operations, filters, and scope expectations for secrets
`harness_schema`	`secret`	Get the exact JSON Schema for `create`/`update` secret bodies

Secret Types

SecretText

Stores text-based secrets: passwords, API tokens, connection strings.

secret:
  identifier: my_api_key
  name: My API Key
  description: API key for external service
  type: SecretText
  spec:
    secretManagerIdentifier: harnessSecretManager
    valueType: Inline
    value: <secret_value>

For other secret types (SecretFile, SSHKey with KeyReference/KeyPath/Password, WinRmCredentials with NTLM/Kerberos) and secret manager configuration, consult references/secret-types.md.

Secret Scopes

Scope	Visibility	MCP Parameters
Project	Only within the project	`org_id` + `project_id`
Organization	All projects in the org	`org_id` only
Account	All orgs and projects	Neither org_id nor project_id

Instructions

Step 1: Determine Requirements

Secret type: SecretText, SecretFile, SSHKey, or WinRmCredentials
Secret manager: Harness built-in or external
Scope: project, org, or account
Tags and description for organization

Step 2: Check for Existing Secrets

harness_list(
  resource_type="secret",
  org_id="<org>",
  project_id="<project>",
  search_term="<keyword>"
)

Step 3: Create the Secret

harness_create(
  resource_type="secret",
  org_id="<org>",
  project_id="<project>",
  body={
    "secret": {
      "identifier": "my_api_key",
      "name": "My API Key",
      "type": "SecretText",
      "spec": {
        "secret_manager_identifier": "harnessSecretManager",
        "value_type": "Inline",
        "value": "<value>"
      }
    }
  }
)

Step 4: Verify Creation

harness_get(
  resource_type="secret",
  resource_id="my_api_key",
  org_id="<org>",
  project_id="<project>"
)

Referencing Secrets in Pipelines

# Project-level secret
<+secrets.getValue("my_api_key")>

# Org-level secret
<+secrets.getValue("org.my_api_key")>

# Account-level secret
<+secrets.getValue("account.my_api_key")>

In connector configuration:

connector:
  spec:
    authentication:
      spec:
        tokenRef: github_pat   # secret identifier

In service variables:

variables:
  - name: DB_PASSWORD
    type: Secret
    value: <+secrets.getValue("db_password")>

Naming Conventions

Secret Type	Pattern	Example
API Keys	`{service}_api_key`	`github_api_key`
Passwords	`{system}_password`	`prod_db_password`
Tokens	`{provider}_token`	`slack_token`
SSH Keys	`ssh_{purpose}`	`ssh_deploy_key`
Certificates	`{service}_cert`	`ssl_prod_cert`

Identifier must match: ^[a-zA-Z_][0-9a-zA-Z_]{0,127}$

Examples

Create a GitHub PAT secret

/create-secret
Create a SecretText for a GitHub personal access token at the project level
using the Harness built-in secret manager

Create SSH credentials

/create-secret
Create an SSH key secret for deploying to production servers as the "deploy" user

Create a Vault-referenced secret

/create-secret
Create a secret that references the database password stored in HashiCorp Vault
at secret/data/production/database#password

List secrets

/create-secret
Show me all secrets in the payments project

Create WinRM credentials

/create-secret
Create WinRM NTLM credentials for the Windows deployment servers

Error Handling

Error	Cause	Solution
Duplicate identifier	Secret with same ID exists	Use unique identifier or update existing
Secret manager not found	Invalid `secretManagerIdentifier`	Verify the secret manager connector exists
Encryption failed	Secret manager connectivity issue	Check delegate connectivity to secret manager
Invalid secret type	Unsupported type string	Use `SecretText`, `SecretFile`, `SSHKey`, or `WinRmCredentials`
Invalid valueType	Case mismatch	Use `Inline` or `Reference` (case-sensitive)

Performance Notes

Never include actual secret values in generated YAML. Use placeholder references only.
Verify the correct scope (account, org, project) before creating — secrets at the wrong scope will not be accessible.
Confirm the secret manager exists and is accessible before creating secrets.

Troubleshooting

Secret Not Accessible in Pipeline

Check scope -- project secrets need no prefix, org secrets need org. prefix, account secrets need account. prefix
Verify the pipeline's project has access to the secret's scope
Confirm the user/service account running the pipeline has core_secret_view permission

External Secret Manager Errors

Verify the secret manager connector is healthy (harness_get on the connector)
For Vault: check the path format includes #key suffix for specific keys
For AWS SM: ensure IAM permissions allow secretsmanager:GetSecretValue
Delegate must have network access to the external secret manager

SSH Key Connection Failures

Verify the private key is in PEM format
Check that the target server accepts key-based authentication
If using KeyPath, confirm the key file exists on the delegate host
Test with credentialType: Password first to isolate key-specific issues

Security Best Practices

Use external secret managers (Vault, AWS SM) for production secrets
Scope secrets as narrowly as possible -- prefer project over account
Never output secret values in pipeline logs
Rotate secrets regularly and update references
Audit secret access via the /audit-report skill

create-secret

このリポジトリの他の Skills

このリポジトリの他の Skills

Create Secret Skill

MCP v2 Tools Used

Secret Types

SecretText

Secret Scopes

Instructions

Step 1: Determine Requirements

Step 2: Check for Existing Secrets

Step 3: Create the Secret

Step 4: Verify Creation

Referencing Secrets in Pipelines

Naming Conventions

Examples

Create a GitHub PAT secret

Create SSH credentials

Create a Vault-referenced secret

List secrets

Create WinRM credentials

Error Handling

Performance Notes

Troubleshooting

Secret Not Accessible in Pipeline

External Secret Manager Errors

SSH Key Connection Failures

Security Best Practices

Create Secret Skill

MCP v2 Tools Used

Secret Types

SecretText

Secret Scopes

Instructions

Step 1: Determine Requirements

Step 2: Check for Existing Secrets

Step 3: Create the Secret

Step 4: Verify Creation

Referencing Secrets in Pipelines

Naming Conventions

Examples

Create a GitHub PAT secret

Create SSH credentials

Create a Vault-referenced secret

List secrets

Create WinRM credentials

Error Handling

Performance Notes

Troubleshooting

Secret Not Accessible in Pipeline

External Secret Manager Errors

SSH Key Connection Failures

Security Best Practices