CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

teamharness-project-management

Use when you act as Leader and maintain durable TeamHarness project state for Quick Task or Project Work: create_quick_project, create_project, plan_dag, plan_loop, ready_nodes, resolve_project, accept_task_result, project completion, and requester report state. Do not use to create Matrix task rooms or send messages.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/teamharness/skills/team/project-management/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-sequenced operational protocol: concrete JSON payloads, explicit validation gates, conflict fences, and checklists make it executable end to end. Its weaknesses are token efficiency (duplicated requester-report and scope statements) and a monolithic single-file layout where large, rarely-needed templates and protocol details should be split into one-level-deep reference files.

Suggestions

Move the Project Status Reports template and envelope spec into a references/ file (e.g., references/report-template.md) and keep only the marker table and a short pointer inline.

Deduplicate the requester-report delivery and artifact-publish steps that currently appear in both 'Accepting Worker Results' and 'Project Status Reports' into a single canonical sequence.

Trim the restated scope/description lines ('Use this skill when maintaining durable project state', the 'Use this skill when acting as Leader for' list) since the frontmatter description already carries that trigger information.

DimensionReasoningScore

Conciseness

Almost all content is proprietary TeamHarness protocol Claude could not know, with no explanations of generic concepts, but there is noticeable redundancy: 'Use this skill when maintaining durable project state' and the Scope list restate the frontmatter, and the requester-report plus artifact-publish steps are duplicated across 'Accepting Worker Results' and 'Project Status Reports'. Mostly efficient, yet several passages could be tightened or merged.

3 / 5

Actionability

Every action ships a complete copy-paste JSON payload (create_project, create_quick_project, plan_dag, plan_loop, ready_nodes, ready_loop_nodes, record_loop_iteration, resolve_project, accept_task_result, pause/resume/complete), with exact file paths, a safe-ID regex, the decision enum, and a concrete notification format. Placeholders like '<current task.submission_id from check_task>' are appropriately bounded.

5 / 5

Workflow Clarity

Sequences are explicit with validation gates throughout: send the assignment message 'only after the tool returns ok: true', accept only after the delegation check 'returns effective: true', do not notify 'if the tool returned ok: false', complete_project only when every task is terminal, and the submissionId fence defines conflict/retry behavior. Numbered checklists for report delivery (steps 1-6) and notification handling (steps 1-5) provide the checklist-and-feedback-loop structure of the top anchor.

5 / 5

Progressive Disclosure

Section headers are clear and the 'Current Boundary' section accurately scopes supported actions, but the skill is a single ~650-line file with no bundle references at all. Content that clearly belongs in separate reference files is inlined — the ~100-line Project Status Reports template, the notification field spec, and the long accept/cancel protocol — so it fits 'some structure, content that should be separate is inline'.

3 / 5

Total

16

/

20

Passed

Description

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

A specific, well-bounded description that names its concrete actions and includes both an explicit use-when clause and a do-not-use boundary. Its main weakness is trigger phrasing built from internal tool-action jargon rather than natural user language, which limits discoverability and keeps completeness and distinctiveness one notch below top.

Suggestions

Add natural-language trigger phrases users would actually say (e.g., 'create a project', 'plan task dependencies', 'accept worker results', 'project status report') alongside the tool-action names.

Include common synonyms or variations of the domain terms (project planning, DAG, task dependencies, iteration loop) so the description matches how requesters phrase these requests.

Clarify the 'Leader' and 'Quick Task or Project Work' terms with one plain-language gloss so the when-clause is triggerable by non-TeamHarness vocabulary.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('create_quick_project, create_project, plan_dag, plan_loop, ready_nodes, resolve_project, accept_task_result, project completion, and requester report state') covering the skill's full capability surface. Coverage is comprehensive rather than minor-gapped, matching the top anchor.

5 / 5

Completeness

Both halves are explicit: 'what' via the named action list and 'when' via 'Use when you act as Leader and maintain durable TeamHarness project state for Quick Task or Project Work', plus a negative boundary ('Do not use to create Matrix task rooms or send messages'). The 'when' clause leans on role/mode jargon instead of concrete natural trigger phrases, so it does not reach the top anchor.

4 / 5

Trigger Term Quality

Relevant domain keywords exist ('project state', 'project completion', 'Quick Task or Project Work') but the trigger vocabulary is dominated by technical tool-action names rather than phrases a user would naturally say. Common variations like 'create a project', 'task plan', or 'dependencies' are missing, so it sits at 'some relevant keywords' rather than good coverage.

3 / 5

Distinctiveness Conflict Risk

Scoping to the TeamHarness Leader role with tool-specific action names and an explicit exclusion makes it mostly distinct with only minor overlap risk against the closely related sibling teamharness skills. It is not a fully clear niche because generic 'project' language could still collide with general project-management skills.

4 / 5

Total

16

/

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

skill_md_line_count

SKILL.md is long (658 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

agentscope-ai/AgentTeams

Path

plugins/teamharness/skills/team/project-management/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.