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.

Quality

75%

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 ./manager/agent/hermes-worker-agent/skills/project-participation/SKILL.md

Quality

Content

72%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 content is concise and gives concrete commands for its core operations, with clean section organization. The main gap is the workflow lacking a verification step before the consequential @mention that advances the project.

Suggestions

Add an explicit verification checkpoint in the Workflow before reporting completion (e.g., confirm the task's deliverable/result file exists and the plan.md task is marked complete) so the @mention only fires after validation.

De-duplicate the 'auto-synced plan' note between the Gotchas and Project Context sections to tighten the body further.

Replace the vague 'Execute the task following normal task execution flow' step with a concrete pointer to what execution entails in this project context.

Dimension	Reasoning	Score
Conciseness	The body is lean with executable commands and no padding about concepts Claude already knows, but the 'auto-synced' detail is repeated across the Gotchas and Project Context sections, a minor redundancy that keeps it off the top anchor.	4 / 5
Actionability	Provides copy-paste-ready commands (`cat ~/shared/projects/{project-id}/plan.md`, `git config user.name/email`), but the workflow steps ('Execute the task following normal task execution flow') stay high-level, leaving a minor gap.	4 / 5
Workflow Clarity	The three-step workflow is clearly sequenced (mark started, execute, report via @mention) but lacks any validation checkpoint before reporting completion, which advances the project — matching the anchor with sequence present but checkpoints missing.	3 / 5
Progressive Disclosure	A simple under-50-line skill with no external references needed; it is organized into clear, well-labeled sections (Gotchas, Project Context, Workflow, Git Config) that satisfy the simple-skill exception for the top anchor.	5 / 5
	Total	16 / 20 Passed

Description

78%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 is well-structured with an explicit 'Use when' trigger and a clear list of covered activities, hitting both what and when. It is slightly held back by the high-level phrasing of its action list.

Dimension	Reasoning	Score
Specificity	Names the domain and three actions ('project plan reading, task coordination with other Workers, and git author config'), but each is stated at a high level rather than as concrete operations, so it sits at the anchor listing 1-2 concrete actions rather than the more granular anchor 4.	3 / 5
Completeness	Explicitly answers both what ('Covers project plan reading, task coordination... and git author config') and when ('Use when you are invited to a Project Room or assigned a task within a multi-worker project') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'invited to a Project Room' and 'assigned a task within a multi-worker project' match what a coordinator would actually say, giving good keyword coverage with only minor synonyms missing.	4 / 5
Distinctiveness Conflict Risk	The 'Project Room' / 'multi-worker' / 'coordinator' framing carves a clear niche, though generic words like 'task' and 'project' leave minor overlap risk with general task-execution skills.	4 / 5
	Total	16 / 20 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: manager/agent/hermes-worker-agent/skills/project-participation/SKILL.md
Commit: 223ddc2

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