Individual skill
create-policy
Create OPA governance policies for Harness via MCP. Define policies that enforce compliance rules on pipelines, services, environments, feature flags, artifacts, code repositories, templates, SBOM, security tests, Terraform, GitOps, connectors, secrets, and more. Use when asked to create, write, fix, or explain an OPA policy, Rego rule, deny rule, governance policy, compliance rule, or policy-as-code for any Harness entity. Trigger phrases: create policy, OPA policy, governance policy, compliance rule, rego policy, deny rule, enforce policy, security policy, supply chain governance.
skills/observability-governance/create-policy/SKILL.md
Source commit e01dc7275f7e261f390be2fe7be4559feadb74ef
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 134
- Repository last updated
- Oct 28, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- agents Repository topic
- legal Derived category
- operations Derived category
- devops Derived category
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,894 bytesreferences/advanced-patterns.mddoc · 18,097 bytesreferences/entity-code-repository.mddoc · 4,308 bytesreferences/entity-connector.mddoc · 6,515 bytesreferences/entity-database.mddoc · 5,001 bytesreferences/entity-feature-flag.mddoc · 12,129 bytesreferences/entity-gitops.mddoc · 6,767 bytesreferences/entity-override.mddoc · 1,880 bytesreferences/entity-pipeline.mddoc · 38,143 bytesreferences/entity-sbom.mddoc · 6,653 bytesreferences/entity-secret.mddoc · 5,346 bytesreferences/entity-security-tests.mddoc · 8,062 bytesreferences/entity-service-env-infra.mddoc · 5,479 bytesreferences/entity-template.mddoc · 3,090 bytesreferences/entity-terraform.mddoc · 25,374 bytesreferences/entity-upstream-firewall.mddoc · 2,767 bytesreferences/entity-variable.mddoc · 1,557 bytesreferences/quality-tests.mddoc · 5,972 bytesreferences/rego-writing-guide.mddoc · 8,590 bytes
Read excerpt
# Create Policy
Create OPA governance policies for Harness Software Supply Chain Assurance (SCS) via MCP.
## Instructions
### Step 1: Identify Policy Requirements
Determine what the policy should enforce:
- What entity type is the policy targeting? (pipeline, service, environment, feature flag, etc.)
- What is the enforcement action (warn, deny)?
- What scope should the policy apply to?
- What action triggers the policy? (onrun, onsave, onstep, etc.)