teamharness-organization

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

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

87%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 a lean, well-organized reference with concrete file paths and actionable ownership guardrails. Its only weak spot is workflow clarity, which is limited because the skill is reference-oriented rather than a sequenced process.

Dimension	Reasoning	Score
Conciseness	Lean and well-organized; lists ownership responsibilities without padding or explaining concepts Claude already knows, and the brief intro serves as framing rather than fluff.	3 / 3
Actionability	Provides concrete, specific guidance — real file paths ('shared/tasks/{task-id}/spec.md', 'result.md', 'TEAMS.md'), explicit ownership lists, and actionable guardrails rather than vague direction.	3 / 3
Workflow Clarity	Content is clearly organized into sections, but this is a reference skill with no multi-step process to sequence and no validation checkpoints, so it does not reach the explicit-sequence bar of the level-3 anchor.	2 / 3
Progressive Disclosure	A short, single-purpose skill with no external references needed, organized into clear sections (Role Boundaries, Safety Boundary), satisfying progressive disclosure for a sub-50-line skill.	3 / 3
	Total	11 / 12 Passed

Description

57%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 clearly scoped to a distinct TeamHarness niche and names concrete ownership domains, but it relies on an abstract verb and lacks an explicit 'Use when' trigger condition, leaving completeness and trigger quality at the mid level.

Suggestions

Add an explicit 'Use when...' clause naming the situations that should trigger this skill (e.g., 'Use when the user asks who owns a TeamHarness workstream or how team responsibilities are divided').

Replace or supplement the abstract 'understand' verb with concrete reasoning actions (e.g., 'determine', 'assign', 'check ownership of').

Soften jargon like 'control-plane' and 'runtime' with plain-language equivalents to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete ownership areas ('project, task, runtime, and control-plane work'), but the single abstract verb 'understand' does not enumerate distinct concrete actions like the level-3 anchor.	2 / 3
Completeness	States what the skill does and includes a 'Use to' purpose clause, but lacks an explicit 'Use when...' trigger condition describing when Claude should invoke it, which caps completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Includes relevant natural terms a user might say ('team roles', 'responsibility boundaries', 'who owns'), but leans technical with 'control-plane' and 'runtime' and omits simpler phrasings.	2 / 3
Distinctiveness Conflict Risk	Clearly scoped to TeamHarness team roles and ownership boundaries — a distinct niche unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 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: plugins/teamharness/skills/team/organization/SKILL.md
Commit: 785c2db

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