Harness Skills plugin
Skills for the Harness CI/CD platform: pipelines, connectors, feature flags, security and cost from a chat with an agent
- 134 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- With the Harness key the agent creates and runs pipelines and changes connectors, freeze windows and policies, which affects production deploys
- Connectors hold access to clouds and repositories, so a skill mistake exposes those services
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/harness-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- With the Harness key the agent creates and runs pipelines and changes connectors, freeze windows and policies, which affects production deploys
- Connectors hold access to clouds and repositories, so a skill mistake exposes those services
This is third-party code. Review the repository files before installing.
What it does
A repository from the Harness platform vendor with ready skills for Claude Code, Cursor, Codex and other agents. Skills are split into plugins by area: pipelines (8 skills), infrastructure (5), access control (2), FME feature flags (16), platform (8), security (11), observability and governance (19) and agents (2). With them an agent writes v0 and v1 pipeline YAML, creates templates, triggers and connectors, diagnoses failed runs and manages freeze windows. Most skills reach Harness through the `harness-mcp-v2` MCP server, started with `npx -y harness-mcp-v2` and fed a key from `HARNESS_API_KEY`. The server is not bundled with the plugins and is configured separately in each tool. In Claude Code every plugin installs with `/plugin install harness-fme --marketplace harness/harness-skills`.
Who it is for. Platform and DevOps engineers who run CI/CD, feature flags and governance in Harness and want to hand routine work to an agent.
Good fit when
- You need pipeline YAML for build and deploy generated from a plain-language description
- A run failed and the agent should find the cause in logs and steps
- Pipelines must be migrated from the v0 format to the simplified v1
- For a release you want to switch on a deployment freeze window or the project-level global freeze
Not a fit when
- You do not use Harness: the skills exist only for its API
- You have no access to the Harness MCP server or an API key: most skills fail without them
- You need a single skill: plugins install by category and each caches about 8 MB of the repository
Example request
Create a Node.js build step template in Harness and work out why the last run of the deploy pipeline failedLimitations
- Most skills need the Harness MCP v2 server and a `HARNESS_API_KEY`. The server is not bundled with the plugins and installs separately.
- Claude Code plugins do not load the repository-level `AGENTS.md` rules, so scope establishment, dependency checks and schema validation work only from a clone.
- Each installed plugin caches a full copy of the repository, about 8 MB.
- Cursor and Codex install the whole repository as one `harness-skills` plugin, and Codex refreshes only when the version in `skills/categories.json` changes.
- `/plugin install` with `--marketplace` needs Claude Code 2.1.275 or newer, with a two-step form for older versions.
How to disable. Remove the installed plugin with the agent's tools, for example `/plugin uninstall harness-fme@harness-skills` in Claude Code. Remove the MCP server and `HARNESS_API_KEY` separately from `.mcp.json` and the environment.
FAQ
Which Harness Skills plugin should I install in Claude Code?
Pick by task: `harness-pipelines` for pipelines, `harness-infrastructure` for connectors and environments, `harness-security` for security. Each category installs with its own `/plugin install`.
Is the MCP server required?
For most skills yes: they need Harness MCP v2. FME feature flag skills can use either the Harness CLI or MCP.
How do I connect the Harness MCP server to Cursor?
Add a `harness-mcp-v2` entry with the `npx` command and the arguments `-y harness-mcp-v2` to `~/.cursor/mcp.json` or `.cursor/mcp.json` and pass the key in `HARNESS_API_KEY`.
How do I invoke a skill in Claude Code?
Use the pattern `/plugin:skill`, for example `/harness-pipelines:create-pipeline`. In Cursor and Codex a skill is invoked by name.
How do I update the plugins?
Run `/plugin marketplace update harness-skills`. Plugin versions are tied to the repository commit.
Discussion
No questions or reviews yet.
Related
PluginsAn MCP server built into the Harness terminal for macOS: agents read sessions and panes, and input is enabled by a separate flag
An MCP server that opens a remote repository clone in an isolated container and gives the agent files, commands, Git and tasks.
A CLI for DeepSeek Harness that publishes a plugin set as a versioned preset, applies others' presets and rolls them back
Cloudflare's official agent skills: Workers, Durable Objects, wrangler, Pages, storage and an MCP server
Official HashiCorp skills for Terraform and Packer: HCL style, modules, tests, imports, Stacks, provider development and image builds
Zoho skills for the Catalyst cloud: Functions, AppSail, Data Store, SDKs, pricing, migration and Zoho MCP control
README in short
The README explains that the repository is a workflow system and differs from a folder of prompts. Tables of skills by category with invocation commands, plugin installs for Claude Code, Cursor and Codex, a no-plugin quick start and MCP setup follow.