persona-exec-assistant
Manage an executive's schedule, inbox, and communications.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill persona-exec-assistant59
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 overview of the skill's domain but lacks the specificity and completeness needed for effective skill selection. It names general areas of responsibility without concrete actions and entirely omits trigger guidance for when Claude should use this skill over others.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions executive assistant tasks, calendar management, email triage, or scheduling meetings'.
Replace vague terms with concrete actions: instead of 'manage schedule', specify 'book meetings, reschedule appointments, check calendar availability, send meeting invites'.
Include natural keyword variations users might say: 'calendar', 'email', 'meetings', 'appointments', 'EA tasks', 'assistant duties'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (executive assistance) and lists three general areas (schedule, inbox, communications), but lacks concrete actions like 'book meetings', 'draft replies', or 'prioritize emails'. | 2 / 3 |
Completeness | Provides a weak 'what' (manage schedule/inbox/communications) but completely lacks any 'when' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms ('schedule', 'inbox', 'communications') but misses common variations users might say like 'calendar', 'email', 'meetings', 'appointments', or 'EA'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'executive' qualifier adds some specificity, but 'schedule', 'inbox', and 'communications' are generic enough to potentially overlap with calendar, email, 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 is a well-structured persona skill that efficiently describes an executive assistant workflow. Its main strength is conciseness and clear references to underlying tools. However, it lacks validation checkpoints (e.g., confirming conflict resolution before scheduling) and could benefit from more concrete examples of expected outputs or error handling.
Suggestions
Add explicit validation steps, such as 'If conflicts found, present options to executive before proceeding with +insert'
Include an example of triage output or meeting-prep output to clarify expected results
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, with no unnecessary explanations. Every line provides actionable guidance without explaining what an executive assistant does or how the underlying tools work. | 3 / 3 |
Actionability | Provides specific commands and workflows, but they are references to external tools rather than executable code. The guidance is concrete but relies entirely on external skill files for actual execution details. | 2 / 3 |
Workflow Clarity | Steps are listed in a logical sequence (start day, before meetings, triage, schedule, draft), but lacks validation checkpoints. No feedback loops for error recovery when scheduling conflicts occur or when actions fail. | 2 / 3 |
Progressive Disclosure | Clear overview structure with well-signaled references to external workflows and utility skills. Content is appropriately split between this persona skill and the underlying tool skills it depends on. | 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.