template-usage

Analyze Harness template dependencies and usage with MCP v2 tools.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/thisrohangupta/cursor-harness-plugin --skill template-usage-thisrohangupta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: template-usage
Source: https://github.com/thisrohangupta/cursor-harness-plugin/tree/main/skills/template-usage
Command: npx skills add https://github.com/thisrohangupta/cursor-harness-plugin --skill template-usage-thisrohangupta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires harness-mcp-v2, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of tracking and understanding Harness template dependencies, usage, and adoption, providing insights into template references, impact analysis, and unused templates.

Core Features & Use Cases

  • Template Dependency Tracking: Identify which pipelines or templates reference a given template.
  • Impact Analysis: Analyze the impact of updating a template before making changes.
  • Unused Template Identification: Find and manage templates that are no longer in use.
  • Version Adoption Tracking: Monitor the adoption of different versions of a template across projects.

Quick Start

Use the /template-usage skill to find out which pipelines are using the 'docker-build-push' template.

Frequently Asked Questions about template-usage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find which Harness pipelines reference a specific template?

Template usage analysis identifies all pipelines and nested templates that reference a given template across the Harness platform. It maps template dependencies precisely, showing exactly where your templates are utilized within projects.

Can I check the impact of updating a Harness template before applying changes?

Yes, template impact analysis evaluates the downstream effects of updating a Harness template before execution. It reviews all dependent pipelines and references to determine what will change, preventing unexpected pipeline failures during deployments.

How do I identify unused Harness templates in my projects?

Unused template identification scans the Harness platform to locate templates with zero dependencies. It filters out templates that no pipelines or other templates reference, allowing you to safely clean up and manage orphaned template resources.

Do I need the Harness MCP v2 server to track template version adoption?

Yes, tracking template version adoption requires the Harness MCP v2 server. The analysis uses MCP v2 tools to monitor which template versions are actively used across different project scopes, ensuring accurate version dependency reporting.

What are the limitations of analyzing template dependencies across different scopes?

Template dependency analysis operates within specific Harness template types and organizational scopes. While it tracks references and version adoption accurately, complex nested template chains may require iterative querying to fully map all cross-scope dependencies.