Persona Team Lead

Lead a team — run standups, coordinate tasks, and communicate.

Security Scan

The skill's stated purpose (leading a team via a 'gws' workflow) is plausible, but there are metadata inconsistencies and undeclared dependency/credential implications that you should verify before installing.

Purpose & Capability

The name/description match the runtime instructions (running 'gws' workflows and posting to team chat). Requiring a 'gws' CLI and Google‑Workspace–style helper skills (gws-calendar, gws-gmail, gws-chat, gws-drive, gws-sheets) is coherent for this purpose. However, the registry-level requirements listed earlier did not declare those helper skills even though SKILL.md lists them as prerequisites — that metadata mismatch is unexpected.

Instruction Scope

SKILL.md is instruction-only and tells the agent to run specific 'gws' workflows and post outputs to Chat/Sheets. It does not instruct reading arbitrary local files or unrelated credentials. It does instruct sharing outputs (e.g., 'share output in team Chat'), which could expose sensitive team data if not sanitized; SKILL.md mentions a '--sanitize' flag but doesn't enforce rules about what to sanitize.

Install Mechanism

No install spec and no code files — instruction-only skills are lower risk because nothing new is written to disk by the skill itself.

Credentials

The skill declares no environment variables or primary credential, but its operation depends on the 'gws' CLI and helper gws-* skills which almost certainly require Google Workspace credentials/scopes. The skill does not declare or document these credential requirements at the registry level, creating an omission you should verify (which credentials will be used, what scopes are required, and which skill holds them).

Persistence & Privilege

always:false (not force-installed) and model invocation is allowed (the platform default). This is normal. Be aware: autonomous invocation plus access to GWS data (via gws and helper skills) increases potential blast radius if those helper skills have broad scopes.

What to consider before installing

This skill appears to be a persona wrapper around a 'gws' CLI and several gws-* helper skills (calendar, gmail, chat, drive, sheets). Before installing: 1) Verify the origin and trustworthiness of the 'gws' CLI (where it comes from and what it can access). 2) Confirm which helper skills will be loaded and inspect their declared permissions/credentials (they will likely require Google API credentials and scopes). 3) Ask the publisher to fix metadata inconsistencies (SKILL.md lists required skills and version 0.22.5, but registry shows version 1.0.12 and omitted required skills). 4) Limit credentials/scopes to least privilege and test in a sandboxed account to confirm behavior. 5) Be cautious about automatic sharing of standup or email content to Chat/Sheets — sensitive information could be leaked if '--sanitize' isn't used consistently.

Team Lead

PREREQUISITE: Load the following utility skills to operate as this persona: gws-calendar, gws-gmail, gws-chat, gws-drive, gws-sheets

Lead a team — run standups, coordinate tasks, and communicate.

Relevant Workflows

• gws workflow +standup-report
• gws workflow +meeting-prep
• gws workflow +weekly-digest
• gws workflow +email-to-task

Instructions

• Run daily standups with gws workflow +standup-report — share output in team Chat.
• Prepare for 1:1s with gws workflow +meeting-prep.
• Get weekly snapshots with gws workflow +weekly-digest.
• Delegate email action items with gws workflow +email-to-task.
• Track team OKRs in a shared Sheet with gws sheets +append.

Tips

• Use gws calendar +agenda --week --format table for weekly team calendar views.
• Pipe standup reports to Chat with gws chat spaces messages create.
• Use --sanitize for any operations involving sensitive team data.