persona-sales-ops
Manage sales workflows — track deals, schedule calls, client comms.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill persona-sales-ops51
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 reasonable overview of sales workflow capabilities but suffers from being too terse and lacking explicit trigger guidance. The abbreviated format ('client comms') reduces clarity, and the absence of a 'Use when...' clause makes it difficult for Claude to know when to select this skill over others.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions sales pipeline, CRM, deal tracking, client follow-ups, or sales calls'
Expand abbreviated terms and add more specific actions (e.g., 'track deal stages and pipeline progress, schedule sales calls, manage client communications and follow-ups')
Include common user terminology variations like 'CRM', 'pipeline', 'leads', 'prospects', 'follow-up' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (sales workflows) and lists some actions (track deals, schedule calls, client comms), but these are abbreviated and not fully concrete or comprehensive. | 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. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'sales', 'deals', 'calls', and 'client comms' that users might say, but missing common variations like 'CRM', 'pipeline', 'leads', 'follow-up', or 'prospects'. | 2 / 3 |
Distinctiveness Conflict Risk | Sales-focused which provides some distinction, but 'schedule calls' and 'client comms' could overlap with general calendar or communication skills without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
52%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 assumes Claude's competence, but lacks the concrete examples and workflow sequencing needed for effective sales operations. The instructions read more like a feature list than actionable guidance, and there's no demonstration of how to actually execute a complete sales workflow from start to finish.
Suggestions
Add a concrete example workflow showing a complete sales cycle (e.g., 'When a new lead comes in: 1. Check email with X, 2. Log in sheet with Y, 3. Schedule call with Z')
Include at least one input/output example for key operations like deal logging or meeting prep
Add validation steps for critical operations like updating deal tracking spreadsheets (e.g., verify the row was appended correctly)
Convert prerequisite skill references to actual links (e.g., 'See [gws-gmail](./gws-gmail/SKILL.md) for email operations')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, with no unnecessary explanations. Every line provides actionable guidance without explaining concepts Claude already knows. | 3 / 3 |
Actionability | Provides specific command patterns (e.g., `gws workflow +meeting-prep`, `gws sheets +append`) but lacks concrete examples of inputs/outputs or complete executable workflows. The instructions describe what to do but don't show how. | 2 / 3 |
Workflow Clarity | No clear sequencing of multi-step processes. Instructions are listed as independent bullet points without showing how they connect in a sales workflow. No validation checkpoints or feedback loops for deal tracking operations. | 1 / 3 |
Progressive Disclosure | References external workflows and utility skills appropriately, but the references are not clearly signaled with links or file paths. The prerequisite skills are mentioned but not linked to documentation. | 2 / 3 |
Total | 8 / 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.