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

93%

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

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 tight, actionable instruction skill with concrete commands and exact file paths. Its only gap is workflow clarity: the main workflow is somewhat high-level and lacks explicit checkpoints or a self-contained execution description.

Suggestions

Replace 'Execute the task following normal task execution flow' with the concrete next actions so the workflow is self-contained.

Add an explicit validation checkpoint after task execution (e.g. confirm plan status legend updated / dependencies satisfied) before the @mention report step.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding or explanation of concepts Claude already knows — e.g. 'Always sync before reading project plan — `agentteams-sync` first'. Every token earns its place.	3 / 3
Actionability	Provides concrete, executable commands and exact paths — `agentteams-sync`, `/root/agentteams-fs/shared/projects/{project-id}/plan.md`, and the `git config` lines — plus a copy-paste-ready status legend.	3 / 3
Workflow Clarity	The Workflow steps are sequenced (sync -> read plan -> execute -> @mention report) but one step defers to unspecified 'normal task execution flow' and validation/checkpoints are only implicit, matching the 2-anchor.	2 / 3
Progressive Disclosure	Under 50 lines with no external references and four well-organized sections (Gotchas, Project Context, Workflow, Git Config), which the rubric permits to score 3 for simple skills.	3 / 3
	Total	11 / 12 Passed

Description

100%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 concise and well-constructed: it opens with an explicit 'Use when' trigger, names three concrete capabilities, and carves out a distinct multi-worker-project niche. It scores at the top of every dimension.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'project plan reading, task coordination with other Workers, and git author config' — matching the 3-anchor exemplar that enumerates distinct operations.	3 / 3
Completeness	Explicitly answers both 'what' (the three covered activities) and 'when' ('Use when you are invited to a Project Room or assigned a task...'), satisfying the explicit-trigger requirement.	3 / 3
Trigger Term Quality	Natural phrasing a user would say: 'invited to a Project Room or assigned a task within a multi-worker project' covers the domain's common triggers well, with no jargon.	3 / 3
Distinctiveness Conflict Risk	A clear, narrow niche (multi-worker project coordination plus git author config) with distinctive triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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: manager/agent/worker-agent/skills/project-participation/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.