persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
53
42%
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 reasonable but high-level summary of project coordination capabilities. Its main weaknesses are the complete absence of explicit trigger guidance ('Use when...') and its broad scope that could easily conflict with more specialized task, scheduling, or document-sharing skills. Adding explicit triggers and more specific actions would significantly improve skill selection accuracy.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'project management', 'coordinate team', 'track progress', 'schedule a meeting', 'share documents with team'.
Increase distinctiveness by specifying what makes this a unified project coordination skill rather than separate task/meeting/doc skills — e.g., 'Manages cross-functional project workflows combining task tracking, meeting scheduling, and document sharing in a single coordinated view.'
Include more natural keyword variations users might say, such as 'to-do list', 'deadlines', 'milestones', 'agenda', 'calendar', 'collaboration'.
| 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 — e.g., it doesn't specify what kind of tasks, what scheduling entails, or what document sharing involves. | 2 / 3 |
Completeness | It describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent and the 'what' is only moderate, this scores at the lower end. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'tasks', 'meetings', 'docs', and 'projects', but misses common variations users might say such as 'project management', 'to-do', 'calendar', 'agenda', 'deadlines', 'milestones', or 'collaboration'. | 2 / 3 |
Distinctiveness Conflict Risk | The description is very broad — 'track tasks, schedule meetings, and share docs' could overlap with task management skills, calendar/scheduling skills, and document sharing skills individually. There's nothing that carves out a clear, distinct niche. | 1 / 3 |
Total | 6 / 12 Passed |
Implementation
60%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is concise and well-structured as a coordination hub, effectively pointing to sub-skills and workflows. However, it lacks sequenced multi-step workflows with validation checkpoints and provides mostly high-level directions rather than fully concrete, executable examples with expected outputs.
Suggestions
Add at least one end-to-end sequenced workflow (e.g., 'Weekly project update process: 1. Run digest → 2. Review output → 3. Append status to sheet → 4. Send email') with explicit validation/verification steps between stages.
Include a concrete, complete example for a common task (e.g., a full `gws sheets +append` command with sample arguments and expected output) to improve actionability.
Integrate the `--dry-run` tip into the workflow as an explicit validation checkpoint before write operations rather than listing it as a standalone tip.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. No unnecessary explanations of what project management is or how the underlying tools work. Every line provides actionable guidance or a concrete command reference. | 3 / 3 |
Actionability | The skill provides specific command references (e.g., `gws sheets +append`, `gws drive +upload`) and one concrete example with flags (`gws drive files list --params ...`), but most instructions are high-level directions rather than fully executable, copy-paste-ready examples with complete arguments and expected outputs. | 2 / 3 |
Workflow Clarity | The instructions are a loose collection of tips rather than a sequenced workflow. There is no clear ordering of steps for a project coordination process, no validation checkpoints, and no feedback loops for error recovery. The `--dry-run` tip is mentioned but not integrated into a workflow sequence. | 1 / 3 |
Progressive Disclosure | The skill acts as a clear overview/coordinator, pointing to specific utility skills (`gws-drive`, `gws-sheets`, etc.) and named workflows (`+standup-report`, `+weekly-digest`, `+file-announce`) as one-level-deep references. Content is well-organized into short, navigable sections. | 3 / 3 |
Total | 9 / 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
c7c6646
- 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.