worker-management

Use when admin requests hand-creating or resetting a Worker, starting/stopping a Worker, managing Worker skills, enabling peer mentions, or opening a QwenPaw console. Use agentteams-find-worker only as a helper for Nacos-backed market import or when task assignment needs you to discover a suitable Worker.

Quality

92%

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

85%Weight 40%Scale 1-3

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

The body is highly actionable with clear sequenced workflows and well-structured one-level-deep references to real bundle files. The only weakness is mild verbosity from restating the runtime fallback and runtime-switch behavior in multiple places.

Suggestions

Consolidate the runtime fallback rule: state it once in the runtime table and have the prose and gotcha reference it rather than re-explaining.

Replace the ~5-line runtime-change gotcha with a one-line cross-reference to the Switching Runtime section to remove duplicated detail.

Dimension	Reasoning	Score
Conciseness	Mostly efficient operative detail, but the runtime fallback rule is restated in the table, prose, and a gotcha, and the ~5-line runtime-change gotcha duplicates the Switching Runtime section; some tightening possible.	2 / 3
Actionability	Copy-paste-ready commands with real flags (agt create worker --name ... --no-wait --soul ...), a concrete runtime table, and full script invocations give fully executable guidance.	3 / 3
Workflow Clarity	Sequences are explicit (confirm inputs -> create -> poll phase=Running; 3-step reconcile for runtime switch) with validation checkpoints and mid-task confirmations before destructive changes.	3 / 3
Progressive Disclosure	An overview SKILL.md with a navigation table pointing one level deep to verified references/ and scripts/ files; details are offloaded and only what is needed is inline.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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

The description is specific, trigger-rich, and explicitly scoped, with a clear Use-when clause and a boundary statement separating it from a sibling discovery helper. It reads naturally as something an admin would request.

Dimension	Reasoning	Score
Specificity	"hand-creating or resetting a Worker, starting/stopping a Worker, managing Worker skills, enabling peer mentions, or opening a QwenPaw console" lists multiple distinct concrete actions rather than vague language.	3 / 3
Completeness	The explicit "Use when admin requests..." clause answers both what the skill does and when to invoke it.	3 / 3
Trigger Term Quality	Natural phrasings like "create or reset a Worker", "start/stop", "manage Worker skills", and "peer mentions" map to how an admin would phrase the request.	3 / 3
Distinctiveness Conflict Risk	The scoped niche (worker lifecycle admin) plus the boundary-setting sentence limiting agentteams-find-worker to market import/discovery makes conflict with other skills unlikely.	3 / 3
	Total	12 / 12 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/worker-management/SKILL.md
Commit: 785c2db

Reviewed: 7 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.