human-management

Use when admin requests adding a human user to the system, changing human permissions, removing human access, or managing human accounts.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

93%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 well-structured, token-efficient skill body with executable examples and clean progressive disclosure into real bundle files. The only weakness is that the provisioning verification step is deferred to the reference rather than surfaced in the body's workflow.

Suggestions

Surface the asynchronous-provisioning verification step (re-querying 'agt get humans <name> -o json') in the body's Quick Create section so the create→verify loop is visible without opening the reference.

Add a brief prerequisite note in the body (referenced Team/Worker CRs must exist before --teams/--workers) so the entry point is self-contained for the common case.

Dimension	Reasoning	Score
Conciseness	The body is lean — compact permission table, terse gotcha bullets, a single quick-create example — with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	The Quick Create block is a copy-paste-ready bash command with real arguments, and the Operation Reference table gives concrete executable commands ('agt get humans', 'agt delete human <name>').	5 / 5
Workflow Clarity	A clear create-then-verify sequence exists, but the asynchronous-provisioning verification checkpoint lives in the referenced doc rather than the body, leaving a minor checkpoint gap in the main skill.	4 / 5
Progressive Disclosure	The body is a concise overview that points to real one-level-deep references (references/create-human.md, scripts/create-human.sh), with an Operation Reference table that makes navigation by admin intent trivial.	5 / 5
	Total	19 / 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, trigger-first description that pairs an explicit 'Use when' clause with four concrete human-management actions and a clear niche. The only minor gap is the absence of synonyms or common phrasing variations.

Dimension	Reasoning	Score
Specificity	Lists four concrete actions — 'adding a human user', 'changing human permissions', 'removing human access', 'managing human accounts' — giving comprehensive coverage rather than vague abstraction.	5 / 5
Completeness	The explicit 'Use when admin requests...' clause gives a concrete trigger, and the enumerated actions state clearly what the skill does, answering both what and when.	5 / 5
Trigger Term Quality	Natural phrases a user would say ('adding a human user', 'changing human permissions') are present, but it lacks synonyms or file-extension-style variations that would push it to comprehensive.	4 / 5
Distinctiveness Conflict Risk	The 'human' qualifier scopes it to a clear niche (human account management) with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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: agentscope-ai/AgentTeams
Path: manager/agent/skills/human-management/SKILL.md
Commit: 223ddc2

Reviewed: 13 days ago

Table of Contents

Discovery Implementation Validation

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.