CtrlK
BlogDocsLog inGet started
Tessl Logo

teamharness-organization

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

58

Quality

66%

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 lean, well-structured instruction-only skill that gives concrete ownership rules and safety boundaries with specific file paths; it is strong overall with only minor opportunities to add examples and remove small redundancies.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, listing concrete ownership duties without explaining concepts Claude already knows; minor redundancy ('Manager owns control-plane operations' appears in both the intro and Role Boundaries, and the opening restates the description) keeps it just short of fully lean.

4 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill, citing exact paths like `shared/tasks/{task-id}/spec.md`, `result.md`, and `TEAMS.md` with specific do/don't rules; it stops short of 5 only because there are no concrete examples of what a spec or result.md should contain.

4 / 5

Workflow Clarity

As a single-purpose guidance skill under 50 lines it is clear and well-organized, with an implicit Worker sequence (acknowledge → read spec → produce → submit → report); it lacks explicit validation checkpoints, but no destructive/batch workflow is present so the cap does not apply.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is well-organized into clearly signaled sections (Role Boundaries, Safety Boundary), meeting the simple-skill exception for a top score with well-organized sections.

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 clearly scopes the skill to TeamHarness organization and ownership, but leads with a single generic verb and lacks an explicit 'Use when...' trigger clause, leaving the triggering situation implied rather than concrete.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggering situations, e.g. 'Use when assigning work across Leader/Worker roles, resolving who owns a task, or deciding whether an action crosses a role boundary.'

Replace the single generic verb 'understand' with multiple concrete actions the skill supports (e.g. 'assign, track, and report team work; resolve role-boundary questions').

Include natural trigger synonyms a user would actually say, such as 'who owns this task', 'team roles', or 'Leader vs Worker', alongside the current terminology.

DimensionReasoningScore

Specificity

The description names the domain ('TeamHarness team roles, responsibility boundaries') and several ownership areas (project, task, runtime, control-plane), but relies on a single generic verb ('understand') rather than listing several concrete actions, matching the 'names domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

The 'what' is clear (understand roles/boundaries/ownership), but the trigger guidance is 'Use to understand...' (purpose) rather than an explicit 'Use when...' clause naming situations; per the guidelines a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like 'team roles', 'responsibility boundaries', and 'who owns' are somewhat natural, but the phrasing is abstract and technical ('control-plane', 'responsibility boundaries') and lacks common synonyms a user would naturally say, fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

Naming the specific 'TeamHarness' system and scoping to organization/ownership gives a clear niche with minimal conflict risk, though 'team roles' and 'responsibility boundaries' could overlap with other team-management skills, fitting 'mostly distinct; minor overlap risk'.

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.

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.