Agent skill

Template Usage

by harness in harness/harness-skills

Track Harness template dependencies, usage, and adoption via MCP v2 tools.

Apache-2.0Auto-check passed

Install Template Usage

skills CLI
$ npx skills add harness/harness-skills --skill template-usage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install harness/harness-skills template-usage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/harness/harness-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/template-usage .claude/skills/template-usage && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
template-usage
GitHub stars
115
Token cost
~1.4k tokens
SKILL.md length
433 words
Files
2 (incl. references)
Skills in repo
64
Repo updated
First seen
Licence
Apache-2.0

At a glance

Track Harness template dependencies, usage, and adoption via MCP v2 tools.

  • Works in 4 steps: Find the Template → Get Template Details → Check Usage References → …
  • Asked about template usage
  • SKILL.md covers MCP v2 Tools Used, Template Types, Template Scopes and Instructions, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Template Usage is an agent skill from harness/harness-skills. Track Harness template dependencies, usage, and adoption via MCP v2 tools. Find which pipelines or other templates reference a given template, analyze update impact, identify unused templates, and compare version adoption. Use when asked about template usage, template references, template dependencies, impact analysis before updating a template, finding unused templates, or tracking template adoption across projects. Trigger phrases: template usage, who uses template, template references, template dependencies…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/report-templates.md`). Compatibility notes: Requires Harness MCP v2 server (harness-mcp-v2)

It works with Model Context Protocol. The repository describes itself as: A collection of structured AI agent skills that enable Claude Code, Cursor, GitHub Copilot, and other AI coding assistants to create, operate, debug, and govern Harness CI/CD… The licence is Apache-2.0.

When your agent uses it

  • Asked about template usage
  • Template references
  • Template dependencies
  • Impact analysis before updating a template

Example prompts

  • “/template-usage”

Requirements

  • Docker
  • Compatibility (from SKILL.md): Requires Harness MCP v2 server (harness-mcp-v2)

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Find the Template
  2. Get Template Details
  3. Check Usage References
  4. Analyze and Present

What it can do on your machine

Read from SKILL.md and the folder at commit c25faee. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires Harness MCP v2 server (harness-mcp-v2)

    From compatibility in the SKILL.md frontmatter.

Context cost

Template Usage loads about 1.4k tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 166 tokens; SKILL.md has 433 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~166
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from harness/harness-skills at commit c25faee, republished under its Apache-2.0 licence (© harness). 433 words, ~1,382 tokens.

Download SKILL.mdSave it as .claude/skills/template-usage/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
template-usage
description
Track Harness template dependencies, usage, and adoption via MCP v2 tools. Find which pipelines or other templates reference a given template, analyze update impact, identify unused templates, and compare version adoption. Use when asked about template usage, template references, template dependencies, impact analysis before updating a template, finding unused templates, or tracking template adoption across projects. Trigger phrases: template usage, who uses template, template references, template dependencies, template impact, unused templates, template adoption. Do NOT use for creating or updating templates (use create-template instead).
compatibility
Requires Harness MCP v2 server (harness-mcp-v2)
metadata.author
Harness
metadata.version
1.0.0
metadata.mcp-server
harness-mcp-v2
license
Apache-2.0

Template Usage Skill

Track template dependencies and usage across Harness via MCP v2 tools.

MCP v2 Tools Used

ToolResource TypePurpose
harness_searchtemplateFind templates by keyword across orgs/projects
harness_listtemplateList templates, filter by scope
harness_gettemplateGet template details, versions, and usage references
harness_describetemplateDiscover template resource schema and fields

Templates are managed via harness_list and harness_get only. For creating or updating templates, use the /create-template skill.

Template Types

TypeDescription
StepSingle step definition (build, test, deploy actions)
StageComplete stage with steps (CI stage, CD stage, approval)
PipelineFull pipeline definition
StepGroupGroup of related steps bundled together

Template Scopes

ScopeVisibilityQuery Parameters
AccountAll orgs and projectsNo org_id, no project_id
OrganizationAll projects in the orgorg_id only
ProjectOnly within the projectorg_id + project_id

Instructions

Step 1: Find the Template

Search by name or keyword:

harness_search(
  query="docker-build-push",
  resource_types=["template"],
  max_per_type=10,
  compact=true
)

Or list templates in a specific scope:

harness_list(
  resource_type="template",
  org_id="<org>",
  project_id="<project>",
  search_term="docker"
)
Step 2: Get Template Details
harness_get(
  resource_type="template",
  resource_id="<template_identifier>",
  org_id="<org>",
  project_id="<project>"
)

This returns the template definition, version history, and metadata.

Step 3: Check Usage References
harness_get(
  resource_type="template",
  resource_id="<template_identifier>",
  org_id="<org>",
  project_id="<project>"
)

Parse the response for referredEntities or usage data. The response includes which pipelines and other templates reference this template.

Step 4: Analyze and Present

Organize findings into a report.

For report templates (Usage Report, Impact Analysis, Unused Templates), consult references/report-templates.md.

Examples

Check who uses a template
/template-usage
Which pipelines are using the docker-build-push template?
Impact analysis before update
/template-usage
I want to make a breaking change to the k8s-deploy template. Show me what will be affected.
Find unused templates
/template-usage
Which templates in our account have no references? I want to clean up.
Track version adoption
/template-usage
Which version of the ci-stage template are different projects using?
Cross-project usage
/template-usage
Show me all usages of account-level templates across all projects
Dependency chain
/template-usage
Show me the full dependency chain for the release-pipeline template --
what does it reference and what references it?
Show full SKILL.md (202 more words)Show less

Error Handling

ErrorCauseSolution
Template not foundWrong identifier or scopeVerify identifier and use correct org_id/project_id for the template's scope
No usage dataTemplate genuinely unused or scope mismatchSearch at broader scope; account templates may be used in any project
Empty search resultsNo templates match queryTry broader search terms or list all templates

Performance Notes

  • Paginate through all usage results before generating the impact report. Large templates may have many references.
  • Check usage across all scopes (account, org, project) for complete impact analysis.
  • Verify version information to distinguish between teams using current vs. outdated template versions.

Troubleshooting

No Usage Data Returned
  1. Template may genuinely have no references
  2. Query scope must match template scope -- an account-level template needs no org_id/project_id
  3. Use harness_search with broader terms to find the template first
Incomplete Usage List
  1. Paginate through results -- increment page until all results are retrieved
  2. Account-level templates can be referenced from any org/project -- check all scopes
  3. Check for both pipeline and template references (templates can nest)
Template Not Found
  1. Verify the exact identifier (case-sensitive, underscores not hyphens)
  2. Identifiers must match pattern: ^[a-zA-Z_][0-9a-zA-Z_]{0,127}$
  3. Check the correct scope -- project templates require org_id + project_id

© harness, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/template-usage of harness/harness-skills.

  • SKILL.md
  • references/report-templates.md

Open the folder on GitHubat commit c25faee

Compare with similar skills

Template Usage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Template Usage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Template Usage this skillharness/harness-skills115—~1.4kAutomated safety check: PassApache-2.0
MCP Server Builderanthropics/skills180k62 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k5 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official37k11 repos~3.1kAutomated safety check: PassApache-2.0
Figma use_figma Plugin API Ruleswarpdotdev/warp65k4 repos~4.4kAutomated safety check: PassAGPL-3.0
Stitch to Remotion Walkthrough Videosgoogle-labs-code/stitch-skills8.4k6 repos~3.2kAutomated safety check: NotesApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 62 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 5 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    37k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed
  • Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.

    65k GitHub starsUsed in 4 repos~4.4k tokens
    Frontend & DesignAuto-check passed
  • Stitch to Remotion Walkthrough Videos

    google-labs-code/stitch-skills

    Official

    Builds walkthrough videos from Stitch design projects using Remotion, with transitions, zoom effects and text overlays on each screen.

    8.4k GitHub starsUsed in 6 repos~3.2k tokens
    Media & CreativeAuto-check: notes
  • MCP Development

    coollabsio/coolify

    A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 1 repo~949 tokens
    Frontend & DesignAuto-check passed

More from harness/harness-skills

All 64 skills in this repo
  • Audit Report

    harness/harness-skills

    Generate audit reports and compliance trails using Harness audit trail data via MCP v2 tools.

    115 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • Chaos Dr Test

    harness/harness-skills

    A skill your agent uses when working with Chaos Engineering steps inside a Harness pipeline.

    115 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed
  • Chaos Experiment

    harness/harness-skills

    A skill your agent uses when the user asks to create, edit, update, design, or configure a Harness Chaos Experiment — including faults, probes, actions, experiment YAML, fault injection, pod-delete…

    115 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • Cleanup Feature Flags

    harness/harness-skills

    Remove a launched Harness FME feature flag from application code, keeping the treatment FME serves today, and open a pull request.

    115 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Configure Repo Scan

    harness/harness-skills

    Configure code scanning in Harness pipelines using STO security scanners.

    115 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed
  • Create Agent Template

    harness/harness-skills

    Generate Harness Agent Template files for AI-powered automation agents.

    115 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed

Questions about Template Usage

What does Template Usage do?

Track Harness template dependencies, usage, and adoption via MCP v2 tools. Template Usage is an agent skill from harness/harness-skills. Track Harness template dependencies, usage, and adoption via MCP v2 tools.

When should I use Template Usage?

Template Usage fits situations like: asked about template usage; template references; template dependencies; impact analysis before updating a template.

How do I install Template Usage in Claude Code?

Run `npx skills add harness/harness-skills --skill template-usage -a claude-code`. Or copy the skill folder (skills/template-usage in harness/harness-skills) into .claude/skills/template-usage in your project. Claude Code loads it when a task matches its description.

How do I install Template Usage in Codex?

Run `npx skills add harness/harness-skills --skill template-usage -a codex`. Or copy the skill folder (skills/template-usage in harness/harness-skills) into .agents/skills/template-usage in your project. Codex loads it when a task matches its description.

Can I use Template Usage in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add harness/harness-skills --skill template-usage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/template-usage, .gemini/skills/template-usage, .github/skills/template-usage and .opencode/skills/template-usage in your project.

What does Template Usage need to run?

SKILL.md names no scripts, command-line tools or credentials: Template Usage is instructions for the agent only. Our summary lists: Docker. Compatibility (from SKILL.md): Requires Harness MCP v2 server (harness-mcp-v2).

Does Template Usage access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Template Usage safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Template Usage use?

Template Usage is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Template Usage use?

About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 517 tokens, read only when the agent opens those files.

What are the alternatives to Template Usage?

Skills that share tags, products or a category with Template Usage: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 37k stars) and Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Template Usage?

harness (a GitHub organization) maintains it in harness/harness-skills, which has 115 GitHub stars. The repository holds 64 skills in this directory. The repository was last updated on October 6, 2026.

Source: harness/harness-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.