CtrlK
BlogDocsLog inGet started
Tessl Logo

organization

Use before any Leader action that depends on current team topology, worker list, worker phase, runtime, room ID, Matrix ID, Team Admin, human identity, or lifecycle state. Always use this skill when assigning tasks, sending cross-room messages, recovering projects, handling heartbeat, waking/sleeping workers, or when any worker/room/identity value might be stale.

68

Quality

83%

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

78%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 tight, actionable skill body with concrete CLI commands, a clear source-of-truth workflow, and an explicit validation checkpoint. Consolidating the repeated Team CR guidance and adding a feedback loop around state-changing lifecycle commands would push it higher.

Suggestions

Consolidate the Team CR name clarification so it is stated once rather than repeated in both the 'Source Of Truth' narrative and the post-code-block note.

Add a short validate-then-retry step for the wake/sleep lifecycle commands (e.g. re-check 'agt worker status' after ensure-ready) to form an explicit feedback loop around state changes.

Replace the '<worker-name>' placeholder with a concrete example value or a one-line note on how to obtain it from the prior 'agt get workers' output.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's domain competence without explaining Kubernetes, Matrix, or CR concepts; the Team CR clarification is restated across two sections and could be consolidated, but otherwise every token earns its place.

4 / 5

Actionability

Provides two copy-paste bash blocks with real 'agt' commands and jq pipelines plus concrete variable resolution; only minor gaps such as the '<worker-name>' placeholder keep it from being fully self-contained.

4 / 5

Workflow Clarity

Clear sequence (resolve Team CR, read state, run lifecycle) with an explicit validation checkpoint ('If CLI output is missing a required room ID... stop and report a metadata problem. Do not guess.'), though the state-changing lifecycle commands lack a full validate-fix-retry loop.

4 / 5

Progressive Disclosure

A short single-purpose skill under 50 lines with no external references and well-organized sections, matching the simple-skill exception for full marks.

5 / 5

Total

17

/

20

Passed

Description

87%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, explicit description that clearly defines both purpose and trigger conditions with concrete, domain-natural phrasing. The main room for improvement is slightly broader synonym coverage of trigger terms.

DimensionReasoningScore

Specificity

Enumerates several concrete action domains ('assigning tasks, sending cross-room messages, recovering projects, handling heartbeat, waking/sleeping workers') alongside the state fields they depend on, with only minor coverage gaps.

4 / 5

Completeness

Explicitly states what the skill is for ('any Leader action that depends on current team topology, worker list...') and gives a concrete 'Always use this skill when...' clause listing triggers, answering both what and when.

5 / 5

Trigger Term Quality

Includes natural domain phrasing a user of this system would say ('assigning tasks', 'cross-room messages', 'waking/sleeping workers', 'heartbeat'), though a few synonyms or alternate phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (AgentTeams topology/runtime state resolution) with domain-specific terminology that minimizes overlap with unrelated skills.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
agentscope-ai/AgentTeams
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.