CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agentteams-test

Complete AgentTeams test cycle including installation, uninstallation, running tests, and exporting debug logs for analysis. Use for (1) verifying AgentTeams functionality (2) CI/CD test validation (3) issue diagnosis and debugging (4) pre-merge testing. Trigger words: test AgentTeams, run AgentTeams tests, agentteams test, make test, verify AgentTeams installation.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

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.

The body is a strong, highly actionable test-cycle runbook: nearly every instruction is an executable command, and the diagnose-interpret-cleanse flow has real error-recovery guidance. Its main weaknesses are the duplicated Quick Start vs. Full Test Cycle commands, an inline diagnosis section that overlaps the troubleshooting reference, and a script reference (export-debug-log.py) that is absent from the bundle.

Suggestions

Collapse the Quick Start and Full Test Cycle Step 1/Step 2 duplication into a single quick-start block that the detailed steps build on, trimming ~15 lines.

Replace the inline Common Issue Diagnosis detail with a brief symptom-to-cause table that points to references/troubleshooting.md for the full diagnosis commands.

Fix the "scripts/export-debug-log.py" reference (file is not in the bundle) and add the bundled scripts (agentteams-debug.sh, run-agentteams-test.sh) to the References section with their skill-relative paths.

DimensionReasoningScore

Conciseness

The body is dominated by lean, executable bash blocks with no padding or explanations of concepts Claude already knows. It falls short of anchor 5 because the Quick Start section duplicates the Full Test Cycle's commands (git clone, config setup, make test) almost verbatim, adding ~15 redundant lines.

4 / 5

Actionability

Every section provides copy-paste-ready commands: full test invocation with env loading, individual install/uninstall, debug log export, per-issue diagnosis commands, and cleanup. Specific examples cover the common cases (success summary, skipped tests, metrics files), matching the top anchor.

5 / 5

Workflow Clarity

The sequence (prepare environment → run full test → interpret results → diagnose issues → cleanup) is clear, and the Test Results Interpretation section plus per-issue diagnosis with fixes form a genuine feedback loop. It falls short of anchor 5 because there is no explicit verification step after install before running tests (validation relies on test-01 implicitly), and some checkpoints are implicit.

4 / 5

Progressive Disclosure

Good structure with well-signaled one-level-deep references: references/troubleshooting.md exists in the bundle and is linked from a References section, alongside relevant external GitHub docs. Minor gaps keep it from anchor 5: the inline Common Issue Diagnosis section substantially duplicates references/troubleshooting.md, and the referenced "scripts/export-debug-log.py" does not exist in the bundled scripts/ directory (which contains agentteams-debug.sh and run-agentteams-test.sh, neither linked from the References section).

4 / 5

Total

17

/

20

Passed

Description

96%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.

The description is excellent: it names four concrete actions, explicitly states use cases with numbered scenarios, and lists natural trigger phrases with variations. Its only weakness is the generic "make test" trigger term, which risks firing the skill outside the AgentTeams context.

DimensionReasoningScore

Specificity

"installation, uninstallation, running tests, and exporting debug logs for analysis" lists multiple specific concrete actions that comprehensively cover the complete test cycle, matching the top anchor. It exceeds anchor 4 because coverage is complete for the skill's domain rather than having minor gaps.

5 / 5

Completeness

Both "what" (complete test cycle with four named actions) and "when" ("Use for (1) verifying AgentTeams functionality (2) CI/CD test validation (3) issue diagnosis and debugging (4) pre-merge testing") are explicitly stated with concrete trigger phrases. This clearly matches anchor 5 rather than anchor 4, where the "when" would be less explicit.

5 / 5

Trigger Term Quality

Explicit trigger words "test AgentTeams, run AgentTeams tests, agentteams test, make test, verify AgentTeams installation" are natural user phrases with variations and synonyms of the core request. This matches anchor 5's comprehensive coverage; anchor 4 would require several natural terms to be missing, which is not the case.

5 / 5

Distinctiveness Conflict Risk

Mostly distinct: the AgentTeams-specific triggers carve a clear niche, but "make test" is a generic phrase that would naturally occur in any Makefile-based project, creating minor overlap risk. Not anchor 5 because that generic trigger could fire this skill for unrelated repositories; not anchor 3 since the remaining triggers are unambiguous.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

agentscope-ai/AgentTeams

Path

tests/skills/agentteams-test/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.