CtrlK
BlogDocsLog inGet started
Tessl Logo

project-participation

Use when you are invited to a Project Room or assigned a task within a multi-worker project. Covers project plan reading, task coordination with other Workers, and git author config.

64

Quality

76%

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 ./manager/agent/worker-agent/skills/project-participation/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 tight, well-structured, actionable skill with concrete commands and a clear workflow supported by a Gotchas quick-reference. The main weakness is minor redundancy between the Gotchas and the detailed sections.

Suggestions

Either trim the Gotchas to non-obvious pitfalls only, or drop the restated detail from later sections, to remove the sync/git-author/report repetition.

Replace "Execute the task following normal task execution flow" with a concrete pointer or one-line example of what execution entails.

Add a brief example of the completion @mention format (e.g., `@coordinator Task 3 complete: <result link>`) to make the final workflow step copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean with no padding or explanation of concepts Claude already knows, but the Gotchas section repeats guidance (sync first, git author, report completion) that is restated in the later sections.

4 / 5

Actionability

Concrete, copy-paste-ready commands are provided (`agentteams-sync`, the plan path, and `git config` lines), but "Execute the task following normal task execution flow" is abstract and no example @mention format is shown.

4 / 5

Workflow Clarity

A clear three-step sequence is given with the Gotchas acting as implicit checkpoints (sync before read, set git author before commits), though there is no explicit verification that sync or git config succeeded.

4 / 5

Progressive Disclosure

At under 50 lines with no need for external references, the content is cleanly organized into well-signaled sections (Gotchas, Project Context, Workflow, Git Config) meeting the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

75%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 cleanly states both when to use the skill and what it covers with concrete, domain-specific trigger language. It is a solid, concise description that would score higher with richer capability detail and more trigger variations.

Suggestions

Expand the capability list with one more concrete action (e.g., reading task dependencies, posting task results) to push specificity toward comprehensive coverage.

Add a synonym or alternate trigger phrasing (e.g., "multi-worker collaboration" or "shared project workspace") to broaden natural keyword coverage.

Tighten distinctiveness by pairing "assigned a task" with the multi-worker qualifier in the trigger clause itself.

DimensionReasoningScore

Specificity

"Covers project plan reading, task coordination with other Workers, and git author config" lists several concrete capabilities rather than vague abstractions, though the actions are terse and not deeply elaborated.

4 / 5

Completeness

Both the "Use when..." trigger and the "Covers..." capability list are present and explicit, satisfying what and when, but the what is a brief list rather than the richer detail of a top anchor.

4 / 5

Trigger Term Quality

"invited to a Project Room" and "assigned a task within a multi-worker project" are natural trigger phrases a user would say, but synonym/variation coverage is limited.

4 / 5

Distinctiveness Conflict Risk

The Project Room / multi-worker framing carves a clear niche, but "assigned a task" is somewhat generic and could overlap with general task-execution skills.

4 / 5

Total

16

/

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.