harness-skills
AGENTS.md127 starsChanged 29 days agoApache-2.0View on GitHub
Scope: This file configures agents working in this repository and agents that load it from a clone. Plugin installs (Claude Code, Cursor, Codex) and npx skills add installs never load it, so runtime rules a skill needs must live in the skill or in a shared file it links (for example references/fme/). This repository contains model-agnostic workflow instructions for AI coding tools working with Harness.io. Most skills use Harness MCP; FME skills also support the Harness CLI for the operations…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository76 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/harness.mdcCursor rule
- manage-rolesSkill
- manage-usersSkill
- create-agentSkill
- create-agent-templateSkill
- dbops-changesetSkill
- choose-metricSkill
- cleanup-feature-flagsSkill
- create-experimentSkill
- create-feature-flagSkill
- create-metricSkill
- discover-feature-flagsSkill
- explain-flagSkill
- feature-flag-onboardingSkill
- fme-pipelineSkill
- instrument-feature-flagSkill
- instrument-metricSkill
- manage-experimentsSkill
- manage-flag-lifecycleSkill
- manage-segmentsSkill
- review-experiment-resultsSkill
- update-flag-targetingSkill
- create-connectorSkill
- create-environmentSkill
- create-infrastructureSkill
- create-secretSkill
- create-serviceSkill
- ai-operationsSkill
- analyze-costsSkill
- audit-reportSkill
- chaos-code-risk-scanSkill
- chaos-dr-testSkill
- chaos-experimentSkill
- create-policySkill
- deployment-readinessSkill
- dora-metricsSkill
- gitops-statusSkill
- incident-responseSkill
- manage-idpSkill
- manage-slosSkill
- optimize-pipelineSkill
- pr-analysisSkill
- scorecard-reviewSkill
- security-reportSkill
- sei-analyticsSkill
- template-usageSkill
- create-pipelineSkill
- create-pipeline-v1Skill
- create-templateSkill
- create-triggerSkill
- debug-pipelineSkill
- manage-freeze-windowsSkill
- migrate-pipelineSkill
- run-pipelineSkill
- create-sbomSkill
- enforce-sbomSkill
- manage-artifactsSkill
- manage-cdeSkill
- The first 60 shown.
The file
We split this AGENTS.md into the rules it gives an agent
9 rules. About 2 are common, 5 are distinctive, and 2 are very specific to this project.
≈2
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 184
When users need end-to-end setup, follow these dependency chains.
- Distinctive: line 188
Use when a user wants to deploy a new service to Harness.
- Distinctive: line 200
Use when a user is setting up a brand new Harness project from scratch:
- Common: line 211
Key rule: Always check if a referenced resource (connector, secret, environment) exists before creating something that depends on it.
- Distinctive: line 215
Before making any MCP API call that creates or modifies resources, always establish the user's scope:
- Distinctive: line 217
Ask for org and project: if not already known. Most Harness resources are scoped to an org + project.
- Very specific: line 224
When creating resources via harness_create, the Harness API validates the payload and returns specific error messages for malformed …
- Very specific: line 235
When creating or modifying skills, start from template/SKILL.md.template and see CONTRIBUTING.md for the full structure guide.
- Distinctive: line 237
Before committing, run the contributor checks:
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Harness Skills
Scope: This file configures agents working in this repository and agents that load it from a clone. Plugin installs (Claude Code, Cursor, Codex) and npx skills add installs never load it, so runtime rules a skill needs must live in the skill or in a shared file it links (for example references/fme/).
This repository contains model-agnostic workflow instructions for AI coding tools working with Harness.io. Most skills use Harness MCP; FME skills also support the Harness CLI for the operations explicitly listed in their Tools tables.
For FME, load the selected SKILL.md, its applicable local references, and references/fme/tool-map.md plus concepts.md; load write-safety.md before writes. Keep shared references accessible when installing/copying skills. Follow the tool map's capability limits and handoff contract: a slash-skill name means read its linked workflow, not assume a model-specific invocation tool. Unsupported operations stop rather than falling back to guessed commands.
Harness MCP Server
The Harness MCP server provides the generic tools below. CLI-only FME sessions use the verified equivalents in references/fme/tool-map.md; other skills retain their declared MCP requirements:
| Tool | Purpose |
harness_list | List resources with filters and pagination |
harness_get | Get a single resource by ID |
harness_create | Create a resource (requires confirmation) |
harness_update | Update a resource (requires confirmation) |
harness_delete | Delete a resource (requires confirmation) |
harness_execute | Run, retry, interrupt, sync, toggle, approve, reject, test_connection |
harness_search | Cross-resource keyword search |
harness_describe | Local metadata/schema lookup (no API call) |
harness_diagnose | Pipeline failure analysis |
harness_status | Project health overview |
Tools accept a resource_type parameter (e.g., pipeline, secret, template) to target specific Harness resources. Tools also support Harness UI URL auto-extraction for org_id, project_id, resource_type, and resource_id.
Skill Directory
Skills live in skills/<category>/<skill-name>/SKILL.md. The categories, and the Claude Code plugin each one becomes, come from skills/categories.json. Each skill folder may contain references/, scripts/, and assets/ subdirectories.
A slash-skill name may appear as /<skill> or /<plugin>:<skill> (for example /harness-fme:explain-flag); both mean the same workflow.
<!-- BEGIN GENERATED:skills --><!-- Generated by scripts/generate_catalog.py from skills/categories.json and SKILL.md frontmatter. Do not edit. -->Harness Pipelines & Execution
Plugin harness-pipelines, folder skills/pipelines/.
| Skill | Description |
/create-pipeline | Generate v0 pipeline YAML (CI, CD, combined, approvals) |
/create-pipeline-v1 | Generate v1 simplified pipeline YAML |
/create-template | Create reusable step, stage, pipeline, and step group templates |
/create-trigger | Create webhook, scheduled, and artifact triggers |
/debug-pipeline | Diagnose pipeline execution failures |
/manage-freeze-windows | Create, toggle, and manage deployment freeze windows and the project-level global freeze |
/migrate-pipeline | Convert v0 pipelines to v1 format |
/run-pipeline | Execute and monitor pipeline runs |
Harness Infrastructure & Resources
Plugin harness-infrastructure, folder skills/infrastructure/.
| Skill | Description |
/create-connector | Create connectors (GitHub, AWS, GCP, Azure, Docker, K8s) |
/create-environment | Create environments (PreProduction, Production) with overrides |
/create-infrastructure | Define infrastructure (K8s, ECS, Serverless) |
/create-secret | Manage secrets (SecretText, SecretFile, SSHKey, WinRM) |
/create-service | Define services (Kubernetes, Helm, ECS) with artifact sources |
Harness Access Control & Users
Plugin harness-access-control, folder skills/access-control/.
| Skill | Description |
/manage-roles | RBAC roles, assignments, permissions, and resource groups |
/manage-users | Manage users, user groups, and service accounts |
Harness FME (Feature Flags & Experimentation)
Plugin harness-fme, folder skills/fme/.
| Skill | Description |
/choose-metric | Recommend primary/guardrail metrics for an experiment or rollout, judged against a good-metric checklist |
/cleanup-feature-flags | Remove a launched FME flag from code and open a PR; archive is handed to manage-flag-lifecycle |
/create-experiment | Creation-only entry point to the manage-experiments workflow |
/create-feature-flag | Create an FME flag that follows project conventions, with safe-default definitions |
/create-metric | Design and create an FME metric, with intent-to-config guidance, traffic type, events, cap, and owners |
/discover-feature-flags | Inventory, targeting-pattern search, promotion-aware rollout report, and stale-flag audit (read-only) |
/explain-flag | Explain one flag's purpose, treatments, and per-environment targeting, flagging inconsistencies (read-only) |
/feature-flag-onboarding | Set up and verify a first feature flag in an existing project; resume partial onboarding |
/fme-pipeline | Generate FME pipelines for rollout scenarios, gates, and flag lifecycle |
/instrument-feature-flag | Gate application code through an extensible flag abstraction, after stack detection and clarification |
/instrument-metric | Wire up a track() call for a metric's event, placed at the real outcome, and verify it arrives |
/manage-experiments | Feature-flag experiment design/lifecycle; delegates metrics and states CLI update limitations |
/manage-flag-lifecycle | Flag metadata, archive readiness, archive/unarchive, and delete |
/manage-segments | Segment metadata, STANDARD membership, and RULE_BASED editor workflows with mandatory pre-write reference checks |
/review-experiment-results | Explain experiment results, including winner, significance, guardrail impact, and data-quality caveats |
/update-flag-targeting | Ramp, rules, individual targets, allocation, treatments, kill/restore, env-to-env copy, and initializing definitions |
Harness Database DevOps
Plugin harness-database, folder skills/database/.
| Skill | Description |
/dbops-changeset | Generate, refine, review, and execute Liquibase changesets with Harness DBOPS |
Harness Platform Operations
Plugin harness-platform, folder skills/platform/.
| Skill | Description |
/create-sbom | Add SBOM Orchestration (generation/attestation) to existing pipelines |
/enforce-sbom | Add SBOM Policy Enforcement (verify attestation + OPA policy sets) |
/manage-artifacts | Artifact registry setup, security scanning, and cross-region replication |
/manage-cde | Cloud development environments, workspace templates, and auto-hibernation |
/manage-delegates | Monitor delegate health and manage registration tokens |
/manage-iacm | Terraform workspaces, drift detection, cost estimation, and approval workflows |
/manage-pull-requests | List, create, update, merge, review, and comment on Harness Code pull requests |
/manage-supply-chain | SBOM generation, artifact signing, and supply chain policy enforcement |
Harness Security Testing & Supply Chain
Plugin harness-security, folder skills/security/.
| Skill | Description |
/approve-exempt | Approve pending STO exemptions at current scope or elevate to Project, Org, or Account |
/configure-agent-pr-attestation | Install and configure the Claude Code PR attestation hook for signed in-toto attestations to the Harness Evidence Vault |
/configure-container-scan | Add container image scanning to pipelines using Harness STO scanners (Trivy, Grype, Snyk, and more) |
/configure-dast-scan | Add DAST scanning to pipelines for runtime application security testing (Traceable, Burp Suite, ZAP, Nikto, Nmap) |
/configure-repo-scan | Configure code scanning in pipelines with STO security scanners |
/configure-secret-scan | Add secret detection scanning to pipelines to find exposed credentials and API keys (Gitleaks, Semgrep, Snyk, and more) |
/enforce-slsa | Add SLSA Verification (verify attestation + OPA policy sets on provenance) to pipelines |
/exempt-vuln | Create STO vulnerability exemptions (waivers) scoped to Project, Pipeline, or Target |
/generate-slsa | Add SLSA Generation (provenance + optional Cosign attestation) to existing pipelines |
/sign-artifact | Add Artifact Signing (Cosign sign + optional .sig upload) to existing pipelines (SSCA) |
/verify-sign | Add Artifact Verification (verify Cosign signature) to existing pipelines (SSCA) |
Harness Observability & Governance
Plugin harness-observability-governance, folder skills/observability-governance/.
| Skill | Description |
/ai-operations | Predictive failure analysis and intelligent alert correlation (AIDA) |
/analyze-costs | Cloud cost analysis, recommendations, and anomaly detection |
/audit-report | Audit trails and compliance evidence (SOC2, GDPR, HIPAA) |
/chaos-code-risk-scan | Scan a code repository for chaos-provable resilience risks and report them as a risk scan |
/chaos-dr-test | Create and edit DR Test pipelines with chaos steps |
/chaos-experiment | Create, edit, and reference chaos experiments (faults, probes, actions) |
/create-policy | Create OPA governance policies for supply chain security |
/deployment-readiness | Pre-deployment readiness checks, environment drift, and canary decisions |
/dora-metrics | DORA metrics and engineering performance reports |
/gitops-status | GitOps application health, sync status, and pod logs |
/incident-response | Deployment-incident correlation, blast radius analysis, and postmortems |
/manage-idp | Service catalog, self-service workflows, documentation, and developer onboarding (IDP) |
/manage-slos | SLO definition, error budgets, incident detection, and operational runbooks |
/optimize-pipeline | Pipeline speed optimization, parallel testing, caching, and monorepo builds |
/pr-analysis | PR pipeline impact, security review, and PR-to-production tracking |
/scorecard-review | IDP scorecards and service maturity review |
/security-report | Security vulnerabilities, SBOMs, and compliance reports |
/sei-analytics | Sprint analytics, investment allocation, capacity forecasting, and release readiness |
/template-usage | Template dependency tracking, impact analysis, and adoption |
Harness Unified Data Platform
Plugin harness-unified-data-platform, folder skills/unified-data-platform/.
| Skill | Description |
/write-hql | Discover fields, then write, validate, and run dashboard-ready HQL queries |
Harness AI Agents
Plugin harness-agents, folder skills/agents/.
| Skill | Description |
/create-agent | Create and update Harness AI agent instances for agentic pipeline workflows |
/create-agent-template | Generate AI agent templates (metadata.json, pipeline.yaml, wiki.MD) |
<!-- END GENERATED:skills -->Cross-Skill Workflows
When users need end-to-end setup, follow these dependency chains. Each step depends on the previous -- do not skip steps or create resources that reference connectors/secrets that don't exist yet.
New Microservice Setup
Use when a user wants to deploy a new service to Harness. Follow this exact order:
- Create connectors (
/create-connector) -- GitHub connector for source code and manifests, Docker/ECR/GCR connector for container images, K8s/cloud connector for target infrastructure - Create secrets (
/create-secret) -- Authentication tokens, SSH keys, or credentials referenced by connectors - Create service (
/create-service) -- Reference the Git connector for manifests, reference the Docker connector for artifact source - Create environment (
/create-environment) -- PreProduction and/or Production with environment-specific variables - Create infrastructure (
/create-infrastructure) -- Reference the K8s/cloud connector for the target cluster. If no connector exists for the target, create one first - Create pipeline (
/create-pipeline) -- Build pipeline based on source code language and manifest type. Reference the service, environment, and infrastructure from previous steps - Create trigger (
/create-trigger) -- Automate the pipeline with webhook (PR/push) or artifact triggers
New Project Onboarding
Use when a user is setting up a brand new Harness project from scratch:
- Create project -- Use
harness_createwithresource_type: "project"and the targetorg_id - Create connectors (
/create-connector) -- All connectors needed for the project (Git, cloud, registry, cluster) - Create secrets (
/create-secret) -- All secret references for connector auth - Create service (
/create-service) -- Service definitions for each microservice - Create environment (
/create-environment) -- Dev, staging, production environments - Create infrastructure (
/create-infrastructure) -- Infrastructure definitions per environment - Create pipeline (
/create-pipeline) -- CI/CD pipelines for each service - Create trigger (
/create-trigger) -- Automate all pipelines
Key rule: Always check if a referenced resource (connector, secret, environment) exists before creating something that depends on it. If it doesn't exist, create it first. Ask the user for the org and project context before starting.
Scope & Context Convention
Before making any MCP API call that creates or modifies resources, always establish the user's scope:
- Ask for org and project if not already known. Most Harness resources are scoped to an org + project.
- Use
harness_listto verify referenced resources exist before creating dependents (e.g., confirm a connector exists before referencing it in a service). - Account-level resources (no org/project) are visible to all orgs and projects. Org-level resources are visible to all projects in that org. Project-level resources are only visible within that project.
- If the user provides a Harness UI URL, extract
org_id,project_id, andresource_idfrom it -- MCP tools support URL auto-extraction.
Schema Validation Convention
When creating resources via harness_create, the Harness API validates the payload and returns specific error messages for malformed requests. Skills do NOT need to embed full API schemas. Instead:
- Each skill lists required fields in its Instructions section (identifier, name, type, yaml, etc.)
- Use
harness_describeto discover the full schema for any resource type at runtime -- this is a local lookup with no API call:harness_describe(resource_type="service") - On validation errors, read the API error message to identify the missing or invalid field, then fix and retry
Skill Standards
When creating or modifying skills, start from template/SKILL.md.template and see CONTRIBUTING.md for the full structure guide. Skills must have: frontmatter (name, description, metadata, license, compatibility), ## Instructions, ## Examples, ## Performance Notes, and ## Troubleshooting sections.
Before committing, run the contributor checks:
scripts/validate-skills.sh- layout, frontmatter, required sections, and description rulespython3 scripts/generate_catalog.py- regenerates the plugin manifests,skills.json, and the skill tables; commit the generated filespython3 scripts/check_links.py- markdown links and backticked path mentionspython3 -m unittest discover -s tests -v
Schema References
- v0 Pipelines/Templates/Triggers: https://github.com/harness/harness-schema/tree/main/v0
- v1 Pipelines: https://github.com/thisrohangupta/spec
- Agent Templates: https://github.com/thisrohangupta/agents
- MCP v2 Server: https://github.com/thisrohangupta/harness-mcp-v2
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.