harness-pipeline
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.
What this skill does
# 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.
```bash
/harness-pipeline trigger --pipeline <pipeline-id> --branch <branch-name> --jira <issue-key>
```
**Steps:**
1. Validate Jira issue exists (using issue-validator)
2. Execute pipeline via Harness REST API
3. Add comment to Jira issue with execution link
4. Return execution ID for monitoring
### status
Check pipeline execution status.
```bash
/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.
```bash
/harness-pipeline logs --execution <execution-id> --stage <stage-name>
```
### list
List recent pipeline executions.
```bash
/harness-pipeline list --pipeline <pipeline-id> --limit 10
```
## Jira Integration
When triggering a pipeline with `--jira` flag:
1. **Pre-execution:**
- Validates issue exists
- Checks issue is in appropriate status
- Adds "Pipeline Triggered" comment
2. **During execution:**
- Optionally updates issue status to "In Progress"
3. **Post-execution:**
- Adds execution result comment
- Links build artifacts
- Transitions issue based on result (configurable)
## Example Workflow
```bash
# 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):
```bash
# 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 `.env` only
- Never logged or exposed
- Minimal required permissions
- Rotate regularly
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.