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

78%

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-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tidy, well-structured short skill with direct commands and good organization, weakened mainly by a vague workflow middle step and a couple of soft action items that undercut actionability and workflow clarity.

Suggestions

Replace 'Execute the task following normal task execution flow' in Workflow step 2 with concrete, specific guidance or a pointer to where the normal flow is defined.

Make 'mark it as started in your memory' actionable by specifying the exact memory write (e.g. the field/path to set and its expected value).

Add a small validation checkpoint — e.g. confirm the plan.md path exists before reading, or verify git author config after setting it — to strengthen the workflow's feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean — short bullets, direct bash snippets, and no padding explaining concepts Claude already knows — so every token earns its place per the lean-and-efficient anchor rather than the mostly-efficient-but-could-tighten level.	3 / 3
Actionability	Provides concrete executable commands (cat, git config) but leaves key guidance incomplete, e.g. 'Execute the task following normal task execution flow' and 'mark it as started in your memory' are vague, matching the some-concrete-but-incomplete anchor rather than fully copy-paste-ready.	2 / 3
Workflow Clarity	The 3-step workflow is sequenced, but step 2 is hand-wavy ('following normal task execution flow') and there is no validation/feedback checkpoint, fitting the steps-listed-but-validation-gaps anchor rather than the explicit-checkpoint level.	2 / 3
Progressive Disclosure	Under 50 lines with no bundle files, organized into clear sections (Gotchas, Project Context, Workflow, Git Config) with no nested references, so the simple-skill carve-out allows a top score rather than a could-be-better-organized 2.	3 / 3
	Total	10 / 12 Passed

Description

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

A strong, concise description that pairs an explicit Use-when trigger with three concrete capabilities and a well-scoped niche, though the trigger language leans on internal terminology a user might not naturally voice.

Dimension	Reasoning	Score
Specificity	Names three concrete actions ('project plan reading, task coordination with other Workers, and git author config'), matching the multiple-specific-actions anchor rather than a single domain mention.	3 / 3
Completeness	Explicitly answers both what it does ('Covers project plan reading, task coordination with other Workers, and git author config') and when to use it ('Use when you are invited to a Project Room...'), matching the clear what-and-when anchor rather than an implied-when level.	3 / 3
Trigger Term Quality	Contains a natural trigger ('invited to a Project Room or assigned a task within a multi-worker project') but the vocabulary is specialized and omits common user-level phrasings, landing on 'some relevant keywords but missing common variations' rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche (multi-worker Project Rooms) with a distinct trigger unlikely to fire for unrelated skills, matching the clear-niche anchor instead of the overlapping-skill level.	3 / 3
	Total	11 / 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/hermes-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.