persona-exec-assistant

Manage an executive's schedule, inbox, and communications.

Quality

52%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/persona-exec-assistant/SKILL.md

Quality

Content

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 well-structured, concise persona skill that effectively serves as an orchestration layer pointing to specific workflows and tools. Its main weakness is the lack of explicit validation steps and feedback loops in the workflow (e.g., what to do if a conflict is found, how to confirm changes before committing). The actionability is decent but relies heavily on external tool knowledge without showing concrete examples of inputs/outputs.

Suggestions

Add an explicit validation workflow for scheduling: e.g., '1. Run `gws calendar +agenda` to check conflicts → 2. If conflict found, propose alternative times → 3. Confirm with executive → 4. Run `gws calendar +insert`'

Include a brief example of triage prioritization output or decision criteria (e.g., what constitutes high/medium/low priority) to make the triage step more actionable

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. Every line provides actionable guidance without explaining what an executive assistant does or how email/calendar systems work. No wasted tokens.	3 / 3
Actionability	Provides specific CLI commands and flags (e.g., `gws gmail +triage --max 10`, `gws calendar +agenda`), which is concrete. However, these are tool invocations rather than fully executable code examples, and key details like how to handle conflicts or what triage prioritization looks like in practice are missing.	2 / 3
Workflow Clarity	Steps are listed in a logical daily sequence (start of day → before meetings → triage → scheduling → drafting), but there are no explicit validation checkpoints or feedback loops. For example, the conflict check before scheduling is mentioned but not structured as a validate-then-proceed workflow with error recovery.	2 / 3
Progressive Disclosure	The skill is a concise overview that clearly references prerequisite utility skills and specific workflows (standup-report, meeting-prep, weekly-digest) by name. References are one level deep and well-signaled, keeping the main file as a navigational hub.	3 / 3
	Total	10 / 12 Passed

Description

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 high-level summary of executive assistant capabilities but lacks the specificity and explicit trigger guidance needed for reliable skill selection. The actions listed are broad categories rather than concrete tasks, and the absence of a 'Use when...' clause makes it difficult for Claude to know precisely when to invoke this skill over others.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about managing calendars, scheduling meetings, triaging emails, or handling executive communications.'

Replace broad categories with specific concrete actions, e.g., 'Schedule and reschedule meetings, triage and prioritize inbox messages, draft email replies, manage calendar conflicts, prepare daily briefings.'

Include natural keyword variations users might say, such as 'calendar', 'email', 'meetings', 'appointments', 'EA', 'assistant', 'time management'.

Dimension	Reasoning	Score
Specificity	Names the domain (executive assistance) and some actions (manage schedule, inbox, communications), but these are broad categories rather than specific concrete actions like 'schedule meetings, draft email replies, prioritize inbox items, block calendar time.'	2 / 3
Completeness	Describes what the skill does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'schedule', 'inbox', and 'communications', but misses common natural variations users might say such as 'calendar', 'email', 'meetings', 'appointments', 'reply', 'draft', or 'EA'.	2 / 3
Distinctiveness Conflict Risk	The 'executive' qualifier adds some specificity, but 'schedule', 'inbox', and 'communications' are broad enough to overlap with general calendar management, email handling, or communication drafting skills.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 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: 3 months 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.