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

73%

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/teamharness/skills/team/organization/SKILL.md
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.

The body is a well-organized, appropriately scoped reference that gives concrete, actionable role boundaries and a clear safety section. Its main weaknesses are minor redundancy between the summary paragraph and the detailed sections, and the absence of small examples that would make the guidance fully copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence, but the opening paragraph ('Leader owns planning, delegation, acceptance, and requester reporting. Workers own assigned task execution.') duplicates the Role Boundaries section that follows, and 'Treat remote members as participants...' restates the earlier prohibition — minor trimming possible, matching anchor 4.

4 / 5

Actionability

As an instruction-only skill the guidance is concrete: exact paths ('shared/tasks/{task-id}/spec.md', 'result.md'), specific deliverables, and explicit escalation ('report the blocker to Manager or platform Admin'). It stops short of fully executable coverage because no examples of specs, results, or blocker reports are given, matching anchor 4.

4 / 5

Workflow Clarity

A simple single-purpose reasoning skill whose role boundaries are unambiguous; the Worker list implies a lifecycle order (acknowledge, read spec, produce, submit, report). It lacks explicit checkpoint guidance for boundary-conflict situations beyond 'report the blocker', keeping it at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist in the bundle), and is organized into clear sections (Role Boundaries, Safety Boundary) with no buried or nested references — per the simple-skill guidance this matches anchor 5.

5 / 5

Total

17

/

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 identifies a clear niche and a concrete purpose but omits any explicit trigger guidance, which limits its discoverability. Users asking about role boundaries would likely find it, yet the lack of a 'Use when...' clause leaves the 'when' half of the description implicit.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working in or reasoning about a TeamHarness team, assigning tasks, or deciding who owns a piece of work.'

Include natural user phrasings such as 'who does what', 'delegation', or 'task ownership' alongside the current terms to broaden trigger coverage.

Trade the jargon-heavy 'control-plane work' for a plainer term (or pair it with one) so the description reads naturally to non-platform users.

DimensionReasoningScore

Specificity

The description names the domain ('TeamHarness team roles, responsibility boundaries') and one action ('understand') applied to a scoped set of objects ('project, task, runtime, and control-plane work'), matching the anchor for domain plus 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

The 'what' is concrete (understand roles, boundaries, and ownership), but the 'Use to understand...' phrasing describes function rather than when to invoke the skill; there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

'team roles', 'responsibility boundaries', and 'who owns' are reasonably natural phrases, but common variations like 'delegation', 'task assignment', or 'who does what' are missing and 'control-plane' is system jargon, matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'TeamHarness' scopes the skill to a clear niche with low conflict risk, but generic terms like 'team roles' and 'responsibility boundaries' create minor overlap risk with other team-organization skills, matching the 'mostly distinct; minor overlap risk' anchor rather than the fully distinct anchor 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/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.