CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

manage-users

Manage Harness users, user groups, and service accounts via MCP. List and search users, create and manage user groups for team-based access, create service accounts for API automation, and view available permissions. Use when asked to list users, create a user group, manage service accounts, check who has access, or set up team permissions. Do NOT use for role assignments or resource groups (use manage-roles instead). Trigger phrases: list users, user group, service account, who has access, team permissions, add user to group, create service account.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable single-file skill: every MCP operation is specified with copy-paste-ready parameters, correct scoping, and pre-change verification notes, plus useful troubleshooting for real failure modes. The main improvements are folding verification checkpoints inline into the destructive delete workflows and trimming the Examples section that duplicates the description.

Suggestions

Integrate validation into the workflow itself: before each delete step, instruct the model to list the resource, confirm the identifier matches the user's intent, and verify deletion afterward — currently verification lives only in Performance Notes.

Trim or repurpose the Examples section, which restates the description's trigger phrases without adding operational detail (the user-group example doesn't show how to obtain the member user_ids that the create call requires).

Add the missing "obtain user_id values" step (e.g. list users with search_term, then harvest resource_id from results) — Step 3's create-group body references user_id placeholders that no preceding step explains how to acquire.

DimensionReasoningScore

Conciseness

The body is efficient — every operation is a compact parameter block with no explanations of concepts Claude already knows — but the "Examples" section largely restates the description's trigger phrases (e.g. "List all users in the account" -- List users with no filter), which is minor over-explanation that could be trimmed. Not a 5 because not quite every token earns its place; not a 3 because padding is minimal and incidental.

4 / 5

Actionability

Every operation is given as a concrete, copy-paste-ready MCP tool call with exact parameters, including fully specified create bodies with realistic values (identifier "backend_team", "ci_bot", email "ci-bot@harness.io") and correct scoping fields (org_id/project_id). This matches the anchor for fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

Steps are clearly sequenced (Steps 1–5) and pre-change verification checkpoints exist ("Verify user email addresses and group identifiers before making changes", "List existing groups and service accounts before creating to avoid duplicates"), so the destructive-operation cap at 3 does not apply. It falls short of anchor 5 because validation is located in Performance Notes rather than inline in the workflow, and there is no post-delete verification or validate-fix-retry feedback loop.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and the body references none, so all content lives in one well-sectioned file (Instructions, Resource Types table, relationship-to-sibling-skill, Troubleshooting). Structure is good with clear headers and an accurate resource-type table, but at ~170 lines the Examples and Troubleshooting sections could be split out, and there are no well-signaled references to reward anchor 5's organization pattern.

4 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: comprehensive third-person capability enumeration, an explicit Use-when clause with natural trigger phrases, and a clear deconfliction boundary against the sibling manage-roles skill. The only gap is slightly incomplete trigger coverage for removal/deletion phrasings.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions with comprehensive coverage of the domain: "List and search users, create and manage user groups for team-based access, create service accounts for API automation, and view available permissions." It is written in third person and contains no vague filler, matching the anchor for comprehensive concrete actions rather than the anchor 4 example with minor coverage gaps.

5 / 5

Completeness

Both "what" and "when" are explicit and concrete: capabilities are enumerated up front, and the "Use when asked to list users, create a user group, manage service accounts, check who has access, or set up team permissions" clause plus a dedicated trigger-phrase list answers when-to-use with concrete triggers — the anchor 5 pattern. Not a 4 because the "when" guidance is fully explicit rather than merely present.

5 / 5

Trigger Term Quality

Trigger phrases are natural and well-chosen ("list users, user group, service account, who has access, team permissions, add user to group, create service account"), covering the common phrasings a user would say. A few natural variations are missing, e.g. removal/deletion intents ("remove user from group", "delete service account") and "find user"; not clearly comprehensive enough for anchor 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (user/group/service-account principals) with a negative boundary — "Do NOT use for role assignments or resource groups (use manage-roles instead)" — that explicitly routes the nearest overlapping intent to the sibling skill. Minimal conflict risk, matching anchor 5.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

harness/harness-ai

Path

plugins/claude/skills/manage-users/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.