agentleFS
thisrohanguptathisrohangupta/harness-skills/skills/manage-delegates/SKILL.md

manage-delegates

Skill2 starsChanged 7 months agoApache-2.0Archived repositoryView on GitHub

Monitor and manage Harness Delegates via MCP. List delegates and check health status, manage delegate registration tokens (create, revoke, delete), and find which delegates are associated with a token. Use when asked about delegate status, delegate health, delegate connectivity, delegate tokens, or troubleshooting delegate issues. Trigger phrases: delegate status, delegate health, list delegates, delegate token, delegate connectivity, delegate troubleshooting, delegate down.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When diagnosing delegate issues, check both the delegate list (for health/heartbeat) and the token status (for auth).

    line 130
  2. Distinctive:

    Always verify delegate connectivity before troubleshooting pipeline failures -- many execution errors stem from unavailable delegates.

    line 131
  3. Distinctive:

    Check the delegate's last heartbeat timestamp -- if stale, the delegate process may be down

    line 136
  4. Distinctive:

    Verify the delegate token is ACTIVE (not REVOKED)

    line 137
  5. Distinctive:

    Check network connectivity between the delegate host and Harness SaaS

    line 138
  6. Distinctive:

    Check if the pipeline uses a delegate selector that doesn't match any active delegate

    line 142
  7. Distinctive:

    Verify the delegate has the required tools installed (kubectl, helm, docker, etc.)

    line 143

≈ “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

Manage Delegates

Monitor delegate health and manage registration tokens via MCP.

Instructions

Step 1: List Delegates

List all delegates in the account to check health and connectivity:

Call MCP tool: harness_list
Parameters:
  resource_type: "delegate"

This returns all delegates with their status, version, connectivity, and last heartbeat. Delegates are account-scoped -- no org/project needed.

Step 2: List Delegate Tokens

Call MCP tool: harness_list
Parameters:
  resource_type: "delegate_token"
  org_id: "<organization>"
  project_id: "<project>"

Filter by name or status:

Call MCP tool: harness_list
Parameters:
  resource_type: "delegate_token"
  name: "prod-token"
  status: "ACTIVE"

Step 3: Get Token Details

Call MCP tool: harness_get
Parameters:
  resource_type: "delegate_token"
  resource_id: "<token_name>"
  org_id: "<organization>"
  project_id: "<project>"

Step 4: Create a Token

Call MCP tool: harness_create
Parameters:
  resource_type: "delegate_token"
  org_id: "<organization>"
  project_id: "<project>"
  body:
    name: "prod-delegate-token"

Step 5: Find Delegates for a Token

Call MCP tool: harness_execute
Parameters:
  resource_type: "delegate_token"
  action: "get_delegates"
  resource_id: "<token_name>"
  org_id: "<organization>"
  project_id: "<project>"

Step 6: Revoke a Token

Call MCP tool: harness_execute
Parameters:
  resource_type: "delegate_token"
  action: "revoke"
  resource_id: "<token_name>"
  org_id: "<organization>"
  project_id: "<project>"

Step 7: Delete a Token

Call MCP tool: harness_delete
Parameters:
  resource_type: "delegate_token"
  resource_id: "<token_name>"
  org_id: "<organization>"
  project_id: "<project>"

Resource Types

Resource TypeScopeOperationsDescription
delegateAccountlistList delegates with health status
delegate_tokenProjectlist, get, create, delete + revoke, get_delegates actionsManage registration tokens

Examples

  • "Are all delegates healthy?" -- List delegates, check status and last heartbeat
  • "Create a new delegate token for the staging project" -- Create token with project scope
  • "Which delegates are using the prod-token?" -- Execute get_delegates action on the token
  • "Revoke the old registration token" -- Execute revoke action
  • "Show me all active delegate tokens" -- List tokens filtered by status ACTIVE

Performance Notes

  • When diagnosing delegate issues, check both the delegate list (for health/heartbeat) and the token status (for auth). A delegate showing as disconnected may have a revoked token.
  • Always verify delegate connectivity before troubleshooting pipeline failures -- many execution errors stem from unavailable delegates.

Troubleshooting

Delegate Shows Disconnected

  1. Check the delegate's last heartbeat timestamp -- if stale, the delegate process may be down
  2. Verify the delegate token is ACTIVE (not REVOKED)
  3. Check network connectivity between the delegate host and Harness SaaS

Pipeline Fails with "No Delegates Available"

  1. List delegates to confirm at least one is connected and healthy
  2. Check if the pipeline uses a delegate selector that doesn't match any active delegate
  3. Verify the delegate has the required tools installed (kubectl, helm, docker, etc.)

Token Issues

  • Tokens are project-scoped -- a token created in project A cannot register delegates for project B
  • Revoking a token disconnects all delegates registered with it
  • Deleted tokens cannot be recovered -- create a new one and re-register delegates

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.