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

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%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, well-organized coordination skill with concrete commands and a clear three-step workflow. It assumes Claude's competence and contains no padded explanation, matching the lean ideal for a simple skill.

Dimension	Reasoning	Score
Conciseness	The body is lean with no explanations of concepts Claude already knows; every section (Gotchas, Project Context, Workflow, Git Config) earns its place and respects the token budget.	3 / 3
Actionability	Provides concrete, executable commands — `cat /home/openhuman/.openhuman/shared/projects/{project-id}/plan.md` and the `git config user.name`/`user.email` lines — that are copy-paste ready with clear template placeholders.	3 / 3
Workflow Clarity	The three-step workflow (mark started, execute, report via @mention) is clearly sequenced; no destructive or batch operation is involved, so the absence of a validation checkpoint does not cap the score.	3 / 3
Progressive Disclosure	Under 50 lines with no need for external references, and content is organized into clearly labeled sections, which satisfies the simple-skill allowance for a top score.	3 / 3
	Total	12 / 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, third-person, and cleanly pairs an explicit 'Use when...' trigger with a concrete list of covered capabilities. It avoids fluff and is clearly scoped to the multi-worker project niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "project plan reading", "task coordination with other Workers", and "git author config" — matching the anchor for listing several specific concrete actions rather than vague language.	3 / 3
Completeness	Explicitly answers both halves: an explicit "Use when..." trigger clause (when) and a "Covers..." summary (what), matching the top anchor.	3 / 3
Trigger Term Quality	Natural phrases a user would say ("invited to a Project Room", "assigned a task within a multi-worker project") give good coverage of realistic trigger language, not technical jargon.	3 / 3
Distinctiveness Conflict Risk	The "Project Room" / "multi-worker project" niche is distinct with clear triggers unlikely to fire for unrelated skills; not above 3 because 3 is the max and it clearly meets it, not below because it is not generic.	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/openhuman-worker-agent/skills/project-participation/SKILL.md
Commit: 785c2db

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