persona-team-lead
Lead a team — run standups, coordinate tasks, and communicate.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill persona-team-lead59
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%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 understanding of team leadership capabilities but lacks the explicit trigger guidance ('Use when...') that is critical for skill selection. The actions listed are moderately specific but could be more concrete, and the description would benefit from additional natural trigger terms users might employ when needing this skill.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about running team meetings, managing standups, delegating work, or coordinating team activities'
Include more natural trigger terms users would say: 'scrum', 'daily standup', 'team meeting', 'delegation', 'sprint planning', 'team coordination'
Make actions more concrete: instead of 'communicate', specify 'draft team updates, write status reports, facilitate team discussions'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names domain (team leadership) and some actions ('run standups, coordinate tasks, and communicate'), but these are somewhat generic management activities rather than highly specific concrete actions. | 2 / 3 |
Completeness | 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 rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this is weaker than that. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'standups', 'team', 'tasks', and 'coordinate' that users might say, but missing common variations like 'scrum', 'daily meeting', 'project management', 'delegation', or 'team management'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to team leadership context, but 'coordinate tasks' and 'communicate' are generic enough to potentially overlap with project management, collaboration, or general productivity skills. | 2 / 3 |
Total | 7 / 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 skill is concise and well-organized, effectively serving as a coordination layer pointing to other utility skills. However, it lacks concrete examples showing actual command usage and expected outputs, and the workflow sequences could benefit from explicit ordering and validation steps for team-facing operations.
Suggestions
Add a concrete example showing a complete standup workflow: running the command, expected output format, and piping to Chat
Include a sample daily/weekly sequence showing how these workflows fit together (e.g., 'Morning: run standup → share to Chat → check calendar')
Add validation guidance for sensitive operations, such as confirming before sharing reports or checking recipient lists
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what a team lead does or how workflows work. Every line provides actionable command references. | 3 / 3 |
Actionability | Provides specific workflow commands and tool references, but lacks concrete examples of inputs/outputs. Commands like `gws workflow +standup-report` are named but not demonstrated with actual usage or expected results. | 2 / 3 |
Workflow Clarity | Lists discrete tasks but doesn't sequence them into a coherent workflow. No validation checkpoints for operations like sharing standup reports or delegating tasks. Missing feedback loops for error handling. | 2 / 3 |
Progressive Disclosure | Appropriately structured as a brief overview pointing to prerequisite skills and specific workflows. Clear signaling of related workflows at the top, with tips separated at the bottom. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- 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.