CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

teamharness-organization

Use to understand TeamHarness team roles, responsibility boundaries, and who owns project, task, runtime, and control-plane work.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/agentteams-teamharness/skills/team/organization/SKILL.md

The canonical home for this skill is teamharness-organization in agentscope-ai/AgentTeams

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 tight, self-contained reference with concrete per-role duties, specific file-path conventions, explicit anti-patterns, and a well-scoped safety boundary — everything is actionable with no filler or background explanation. Its only notable flaw is mild redundancy between the intro summary and the Role Boundaries section. Organization and disclosure are exemplary for a skill of this size.

DimensionReasoningScore

Conciseness

The body is efficient with no explanations of concepts Claude already knows, but the opening summary ('Leader owns planning, delegation, acceptance... Manager owns control-plane operations') and 'Use this skill to reason about team roles...' largely duplicate the description and the Role Boundaries section, matching 'efficient; minor instances that could be trimmed'.

4 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill — specific paths like 'shared/tasks/{task-id}/spec.md', 'submitting result.md', and 'refer only to the approved credential name or environment variable name, not its value' — but there are no examples (e.g., of a blocker report or acceptance decision), leaving minor gaps versus fully executable guidance.

4 / 5

Workflow Clarity

This is a simple, single-purpose conceptual skill under 50 lines, and the per-role duty lists (acknowledge → read spec → produce deliverables → submit result.md → report) are unambiguous and well-sequenced; no destructive or batch operations are involved, so the simple-skill exception applies and the single action is fully clear.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (no references/, scripts/, or assets/ exist) and no need for external references; the content is split into clear, well-organized sections (Role Boundaries, Safety Boundary) with nothing that belongs in a separate file, which scores 5 under the simple-skill provision.

5 / 5

Total

18

/

20

Passed

Description

53%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 clearly identifies the domain and purpose but reads as a scope statement rather than a trigger-rich invocation: it has a clear 'what' with no explicit 'Use when...' guidance and only one action verb. It is distinctive thanks to the TeamHarness naming, yet misses natural trigger phrasing users would say. Adding an explicit when-clause with concrete trigger phrases would lift completeness, specificity, and trigger quality simultaneously.

Suggestions

Add an explicit 'Use when...' clause with concrete triggers, e.g., 'Use when deciding who should perform a task, clarifying Leader/Worker/Manager responsibilities, or checking whether an action crosses a role or control-plane boundary.'

Include natural trigger terms and synonyms users would say, such as 'leader', 'worker', 'manager', 'delegation', 'task assignment', or 'who should do this'.

Replace the single verb 'understand' with multiple concrete actions like 'determine task ownership, assign responsibilities, and escalate blockers to the right role'.

DimensionReasoningScore

Specificity

The description names the domain clearly ("TeamHarness team roles, responsibility boundaries") and enumerates ownership areas ("project, task, runtime, and control-plane work"), but offers only one action verb ("understand"), matching the anchor for a clear domain with 1-2 concrete actions rather than the several specific actions of level 4.

3 / 5

Completeness

The 'what' is clear ("understand TeamHarness team roles, responsibility boundaries, and who owns ... work"), but there is no explicit 'Use when...' clause or equivalent trigger guidance — "Use to understand" states purpose only weakly implying 'when' — so completeness is capped at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Terms like "team roles" and "who owns ... work" are natural, but the description omits common variations users would actually say, such as "leader", "worker", "manager", "delegation", or "who should do this task", matching the 'some relevant keywords but missing synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

The proper noun "TeamHarness" plus the specific ownership scopes give the skill a clear niche with minimal conflict risk, but generic phrases like "team roles" and "responsibility boundaries" could overlap with other team-management skills, fitting 'mostly distinct; minor overlap risk' rather than the fully distinct level 5.

4 / 5

Total

13

/

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

agentscope-ai/AgentTeams

Path

plugins/agentteams-teamharness/skills/team/organization/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.