markus41/harness-pipeline
plugins/jira-orchestrator/skills/harness-pipeline/SKILL.md
This skill should be used when the user asks to "run a Harness pipeline", "trigger a deployment pipeline", "monitor a Harness execution", or "check pipeline status" — executing and watching Harness pipelines with Jira integration.
$ install --global
skillsauthnpx skillsauth add markus41/claude harness-pipelineInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 5, 2026, 6:40 AM116.8s1 file scanned
SKILL.md
- name:
- harness-pipeline
- description:
- This skill should be used when the user asks to "run a Harness pipeline", "trigger a deployment pipeline", "monitor a Harness execution", or "check pipeline status" — executing and watching Harness pipelines with Jira integration.
- scope:
- development, ci-cd, pipeline
Harness Pipeline Skill
Execute and monitor Harness CI/CD pipelines with automatic Jira issue linking.
Usage
/harness-pipeline <action> [options]
Actions
trigger
Trigger a pipeline execution.
/harness-pipeline trigger --pipeline <pipeline-id> --branch <branch-name> --jira <issue-key>
Steps:
- Validate Jira issue exists (using issue-validator)
- Execute pipeline via Harness REST API
- Add comment to Jira issue with execution link
- Return execution ID for monitoring
status
Check pipeline execution status.
/harness-pipeline status --execution <execution-id>
Returns:
- Pipeline name
- Current status (Running, Success, Failed, Aborted)
- Stage statuses
- Duration
- Error details (if failed)
logs
Get pipeline execution logs.
/harness-pipeline logs --execution <execution-id> --stage <stage-name>
list
List recent pipeline executions.
/harness-pipeline list --pipeline <pipeline-id> --limit 10
Jira Integration
When triggering a pipeline with --jira flag:
-
Pre-execution:
- Validates issue exists
- Checks issue is in appropriate status
- Adds "Pipeline Triggered" comment
-
During execution:
- Optionally updates issue status to "In Progress"
-
Post-execution:
- Adds execution result comment
- Links build artifacts
- Transitions issue based on result (configurable)
Example Workflow
# 1. Validate the Jira issue first
/jira validate PROJ-163
# 2. Trigger pipeline with Jira link
/harness-pipeline trigger \
--pipeline my-ci-pipeline \
--branch feature/PROJ-163 \
--jira PROJ-163
# 3. Monitor execution
/harness-pipeline status --execution <returned-execution-id>
# 4. View logs if needed
/harness-pipeline logs --execution <execution-id> --stage build
REST API Calls
This skill uses the Harness REST API (NOT MCP):
# Trigger pipeline
curl -X POST "${HARNESS_API_URL}/pipeline/api/pipeline/execute/${PIPELINE_ID}" \
-H "x-api-key: ${HARNESS_API_KEY}" \
-H "Harness-Account: ${HARNESS_ACCOUNT_ID}" \
-H "Content-Type: application/json" \
--data-urlencode "accountIdentifier=${HARNESS_ACCOUNT_ID}" \
--data-urlencode "orgIdentifier=${HARNESS_ORG_ID}" \
--data-urlencode "projectIdentifier=${HARNESS_PROJECT_ID}"
Error Handling
| Error | Cause | Resolution | |-------|-------|------------| | 401 Unauthorized | Invalid or expired PAT | Regenerate PAT token | | 403 Forbidden | Insufficient permissions | Check PAT scope | | 404 Not Found | Pipeline/execution not found | Verify identifiers | | 429 Too Many Requests | Rate limited | Wait and retry |
Security
- PAT tokens stored in
.envonly - Never logged or exposed
- Minimal required permissions
- Rotate regularly
Related Skills
markus41/writing-plans-enhanced
development
VerifiedTrustedCommunity
Enhanced plan-authoring skill with Pre-Writing context gathering, task metadata, non-TDD templates, Red Flags, telemetry, and an automated plan linter. Use when you have a spec or requirements for a multi-step task, before touching code.
13SKILL.mdUpdated Apr 25, 2026
markus41/plugins/scrapin-aint-easy
tools
VerifiedTrustedCommunity
Documentation intelligence engine with graph-based API docs, algorithm library, and drift detection
13SKILL.mdUpdated Apr 17, 2026
markus41/ultraplan
tools
VerifiedTrustedCommunity
Ultraplan cloud planning — kick off a plan in the cloud from your terminal, review and revise in the browser, then execute remotely or send back to CLI
13SKILL.mdUpdated Apr 17, 2026
markus41/plugins/claude-code-expert/skills/mcp
tools
VerifiedTrustedCommunity
--- name: mcp description: Configure MCP servers for Claude Code — stdio vs HTTP, authentication, Tools/Resources/Prompts distinction, channels (CI webhook, mobile relay, Discord bridge, fakechat), and cost of always-loaded tools. Use this skill whenever adding an MCP server, debugging connection issues, choosing between MCP Tools vs Prompts vs Resources, installing channel servers, or managing .mcp.json. Triggers on: "MCP server", "mcp config", "add Obsidian MCP", "install context7", "channels"
13SKILL.mdUpdated Apr 17, 2026