persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
57
48%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/persona-project-manager/SKILL.mdQuality
Discovery
25%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 provides a basic overview of project coordination capabilities but is too brief and generic to effectively differentiate itself from other skills. It lacks explicit trigger guidance ('Use when...') and doesn't include enough natural keywords or specific actions to help Claude reliably select it in the right contexts.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'project management', 'task tracking', 'schedule a meeting', 'share documents', 'deadlines', 'milestones', 'to-do list'.
Increase specificity by listing more concrete actions, e.g., 'Creates task lists with assignees and deadlines, schedules calendar meetings with agendas, shares and organizes project documents.'
Narrow the scope or add distinguishing details to reduce conflict risk with other scheduling, task management, or document-sharing skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names a domain (project coordination) and lists some actions (track tasks, schedule meetings, share docs), but these are fairly high-level and not deeply specific about concrete capabilities like creating Gantt charts, assigning task owners, or integrating with specific tools. | 2 / 3 |
Completeness | Describes what the skill does (coordinate projects, track tasks, schedule meetings, share docs) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also somewhat thin, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'tasks', 'meetings', 'docs', and 'projects', but misses common user variations such as 'project management', 'to-do', 'agenda', 'calendar', 'deadlines', 'milestones', or tool-specific terms. | 2 / 3 |
Distinctiveness Conflict Risk | Very generic description that could overlap with task management skills, calendar/scheduling skills, document sharing skills, or general productivity tools. 'Coordinate projects' is broad enough to conflict with many other skills. | 1 / 3 |
Total | 6 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a concise, well-organized orchestration skill that effectively delegates to sub-skills and workflows. Its main weaknesses are the lack of concrete, executable examples showing full command invocations with realistic arguments, and the absence of validation/verification steps in what are essentially multi-step batch operations (upload then announce, schedule then confirm).
Suggestions
Add at least one fully executable end-to-end example showing a complete workflow (e.g., uploading a file and announcing it) with realistic arguments and expected output.
Integrate the `--dry-run` tip directly into the workflow instructions as an explicit validation checkpoint before write operations, rather than leaving it as a separate tip.
Add verification steps after key operations (e.g., confirm file upload succeeded before announcing, verify calendar event was created with correct attendees).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. No unnecessary explanations of what project management is or how the tools work. Every line provides actionable direction, and it correctly assumes Claude knows the underlying concepts. | 3 / 3 |
Actionability | The skill provides specific command references (e.g., `gws sheets +append`, `gws drive +upload`) and one concrete example with flags, but most instructions are high-level directions rather than fully executable, copy-paste-ready commands with complete arguments. There are no concrete input/output examples showing a full workflow execution. | 2 / 3 |
Workflow Clarity | Steps are listed but presented as loosely ordered bullet points rather than a clear sequence. There are no validation checkpoints — for instance, no verification after uploading files, no confirmation step after scheduling meetings, and no feedback loop for error recovery. The `--dry-run` tip is helpful but buried in Tips rather than integrated into the workflow. | 2 / 3 |
Progressive Disclosure | The skill is well-structured as a concise overview that delegates to utility skills (`gws-drive`, `gws-sheets`, etc.) and named workflows (`+standup-report`, `+weekly-digest`, `+file-announce`). References are one level deep and clearly signaled. Content is appropriately split across the prerequisite skills. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- googleworkspace/cli
- Commit
a3768d0
- 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.