agentleFS
thisrohanguptathisrohangupta/harness-skills/skills/template-usage/SKILL.md

template-usage

Skill2 starsChanged 7 months agoApache-2.0Archived repositoryView on GitHub

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).

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search by name or keyword:

    line 55
  2. Distinctive:

    Check usage across all scopes (account, org, project) for complete impact analysis.

    line 165
  3. Distinctive:

    Verify version information to distinguish between teams using current vs.

    line 166
  4. Very specific:

    Use harness_search with broader terms to find the template first

    line 174
  5. Distinctive:

    Check for both pipeline and template references (templates can nest)

    line 180
  6. Distinctive:

    Verify the exact identifier (case-sensitive, underscores not hyphens)

    line 184
  7. Distinctive:

    Check the correct scope -- project templates require org_id + project_id

    line 186

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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?

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.